Bristol_Jonesey

I'm doing an orchestral piece right now and have a fully loaded template of EWQLSO Platinum (which takes 8 minutes! to load all it's samples) but once up & running, the machine & Sonar do not complain. 

It's using about 9Gb of the available RAM 

Get yourself an SSD drive Jonesey, going on 14GB in my standard template... takes about 1 min to load

I'm thinking of starting all over and going back to 32-bit, but honestly, I don't know what I'll be losing.

Your computer will only be able to use a little over 3GB of your 4GB of memory. There is no reason to do that. If you want to use 32-bit Sonar, just install that. It will run along with the 64-bit version. 


As for your error message: where did you get that plug-in? It doesn't sound like a Cakewalk plug. 


Errors during installation: 
C:Program Files/Cakewalk/Shared Plugins/Multivoicechorusflanger.dll  Unable to register the DLL/OCX: RegSvr32 failed with exit code Ox3. 

The Multivoicechorusflanger.dll is one of the "half-rack" effects that was originally part of Project 5. It has been bundled with SONAR for some time. It is part of the basic X2 SONAR 64bit installation.

OK, before I reinstall everything, I've put a tech support request into Cakewalk, and we'll see what happens. Would really like to stay with 64-bit since there's a chance I'll upgrade my RAM.
Thanks for all the help.

Glyn Barnes

Frank Haas


Unfortunately not all plugins are available in 64bit. Pentagon will never be..).
 
 
 

Explain then, why I have a working version of 64 bit version of Pentagon on my system? 
I have been running 64 bit Sonar since the release of 8.5 in the fall of 2009, three years ago, so its hardly the bleeding edge anymore.
       

sorry to hijack the thread...
hey glen, as far as pentagon i goes - mine "works" sans a few patches that kill sonar.  i think the most widely reported one is the "Nothing" patch in Bank A.  can you take a look at that - try to load it in your version of PI and see if it works right???

to original question... coupled with hardware benefits, i find the soft synths in 64bit sound way better than 32bit equivalent and a very good reason to upgrade. I bought diva 64 bit yesterday and am completely flabbergasted at how good it sounds. It does my juno 106 a it better than my juno 106 does, which i never expected it would even get close to. 64 bit is a no brainer tbh.

swamptooth


sorry to hijack the thread...
hey glen, as far as pentagon i goes - mine "works" sans a few patches that kill sonar.  i think the most widely reported one is the "Nothing" patch in Bank A.  can you take a look at that - try to load it in your version of PI and see if it works right???

A disclaimer to start with. I am traveling and I have X2 on my laptop just so I can get familiarize myself with the new features. The laptop is not optimized for Audio and is using the ASIO 4 all driver, Performance is erratic to say the least.

I tried the Nothing patch - result a click, then silence.  I changed patches and it was OK again. I browsed a large number of patches at random and "Nothing" is the only one where I found this problem. I tried editing some of the patches, no problems until I changed the Simulator settings on one patch to Valley 3, I immediately got the the same issue. I checked the "Nothing" patch again, and sure enough it uses Valley 3. When I changed the simulator to "none" the Nothing patch worked.  All the "Valley" simulator effects seem to have a problem.
 
Edit - I started a new thread for this issue 
http://forum.cakewalk.com/tm.aspx?high=&m=2708401&mpage=1#2708401

I saw a lot of posts about the expansion of available RAM for 64-bit users, but I didn't see anyone bring up the fact that native 64-bit code gets to use a much bigger and more efficient register set (and additional instructions) within x86-64 CPUs compared to the old i386 register set and it's 32-bit-max small set of registers. Properly used these newer, larger, and more numerous registers can prevent many unnecessary memory accesses outside the CPU complex. I've noticed this bring a lot of headroom to my Sonar use on the same systems (using 64-bit OS + 64-bit Sonar vs. 32). This is why I've always tried getting to 64-bit as soon as possible, but have just done so in the last few years due to a lot of the 32-bit plug in issues a lot of us have been dealing with. I tried XP-64 several years ago and that did show the performance boost, but the incompatibilities were too numerous for me at that time.

But yeah, definitely worth the move now if you are using modern hardware and can deal with some incompatibilities that are reducing as time goes on. 

  x64 enables faster processing in addition to more memory allocation. I'm a guitarist and rarely use more than 4 gb of ram, but I love x64. VC and perfect space are two of the thirty two bit plugs I like. I wouldn't go back to 32. bitbridge is acceptabe to me. http://channel9.msdn.com/...usic-with-Sonar/ 

64-bit is important to me because I use a lot of virtual instruments (orch libraries, etc) so the ability to address all 12 GB of memory I have installed is a big deal.

For some people, this would not matter much.

I did have a bit of a struggle getting some 32-bit plugs to work at first, but all is well now.