Jump to content
  • 0
Sign in to follow this  
OndrejLukasek

Sharing and sending of a project

Question

Hello,
I'm a newbie to Cakewalk, so I don't really know how to do things properly.
Currently I'm working on a project with my friend and he did part of it and the rest we're planning to do at my place together. I'm trying to figure out, how can he send that project to me. No way seems to work or I just don't know how to do it. Or is there any easy way to send projects?
Could anyone help?
Thanks, I appreciate all the help I can get. :)

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 1

If you're both using Cakewalk, the easiest way is to zip up your project directory and either use a cloud drive for sharing the file, or just email it.

If you're both using separate DAWs, there are various ways:

  • Export as OMF (assuming the other DAW supports this)
  • Export the tracks as Audio
  • Upload the project to BandLab

Share this post


Link to post
Share on other sites
  • 1
Posted (edited)

Cakewalk stores each project in a folder. If you friend is coming over to your house then just save that folder to a thumb drive and copy to your computer

If you open the project and then use “save as”  with copy audio checked, browse to a portable drive and save this is quick method to make backup files  

 

 

Edited by John Vere

Share this post


Link to post
Share on other sites
  • 1
Posted (edited)

if you're planning on sharing - some preparations are needed to do this smoothly:

 

make sure your audio clips are bounced to clip and extended (not dragged!) to 1:0:0 mark so the person receiving them can align them to the zero mark. yes, you can export them individually as broadcast wav which have the time markers embedded, but what if the recipient cannot use that? so zero mark is best.

if you know the person on the receiving end will not have the plugins needed, print a separate track with the effects and then remove them from the project once you have documented their settings.  make sure any plugins which are yours exclusively and not likely to be available (easily) for the other person (and which you determined are critical to the mix) are documented. Word is a good choice with screenshots.

make sure all the clips and associated file names are understandable. it makes it much harder for someone to sort through clip#99 clip#A mix_clip#5 etc

create a copy of the project with it's own audio file directory. this (check the copy audio files box) makes copies of the audio clips and only the ones you're actually planning to share and not a variety of clips which will be confusing to someone needing to patch them together. this is where you can export OMF file as well - open the newly saved-as project and export.

ensure the person you're sharing with can read your files at the sample rate and bit depth of your project. it won't be helpful if the person getting your files can only support 44.1K @ 24 bit to send files which are 96K @ 32 bit... if not, convert the audio files to the required sample rate and bit depth.

export a "draft" mix (or demo/reference etc mix) so the person receiving the package have a rough idea of what you're doing at the time you sent it...

then zip the new project directory. this captures the project file, OMF, Word doc, rough mix, and audio clips into a single blob which is universally accessible. the recipient of the package can use the project file or just import the audio clips into the DAW of their choice.

now share the blob via USB drive, or via cloud services.

of course, if the person you're exchanging with use the same version of CbB, then you can skip the OMF and leave any shared plugins in place.

feel free to have people sending you their projects take the same efforts to package up their work before sending it. 🙂 

 

Edited by Glenn Stanton
tweaked on OMF

Share this post


Link to post
Share on other sites
  • 0
Posted (edited)
4 hours ago, Glenn Stanton said:

if you're planning on sharing - some preparations are needed to do this smoothly:

 

make sure your audio clips are bounced to clip and extended (not dragged!) to 1:0:0 mark so the person receiving them can align them to the zero mark. yes, you can export them individually as broadcast wav which have the time markers embedded, but what if the recipient cannot use that? so zero mark is best.

if you know the person on the receiving end will not have the plugins needed, print a separate track with the effects and then remove them from the project once you have documented their settings.  make sure any plugins which are yours exclusively and not likely to be available (easily) for the other person (and which you determined are critical to the mix) are documented. Word is a good choice with screenshots.

make sure all the clips and associated file names are understandable. it makes it much harder for someone to sort through clip#99 clip#A mix_clip#5 etc

create a copy of the project with it's own audio file directory. this makes copies of the audio clips and only the ones you're actually planning to share and not a variety of clips which will be confusing to someone needing to patch them together. this is where you can export OMF file as well.

ensure the person you're sharing with can read your files at the sample rate and bit depth of your project. it won't be helpful if the person getting your files can only support 44.1K @ 24 bit to send files which are 96K @ 32 bit... if not, convert the audio files to the required sample rate and bit depth.

export a "draft" mix (or demo/reference etc mix) so the person receiving the package have a rough idea of what you're doing at the time you sent it...

then zip the new project directory. this captures the project file, OMF, Word doc, rough mix, and audio clips into a single blob which is universally accessible. the recipient of the package can use the project file or just import the audio clips into the DAW of their choice.

now share the blob via USB drive, or via cloud services.

of course, if the person you're exchanging with use the same version of CbB, then you can skip the OMF and leave any shared plugins in place.

feel free to have people sending you their projects take the same efforts to package up their work before sending it. 🙂 

 

Never thought it could be that complicated. But it makes sense to me. Thank you for taking so much time for your explanation!
Shame there is no automated option for sharing like GitHub. That would be awesome!

Edited by OndrejLukasek

Share this post


Link to post
Share on other sites
  • 0
5 hours ago, John Vere said:

If you open the project and then use “save as”  with copy audio checked, browse to a portable drive and save this is quick method to make backup files

Simple, but it works, thank you!

Share this post


Link to post
Share on other sites
  • 0

it's not so much complicated as it is preparation work so your projects are in the best condition possible when sharing them, otherwise the recipient has to do all the work, and they could get it wrong resulting in a lot of wasted time. plus, you're likely to do a bunch of these steps when it comes time to archive a project. knowing if you rehydrate it, you'll mostly have things organized in a way that helps you get back to mixing instead of patching up a mess...

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×
×
  • Create New...