Main menu
You are here
MIDI CC, hardware controllers, Noisemaker and qtr
16 November, 2013 - 10:53 — danboid
I want to be able to control parameters under Noisemaker/ qtractor using my MIDI controller. I know how to control the parameters using qtr's automation menu but that menu doesn't list the CC values of the parameters, if they have preset CC values, so I'm unable to set up bindings for them under qtr's controllers menu.
Noisemaker used to have a MIDI learn (or MIDI MAP, as it calls it) feature but falkTX has removed this in the latest versions as he claims it violates the VST spec and he says LV2 doesn't support this at all!
qtr doesn't support MIDI learn yet, does it? If it does, I've not been able to find it!
Thanks Rui!
Forums:
re. MIDI CC, hardware controllers, Noisemaker and qtr
Dan,
qtractor has MIDI learn / mapping for ages now; it predates TYOQA :)
to access the "MIDI Controller..." menu you'll have to summon the generic plugin/Properties... window and right-click on the slider or control you wish to map--there you'll get the so called "MIDI Controller" dialog that allows you to assign/learn/map any MIDI event type, not only CCs (Type=Controller) to each plugin scalar parameter.
the part called "MIDI Learn" is about that while you have the dialog up you can tweak the knob or slider in your "physical" controller and the actual emitted MIDI event type should be there promptly recognized ready, set and go-- no need to look up the controller's user manual :)
cheers
Oh yeah!
I knew qtr had this feature hiding somewhere - thanks for reminding me Rui!
Slight nitpick time (again) - I dunno if its something in my config here but it takes a few seconds / turns of my controller before the controller actually takes effect, after having 'OK'd the MIDI controller assignment window.
I was going to add this to the wiki as I thought the full 0.5 manual had been wikified but it seems that is not the case. I hate to admit it but I'm not in any mood to get the rest of the manual wikified right now but I promise I will contribute to it after someone has done the boring bit of converting the rest of the existing manual.
re. it takes a few seconds / turns...
maybe it's the "catch-up" effect when the target parameter value will follow only after the controller value catches up with it.
this MIDI controller "catch-up" feature is on by default and fundamentally serves to prevent sudden, undesirable, unintentional live changes to the target parameter. it can be turned off if you wish: just keep that "Hook" option checked on.
cheers
Add new comment