Thanks for your responses. I was able to use the Hook option successfully with the sliders/faders on the Launchkey, which is exactly what I wanted out those buggers. I'm still a little unclear about how latch works, but no matter, the mididings script fixes things up quite nicely for me.
As I mentioned before, and after having even *more* time to think about it, I think integrating mididings into Qtractor would be a really nice feature. Here's my proposal: How about adding a "Run mididings script" options to the General tab of the View/Options menu? If a file is specified, and it exists, spawn a mididings process using QProcess. I'm not sure if I would rather have the user connect the mididings output to the Qtractor input via Qjackctl, or have it done automagically (I'm leaning more toward having the user perform the connections). What's nice about this is that mididings can be used a shim between various pieces of hardware and Qtractor and probably saves you some time in the long run: "Hey Rui, I have a SoundBlaster 3000 combination MIDI controller/latte machine and can't get button XYZ to work. Fix it!"
If it's OK with you, I'd like to open a feature request ticket on GitHub just so that we have a record of the request. And again, I'm willing to help with coding.
I hope you and your family had a wonderful Christmas, and I wish you a Happy New Year.
Hi again Rui,
Thanks for your responses. I was able to use the Hook option successfully with the sliders/faders on the Launchkey, which is exactly what I wanted out those buggers. I'm still a little unclear about how latch works, but no matter, the mididings script fixes things up quite nicely for me.
As I mentioned before, and after having even *more* time to think about it, I think integrating mididings into Qtractor would be a really nice feature. Here's my proposal: How about adding a "Run mididings script" options to the General tab of the View/Options menu? If a file is specified, and it exists, spawn a mididings process using QProcess. I'm not sure if I would rather have the user connect the mididings output to the Qtractor input via Qjackctl, or have it done automagically (I'm leaning more toward having the user perform the connections). What's nice about this is that mididings can be used a shim between various pieces of hardware and Qtractor and probably saves you some time in the long run: "Hey Rui, I have a SoundBlaster 3000 combination MIDI controller/latte machine and can't get button XYZ to work. Fix it!"
If it's OK with you, I'd like to open a feature request ticket on GitHub just so that we have a record of the request. And again, I'm willing to help with coding.
I hope you and your family had a wonderful Christmas, and I wish you a Happy New Year.
Bruce