VST3 was introduced 6 years ago, back in 2008.
 
Here's a list of improvements over the circa 2001 VST2 implementation:
 
https://www.steinberg.net/nc/en/support/knowledgebase_new/show_details/kb_show/vst3-in-cubase-and-nuendo-technical-background.html

mike_mccue
VST3 was introduced 6 years ago, back in 2008.
 
Here's a list of improvements over the circa 2001 VST2 implementation:
 

Note Expression is a biggy.  I'm currently thinking about switching over to Cubase because when you are trying to control expression + various articulations, etc, having to assign a specific midi channel and then only have 16 channels of MIDI CCs is not only limiting, it's a pain in the butt.
 
Really, I wish I didn't have to switch, but I think I am going to have to pull that trigger... which means more wasted HD space for all the crap that comes with the full version of Cubase :(
 
That, and I have an unresolved problem with my one 8Dio library where the danged thing loads out-of-tune after saving a project (is fine if I reload it, and then redo any tweaks, but who wants to do that every time you load a project).
 
But... it's VST Expression that is really lacking in Sonar.  So sad. 

VST Expression also has to be supported by the instrument itself, so I would check that the ones you want to use can actually take advantage of it.
 

stevec
VST Expression also has to be supported by the instrument itself, so I would check that the ones you want to use can actually take advantage of it.
 

I don't think this statement makes any sense in terms of what an expression map does as I understand it anyway.  It's true that not every library may be mapped the same way,  and every library may not be pre-mapped, but the way I understand it (only from being told by folks that use it) is that you can create your own expression maps, so you can map note information for key switch articulations, you can map CCs for instrument controllers, and you can even use midi-learn from your VST instrument and simulate a CC knob/slider movement to map a particular CC to the particular VST instrument control, and the expression map and lane expression data supersedes any other MIDI data going to the VST instrument.
 
Once you are mapped, then, you can freely draw CC information for any number of tracks without affecting other tracks, and you can use note expression to manage key switching.   Essentially, the DAW's expression map supersedes any incoming midi data for that track/lane, so now you are no longer limited to 16 midi channels for controlling your VSTs.
 
And if you think about it, you can already to that pretty much with note data in Sonar (minus the nifty note expression symbols, etc), but you can't do it with CC data (at least I haven't found a way to do it--please, please correct me if I am wrong because I don't want to migrate to a new DAW).
 
My experience is that Sonar forces me to choose a channel for a CC, and once I do this, that channel/CC is marked in use for the whole project, and that CC will affect every instrument on that midi channel that responds to that CC. If CC data were to remain local to the track or to supersede incoming MIDI CCs if written to a track lane, and if every track lane could re-use MIDI channel CCs, there'd be no reason to move, and that's leaving out the nifty expression map note data and the fact that helps when you are printing out score notation.
 
At any rate, I am primarily looking at this as a way to simplify workflow for Kontakt-based instruments, and that's what the folks using Cubase tell me about VST expression.  The devil may be in the details, but there seem to be a lot of people sold on this, and they are using it for a reason, and that reason isn't--I don't think--that they are just Cubase fanboys.

Well Kontakt is VST 2 only and there is no mention of a Kontakt update in the Komplete 10 publicity so it look like it will be a long wait to get per note expression in Kontakt in any DAW.

My experience is that Sonar forces me to choose a channel for a CC, and once I do this, that channel/CC is marked in use for the whole project, and that CC will affect every instrument on that midi channel that responds to that CC.

Are you sure about this? I routinely use the same CC for different things on different tracks. Basic functionality such as CC7 for volume wouldn't work if it was true. For that matter, multi-track MIDI wouldn't be possible if one track's MIDI commands were sent to every track assigned to the same MIDI channel.
 
Not saying you're wrong about this. I may have just misunderstood your explanation.
 

bitflipper

My experience is that Sonar forces me to choose a channel for a CC, and once I do this, that channel/CC is marked in use for the whole project, and that CC will affect every instrument on that midi channel that responds to that CC.

Are you sure about this? I routinely use the same CC for different things on different tracks. Basic functionality such as CC7 for volume wouldn't work if it was true. For that matter, multi-track MIDI wouldn't be possible if one track's MIDI commands were sent to every track assigned to the same MIDI channel.
 
Not saying you're wrong about this. I may have just misunderstood your explanation.

Nope, I am not sure about this :)  Apparently I have been suffering due to early error-induced delussions.
 
In fact, I just went into my studio and tried to replicate the situation that sent me down the ridiculous workflow path of assigning every instrument to its own midi channel, and I cannot recreate that experience.
 
I set up two tracks with two Kontakt instruments--French horns & a2 clarinets--and I assigned them both (default) to midi channel 1, put in a quick melody line for the brass, added dynamic control on midi channel 1 of expression (CC11), transition speed (CC16) and dynamics (CC1), then I copied everything in that track down to the woodwinds track, and then I altered all the CC data for the woodwinds, and then I brought up both instruments on my second screen and confirmed they were following their respective controller data and not all responding the same.
 
I have no idea what I did wrong way back when that had me create that horrendous and impossible workflow, but it's good to know that I won't have to switch DAWs to get rid of that crazy workflow.
 
Good lord, who knows?  But thanks for asking the question, or else I wouldn't have tried to capture the problem, and then I wouldn't have found out that whatever sent me off on that path was probably something else I did way back when I was first playing with X3 and my misunderstanding about what was happening.
 
Well, you saved me buying a new DAW.  Thanks:)

I didn't have any problems when I initially installed Analog Lab - they must have gotten into the right folders, but Arturia were definitely visible.
My problems came up when I installed Melodyne Studio...there was nothing I could do to get X3 to recognize Analogue Lab.
Long story short - I did a System Restore to an older date, and it came back the right way. 
 

How do I get Arturia Analog Lab 2 to work in Sonar Platinum. I also have Arturia SEM V2 which works but there is a half second delay from when I press the key on the Arturia MiniLab controller to when you hear the note being played. This latency is also present when using Rapture Session. Since I began having these problems I have read that many other people have had the same issues but no one seems to have an answer. Is it an issue with the Arturia products or is it an issue with Sonar?

Appending to an old thread is not the best idea.
 
Arturia Analog Lab 2 should work after installing and authorizing from Arturia then scanning the plug-in in SONAR. No special action is necessary.
 
The delay in hearing a note being played is either a misconfigured audio interface and/or plug-ins in the project. Information about the audio interface used might be helpful. To bypass all effects in the project use the shortcut "E" or the FX button in the mix module.