Still doing it like Steve suggests, using Google. I haven't tried that workflow out in production yet, only testing. If you go this route, you can even do it via the site that gives Cakewalk by BandLab its name, as export/upload of stems and mixes directly to your BandLab account is now built in to Cakewalk. I would avoid emailing projects and use a file sharing service instead. Working on "Save As" projects preserves snapshots of the project over time making it easy to recover should a problem arise. All users work on local copies of the same "Save As" zip. Instead of bundling the project, use " Save As" with "Copy all audio with project" enabled to a new folder. This is the Cakewalk default so, should not be a problem. Make sure all users use per-project audio folders. Single files are the easiest to manage but multiple files can be handled either by zip or bundle.Ģ) All collaborators have a copy of the project. Collaborators send back their contributions to be integrated into the project. Could it be as simple as a muted clip or take lane?Īs to alternatives to full project bundles:ġ) One user maintains the project sending a submix or stems to collaborators. It is hard to say without inspecting the project what the problem is. If no errors were displayed when unpacking the bundle or loading the project there is something else going on. Usually when a bundle or an audio clip is corrupted, CbB will display an error. This is why one should not use bundles for archiving but when collaborating the original project should be on one of the collaborator's machines. This can be a disaster if the bundle is the only copy of a project. What is true about a corrupted bundle is they are, for the most part, unrecoverable. It is not clear if the incidence of corrupted bundles is particularly higher than any other file type. Project and audio files get corrupted too. They have been around for decades and there are reports of corrupted bundles. They have a long history of becoming corrupt.
0 Comments
Leave a Reply. |