Problem with .cwb files (SOLVED)

I have been sent 2 seperate .cwb files by a fellow sonar user, who is using X1.  I am using X2.

Both bundles contain multiple instances of Dim Pro, audio, and TTS-1.  All the files are fine except for the Dim Pro tracks.  The Synths appear as frozen in the rack, only they haven't been frozen and the midi files don't play.  I cant open the synths to see what patches were loaded.  I know I can get the patches from the other user and re-instantiate the Dim Pro's, but, I intend to collaborate with this user in the future, so how can we stop this happening. 

All TTS1 synths work as expected, its just Dim Pro.

Any thoughts?

Thanks CJ I suspected it might be the version of Dim Pro, I'm on 1.5 but not sure what he is on.  

I'd stick away from using cwb files.
 
Simply save as cwp file, and remember to check "save audio with project".

STinGA


Thanks CJ I suspected it might be the version of Dim Pro, I'm on 1.5 but not sure what he is on.  

I would just ask him.
 
FYI: I get CWB files from time to time and i always tell the person to bounce all MIDI to audio before saving it to a CWB file.

If you have the same synths as your friend he should not need to freeze. 

Think about this most of the demo songs from CW play back just fine on any system as long as the system is up to it spec wise. They often come as bundle files.

The older ones have both MIDI and audio in them. Some of the newer ones as well.

The other question is if the FX in the project is the same on your system and his. Though Sonar can deal with this by alerting you that a plugin is missing. The project will still play back though. 

As to why your Dim Pro is not working using his tracks is a head scratcher. Even if you don't have the right patch the synth should still work. Also I'm not sure why it appears frozen if he didn't freeze it. 

What you may want to do is insert a new Dim Pro and output the MIDI track to it. Ask him for the patch he used and you should be good to go. 

I would also check which version he has of Dim Pro. As well as know exactly his version of Sonar as well as any patches to it. 

I have found that Sonar is remarkable in its ability to open old project files. It has been improved through the years to handle just about all issues. 

Keep in mind that bundle files are not played directly. They are uncompressed and a folder is created that holds the project file and a folder for any audio. It is this project that opens into Sonar. Not the bundle file.  That remains intact. 

Sorry John, I should elaborate,

The synth doesnt show as frozen, more .... Erm, disconnected, and I can't reinstantiate it. The freeze button appears pressed in but not blue. Does that make sense? I have occasionally seen this behaviour in my own projects where a synth mysteriously disconnects and I have to add a new instance and copy the midi to the new instance. 

Well, what I have done is ask him for the patches and I have inserted new instances. Everything works fine in both projects just as he programmed them. 

However, I don't want to do this every time he sends me a project. It's certainly weird.

I will get him to send me a new project with just one instance of dim pro in it and see what happens this time. Just incase there is something peculiar to those projects. 

Ah... I finally remembered. There is an on/off switch for each synth in the synth rack, but it can only be seen when the synth rack is undocked. Not sure if this applicable, but this is handy thing to know if a synth ever shows up disabled for some reason.

You can find a description of this and the synth rack in the help file under the title "Using the Synth Rack Browser"