Jose: No time to look at that issue right now, way too many problems with this DAW... but I will if I can get things working.

mudgel: Thanks, man... the mystery deepens with Dim Pro. Will be looking into it more hopefully soon...

UPDATE:

Well, I think I've just about hit the wall. Very disappointed and frustrated. Just about worn out right now on this. Now I can't even open my own Sonar project files... the very test sessions that I am creating with this very installation of Sonar. It says "Could not open file. The file may be damaged or incompatible with this version of Sonar." ... and I had just created it! Happening on all new test files I'm creating with these plugins.

Then, I try to open the file in compatibility mode <shift key> with *all* the plugins selected and it opens. That makes absolutely no sense to me, and it makes me feel zero confidence with this config. Clearly some plugin combination is causing the issue, and it may take me many hours to figure out what combination is doing it. Problem is, I *need* every single plugin I put into the session, so what plugin would I be willing to give up? None of them.

Feeling a bit bleak, and honestly contemplating throwing in the towel right now.

Ironically, I looked at every plugin that was used in that test session, and almost every single plugin was 32-bit running in BitBridge. So why the @#$% am I running x64 for a session like this? <sigh> The reason? Because I need all the RAM when I start adding loads of RAM-hungry plugins. I couldn't even get to that step. But in the end, HAVE to run x64.... if it can't handle what I'm doing to it now, there's no way this will hold up in a production project.

I hate being so transparent and honest here about my emotions, folks, but I'm honestly feeling pretty down about this right now. So much time invested and this just doesn't work the way I was hoping. Disappointment mixed with frustration mixed with latent anger mixed with exasperation. Not sure what I'm going to do at this point. Try to keep going? Or throw in the towel? :(

Yet another update:

Still experimenting to see if I can see a pattern. A sane man would give up now, it's like I'm setting myself up for another kick in the face. I'm going to try to move more things off of BitBridge and try more plugins on JBridge, see what happens. I'll also try designating certain BitBridge servers. I think the load order or procedure for plugins when I reload a saved project is different than when I'm building the session. Wondering if there's something to do with the order the plugins are created. This is insane. :(

You're a great guy, Jose! If there's anyone who deserves the award for #1 kick-ass Cakewalk forum user, you would be my vote in a heartbeat.

Right now I feel burned out on the project. Sonar 8.5.1 x64 seems pretty darn good in a vacuum, it's just the combination of plugins that I believe are giving me the problems. I really think that's the key for anyone contemplating the move to x64. They really will have to sit down and do the homework on all their own plugins themselves. Not only that, it seems possible that interactions of some plugins with others might have issues as well. And on top of that, it's a constantly moving target since the developers are changing things quickly.

After what I've experienced so far, if I could wait another year to go to x64, I would. However, I really, really want to see how Kontakt 4 x64 goes... and the other NI plugins before making my final decision, if possible. I just don't know if I can make it that far. These plugins that I'm testing right now are critical too. And I'm just being optimistic that Kontakt 4 x64 will work. :)

Anyway, bottom line is that this whole x64 thing is not nearly as mature as I was hoping. It's better than the last time I tried to move to x64, but there are still some serious teething problems. My optimism got the better of me, and I think I should have just waited. Again. :(

As for your offer, I may take you up on it. :) As far as I know, Arturia does not yet have the Syncrosoft-based versions of their plugins available as trials/demos, for example. You'd be running the older version to test. So that sucks. I will continue testing, but at a slower pace. It's clear that things will have to be very deliberately tested in various real-world plugin combinations before I feel comfortable devoting a hard-core project to it.  

As for my latest problem, I think I am narrowing it down to a compatibility with BitBridge and the Arturia plugins. My preliminary feeling is that when the project is loaded from the saved file, it doesn't like the Syncrosoft protection. However, if each plugin is loaded one-by-one (either in safe mode or when originally creating the project) then BitBridge seems okay with Syncrosoft. However, I haven't proven this, or created a repeatable recipe for it yet. And there are some other variables I haven't checked yet.

