Folks,

This post is not specific to RemoteSL users so I hope anyone can input. I've recently discovers that Novations "Automap Universal" only works for Armed Parameter record (Automation data) rather then transmitting midi CC's when I want to automate a softsynth. RemoteSL can transmit midi CC's but only for manual templates or maybe Cubase remote files. Anyway, this all has lead me to questioning the best process for automation in SONAR.


After re-reading SONAR INSIDER (Sonar 3 by Craig Anderton) there is some food for thought in the Automation section. He mentions differences between DX automation, VST (wrapper) Automation and midi CC's. There is a big performance drain when using Automation instead of midi CC's when controlling softsynths. Granted your system maybe up to the job but what happens when you start adding lots of softsynths and automation's. The bigger the project becomes, the more you may struggle.


I guess what I'm trying to debate is which do you prefer? what are you comments on this? The fact that I'll have to go the Automation route (arm parameter) if I want to use my RemoteSL's Universal feature is a little concerning CPU wise. But I can probably choose midi (without Automap universal) if it comes down to that.



Please add your thoughts experiences if this interests you...

Ste (EIRE)

Hmmmm Looks like this is not worth debating then?....

I have Novation's KS4 and record the knob movements when controlling the synth. It happened a couple of times that Sonar choked and had to shut down. I also have the Edirol PCR800 for controlling the softsynths and until now I haven´t had problems with the automation. I use about 3 or 4 softsynths in a project.

Recently I bought the Remote SL Zero, but I haven´t got it working, yet. It does automap a synth like Rapture, but not the sections I want to control, like the filters.

its been a decade, so I figure I'll chime in:
 
Sonar Automation PROS:
-Simple to setup
-easy to edit, draw and manipulate the envelope
 
Sonar Automation CONS:
-no CC data is recorded, so cannot export MIDI track to another DAW or save it for archival purposes
-can't control per-note parameters as good.   In PRV it is easy to simply click under a note and set a controller value for that note.   In Automation, you can draw curves, but not per-note values.
 
MIDI CC PROS:  
-ability to export MIDI track to another DAW or save it for archival purposes.  Just keep a notepad file of the mappings between CC -> parameter, then you can use the VST in another DAW or even Sonar but in a new project
-can edit per-note parameters (see above)
 
MIDI CC CONS:
-manual setup of CC to synth mappings everything you use the synth.
-drawing curves is not as easy as automation lanes (however recent PRV changes have improved this)
 
Am i missing anything here?

The performance hit probably comes from the use of many continuous controllers.  If you want to explore this, there are many CAL programs that can thin controllers on existing MIDI projects, but for live/real-time issues, you'll probably need to play with either MIDI buffers or the Control Surface refresh rate.  I really don't know much about the controller the OP is using.