Sonar is NOT Cubase's biggest competitor...NOT EVEN CLOSE...CUBASE - WORLD WIDE is the LARGEST INSTALLED DAW in the WORLD....

 
Can you reveal the source of these statistics?  
 

Jim Roseberry

Sonar is NOT Cubase's biggest competitor...NOT EVEN CLOSE...CUBASE - WORLD WIDE is the LARGEST INSTALLED DAW in the WORLD....

 
Can you reveal the source of these statistics?  
 

All you have to do is read any Industry publication.  It's a well published fact.

Sonar themselves will tell you so.  They know where they stand.

( The source, btw...was Computer Music )

In the aritcle it stated that "While Pro Tools considers itself to be the Industry Standard, statistically Cubase is installed
in more Professional Studio's Worldwide then Pro Tools"

Cheers!

john6448


For my particular uses, Sonar has made a marketing choice not to pursue VST3 or an improved Staff View, and it's choice has left me feeling that I may have hitched my wagon to the wrong DAW. It is what it is, and no amount of bickering is going to change it.

Have you sent a request to CW to implement these features?  The CTO has stated right here that customer requests are a primary driver of what they put in new releases.  It's apparent that most of us value the kinds of features coming now in X2 over things like VST3.  If you and others in your position would send enough requests to CW for any particular feature, your wishes might just be granted one of these days.  CW is just trying to keep the greatest number of customers happy within the constraints of limited resources, just as any decent company would do. 
 
No DAW (or product of any kind) can be perfect for everyone, so there will always be those who wish Sonar was just a little different.  It's not worth throwing tantrums over, it's just the way the world is.  You take what you can get and make it work.  But hey, if someone had shown you ten years ago what was possible with ITB music production today, wouldn't your mind have been blown?  We do live in amazing times, eh?

Cheers,
Eddie

Noel Borthwick [Cakewalk
]

john6448

VST3 is important to me, particularly because I work with orchestral music and Cubase has used it to make articulation switching so easy. 

Sigh. This is exactly the point I have been trying to make all along.  VST3 in itself doesn't give you "articulation switching" and even if we implemented the spec you wouldn't get that. That is a whole different feature which just happens to have some support in the VST3 spec. If that feature in itself is specially important to you by all means feature request it but asking for VST3 for sure isn't going to get that to you. Its like going to another vendor and asking why don't you support prochannel modules - its implemented in VST 2.4 after all :) 

I'll say it again. VST3 is a plugin spec - no more and no less. It is simply a template for implementing a common protocol to communicate with plugins.  It won't get you any new features! 




>>cclarry
>>But that does not dimish the importance of VST 3 implemenation. 
>>Plug Manufacturers and PC DAW's have been using and implementing it for 4 years now...while Cake sits on their lists. 
>>I don't use it...I don't need it...BUT...I understand the NEED and reason for the NEED, and that is why I support 
it. 

Lets see - you have no need for VST3 yourself and yet you want us to invest our resources in it just in case someone wants it. I'm afraid I don't see a lot of sense in that argument. We use our development time wisely to deliver tools that benefit the most of our customers base and not for some hypothetical gain. I think most people will agree that this is a better model. 

Noel,
 
This is a very unreasonable reply  - from the CTO especially.
Waves plugins rely on the VST 3 standard for some of their better functionality.
FabFilter Plugins rely on VST 3 standard as well, and most other Plugin manufacturers
and DAW's are supporting this format.

I could go on...listing what has been posted here in this thread....that some of the synths require VST 3
that other things require VST 3...and while it is just a standard, as you stated, it is an INDUSTRY STANDARD
that has been around for over 4 years now!
 
Your attempts to diminish the importance of this are ludicrous, to say the least.  Do you really believe
that your customers are that naive?

I could care less one way or the other..other then the fact that I see about 50 percent here, on this forum alone, who
not only WANT it ..but NEED IT for their software to work most effeciently.  And a LOT who stated emphatically that
they would not upgrade to X2 until VST 3 is implemented because the work they do requires it, so they are using "other
DAW's, that DO support it".

