Jump to content

Freshly Baked ReMixer Challenge 2008 (Phase 3: Match-Ups, Mixing, March 16th Deadline

Ramaniscence

By Ramaniscence,
in Competitions

 Share

Recommended Posts

V___ Newbie

V___

Posted
Posted

My original MMX track fucked up; I heavily compressed it then made alterations then compressed again, altered again, and then started EQ'ing like crazy. End result: completely fucked instruments. i'm gonna have to restart it....

Chrono Trigger... well lets just say my interpretation of the source is very very liberal

Hmm, well couple more days left....

Link to comment
Share on other sites
Kanthos Newbie

Kanthos

Posted
Posted

I've had Cubase crash and burn when loading old files, although it wasn't corruption. Cubase doesn't really like VSTs that load a lot of samples when they launch. I can save an instance of Kontakt in a project, for example, but if Kontakt tries to load instruments, Cubase dies. Took me a while and a couple lost projects to figure that out.

Link to comment
Share on other sites
Steffan Andrews Newbie

Steffan Andrews

Posted
Posted

I've had Fruity Loops corrupt many session files in the past. Very frustrating.

I set Cubase to auto-save every 10 minutes and keep at minimum 5 backup versions. In addition to that, I save iterative sessions as "CT Remix - Tyrano Lair 01.cpr", "CT Remix - Tyrano Lair 02.cpr" etc. every time I reach a milestone or complete a significant amount of work. If the current file gets torched or you do something stupid and save it, you're able to go back in time to previous versions. There's absolutely no reason for "corrupt" sessions making you lose all of your work if you operate this way.

Link to comment
Share on other sites
Dhsu Newbie

Dhsu

Posted
Posted
I've had Fruity Loops corrupt many session files in the past. Very frustrating.

I set Cubase to auto-save every 10 minutes and keep at minimum 5 backup versions. In addition to that, I save iterative sessions as "CT Remix - Tyrano Lair 01.cpr", "CT Remix - Tyrano Lair 02.cpr" etc. every time I reach a milestone or complete a significant amount of work. If the current file gets torched or you do something stupid and save it, you're able to go back in time to previous versions. There's absolutely no reason for "corrupt" sessions making you lose all of your work if you operate this way.

It might be better, if not easier, to use a Subversion repository along with the TortoiseSVN client. It will make full backups of your work every time you commit your changes, without taking up the full amount of space because after the initial save it only stores the changes. And you can revert back to ANY version of your file at any point. Technically it's designed for collaborative efforts, but I've found it functions exceptionally as a backup system as well, and I don't know of any single-user equivalents.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...