Issues transferring projects between 32 and 64 bit computers

I do this all the time, not really had the problems you're having. Sorry about that.

TStorms

Thank you. So, using Sonar bundle files is not possible between two different computers running it as a 32 and 64 bit application?

 
You're welcome. I don't have any experience with bundles but I don't see where that would be a problem. The issues usually come up when you're not using a common set of plugins, VSTs and such. 
 
I have worked with people having other Sonar configurations than mine (different plug ins, VSTs, I/O cards, etc) and it was always a pain in the butt to transfer projects as a whole. Working with plain audio was easier in the early stages. At mix time, we would do it all on one machine because of the different tool sets - I might have had Ozone while the other person had T-Racks, for example. 
 
Of course, I suppose you could agree to always use a common configuration and there wouldn't be any problem at all as far as I know.

Thank you very much for the comments. However, I really don't think it was an issue of the plugins that were used. This was during the initial tracking of the song. I don't think I HAD any plugs inserted in the project at that time. I don't believe I had even started to experiment with different compressors and 'verbs at that point. It was just the raw tracks. And I hadn't used Session Drummer yet, at that point. It was AFTER I brought the project home that I decided to replace the scratch drum machine track (which was basically just a click track) with better drums. And I've since switched to EZDrummer, so I don't even know if I'd have a problem with that software. But I was concerned that other things may have been trying to run 64 bit as well, such as other plugins (which I would have added later - as was the case with SD, or even the main Sonar application itself). So, I felt it was better to just recreate the project from scratch. So, the problem seemed to occur from transferring a project file from a 32 bit version of Sonar to a 64 bit version. I still don't know what's up with this, but I'm sure that it isn't supposed to cause any problems like this.

BLUtunes


Hi everybody,

I created a Sonar project on my computer (which runs Windows XP, so I have Sonar installed as a 32 bit application). Then, I took it over to a friend’s house to add some extra tracks. He has a more modern computer and runs Sonar as a 64 bit application.

Later, when I was trying to add some drums with Session Drummer, I realized that SD had opened as a 64 bit application! This caused incredible latency problems and just generally made it unstable. Furthermore, I didn’t know what ELSE might be trying to run in 64 bit mode – other plugins, or possibly even Sonar itself. I was forced to reconstruct a NEW Sonar project and import all of the tracks separately.

How can I keep this from happening in the future? I certainly want to continue to work with my friend (who is probably the best guitarist I’ve known in all the decades that I’ve been playing music).

Thanks,
Brad

some facts:
You can run the 32 and 64 bit version of SONAR on the same 64 bit machine.
The SONAR file whether the compressed cwb, or the cwp project and associated .wav files, don't know anything about 32 and 64 bit versions of SONAR. They should open just play fine whether using SONAR 32 or 64 bit.

Perhaps there are hardware differences between your machine and your friends machine and your sound cards which mean that you need to tweak his machine to play your projects.

If you've edited a file (your 32 bit created file)  on your mate's computer (64 bit) and then open it on your computer it can't open up as 64 bit unless you have SONAR 64 bit installed yourself.
 
You talk about using SD 1 whihc is reasonably old version so it could be that there are incompatabilities between it runniing on SONAR 64 bit versus 32 bit.
I think it's a 32 bit application so would use BitBridge on your mates Pc but just run in normal 32 bit mode on yours.
 
Hope there's something in there that might give you a clue.