No you should not invest your money to satisfy me..you should invest it to satisfy the MANY customers you now have
who not only WANT it...but NEED it to do their jobs.  And there are far more then just the ones on this forum, as those who
use this program for a lving do not have the time to sit here on this forum and discuss it.

Really....really...really...who's being fooled here?

NEW VST 3 Features - from steinberg site.

Improved performance

Managing large plug-in sets and multiple virtual instruments on typical studio computer systems can often be difficult because of CPU performance limits. VST3 helps to improve overall performance by applying processing to plug-ins only when audio signals are present on their respective inputs. Instead of always processing input signals, VST3 plug-ins can apply their processing economically and only when it is needed. Multiple dynamic I/Os

VST3 plug-ins are no longer limited to a fixed number of inputs and outputs. Their I/O configuration can dynamically adapt to the channel configuration they’re inserted in, meaning that any VST3 plug-in can be surround-capable with true multi-channel processing. For example, all the new VST3 plug-ins in Nuendo 4 can work in stereo-mode when inserted into a stereo channel, but switch to 6 channels when inserted into a 5.1 channel. Each audio channel is processed independently. Interaction between channels depends on the type and design of the plug-in. In addition to their flexible audio bussing capabilities, VST3 plug-ins may also offer a dedicated event bus. Typically, this is a MIDI input for control/modulation but these busses are no longer restricted to MIDI standard only. Future plug-ins may replace the common MIDI interface with alternative methods of control. Activating/deactivating busses

A typical issue with current virtual instruments is their audio output bussing system and how they’re connected to the mixer after loading. Especially virtual samplers with multiple outputs often occupy more mixer channels than need. The VST3 interface offers the possibility to deactivate unused busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load. Resizable edit windows

VST3 introduces a new approach to plug-in GUIs though window resizing, allowing for extremely flexible use of valuable screen space. Sample-accurate automation

VST3 also features vastly improved parameter automation with sample accuracy and support for ‘ramped’ automation data, allowing completely accurate and rapid parameter automation changes. Logical parameter organization

The plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the plug-in. Parameters like “Cutoff” and “Resonance” could be grouped into a section called “Filter”. This makes searching for a certain parameters easier, such as on an automation track. This also allows assigning a group of parameters to a specific MIDI Channel input and audio output bus. Optional VST3/SKI combination

As a direct result of the modular interface design of VST3, the Steinberg Kernel Interface (SKI) can be combined with VST3 plug-ins. SKI is an additional SDK that allows extremely close integration of a plug-in with a Steinberg host application, and allows functions to be carried out almost from within the application. This extends to the ability to create tracks, copy, cut, paste or process events in the Steinberg host application. SKI is provided to selected industry partners upon request. VSTXML for remote controllers

Remote controllers for audio and MIDI software applications have become increasingly popular. With VSTXML, VST3 offers far more flexible control of VST plug-ins by remote controllers. Using the knobs and faders on the control surface, parameters can be recorded, renamed and edited in many ways. Parameters that cannot be edited can be routed for display purposes to the control surface, for example to show Gain Reduction on compressor. UTF16 for localized parameter naming

In VST3, all strings that can be displayed to the user are in Unicode (UTF16) format. Usage of this universal character base allows the host application to display characters in localized languages. No MIDI restriction for parameter value transfers

VST3 has a dedicated interface for event handling that carries a much wider range of functionality than standard MIDI events would be able to provide. This opens up a big range of opportunities for musical use cases with very high potential for innovative product design. For example with VST3 some controller events (for example, pitch) can be referred to a note event (using a note unique ID). This offers the possibility to e.g. modulate only a single note which itself is part of a chord. Audio inputs for VST instruments

The VST3 interface expands VST instruments by adding the ability to create audio input busses. As a result, audio data can be routed to an VST3 instrument. A synthesizer which has a built-in e.g. vocoder effect is able to process audio data coming in from other sources as well. Multiple MIDI inputs/outputs

