eratu


UPDATE:

Okay, I've now installed all the plugins and libraries from NI Komplete 4 and 5 that are NOT inside Komplete 6. I'm waiting a bit more to install K6. I just wanted to keep the old goodies that NI has discontinued. :) I use Akoustic Piano, Vokator, etc. and those have been discontinued and removed from K6. Also, Kontakt 3 and 4 are missing some samples from the Kontakt 2 library....

Verdict: All the older NI plugins I have installed appear to be working just fine with BitBridge so far. Relief!

I even have Kontakt 2 and 3 on there. I also have the x64 version of Kontakt 3.5 installed and it appears to be working fine in Sonar x64. Yay! I will have to test it more, but at least it loads up without BitBridge and seems to be working great.

Next up I will install my sample library (and most of them use a variant of Kontakt players) and then I'll install Komplete 6.

Seems things are starting to come together.... :)

AndyW


Eratu and Jose....I (and I am sure many others) have been lurking in this thread from the beginning and I want to say a heartfelt "Thank You!" for posting your journey.  I recently got an i7 system and installed Win 7 64 and am going through the "reinstall DAW" process to get my "completely 64 bit" DAW up and running.  I am taking a different "minimalist" approach where I am trying to avoid dragging everything on my win XP DAW with me and only taking what I really use but your using a lot more plugs than I do really paves the way(especially with Dim Pro...really appreciate you navigating that minefield for me/us!).  If you don't mind, I would like to post any issues or discoveries I have with my upgrade on your thread if that's OK with you as I use a different set of plugins.  If not, I'll start a new one.  Don't want to hijack.  Keep charging...a number of us are only a few days behind you! 

BTW, I bought Jbridge without even trying it out based on your commentary...agree with you that those are the kind of people we should support.

eratu

vksf01


hi eratu,
thanks for this informative thread.  i've been "living vicariously" through your x64 experiences since i'm planning the 64-bit jump as well.  from what i can see, the big issue with you (other than the fabfilter one) is the synchrosoft issue.  how is that working out for you?  i have 2 synchrosoft protected vstis, analog factory and predator, and i use predator a lot.  it would really suck if i lost the use of that.

thanks!

I'm almost certain I'm through the worst of it. I haven't mentioned everything in this thread, but suffice it to say, several people have been involved and we all owe them thanks! They know who they are, if they read this.

As for the syncrosoft-based plugins, I can say that I am basically up and running with them via a couple of creative workarounds. Cakewalk is also aware of some potentially related issues, as has been reported elsewhere.

For syncrosoft plugins, this would be my recipe to get them working:

1) Buy JBridge. :) If anything is acting strangely, that's a great tool to have handy to use as backup.

2) Have Sonar 32-bit installed along side Sonar 64-bit for testing purposes. Trust me. You will not regret it when the going gets tough. I have not remotely described in this thread the number of different tests I've done to help track down the root causes of the problems, and it was essential that I had the 32-bit version handy for comparison.

3) Test and then retest when it comes to a plugin with copy protection. There have been some funky issues that I've had to work through, and there is no definitive solution yet for the Arturia Moog Modular V 2.5 plugin issue, for example. If that plugin has an issue, I'm sure other syncrosoft-related plugins will have similar issues. Make sure you save a project, then reload it successfully before committing to a usage pattern for the plugin.

4) Be aware that there are a couple of ways to instantiate a VSTi plugin. Some people (like me!) have forgotten the old-school way of putting them into the FX bin of an audio track as an inline synth plugin. If things aren't working for you via the synth rack alone or synth-rack-based instrument tracks, try the inline method. :)

5) If you do get into a bind, get in touch with Cakewalk and the developer of the plugin. Make sure you document every step of the way that causes the problem. From my experience, I really feel that Cakewalk wants to make as many plugins as possible work with BitBridge. It is not trivial what they are doing. There is no other bridge solution that does as much as BitBridge attempts to do at this time, and it's even latency-compensated. So be patient too.

But seriously, I think it won't be that bad for your Analog Factory and Predator plugins. I thought both of my Arturia plugins were causing me issues, but I was wrong -- the CS80V2 is behaving just fine, even with the syncrosoft protection. The naughty one was the Moog Modular V 2.5, but I have two workarounds for it now, and I look forward to a final solution in an upcoming update. :)

PLEASE do let us know how it goes for you... I have my eyes on more Arturia plugins and other syncrosoft plugins as well, so it would be good to cross-reference solutions.

Also, the FabFilter issue is still open, but there are some workarounds for that too, now. I think I've mentioned two ways to get around those problems.

Sylenth1 x64 is just plain broken from what I can tell, but the 32-bit version works fine in BitBridge.

Dim Pro x64 is up and running fine after a lot of runaround. (UAC and admin solutions)

All my NI plugins are working fine so far. I'm shocked by that. :)

And all other plugins I've installed so far are working with BitBridge. :)

When I started out, I think my goal was that 90% of my core plugins had to work with BitBridge in order for me to consider my move to Win 7 x64 and Sonar 8.54 x64 a success. And at the current tally, I'm pretty close. That says a lot for the hard work of the Cakewalk team.