Bristol_Jonesey

 

All of which really begs the question - why are you persisting with Sonar?

See post #24 and #200.

I hope that a free update will come later of X2 year 2013 that address VST3 issue...

Scott -

From my perspective...I've made every upgrade beginning at CWPA 8. And for the last eight years (part-time for the five years prior to that) I have made my living with Cakewalk products. For me, I buy products (not just software) after researching then deciding what features will work for me and which won't. If there are more negative features than positive, I pass. If I go ahead with the purchase, I embrace those features that work and stay away from those that don't. I have been very successful using this strategy.

Now, I'm assuming you haven't purchased X2 yet. I assume this because, as a professional, I know you've done your homework. If you see that the lack of VST3 as a deal breaker for you, what choice do you have but to move to another platform? I totally understand the expense and time but if the product is going to stop you in your tracks, I don't see that you have any other choice. The only pitfall here, no DAW is ever going to do 100% exactly what every person is going to need.

I have seen these same exact threads occur year after year, it's just different issues. And for the most part, those mostly greatly stressed out over the non-implementaion de jour are still around when the next version rolls around.

All in all, X2 am what it am. The back and forth debate regarding the inclusion or lack of VST3 is a moot point. It's not in X2 and won't be at this time. Feel free to submit Feature Requests as some of us have done for two years for something as seemingly simple as color customization.

So good luck whichever direction you decide to pursue.

And FWIW, I do understand I won't change your mind.

I had to check in and see for myself how a VST3 topic could possibly extend to seven pages. And now that I've read the whole thing through, I still don't know.

I have never seen so much badly-understood information become the basis for evangelical breast-beating, so much opinion and speculation stated as fact, and so many marks so widely missed. Not on this forum, anyhow. 

Those of you who have neither written nor worked from an interface spec and don't know what one is, please shut the fck up. You are killing the SNR here.

It is sad to watch that it isn't so fast implemented new technologies/ features as you use to do before in your old days, x64bit etc..
It was that, that made me leave LOGIC/ Cubase to favor SONAR + other features like change all the colors that was locked in Cubase no DX.

That has also been taken away now in X1 perhaps X2 too? Now SONAR is LOCKED all the colors but Cubase colors are unlocked, you can change them since version Cubase 5.
 

Still I'm in this boat but start having doubts though....perhaps I will need to crossgrade back to Cubase instead that guarantee VST3 support year 2013 and other features...still like Sonar alot...will miss Pro Channel and icons..

pdlstl


Scott -

From my perspective...I've made every upgrade beginning at CWPA 8. And for the last eight years (part-time for the five years prior to that) I have made my living with Cakewalk products. For me, I buy products (not just software) after researching then deciding what features will work for me and which won't. If there are more negative features than positive, I pass. If I go ahead with the purchase, I embrace those features that work and stay away from those that don't. I have been very successful using this strategy.

Now, I'm assuming you haven't purchased X2 yet. I assume this because, as a professional, I know you've done your homework. If you see that the lack of VST3 as a deal breaker for you, what choice do you have but to move to another platform? I totally understand the expense and time but if the product is going to stop you in your tracks, I don't see that you have any other choice. The only pitfall here, no DAW is ever going to do 100% exactly what every person is going to need.

I have seen these same exact threads occur year after year, it's just different issues. And for the most part, those mostly greatly stressed out over the non-implementaion de jour are still around when the next version rolls around.

All in all, X2 am what it am. The back and forth debate regarding the inclusion or lack of VST3 is a moot point. It's not in X2 and won't be at this time. Feel free to submit Feature Requests as some of us have done for two years for something as seemingly simple as color customization.

So good luck whichever direction you decide to pursue.

And FWIW, I do understand I won't change your mind.

Nothing new, no revelations here but it is a refreshing thing to see you seem to "get me" now.
 
Hopefully Bitflipper and others realize that I'm not pushing for VST3 (although it is one more straw on the camel's back) as I realize that would be a monumental task to implement at the moment and the features I specifically seek could likely be achieved without VST3 implementation.  I have no interest in confusing the issue and despite how some perceive this thread I've learned a few things. However, I am disappointed to see that Sonar still does not appear to have interest in supporting Waves plugins to their full capacity.
 
In the short term it's a toss up between doing the majority of my work in Sonar and using Audition when necessary or seeking a new DAW that would better allow me to largely work in a single program without disruption. Long term is obviously impossible to predict, we can only watch for "signs"...either way is not ideal nor is it an easy decision.
 
Now if someone cares to explain to me the real "issue" of Waves not being fully compliant with Sonar, as this is not the case in other major DAWs, I'm all ears. I can only suspect I that I will continue to hear speculative answers and those that shed little light on the subject, sadly from Cakewalk representatives as well.

Hi SToons,

I hope your Mother's pacemaker procedure went well.

Someone posted the waves compatibility map and it showed Waves is fully compliant with not very many DAWs at all. 

You are going on a massive crusade because you bought a Waves Bundle, as is cclarry.  You are repeatedly pushing your backward opinion in the face of all evidence.

backwoods


Hi SToons,

I hope your Mother's pacemaker procedure went well.

So far so good.

Someone posted the waves compatibility map and it showed Waves is fully compliant with not very many DAWs at all. 

No, just the major ones.

You are going on a massive crusade because you bought a Waves Bundle, as is cclarry.  You are repeatedly pushing your backward opinion in the face of all evidence.

What backward opinion? That Sonar does not fully support Waves. Yeah, real backwards. Completely accurate.
 
What backward opinion? What evidence have I ignored? Facts please. And quotes. And make sure you read all my posts carefully as I have no trouble shoving the foot all the way in once you put it there.

There are very few professional compressors that will sidechain in Sonar.  incorrect

Why should they? Why should other companies bust their butts and spend serious money to make plugins "Sonar compatable" when they can instead code for existing formats such as VST3 which is supported by:  FL Studio  Cubase  Nuendo  Adobe Audition  Presonus Studio One 2  Sony Acid   acid does not support vst3 

What evidence have I ignored?  What noel said- the userbase in main doesn't give a flying fck about VST3

can't be bothered rereading your other posts sorry


p.s. Sidechaining is not my preferred method for ducking or deesing. It's a lot easier to do with manual envelope adjustments. Not sure how you "Professionals" do it.

backwoods


There are very few professional compressors that will sidechain in Sonar.  incorrect

Why should they? Why should other companies bust their butts and spend serious money to make plugins "Sonar compatable" when they can instead code for existing formats such as VST3 which is supported by:  FL Studio  Cubase  Nuendo  Adobe Audition  Presonus Studio One 2  Sony Acid   acid does not support vst3

That's the best you can do? Wow, the significance of those errors in absolutely astounding...especially considering I offered no arguement otherwise in our subsequent "discussions" on compressors and had figured we were past that. I erroneously assumed you meant some issue that was relevant. My bad.