Unlike with VST 2.x,, a VST3 plug-in can have more than only one MIDI input or one MIDI output at the same time. 64-bit processing

VST3 plug-ins are generally able to process audio data in 64-bit.

Eddie TX

john6448


For my particular uses, Sonar has made a marketing choice not to pursue VST3 or an improved Staff View, and it's choice has left me feeling that I may have hitched my wagon to the wrong DAW. It is what it is, and no amount of bickering is going to change it.

Have you sent a request to CW to implement these features?  The CTO has stated right here that customer requests are a primary driver of what they put in new releases.  It's apparent that most of us value the kinds of features coming now in X2 over things like VST3.  If you and others in your position would send enough requests to CW for any particular feature, your wishes might just be granted one of these days.  CW is just trying to keep the greatest number of customers happy within the constraints of limited resources, just as any decent company would do. 
 
No DAW (or product of any kind) can be perfect for everyone, so there will always be those who wish Sonar was just a little different.  It's not worth throwing tantrums over, it's just the way the world is.  You take what you can get and make it work.  But hey, if someone had shown you ten years ago what was possible with ITB music production today, wouldn't your mind have been blown?  We do live in amazing times, eh?

Cheers,
Eddie

Eddie,
 
First and foremost, you cannot base your Company position on the "feature requests" of a forum.
They should be considered in view of the WHOLE INDUSTRY.  Not given the ultimate weight of
what to implement.  This is merely common sense and good Business Practice.

VST 3 is an INDUSTRY...not social or political STANDARD...and, no matter how much Cake hates Steinberg,
they have been the drivers of this from the onset and you can rest assured that's not changing anytime soon.

I could go into a whole of detail, but, after reading these posts....
 
It would be pointless...

Cheers

firefly9000


NEW VST 3 Features - from steinberg site.

Improved performance

Managing large plug-in sets and multiple virtual instruments on typical studio computer systems can often be difficult because of CPU performance limits. VST3 helps to improve overall performance by applying processing to plug-ins only when audio signals are present on their respective inputs. Instead of always processing input signals, VST3 plug-ins can apply their processing economically and only when it is needed. Multiple dynamic I/Os

VST3 plug-ins are no longer limited to a fixed number of inputs and outputs. Their I/O configuration can dynamically adapt to the channel configuration they’re inserted in, meaning that any VST3 plug-in can be surround-capable with true multi-channel processing. For example, all the new VST3 plug-ins in Nuendo 4 can work in stereo-mode when inserted into a stereo channel, but switch to 6 channels when inserted into a 5.1 channel. Each audio channel is processed independently. Interaction between channels depends on the type and design of the plug-in. In addition to their flexible audio bussing capabilities, VST3 plug-ins may also offer a dedicated event bus. Typically, this is a MIDI input for control/modulation but these busses are no longer restricted to MIDI standard only. Future plug-ins may replace the common MIDI interface with alternative methods of control. Activating/deactivating busses

A typical issue with current virtual instruments is their audio output bussing system and how they’re connected to the mixer after loading. Especially virtual samplers with multiple outputs often occupy more mixer channels than need. The VST3 interface offers the possibility to deactivate unused busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load. Resizable edit windows

VST3 introduces a new approach to plug-in GUIs though window resizing, allowing for extremely flexible use of valuable screen space. Sample-accurate automation

VST3 also features vastly improved parameter automation with sample accuracy and support for ‘ramped’ automation data, allowing completely accurate and rapid parameter automation changes. Logical parameter organization

The plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the plug-in. Parameters like “Cutoff” and “Resonance” could be grouped into a section called “Filter”. This makes searching for a certain parameters easier, such as on an automation track. This also allows assigning a group of parameters to a specific MIDI Channel input and audio output bus. Optional VST3/SKI combination

