Hi
I am a newbie so please forgive me if I'm just being stupid here. I would like to send single dry tracks of both midi and wave to my cousin so he can add bass tracks and send it back to me to mix. I'm having a hard time figuring out how to do this can anybody help?
Thanks Tim

If he is also running sonar, you can just burn the entire song file plus the audio folder to a DVD and mail it to him. Usually the entire thing is just too huge for emailing as say a zip file. Alternately, if you have storage space, you can upload it to a server and have him download it from there. Best, Ed

In Sonar you can save as a cwb (bundle file). If he's not using Sonar, you have to bounce each track. It may be easier to take a couple of mixdowns instead (ex. each bus - guitars, drums, etc), and send the midi on the side. That is if he's not going to mix anyway.

Set up a Soundcloud account  and send the individual tracks there as separate files.  Make sure you set them as downloadable.  You will need to bounce down each track separately as wav files by muting all the others.

1) As was mentioned save the project as a Cakewalk Bundle (the extension .cwb).

2) Put that file into a folder on your desktop then Zip it (right click the folder > Sent to > Compressed (Zipped) Folder). By doing this you will lessen the time it takes to upload/download the file. (Your cousin will have to right click the zipped folder > Extract All to unzip it when you send it to him.)

3) Set up a Dropbox.com account, learn how to upload to it. Then send your cousin the download link.

This is all provided your cousin has a compatible version of Sonar. If not you can save it as an OMF file which will open in other programs. Saving an OMF file is detailed in the manual.

You can also make the download/upload times shorter by mixing down the current project to a single stereo track. Import it back into Sonar. Save that as a new file (following the procedure I detailed). Have him record his parts to that backing track. Then when he returns it you can Import those tracks back into the original project and delete the backing track or just copy/paste his tracks into the project.

Be sure to be consistent with your Bit Depth, Samplerates and tempos or you'll run into problems.

Cheers.

Forget step 1, use a per-project folder instead, bundles are not worth the trouble or risk. Don't expect too much compression when you zip up the project folder. If you want to ship a smaller project, perform a "Save As" (make sure the "copy audio with project" box is checked). The "Save As" function will create a project that only includes audio actually used in the project.

I've seen that issue with bundles brought up a few times now but haven't experienced any problems as of yet (done quite few back and forth with bapy and the lads so far). What happens? I'll check out the per project thing/copy audio thing. I didn't really understand why that was a separate thing but I guess this is why. 

As far as the zipping step... it really did seem to help. Dropbox is painfully slow as it is. It works though.

A bundle is just the project file with the audio appended to the end. Sometimes these get corrupted and will not unpack correctly. Years ago bundles were the only reasonable way to consolidate the parts of a project for sharing. When per-project directories came along, bundles became redundant. Single files can easily be created by any number of archiving utilities that have proven more reliable than bundling. If you are going to zip anyway, why go through the extra step of the bundling process.

Right on. I didn't realize bundles were a relic. The documentation isn't very clear on that and pushes CWBs for this purpose so thanks for the info. I'll have to experiment with the newer methods. Thanks.

I have tried several different things over the years. 

Everything from sending the bundles to individual tracks and more. 

If you are working on a project together, the most efficient way I have found to work across the net is for you to record as much as you can to give the idea of the song.... export the wave and convert it to an MP3 and email it to him. I suggest leaving 2 empty measures in the song and be sure the click is audible in those 2 lead in measures. 

When he gets it he simply sets the project up, sets the tempo and imports the MP3 and goes to work. Some folks don't like working with mp3, although I have never had issues with them.....waves are just as good and with a file server site, easy to share.   He sends waves back to you since you are mixing the project. I use Drop box and simply share that folder with everyone in the collab. They are able to go in and get files and leave files. 

Midi files for entire midi projects are small and are no problem to send in most cases attached to an email.

I just had someone send me a zipped project with 8 audio tracks in it. Sendspace was the file server.... aside from the fact that it's pretty hard to tell where to clikc on sendspace these days... all the links have some sort of DL on them and you don't want the crapware..... but I did eventually find the right one. A few minutes to DL it, and unzip it and it loaded up and ran just fine.

On the song Come & Go on my music page.... the music was recorded here with Sonar, while the vocals were recorded at another studio in the next town over, running Pro Tools.... we had absolutely no problems sharing files to make that song work.