Erm, ARA is possible with 2.4, too, btw

And I agree with Noel, there is no "pressure".

But hopefully Cakewalk sees at least the possibilities with so called polyphonic automation and expression map integration of Vst3.5 compatible plugins, along with ARA (R-Mix track edits, anyone?)

And implement Note bound automation data (and note bound polyphonic midi cc/NRPN data consolidated in Realtime to monophonic midi cc/NRPN or channel wrapped) in an even more elegant way than steinberg did as of now...

Oops, there it goes, the reason for vst3.5...

Hmm... I wonder.. I have Padshop pro and Retrologue from Steinberg (included in Cubase), and as far as I know they are VST3. Still - they seem to work without a hitch in Sonar X1 pro expanded. In fact - I have no single plug-in that does not work with Sonar. I think I will not have any problem waiting until Cakewalk implements VST3 in the future. Waiting won't kill me. I can work full speed (and I am sure I can with X2 too) and that's what counts...

I see two reasons for VST 3 implementation.
Does it benefit the DAW itself.
Or, is it for the plugs which can be used by the DAW.

For real 'data' I am looking at the KVR website which my all analysis, lists every new instruments, synths, samplers, fx's, plugs and DAWS coming to the market. I am not seeing anything new or recent that is VST3 only.
 
Will a VST3 build make Sonar 'inline midi algorithms' more Cubase like or does it just need to include the ability to 'host' VST3 plugins.

@simpleman: As far as I know using the VST3 in a more Cubase manner (I assume you mean note articulation), means a complete rewrite of the Sonar piano roll view. Not just a simple "adaption" to VST 3 parameters. That's a lot of work, and will take a lot of time (especially when you consider MIDI is connected to a lot of other things in Sonar too).

JClosed


Hmm... I wonder.. I have Padshop pro and Retrologue from Steinberg (included in Cubase), and as far as I know they are VST3. Still - they seem to work without a hitch in Sonar X1 pro expanded. In fact - I have no single plug-in that does not work with Sonar. I think I will not have any problem waiting until Cakewalk implements VST3 in the future. Waiting won't kill me. I can work full speed (and I am sure I can with X2 too) and that's what counts...

The VST 3.5 standard allows you to write plugs that are backwards compatible with 2.4 compliant hosts.  
But, you lose some (enhanced) functionality....again i.e. Waves Vocal Rider....it will work fine...you just
lose Side Chain ability.


They'll work...they just wont be "fully" functional, if so written.  As the host must also be VST 3.5 compliant to
utilize it.

This is why Waves has stated that, in the next Major Release VST 2.4 will
not be supported.

New topic please...this ones a dead horse...
History repeats itself...

...

Noel Borthwick [Cakewalk
]

We have a close relationship with plugin vendors many of whom are development partners with us. So we're generally aware of their needs and future plans and do our best to accommodate them....


To clarify again. We are not against doing VST3 support and as a host we try and support compatible formats as much as we can. 
 
 
As I said development of this is on the table and we will do it at an appropriate time.

 
Good and thanks for that clarification!

.....

 

pdlstl

With each one of your posts I wonder even more as to why you've chosen SONAR as your platform of choice. Why do you even entertain using it when it comes from such an out-of-touch company? Especially when your vast experience showed you nothing but Cubase.
 
I'm cornfused.

See post #24.
 
I'm cornfused too...
 
I have used cakewalk products for years and always loved them. Still do. Generally prefer the workflow than in any other program. Then came X1 and I refused to buy in, partly because I need a new system to really benefit, and also due to the "problems" with X1 and the fact it required learning a new workflow after all these years of use with different hot-keys, screen layouts etc. - those of my peers who did purchase X1 ended up using 8.5.3 thru till the d-patch came out. After I puchased Sonar 8.5.3 I purchased the Waves Complete collection ver 7. Now as my needs progress in terms of production capabilities I find myself in need of sidechaining and surround capablities more frequently.
 
As I have explained in previous posts, I find myself in the position of having to make the choice, now after all these years, of moving on or sticking with Sonar. Until now it has suited my needs and moved in a mutual direction. If I ultimately have to learn a whole new workflow and also look towards the future it may be in my best interests to move on to some other DAW which will allow me to use tools I already have more efficiently. This is my conundrum, plain and simple.
 
Cons of moving on obviously require more immediate expense (new software vs upgrade cost), learning new software (even though X1 is different it still has many similiarities to previous versions.
 
None of this is to attack Cakewalk, it's about personal needs and self-preservation. I can/will never be a "fanboi" of any software to the point it excludes the reality of how these choices affect me professionally.