I shall stay tuned, then!  Thanks for the info.

I thank you all for the information

Do Sonar X1 32 bit works well on Windows 7 64 bits?

JM - Yes - SonarX1 32 works perfectly in a Win7 64bit environment.  Just be careful with your plug-in locations.  The 32bit plugins should reside in Program Files (x86) now.  If you are thinking about trying SonarX1 64 someday, you have to be very careful to separate the plugins in the proper folders and make sure your scan folders are set right.

I got my new computer about a week before X1 came out, and since it was my first computer with more than 4GB RAM, I installed W7 64.  I installed 8.5 64 bit as well as 32 bit.  8.5 64 bit was kind of hinky, so I went with 32.  As a result, when I got X1, I only installed 32 bit.  About a week ago I decided to try X1 64  bit, partially because Pro Channel made a lot of my old 32 bit plugins redundant.  I was amazed.  X1 64 is at least as stable  as 32, and CPU load barely registers, as compared with about 25% average in 32 bit.  As my projects get more complex, as they surely will, this increased headroom will become more and more important.  The only plug I really miss is Waves L1, and I only use that on final mixes.  So I can take the mixed final, export it to X1 32, and run it through that (if it comes to that, and I'm not sure it will).  All the other 32 bit plugs (IK,mostly) run seamlessly under bitbridge. I don't even know it's there.  If you have the RAM, by all means, use it.  

Not all plug-ins x32 work well on Win x64.

your are right that  is why i went back to 32bit

To second something that GuitarTrek says, if you are running X64 and 32 (as I sometimes do), you want to be sure your plugin folders don't get mixed up.

Your 32 bit host CAN'T EVEN SEE your 64 bit DLLs.

On the other hand, your 64 bit host can see both 32 bit and 64 bit DLLs (that is true of VST only as far as I know).  So even though you have both, you may want to be sure your 64 bit DLLs are named differently than your 32 bit ones.

For example, Flibbertygibbit.dll would be your 32 bit one, and would reside someplace inside the Program Files (X86) ////Vstplugins folders.

And Flibbertygibbit_64.dll might be your 64 bit one and would reside in the plain old "program files" structures.

Your 32 bit host can't recognize the 64 bit plugin anyhow, but this naming convention would let your 64 bit host "see both".  If you (or the installer) named them both the same, then your 64 bit host would only see one.  Probably the first one in the Vstplugin folders search order.


...a nearly useless tidbit there, unless you move stuff around in your spare time between games.

Ever since I've gone to 64 bit I've always installed the 32 bit version as well because there are some plugins that I have that just wont work in the 64 bit version.

Originally this was many plugins, but over the last 2.5 years it is now down to 1 single MFX (MIDI) plugin.
I've never had a problem as the actual SONAR project files are independent odon't care whether they are created in a 32 or 64 bit version of the program.

So if you have any doubts and you're on a 64 bit OS I say install both as they are designed to operate in their own space, can comfortably coexist and wont interfere with each other. It only costs few hundred MB of disc space for the program and then whatever space in duplication of plugins you create.

If you're intersted in going ahead it is important how you setup your plugins though. YOu can always PM me and I'll send you an excellent pluing installation plan for use with a combined bit 32 and 64 bit installation.

I was using several 32bit VST's in my SonarX1 64.  Today I installed their 64bit equivalents and modified the scan folders.  I had to jockey around the vstfolders though.  The manufacturers have a variety of spots they like to deposit them in.  Some \Cakewalk\VSTplugins... others \Steinberg\ and other flavors too. 

Today I installed DimPro 64 and Trilian 64.  I'm still using Ozone4 32bit - I'm going to change that another day to Ozone4 64bit.