Anderton

SilverBlueMedallion
Second, I would need to insert a new value when the Middle bridge of the song comes in...   how exactly do I go about doing this?   I know the Controller pane of the PRV can kind of do this, but I want to enter an exact numerical value for the parameter (not draw it in).

Seems like the Event List view would be ideal for these kinds of ultra-precise applications.

true, i could do that, but I don't know the MIDI CC value that is controlling this synth parameter... do you know of a way I can find a mapping of this in Sonar?
Secondly, there IS an option in the synth rack for Snapshot Automation - it just seems like it does nothing, which means that this is a bug.

SilverBlueMedallion
 I don't know the MIDI CC value that is controlling this synth parameter... do you know of a way I can find a mapping of this in Sonar?

It would not be found in SONAR. If there is a way to control a given parameter with CC, it would be in the plug-in documentation. Alternately, it might be controlled via plug-in automation instead of MIDI, depends on the plug-in.

scook

SilverBlueMedallion
 I don't know the MIDI CC value that is controlling this synth parameter... do you know of a way I can find a mapping of this in Sonar?

It would not be found in SONAR. If there is a way to control a given parameter with CC, it would be in the plug-in documentation. Alternately, it might be controlled via plug-in automation instead of MIDI, depends on the plug-in.

Understood, thank you!  I thought that since Sonar is able to see each parameter setting name and value that somehow it could see the MIDI CC attached to it as well.
 
Either way, I hope the bakers look into the broken Snapshot Automation in the synth rack:
 
http://forum.cakewalk.com...-m3397040.aspx#3397040

SilverBlueMedallion
Understood, thank you!  I thought that since Sonar is able to see each parameter setting name and value that somehow it could see the MIDI CC attached to it as well.

I don't think so. Some plug-ins provide hard-coded CC support. Some include a tool to map CC to its parameters. Some use MIDI learn. Some use automation only. It is up to plug-in developer.

scook

SilverBlueMedallion
Understood, thank you!  I thought that since Sonar is able to see each parameter setting name and value that somehow it could see the MIDI CC attached to it as well.

I don't think so. Some plug-ins provide hard-coded CC support. Some include a tool to map CC to its parameters. Some use MIDI learn. Some use automation only. It is up to plug-in developer.

understood - thank you!

scook

SilverBlueMedallion
Understood, thank you!  I thought that since Sonar is able to see each parameter setting name and value that somehow it could see the MIDI CC attached to it as well.

I don't think so. Some plug-ins provide hard-coded CC support. Some include a tool to map CC to its parameters. Some use MIDI learn. Some use automation only. It is up to plug-in developer.

this leads me to a question, when you assign a knob or a rotary to a synth parameter in ACT, are you essentially updating or changing the MIDI CC of that parameter to match what the knob or rotatory is set to?
 
I know my Rotary #1 is set to CC #25.  So if I use ACT to map Rotary #1 to "Attack" on the softsynth, can I assume that "Attack" is now mapped to CC #25?

SilverBlueMedallion
 
Secondly, there IS an option in the synth rack for Snapshot Automation - it just seems like it does nothing, which means that this is a bug.

Actually it does do something, but not what you want. If you're recording VST automation by moving knobs and then click on Snapshot in the synth rack, it sets the automation line to the last node if there's no additional automation past that point, and locks out further automation writing. If you're writing over existing automation but then stop writing and let the song keep playing, and then click snapshot later on, the last new automation node you wrote will jump to the node on the existing automation, as if you had stopped the transport but the transport will still keep playing. I'm not saying this is particularly useful, but it does do something.
 
However, MIDI automation (e.g., automation for controller 1, controller 7, etc.) does do snapshots as expected, as does automating the arpeggiator.