ORIGINAL: Brandon Ryan [Cakewalk]

ORIGINAL: UnderTow

ORIGINAL: musicmanrdu

I have to agree with this guy. I use Waves plugins heavily, especially the L1 Ultramaximizer (much better than the limiter in the Sonitus Compressor FX) and I'm not spending $800 or more to upgrade to the latest and greatest Waves plugins just so I can use them in Sonar 5. I was considering upgrading, now I'm not so sure.

Don't all the Waves plugins come in bundles that you can download from the Waves site? By a bundle I mean they contain TDM, RTAS, VST and DX versions in one package? And anyone can download the packages so if you have the authorization on your PC, just get the latest version from the Waves site.

That having been said, this isn't the case for all DX plugins. I think CakeWalk need to create a bit bridge for DX plugins A.S.A.P. or their 64 bit audio engine will be a bit useless for most making it little more than a marketing gimmick (if it isn't allready ... ). You just can't trust all developers to upgrade their code in a timely fashion.

Next time you create a new version of Sonar, dump all the "free" 3rd party plugins and spend the money on developing the actual functionality of the software. That is money better spent. That will impress the professionals much more. You can always get (better) plugins elsewhere. You can't get extra built in functionality elsewhere.

UnderTow

You are confusing x64 and the 64-bit audio engine. These are two separate things and can be used exclusive of each other. There is no reason you can't run 32-bit DX plugs in the 32-bit version of SONAR5 and still use the 64-bit mix engine. The two are independant of one another.

Also, there aren't a bunch of free 3rd party plugins in SONAR5. The Sonitus we own and the Lexicon has been with SONAR since version 3 I believe. The new synths are all created by RGC Audio which Cakewalk acquired and is now "in-house". So these plugs are all an integral part of SONAR now and the only 3rd party involvement is from Lexicon. The Pantheon is definitely not "free" and I doubt anyone would want us to remove it from SONAR.

ORIGINAL: Brandon Ryan [Cakewalk]
In most cases there will be a VST version of the effect or instrument. If not, and you really want to run the x64 version, I would apply pressure on the manufacturer to update the plug so it can be used in a 64-bit environment.

ORIGINAL: ooblecaboodle

Bugger.
So that means no Timeworks EQ, No Timeworks CompressorX, No Waves, and no DX Izotope Vinyl.

That really is pretty sh*t, and it strikes me as a really dumb move.
If you created a bitbridge for VSTs, why not DX'? For a few years you've had people accusing you of not supporting VST fully, and now you don't even support DX fully?

So this fantastic sonar 5 will have:

NO more than 16 ReWire channels

Well, I'm sold
This is a sad day, I really am dissapointed. Don't wait up for my order.

Brandon or Ron, will plugins running at 64 bits internal resolution, but coded for the current 32 bit sound engine DAWs, interface with Sonar at 64 bits, or will the plugins require recoding to do this?

will my wavelab work in a 64 bit enviroment ?

ORIGINAL: Keni

Thanks to Ron, Brandon and Alex for helping to clear up this info...

Now I suggest that we "push" some solid programmer to create a "wrapper" for 32bit DX plugins so that they can be run in the 64bit Sonar version as there is (BitBridge) for the VSTs....

I'm a little surprized that this wasn't done prior to BitBridge for VST support as Cakewalk/Sonar has remained a staunch DX-based host until ...... now?

Keni

ORIGINAL: LixiSoft

will my wavelab work in a 64 bit enviroment ?

Why not ask Steinbug.........but I bet the answer is NO

DXi plug-ins should not work, but you can install the VST version of your plug-ins, so you should not have any problem...I say you shouldn't

ORIGINAL: jlgrimes

Compatibility only becomes a concern when running the x64 version of SONAR5, which is in no way required. It's only there for users that would like to take advantage of their 64-bit ready computers.

These kind of nags are to be expected though since 64 bit systems are just now starting from the ground up.

ORIGINAL: UnderTow

ORIGINAL: Brandon Ryan [Cakewalk]


I'm not trying to be argumentative at all. I'm just trying to make sure this is all clear. However there is some confusion here (understandable), probably due to some assumptions about SONAR5's 64-bit capabilities. So let's forget x64 and just talk about the 64-bit floating point mixing: Bit-bridge is only applicable under x64. There basically is a "bitbridge" of sorts, inherent in the 64-bit audio engine when running on 32-bit machines. Simply, if SONAR encounters a plugin that doesn't support 64-bit floating point it will interface with that plugin at 32-bit. It's just like a 32-bit mix engine talking to plugins that support 64-bit floating point (Timeworks, Ozone, etc) only in reverse in this case.

So basically you turn on the 64-bit engine and all your plugins still work. It's just that SONAR's entire mix engine is running at 64-bit and keeps that resolution when interfacing with 64-bit plugins. When interfacing with 32-bit plugins, 32-bit code is passed between the plugin and SONAR's mix engine.

When on x64 you can run all of SONAR5's internal plugins as they have been coded to work with x64. When using 3rd party plugins, you can install the VST versions of plugs and they will run using Bit-bridge. If a plugin manufacturer updates to 64-bit DX then the DX version can be used at native 64-bit processing (x64).

I sincerely hope this makes sense.

Yes it does. :) Thanks for clearing things up. :)

UnderTow