Projects won't open in 64 bit-Solved

I've continued to use 32bit Sonar even though I've had 64 bit computers.  Every time I decide to try the 64 bit version, I've always been disappointed since I can't detect any noticeable improvement.

But I recently had a brand new computer built for me, and I feel I really ought to start taking advantage of how 64 bit can access more RAM.

However - I can't get any of my existing projects to open in 64 bit Sonar.   The progress twirly thing just spins and spins forever, then if I click anywhere, the screen goes semi-white and Sonar isn't responding, I have to stop everything and let Sonar crash.

I Can start new projects in 64 bit, and all seems to be working ok.  But that's not very helpful, because I have several projects in the half-finished stages, and I was hoping to keep building those in 64 bit.

What gives with that?  I suppose I need to un-install and re-install, then go through the patch fixes?

Computer specs:

Windows 7 Home Premium, Service Pack 1
AMD Phenom II 3.00 GHz
8 GB RAM
64 bit OS
Alesis i|02 interface

Randy B.

Beagle


this is probably due to one of your 32 bit plugins in your existing projects not playing right with bitbridge.  what plugins and softsynths do you have in these projects which do this?

Ah- Of course.  THANKS, Beagle - See what a 64 bit newbie I am?  The project I was testing has just one instance of Aria in it.  I'd forgotten that there are two different .dll files - 32 bit and 64 bit.  So, I deleted Aria in a new copy of the project, opened that in 64 bit Sonar, inserted the 64 bit Aria, and re-constructed the instrument lay out.  Ta da.

BUT - now I'm sitting here unimpressed with the 64 bit Sonar again.  The CPU usage on that project was at 28% in 64bit, and at 12% in 32 bit.--- What the...?  -- I'll need to have some patience, see how I can start using the 64 bit Sonar with some actual advantage being involved.  If I had a million instruments in a project, that would be an improvement, but with the CPU more than twice as high---seems like that'll be limiting me.--- I'll try more - Later.

THANKS again!
Randy B.

Beagle


glad to help get that first bit sorted out.

not sure why the CPU hit is higher for the same project, tho.  you might want to try disabling or freezing each plugin or softsynth and see which one might cause the CPU spike.

I've marked this thread topic as SOLVED now, Beagle, because it was just a simple matter of forgetting that there are two versions of Aria, one for 32bit, one for 64bit. 

And I was just moving too fast last night when I replied to you.   This morning I've changed settings so that the test project is now using 12% CPU in both versions of Sonar.

I have a slight handicap with my audio interface, because a true 64 bit driver isn't available for it.  The only option, confirmed by Alesis and my tech help guy at Sweetwater, is to use Asio4All.  The default settings in Asio4all's control panel has a high Asio Buffer Size, somewhere over 500.  Moving that down all the way gave me a great latency of only 1.5 msecs, but that was what was causing my CPU usage to be twice as high as expected.  I've changed that buffer again to 240 samples, which gives me a more-than-acceptable latency of 5.4, and now the CPU usage is down to 12%, same as what this project has in the 32bit Sonar.

So, fine, I can just keep changing that setting in Asio4all depending on the needs of a given project.

Thanks again.

Randy B.