Well not sure if theres a workaround
but when i assign say a knob to my radium 61 keyboard and its already preprogrammed in another synth, it modifies it as i am using it... any workarounds??
RoNC
midi mapping issue
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
do you mean it still reads and acts upon the controller data just when you are remapping it?
if that's the case then it's probably a bug - i'm sure that when it's in 'learn' mode it shouldn't do anything but learn the incoming midi CC data. the only workaround would be to first map it to a control you know is unused, then remap from that back to the one you want.
i'll check it later
if that's the case then it's probably a bug - i'm sure that when it's in 'learn' mode it shouldn't do anything but learn the incoming midi CC data. the only workaround would be to first map it to a control you know is unused, then remap from that back to the one you want.
i'll check it later
Kick, punch, it's all in the mind.
-
- KVRAF
- Topic Starter
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
dose it still happen if the controller input is unarmed or on another track? (or did i miss understand you & you are controlling the synth via the cc mapper aswell)
Subject
Subject
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
is it because of a mapping in the automation dialog? or is it because the plugin is programmed to respond to the same CC internally?
i presume it's not the former. i just tried mapping multiple parameters to the same CC, and while T2 doesn't remove the old mapping (which it probably should do) it ignores any that come after the first one encountered - the list is processed in the order shown and later occurences of the same CC are ignored. so i imagine this is not what your problem is.
if it is that the synth is programmed to respond to that particular CC internally, then it will always respond to that CC unless there is a way in the plugin of deactivating the midi cc response. if the plugin recieves the data, it will use it.
if it is recieving the data then, it means that you have your controller connected to the track input. the way around it? simply remove the midi input from that track. T2's mapping works on the midi as it is recieved at the port before it is sent to the tracks, so your T2 based mapping will still work, and the CC won't get sent forth along the track to be gobbled up by the innocently confused plugin.
i presume it's not the former. i just tried mapping multiple parameters to the same CC, and while T2 doesn't remove the old mapping (which it probably should do) it ignores any that come after the first one encountered - the list is processed in the order shown and later occurences of the same CC are ignored. so i imagine this is not what your problem is.
if it is that the synth is programmed to respond to that particular CC internally, then it will always respond to that CC unless there is a way in the plugin of deactivating the midi cc response. if the plugin recieves the data, it will use it.
if it is recieving the data then, it means that you have your controller connected to the track input. the way around it? simply remove the midi input from that track. T2's mapping works on the midi as it is recieved at the port before it is sent to the tracks, so your T2 based mapping will still work, and the CC won't get sent forth along the track to be gobbled up by the innocently confused plugin.
Kick, punch, it's all in the mind.
-
- KVRAF
- Topic Starter
- 6490 posts since 14 Jun, 2004 from Rochester, NY