As a direct result of the modular interface design of VST3, the Steinberg Kernel Interface (SKI) can be combined with VST3 plug-ins. SKI is an additional SDK that allows extremely close integration of a plug-in with a Steinberg host application, and allows functions to be carried out almost from within the application. This extends to the ability to create tracks, copy, cut, paste or process events in the Steinberg host application. SKI is provided to selected industry partners upon request. VSTXML for remote controllers

Remote controllers for audio and MIDI software applications have become increasingly popular. With VSTXML, VST3 offers far more flexible control of VST plug-ins by remote controllers. Using the knobs and faders on the control surface, parameters can be recorded, renamed and edited in many ways. Parameters that cannot be edited can be routed for display purposes to the control surface, for example to show Gain Reduction on compressor. UTF16 for localized parameter naming

In VST3, all strings that can be displayed to the user are in Unicode (UTF16) format. Usage of this universal character base allows the host application to display characters in localized languages. No MIDI restriction for parameter value transfers

VST3 has a dedicated interface for event handling that carries a much wider range of functionality than standard MIDI events would be able to provide. This opens up a big range of opportunities for musical use cases with very high potential for innovative product design. For example with VST3 some controller events (for example, pitch) can be referred to a note event (using a note unique ID). This offers the possibility to e.g. modulate only a single note which itself is part of a chord. Audio inputs for VST instruments

The VST3 interface expands VST instruments by adding the ability to create audio input busses. As a result, audio data can be routed to an VST3 instrument. A synthesizer which has a built-in e.g. vocoder effect is able to process audio data coming in from other sources as well. Multiple MIDI inputs/outputs

Unlike with VST 2.x,, a VST3 plug-in can have more than only one MIDI input or one MIDI output at the same time. 64-bit processing

VST3 plug-ins are generally able to process audio data in 64-bit.

I referenced this earlier...the die hards who don't care, including the CTO, are going to argue the "unimportance" of this into the ground.

Time will tell....

dantarbill


I've had WaveLab 7 since it was first released.  It supports VST3 and includes a number of VST3 plugs.  I use WaveLab more regularly than I use SONAR (I'm afraid).  I have yet to have even opened a VST3 plug...or had a need to.
 
I think there's a much more compelling case for implementing ARA support than VST3 at this point...especially if your development resources are constrained.

I definitely agree with your last statement and I really hope that Cakewalk prioritizes ARA over VST3.  The Melodyne ARA integration in Studio One v2 makes a huge difference and I personally prefer Melodyne by far over V-Vocal.  I have used the VST3 versions of many plugins in both Wavelab 7 and Studio One v2, but honestly haven't really realized much, if any, benefit from it.  That said, there are compelling reasons to support  VST3  and I'm glad to see that Cakewalk is planning on adding support for it. 

cclarry

James_S

cclarry

Noel,

This is a very unreasonable reply  - from the CTO especially.
Waves plugins rely on the VST 3 standard for some of their better functionality.
FabFilter Plugins rely on VST 3 standard as well, and most other Plugin manufacturers
and DAW's are supporting this format.


Really....really...really...who's being fooled here?

Fabfilter plugins all come as both vst2 and vst3 with no functional difference between them. They don't rely on vst3 at all.

I'm not quite sure why you are trying to undermine cakewalk at the moment, but it's just coming across as a personal rant now ...

Cheers

James

FabFilter Plugins, if using VST 3, would greatly benefit from it.  Just read the info...

I have the plugins - I don't recall seeing any functions that are only available in vst3. 

Linear Phase

cclarry

.......

NOT WISE...

Cheers!

"not wise?"  What happens when Cakewalk does add vst3?   Sonar is definitely Cubase's main competitor, so what do you think Yama/Stein is going to do?  
 
 

I HIGHLY, HIGHLY doubt this.  I love Sonar and all, but I have a strong feeling that Pro Tools, Logic, FL Studio, and probably even Abelton are all higher up on that list of competitors.  Maybe a couple others as well.  I think Sonar has a very small user base actually.  I very rarely encounter anyone in the professional world using Sonar.  I come across people using the others that I mentioned all the time.  Honestly, when I mention Sonar to most people I just get met w/ a blank stare, usually followed by a question as to why don't I use (insert other program here).  LOL!  I think some of you guys might need to get out a little more.

