I am planning on working on a piece with someone else remotely. We both have Sonar. But we don't own the same instruments. This piece is going to be for a medium-sized jazz band of about ten players. The plan is for us to take turns back and forth working on the arrangement in Sonar, probably by sending the cwp back and forth via email (then when we're done, we'll export it to Sibelius or whatever, but that's out of scope for this post).
 
What is the best way of doing this, so that we can seamlessly go back and forth and be hearing essentially the same audio as we work? I assume there is some recommended best practice among folks who do this regularly. I've only ever worked on my own projects, but on the occasions when I've sent a project to someone or they to me, it's always a bumpy ride getting the instruments all in place.

Google drive is your friend. I do this all the time and have a generic Google account which I store all my projects on. As long as the other remote users have the same DAW and hopefully as a bonus have all the same effects its easy. Store all the audio files and projects in there own separate folder on your Google drive and share with others.The scary side is with this capability forces you to allow others to have access to the files (you can dictate who has access to what access from single files to full directories). So with it comes the danger of other users deleting files by accident so backing up on a regular basis is a good practice.  Also create Subs busses and bounce all subs to a main sub. This allows ease of transition for those with different audio interfaces. 

Thanks. Unfortunately, the real problem is the fact that we have different instruments on our systems. File sharing is the easy part.

jkoseattle
Thanks. Unfortunately, the real problem is the fact that we have different instruments on our systems. File sharing is the easy part.

Define different instruments on your system. Are they virtual instruments or live instruments being recorded on tracks?

Not sure that I understand the problem. 
 
Make sure that all the tracks on the shared .cwp are rendered to audio with any non sonar FX applied and it should sound the same for everyone.

These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.

jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.

Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.

Zargg

jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.

Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.

 
This would seem a sensible route for a midi only project. Your original post referred to "hearing the same audio" which is what threw me.

paulo

Zargg

jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.

Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.

 
This would seem a sensible route for a midi only project. Your original post referred to "hearing the same audio" which is what threw me.

Me too
Which was why I marked the first reply as helpful. It answered the OP's originally formed question.

Hi Jim,
I do compositions predominately in MIDI and when I've collaborated with others using Sonar, I always record my portion down to an audio track.  That way, if they can't get the exact settings I have (for some reason), they will have my bounced version in the project as reference.
Just a thought...
 
By the way, love the music man! 
Great stuff!