I hope to update again, but there's hardly any fuel left in me for this. I was way too optimistic when I started, and my mind is already spinning with the urgent need to get back to "normal" work, and get running in 32-bit asap... this has been a costly endeavor and the red flags are waving.

Best, James

Eratu,

What should I be doing now? 

So far I've been able to insert 15 instances of each of the FabFilter Plugins (Simpleton, Timeless 2 and Volcano 2) in a 15 audio track project I created.  That's a total of 45 plugins.  So what now?  How do I make this thing crash or fail?  Do I need to insert a synth?  I've never used these plugs so I have no idea what to do :-P

Hey Jose, Wow, you're fast... thank you, sir, as always!

The problem with the FabFilter plugins has to do with issues with BitBridge 2.0. If you get 2-3 different FabFilter plugin types per BitBridge instance, you get the ""The folowing plugin failed to load..." error.

Best way to force it is to set up a project in Sonar 8.5.1 x64 with some FabFilter VSTi -- One and Twin 2. Then put several different Simpletons, Timeless 2's and Volcano 2's, and eventually you'll hit the "The folowing plugin failed to load..." error. OR, you can force this situation even more quickly by designating a specific BitBridge server to have more than one type of FabFilter plugin on it. Hope that makes sense.

Also note that I'm running Win 7 x64. I have no idea if that is adding to the problem or not.

EDIT: for clarity, typos

Eratu,

What I did was put one of each kind into each track.  But I'll try your suggestion.

BRB

Hey Jose, I'm calling it quits for the night, but let's catch up tomorrow, maybe even chat. :) Take care, my friend.

That's great to hear, Jose! So what are the differences between our systems/configs?

1 - Windows 7 x64 vs. Vista SP2 x64
2 - Did you install the FabFilter VSTi as well? Try that, and putting the plugins on one VSTi.
3 - Other plugin conflicts?
4 - You're running the demo versions (I don't think this is the problem since I believe they are the same)
5 - Anything else?

Maybe we should talk, and/or exchange a session file. Any chance you're upgrading to Windows 7 sometime soon. :) I get the error every time. :(

James (eratu),

What MOBO and Graphics card are you running?

mudgel


James (eratu),

What MOBO and Graphics card are you running?

Asus P6T and nVidia Quadro FX570, working great together.

I doubt there's a problem in that area, but who knows? I use the same graphics card in another DAW and it's fantastic on XP -- even tested it with Vista x64, plus everything else with Sonar on this system seems to run great. Even running at 32-sample latency... as long as I don't use the plugins in question. I think it's more likely a BitBridge/JBridge/specific-plugin/Win 7 issue.

I'm 99.5% certain it has nothing to do with the graphics card in this case. This would have shown up in other areas that are working fine. Keep in mind I've now tested a decent session at 32 samples on this specific machine, not to mention another DAW. On this machine I've tested just fine as long as I avoid using these plugins. I use the Quadro cards because the drivers/stability is so good. They are workstation cards -- not consumer cards. So I'm almost 100% certain it has to do with the plugins -- which by the way seem to be working better with JBridge.

Dim Pro x64? Haven't gotten it sorted yet, but I have a lot of good ideas to try thanks to the responses in this thread. (thanks again, guys!)

The FabFilter plugins -- check them out at www.fabfilter.com -- they are KILLER plugins that I use all the time... essential tools for my work, and if they don't work in Sonar, then I don't work in Sonar. Fortunately, I have them working with JBridge, although I haven't pushed them really hard yet so the case is still open. FabFilter is also aware of the issues. They have many uses... FabFilter Twin 2 is a wonderful, extremely powerful pseudo modular synth with a great interface and high-end sound. Love it. FabFilter Volcano 2 is one of the coolest filter plugins I own with awesome modulation features... and Timeless 2, well, there, my friend, is one of the most inspirational, bad-ass sound design plugins of all time. They can all be used for sound design, production, effects, etc.

LOL! Very funny, Freddie! Thanks, man. :) At the very minimum, you made me laugh. :)

eratu


LOL! Very funny, Freddie! Thanks, man. :) At the very minimum, you made me laugh. :)

Great!