backwoods


ccLarry and his VST3 fetish is about as tiresome as Silktone and his midi-cross-chatter obsession  


Poor old Noel having to come on and defend himself against this tripe. It's like Spike Milligan wrote "Einstein could stand in front of a class of 30 monkeys and lecture them for ten years but at the end of that time they'd still all be monkeys."


I own Nuendo5 in addition to Sonar. For fabfilter there is no difference except the VST3 ones put themselves into the dynamics folder automatically. Big Deal!

bu.but.but! Virtual Studio Technology 3 or 3.5 now is .6 or 1.1 higher over Virtual Studio Technology 2.4! It's just better!

Sorry cclarry, must have missed your post.

I'm not sure how those new features don't matter, but to each his own. I understand the feeling some people have: VsT3 just isn't that implemented yet so why make such a fuss.

While I DO get that, I also want to remind everybody that the future moves forward (as silly as it sounds - nobody does version 2.0 of something then later on comes with version 1) and things TAKE TIME TO IMPLEMENT. They also go through a lot of beta, or bug removal processes that ARE NOT INSTANT. You know, those moments when you tear your hair out because something isn't working just right :)

Jumping on new technology is smart because it let's you implement it and work out the kinks, while also being prepared when exclusive VsT3 comes out. So when the inevitable happens you don't get caught with your pants down.

To wait around with new plugs while Cake get VsT3 ready and tries to iron out kinks isn't my idea of fun.

I do plan on updating my Waves collection later on and going into UAD territory.

Freddie H


Noel!
 
You said that Pro Channel is based on VST 2.4 standard. Why in God name did you base it on VST 2.4 when you could make it for VST 3.0? That seems not wise to me. It seems you haven’t really thought about the FUTURE at all at Cakewalk.   
VST 3.0 has been out over 4 years now so it’s just matter of time before VST2.4 die, ends? You know, I don’t see any VST 1.0 plugins around on the market anymore… same will happen with VST 2.4 too.It’s just a matter of time before VST 3.0 going to be the only standard in any DAW, next up will be VST 4.0
 
Then you site there with Pro Channel in VST2.4 format that you have invest time and money in that are outdate that no one can actually use.

Ummm, probably because it's cheaper/easier/faster to add a new feature into a core application that has an API already implemented and for all intensive purposes 'proofed'. I'd really like to see some of you try to run a successful software company. Especially in this current market.

..........User: ... So I had Vocal Rider for a while now and I couldn't use it with Sonar ... That plug uses the VST3 side chaining STANDARD that cakewalk ... fire it back up...but only to be shot down again with this VST3 thingy not supported.
 
 

firefly9000


Sorry cclarry, must have missed your post.

I'm not sure how those new features don't matter, but to each his own. I understand the feeling some people have: VsT3 just isn't that implemented yet so why make such a fuss.

While I DO get that, I also want to remind everybody that the future moves forward (as silly as it sounds - nobody does version 2.0 of something then later on comes with version 1) and things TAKE TIME TO IMPLEMENT. They also go through a lot of beta, or bug removal processes that ARE NOT INSTANT. You know, those moments when you tear your hair out because something isn't working just right :)

Jumping on new technology is smart because it let's you implement it and work out the kinks, while also being prepared when exclusive VsT3 comes out. So when the inevitable happens you don't get caught with your pants down.

To wait around with new plugs while Cake get VsT3 ready and tries to iron out kinks isn't my idea of fun.

I do plan on updating my Waves collection later on and going into UAD territory.

Couldn't agree more Firefly...
 
It's better to be the FIRST on the bandwagon, spend the money NOW, and iron out the kinks...then to be LAST on the bandwagon, spend TWICE the money later, and get left with an arrow in your head...