Cakewalk pushing Antares Elite bundles that don't work in 64bit?

Bought the Antares Choir and Aspire bundle assuming if Cakewalk was pushing it they'd have tested it. Not to get into finger pointing prematurely, maybe there's a problem with my install, but maybe they just never tested in 64bit or tested and never told us it wouldn't work.

Anybody have any luck running the Antares Elite bundle in X1 or SPE 8,5 in 64 bit Win7?

I installed as administrator, I went out and bought the iLok dongle in ( device manager says it is working properly, but how can I know for sure?), I authorized through iLok and put the licenses on the dongle.

I don't have X1 or SPE 8.5 32 bit versions installed and don't want to install them just to get this working.

And of course, Cakewalk won't take returns on software. Am I stuck? Am i out $90 for software and $50 for an iLok I didn't need?

any help would be greatly appreciated. I wanted to use these effects on a score I need to finish in a couple of days.

thanks

Some of Cakewalks own plugins don't work in 64 bit but need to be bridged. Sadly Bitbridge will work with a plugin on my system and not on yours. such is the 64 bit landscape when bridging 32 bit plugins. maybe on their tests it did work; who knows. The real point is do you want to get it working.

Many of us who work in 64 bit also use jBridge as it seems to complement Cakewalk's own Bitbridge technology.

Bitbridge is getting better but I prefer the extra options that jBridge provides. For $20 it's hardly a big cost and gives you options to allow you to keep working on 64 bit. I'm interested in solutions not going on about waht cakewalk should and shouldn't do. If it hadn't been for their pushing since 2005 we wouldn't have the 64 bit options we have now.

Just google jBridge. It's a one man show but he updates very regularly and will work with you to help you iron out issues. The best part is that SONAR's plugin manager gives you the option on a plugin by plugin basis to choose jBridge over it's own BitBrodge. jBridge has some other very nifty tricks up its sleeve and is a worthy tool for your 64 bit kit.

I have Antares Choir and Aspire both running perfectly well with X1a, Windows 7 x64. No problems at all. I have JBridge, but they don't need it. I also have Sonar x32 installed (to run Rewire to Reason - but that's another x64 issue (feel the frustration)).
 
I didn't do anything different than I would normally do to install.
 
I too purchased an iLok specifically for that purpose - but have now found that it has opened a whole world of software that i didn't buy because of iLok.
 

antares says it's older software I have version 4 will not run on the 64 bit system after I bought the dongle as well at east I have for when I get a copy of protools 9 I feel you pain.  $$$$$$$$

Will this "jbridge" solve my problem of only being able to run 1 UAD plugin at a time?

Benny, you say you have it on win 7 64, but are you running it in Sonar 64 bit or Sonar 32 bit?

 
It runs on Sonar x64

Jind

Bub


The same deal with Guitar Rig Pro 4. Back when it was being sold with Sonar 8.5 they advertised it as 64bit but it's not.

Guitar Rig 4 Pro has been available as a 64 bit plugin for quite some time now.  Am I reading your reply incorrectly?

Nope. It's not 64bit.

One quick way to check, turn on 64 bit precision engine and load Guitar Rig Pro 4 as a VST.
You know how you should see the ''        '' underneath the VST's name if it is 64bit ... GRP4 only shows up as '       ' (32bit) even if you load the 64bit version of the .dll. This means that it is going through bitbridge which is what upset me about it. I try to only use 64 bit plugs so I don't have to deal with bitbridge at all.

So far I've confirmed this on 3 PC's in 8.5 and X1. Check it out and come back and post your findings.

John


That is for showing if the FX is processing in stereo and also if it is using 64 bits for processing. It says nothing about whether a plugin is native 64 bits. You can tell though with the FX dialog header. A native 64 bit FX will have a smooth header a bridged FX will show a hashed header. Also a bridged FX meaning 32 bits will not goto the background and show up as a separate window on the task bar.

Native bit depth has no relation on what bit depth it processes at.

So what your saying is, an FX can use 32bit processing in Sonar and can still be 64bit native and therefor not need Bitbridge?

Also, I'm not sure what you mean by the FX dialog header. Can you explain that a little more and how I find that. That's not something I'm familiar with.

I emailed NI tech support about this a while back. I asked them about Bitbridge and it showing as a 32bit plug in Sonar. They said GRP4 was in fact a 32bit application even though it says 64bit.

John

Also, I'm not sure what you mean by the FX dialog header. Can you explain that a little more and how I find that. That's not something I'm familiar with.

Sure you are its the FX window.

Any chance of a screenshot showing me what you mean by the hashed header. I'm still not getting it.

Any chance of a screenshot showing me what you mean by the hashed header. I'm still not getting it.

This is a 32 bit plugin.


Below is a 64 bit plugin.

Glad I could help Bub. 64 bits is the only way to fly.

Techically when you have both the 32 and 64 bit version of the same plugin installed SONAR x64's plugin manager should scan only the 64 bit version, even if you have both the 32 and 64 bit VST Plugin folders in the scan path. Unfortunately some plugins don't behave properly and you occassionally get both version scanned by the 64 bit Plugin Manager. That's why I do the following with my plugin folders.

The reason I have an additional folder just for 32 bit (x86) plugins is for those where the manufacturer wants to always install both a 32 and 64 bit version. when it works properly then the 64 bit VST scanner doesn't load the 32 bit version but when it doesn't work properly it means I end up having 2 of the same plugin where the 32 bit one is also running through  Bitbridge. For those plugins only I use the 3rd folder. This of course has to be worked out by trial and error.
1. Program files\Cakewalk\Vst Plugins\ Manufacturer\plugin
All 64 bit Plugins
2. Program files (x86)\Cakewalk\Vst Plugins\Manufacturer\plugin
All 32 bit plugins you want to run in x64
3. Program files (x86)\Cakewalk\VST Plugins (x86)\ Manufacturer\plugin
All 32 bit plugins for which you already have 64 bit versions and the VST scanner insists on installing the 32 bit version as well under bitbridge.
SONAR x64 scans 1 & 2
SONAR x86 scans 2 & 3

mudgel


I can use Perfect Space without any problems through bitbridge or jBridge. Both work equally well.

Not here. It was Crash-fest 2010 for me.

Thanks for the info about the 32/64 bit plugins.

I've tried several reinstalls of the Anatares plugs and tried JBridge but it too chokes on the scan of the plugs. I wonder if Benny's having both Sonar 32 and 64 on his computer enable sonar 64 to 'accept' the antares 32 bit plugs. don't know why it would work on Benny's system and not mine. Any ideas?

Thanks