T2 demo controller mapping
-
- KVRist
- 476 posts since 6 Aug, 2004
Haia ,
When i map a midi controller /slider from my masterkeyboard to a vsti filter (for example)in
the new t2 automation /or shortcut ctrl+shift+m
dialog , then closing the dialog window (red x on right corner ) ,then moving the controllerslider indeed
opens the filter cutoff.
Then i record the movements in a clip over some chord
progressions the controller data is visible in the clip
but when replaying the clip the CONTROLLER DATA doesn't play the filter movements i recorded.
in midi input icon 'use controllers is on (otherwise
you couldn't record it in the first place)
Any thoughts about this???
paladium
When i map a midi controller /slider from my masterkeyboard to a vsti filter (for example)in
the new t2 automation /or shortcut ctrl+shift+m
dialog , then closing the dialog window (red x on right corner ) ,then moving the controllerslider indeed
opens the filter cutoff.
Then i record the movements in a clip over some chord
progressions the controller data is visible in the clip
but when replaying the clip the CONTROLLER DATA doesn't play the filter movements i recorded.
in midi input icon 'use controllers is on (otherwise
you couldn't record it in the first place)
Any thoughts about this???
paladium
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
the record shouldn't be recording controller data, it should be recording automation curves.
When a CC is mapped to an automation parameter, it effectively stops acting as a MIDI device, and starts acting just like an automation control. Recording it should therefore produce a standard automation curve, and no MIDI data.
Not sure what you are doing, but check that you don't have the "disable automation mapping" option enabled for the MIDI inout device.
Now, active the automation record option (the red "A" symbol above play) and try again.
When a CC is mapped to an automation parameter, it effectively stops acting as a MIDI device, and starts acting just like an automation control. Recording it should therefore produce a standard automation curve, and no MIDI data.
Not sure what you are doing, but check that you don't have the "disable automation mapping" option enabled for the MIDI inout device.
Now, active the automation record option (the red "A" symbol above play) and try again.
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 1974 posts since 21 Jun, 2002 from Earth
you are mapping params to a VST. You should turn on the automation record.. then record your movements. It will create a VST automation curve.. as opposed to midi-cc. 
damn! I type slow.. valley beat me to it...
damn! I type slow.. valley beat me to it...
ModuLR / Radio
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
yeah, i was pleased into petals that the CC data got converted into automation lines. very very good news. i'm incredibly delighted with this demo. seriously top stuff. even being able to resize the window and have it floating is handy too
Kick, punch, it's all in the mind.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
Me too! I don't need to bother assigning MIDI ccs to knobs in Synthedit any more! Of course, it also means that any automation created in this way will be present and correct if the edit is opened in T1..haydxn wrote:yeah, i was pleased into petals that the CC data got converted into automation lines. very very good news.
