What is the difference between Automation and CC sent to a Synth?

Automation can communicate with a plug-in two ways. Most plug-ins expose parameters via the program interface (DX, VST, VST3) for automation. These are the named parameters in the automation drop down. Some plug-ins (such as synths) listen for MIDI data. This may be sent using the MIDI parameters in a MIDI track's automation lane.
 
MIDI CC data shown in the PRV and as part of the clips in the Track View is stored in a different place than the data shown in the automation lanes. This data is sent to the plug-ins that listen for MIDI data the same way as the MIDI data stored in an automation lane.
 
There is a function to convert MIDI CC data to an automation lane. Going the other way is a little tricky but may be done by recording the CC data from the automation lane into a MIDI track.
 
What parameters a plug-in responds to via the program interface and CC data is up to the developer. Some plug-ins have ways to assign parameters arbitrarily to automation or MIDI. These plug-ins usually have some UI for making assignments. For MIDI this is often called "MIDI Learn."

HI:)
 
@scook
 
>>>There is a function to convert MIDI CC data to an automation lane. Going the other way is a little tricky but may >>>be done by recording the CC data from the automation lane into a MIDI track.
 
That's the problem! How can I do that?? I never did that and I don't think it's possible inside Cakewalk. Bounce does only work for Audio, aux Tracks too! From an Instrument Track you can't send automation to another Track nor record Midi Data from a Midi Track, so:
 
Any Idea?
 
Thanks;)
Bassman.
 

@scook
 
Ok, I'll try that, I've had installed LoopBE some time ago........thanks:)
 
Bassman.
 

It is up to the plug-in developer to expose automation and implement whatever they choose from the MIDI spec.
 
Most synths use MIDI data and CC events are part of that data stream. Just like MIDI note data tell the synth what note/velocity/how long to play, CC data can instruct the synth to do actions such as sustain or modulate audio.
 
Cakewalk can send CC events using an automation lane, as part of the MIDI clip or both. When CC events are recorded as part of a MIDI clip, they are edited in the CC lanes of the PRV. It does not matter if the CC data is created in an automation lane or recorded in the MIDI clip, they are both part of the MIDI data stream.
 
The plug-in automation is sent using a different data stream. Most synths listen for both automation and MIDI data streams. Most effect plug-ins just listen for automation but some also listen for MIDI data (for example those with MIDI learn capability or VST MIDI plug-ins).
 
There is also automation for certain DAW functions such as track volume, pan and mute.
 
 

Hi:)
 
@scook
 
Automation must work different, I can't record anything with a virtual midi cable and I've tried Loopbe, midiloop and midiyoke.
My Envelope Track to AD is set to Midichannel 10, but there are about 300 parameters to automate, you know with 1 midichannel only 128 are possible! So automation has to work in any other way, there is no Midi Data coming out to record. Tried with channel 10, 1 and none to send and record, no data receiving:(
 
Next I try to go extern through a midi cable, but I can't see that this makes a difference instead of virtual cables!
 
Bassman.
 

Hi:)
 
>>>Looking at the AD2 manual CC data can control some hi hat and snare parameters. The bulk of automation is not >>>handled with MIDI data. 
 
That's why I can't find any map:)
 
So, I'll do it as usual with automation......
 
Thank you scook:)
 
Bassman.