2:43AM

brconflict
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008.

I liked the RSX.  Affordable, attractive and great little car with an awesome interior. They dumped production after 2005, I believe. Dumb.
 
Well, my Sonar X2aP seems to be getting better. I had one WSOD crash the other day while turning on console emulators down the line while audio was playing. Sorry, but my bad habits don't allow me to not audition constantly while making changes. I increased my buffer size in an attempt to cure the crash. More testing to follow. If not getting better, then I will be buying a Firewire card and going forward with that.
 
I will retract my statement about jumping ship with Sonar. I am vested, and I want to see it get better. I know the system, and I know how to use it...mostly. ProChannel modules are a convenient plus and something definitely unique to Sonar. I like the convenience, I suppose. On the other hand, there are some great non-ProChannel plugins out there. So is it really necessary to have the ProChannel strip in the first place?  At the end of the day, what difference does it make whether the plugin is a ProChannel or in the FX Bin? Overall, I like using ProChannels, which is why I upgraded to Producer in the first place. As long as Cakewalk programs QUALITY in the ProChannel modules, then I will usually try to use them over other, similar plugins (compressors, saturation, and EQ definitely).
 
However, I don't agree with paying MORE for any updates. Come on now...

Cubase has channel strips. Pretty much the same idea as PC  - its built into the inspector and mixer - you can see eq, compressor, limiter, transient shaper, saturation, etc. You also can add fx as per normal.

2:43AM

brconflict
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008.

I liked the RSX.  Affordable, attractive and great little car with an awesome interior. They dumped production after 2005, I believe. Dumb.
 
Well, my Sonar X2aP seems to be getting better. I had one WSOD crash the other day while turning on console emulators down the line while audio was playing. Sorry, but my bad habits don't allow me to not audition constantly while making changes. I increased my buffer size in an attempt to cure the crash. More testing to follow. If not getting better, then I will be buying a Firewire card and going forward with that.
 
I will retract my statement about jumping ship with Sonar. I am vested, and I want to see it get better. I know the system, and I know how to use it...mostly. ProChannel modules are a convenient plus and something definitely unique to Sonar. I like the convenience, I suppose. On the other hand, there are some great non-ProChannel plugins out there. So is it really necessary to have the ProChannel strip in the first place?  At the end of the day, what difference does it make whether the plugin is a ProChannel or in the FX Bin? Overall, I like using ProChannels, which is why I upgraded to Producer in the first place. As long as Cakewalk programs QUALITY in the ProChannel modules, then I will usually try to use them over other, similar plugins (compressors, saturation, and EQ definitely).
 
However, I don't agree with paying MORE for any updates. Come on now...

Cubase has channel strips. Pretty much the same idea as PC  - its built into the inspector and mixer - you can see eq, compressor, limiter, transient shaper, saturation, etc. You also can add fx as per normal.
 
Things to think about re: PC
- generally speaking they don't work outside of Sonar so don't expect to be able to use them if you decide in the future to use something else
- they are limited in design by the width of the inspector.
- lots of scrolling - oh and you have to click on the inspector before you can scroll grrr
- really- what benefit does it bring over VSTs in an fx bin
 
I remember investing a lot back in the early days in DXi - same deal. Its peculiar to Sonar and will have limited shelf life I suspect as no one supports the format. I had to buy a lot of plugins later in VST. Very annoying.

SteveStrummerUK
 
Here's a question for those of you hovering between jumping ship or sticking with Cakewalk.
 
If all your Pro-Channel modules had also been made available as standard VST plug-ins (like the CA-2A now is) so you could use them in any host program, would that make your decision to defect easier?
 
Some might suggest that making them proprietary and only able to work inside the Pro-Channel was a shrewd bit of business.
 
 
 

No. Only one thing keeps me from jumping ship- I said they had one more chance to get it right.
If whatever they do isn't right their next shot is their last with me.
 
Simple as that after the last few years of crap I've delt with since the release of X1.
 
 

.

I just bout the Sonnitus VSTs from Cakewalk as I couldn't use DXis in Cubase 7 - I didn't realise there was a 64bit version out there... what on earth?? That is really annoying as I don't like mixing 32 bit and 64 bit environments = crash central

Lack of x64 versions stopped me buying, I'm interested to hear that they do exist! Wtf?

mike_mccue
"I remember investing a lot back in the early days in DXi - same deal. Its peculiar to Sonar and will have limited shelf life I suspect as no one supports the format. I had to buy a lot of plugins later in VST. Very annoying."
 
 
What is really annoying is that the very same company that promoted the DX format plug ins will not sell its Producer licensees the versatile and useful 64bit Sonnitus VSTs that they include with the SONAR Studio package.
 
You can buy an extra copy of SONAR Studio if you want to upgrade your Sonnitus VST to 64bit but you can't buy the 64bit VSTs separately the way you can buy the Pro Channel cripple ware.
 
I've been thinking of buying a used copy of SONAR X1 Studio on eBay just to get the 64bit Sonnitus VSTs for use with Studio One (x64).

I was so surprised by this I actually checked it out and you are absolutely correct! Straight from the Cakewalk store

'SONAR X1 Studio also includes the entire Sonitus Suite (as both 32-bit and 64-bit plug-ins) and is supported on Windows Vista and Windows 7.'
 
Why would you bundle 32 bit plugins with your 64 bit flagship product - when 64 bit plugins are already there?
Why would you sell 32bit plugs ins when 64 bit plugins are available?
 
This is FUBAR.
 
 
 
 

2:43AM

brconflict
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008.

 At the end of the day, what difference does it make whether the plugin is a ProChannel or in the FX Bin?

Good question. I don't use Pro-Channel except for it's larger FX bin, since the existing one is tiny. I've tried a few sessions with the full Console Emulation (all channels and busses), but I didn't really find them better for what I do. Even the A-type and S-type CE's took away a little bit of the punch and transient response, where they aren't really supposed to do that in the real consoles. They glue it together a bit more, but they didn't do what I've hear the real consoles do, unfortunately.

SONAR Producer has included 64bit Sonitus plug-ins for as long as they have been available.  There is no 64bit VST version of the Sonitus plug-ins, the format shipped with SONAR is 64bit DX. The Sonitus suite sold at the Cakewalk store is the 32bit with both VST and DX formats.

scook
SONAR Producer has included 64bit Sonitus plug-ins for as long as they have been available.  There is no 64bit VST version of the Sonitus plug-ins, the format shipped with SONAR is 64bit DX. The Sonitus suite sold at the Cakewalk store is the 32bit with both VST and DX formats.

I didnt think DX was 64bit? Thats what bit bridge was for?