TranceAddict Forums

TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- Anyone else get absolutely pissed when...
Pages (2): [1] 2 »


Posted by jupiterone on May-17-2007 22:22:

Angry Anyone else get absolutely pissed when...

You lose your entire project?

Basically I've been working on a monster of a track right now for about a week, i saved it two seconds ago, and i try openning to again and its basically corrupt and i get an error.

Jesus Christ almight I am on the verge of basically throwing my computer out the window.

Is there anything that could possibly roll back changes on my system by time? Instead of system restore that goes by days and points?


Posted by Eric J on May-17-2007 22:41:

Does your DAW software have an auto-backup feature?


Posted by CReddick on May-17-2007 23:02:

It sucks to learn these things the hard way. I learned a long time ago to:

1) Always 'save as' a new version of the file as often as possible. Every time i sit down for a new session, new file. Major changes to your project, save as to make a new file.

2) Copy your whole project folder to a new physical drive occasionally to create a 'safety net' version of in progress projects. even if you lose your whole projects/media drive, you still have the safety net backup.

haven't lost a project since.


Posted by DigiNut on May-18-2007 00:57:

Yeah, happened to me a few years ago and I was pissed. I learned my lesson - always save a new version after doing anything important. I do this with all important work, not just music productions. If it's a massive production that I've worked really hard on I may even back up the entire project folder.

Can you recover it after it's already been corrupted? Not likely. You could try something like Active Undelete but usually those things aren't too helpful.


Posted by jupiterone on May-18-2007 01:22:

Ya it's basically gone. I was basically slamming my desk for minutes and screaming. I don't get what happened, I was opening up Reaktor then Cubase just froze up...dissapeared and thats that.

Tried loading it up I was like god damnit, thank god I didn't do anything that important in that sessions, then bam, error.

No backup either, well thats something new to learn from.


Posted by Fledz on May-18-2007 01:29:

Whenever I make a change I save a new copy.

This is the way I name stuff:
Name, then something you just worked on (then the order in which it was saved)

So,
Airgate Bass (14) means the track is called 'Airgate' and I was working on the bassline, plus it's the 14th version I saved.

Works out quite well as the files are tiny and you can always go back if you need to, plus you know what you just worked on. I just had to backtrack 4 saves because I stuffed something up and couldn't fix it.

Backing up project folders is a smart thing to do too.


Posted by Mr.Mystery on May-18-2007 02:47:

Never happened to me, apart from the time my HD died once - in retrospect it was a good thing since most of those files were awful anyway.


Posted by wrzonance on May-18-2007 03:25:

...people don't have descriptive subjects for their threads.


Posted by jupiterone on May-18-2007 03:27:

quote:
Originally posted by DJFreaq
...people don't have descriptive subjects for their threads.


It usually attracts more people.


What a tactic.


Posted by wrzonance on May-18-2007 03:34:

Totally


Posted by Jason_R on May-18-2007 07:46:

quote:
[i][b]O


2) Copy your whole project folder to a new physical drive occasionally to create a 'safety net' version of in progress projects. even if you lose your whole projects/media drive, you still have the safety net backup.

.


Good advise. Doubt many of us only have 1 drive and it only takes seconds to do. If you think losing one project is bad imagine losing everything!


Posted by substorm on May-18-2007 15:54:

Change to Ableton :P... Sorry Cubase users but dont think that would have happend in Live... I had my PC crash during a production, but when i started it up again and the started Live.. I got the text 'Do you wanna continue from your unsaved project'. Never had that problem though i have a 4 year old Simens "box" that crashes every once in a while i have never lost a project due to this..

But i feel for you mate..

Cheers
C


Posted by wrzonance on May-18-2007 16:28:

Ableton has crashed on me plenty of times.


Cubase has crashed on me plenty of times.


Reason has crashed on me plenty of times.


ProTools has crashed on me plenty of times.


Software CAN and WILL mess up and crash, and you WILL lose projects no matter what DAW you're using.


What I have found out over the years is most often it is your hardware configuration, and how well tuned your operating system is. This is especially true with Windows.


My current daw, I have a custom Windows XP installation with just the bare necessities to make audio land work. Now that I have tuned my operating system the way I like it. And I have all the correct drivers, and no excess. So far all of the software I use hasn't had any serious problems.


AND WHEN IT DOES CRASH


It is a VST plug in I'm using that causes it to shit the bed. The same has happened in Live and ProTools, load a nasty plug-in, and poof, crash! Spinning pinwheel of death, etc.

quote:
Originally posted by substorm
I got the text 'Do you wanna continue from your unsaved project'.


And another thing to point out. All (good) DAWs have an option to auto-save back-ups of your projects. Live, does, Cubase does, and ProTools. Please, make sure you turn that on, or you have only yourself to blame.

In an ideal world, software would never crash on you. But unfortunately, humans are fallible, and thus software is fallible because it is created by humans.

Get real people.

-----Adam


Posted by substorm on May-18-2007 17:09:

quote:
Originally posted by DJFreaq
And another thing to point out. All (good) DAWs have an option to auto-save back-ups of your projects. Live, does, Cubase does, and ProTools. Please, make sure you turn that on, or you have only yourself to blame.

-----Adam


Well that was little my Point.. I he would have had Live installed he wouldnt have had to TURN anything ON. Its there by defult, and as a new user this may be something that not everyone thinks of, or eaven a experienced user. I think all DAW�s should have this as a defult. When it comes to security in programs, i think its better to turn tings off if you dont need them, like for example XP. Its not the best cofiguration as defult for music creation, but you can make it by turning things off.

Cheers


Posted by wrzonance on May-18-2007 17:27:

quote:
Originally posted by substorm
If he would have had Live installed he wouldnt have had to TURN anything ON. Its there by defult


Totally. Wouldn't it be dope if ALL DAWs had auto-save enabled by default?


Posted by substorm on May-18-2007 17:54:

quote:
Originally posted by DJFreaq
Totally. Wouldn't it be dope if ALL DAWs had auto-save enabled by default?


Yes.. I mean, imagine how it was the first time you got your "first" DAW, did you sit and read the damn manual for hours, hell no i didnt..well some of it (Live�s built in tutorial that is greate) but i just wanted to get to it. And most crashes will probobly accure when you are new and just put in shit loads of VST�s and stuff. I cant see any reason why this isnt set by defult.. anyone?

Cheers


Posted by mysticalninja on May-19-2007 06:17:

?
quote:
Anyone else get absolutely pissed when...
You lose your entire project?


nah man wuts wrong with u i love it when that happens.

might be just me but ableton seems alittle less stable than qbase. when cubase crashes it says 'an error has occured save a back up of your project', ableton just disapears lol

quote:
And most crashes will probobly accure when you are new and just put in shit loads of VST�s and stuff.
yeah thats when ableton seems unstable with alot of vst's... doesn't seem to be able to handle as much as cubase on my computer.. what does using alot of vst's have to do with being new tho


Posted by substorm on May-19-2007 12:20:

quote:
Originally posted by mysticalninja
.. what does using alot of vst's have to do with being new tho


Well, every computer has a limit, right? You cant have as many plugins going at the same time. I just speak of self experience.. I mean when i just started using vst�s i didnt know shit about it.. i have used Reason for several years and i didnt know much more than that.

So when got my first sequencer which was Live.4 i started to do my thing, added vst after vst, as if it was the subtractor in Reason, tho it didnt work that well due to my computer "said no".

Dont sayning that its wrong to have many vst�s running, you just have to know the limit of your computer. Not that easy always!

So, i think its better to make your sound, save the file with the midi, export the midi, then bounce to wav, delete the vst channel and then save to a new project file, and so on... More secure and more powerfriendly..

Cheers
C


Posted by substorm on May-19-2007 12:24:

quote:
Originally posted by mysticalninja
?

nah man wuts wrong with u i love it when that happens.

might be just me but ableton seems alittle less stable than qbase. when cubase crashes it says 'an error has occured save a back up of your project', ableton just disapears lol


Wrong, and more wrong.... It does tell you that an error has accurd, or more Windows tell me this, not Cubase or Live.... However Live creates a backupfile automaticly, which Cubase doesnt..

As i said, Live has this as a defult, not cubase... So again if i had used Live he would have had a backupfile by now.

Cheers
C


Posted by DigiNut on May-19-2007 16:52:

Actually, Substorm is right on one point - Cubase really should make a backup when it crashes. Most other commercial applications do this (MS Office for example, except for that POS MS Project), and it's actually really not that hard to do.

Yes, it is possible that whatever caused the application to crash also corrupted whatever memory contained the current project, and the backup will be garbage - but it also might not, and it's not that difficult to write an exception handler to try to perform a backup before giving up completely.

I've always maintained that Steinberg has great designers but a rather shitty development team. I know that Cubase itself is reasonably stable and it's usually the plugins that cause problems, but I've worked with other plugin-based architectures and the cardinal rule of this type of design is never trust your plugins. Cubase/Nuendo should protect itself - and certainly the user - against runaway plugins, and it doesn't. Other sequencers such as FLS or Ableton Live aren't wonderful in this respect either, but I think they make a better effort to clean up the mess.

I'm still going to use Cubase though. Ableton Live just isn't appropriate for the kind of production I do, neither is Reaper or any of the other wonderful sequencers that legions of diehard fans always insist is the most reliable/best performing/overall greatest.


Posted by wrzonance on May-19-2007 20:10:

quote:
Originally posted by DigiNut
I'm still going to use Cubase though. Ableton Live just isn't appropriate for the kind of production I do, neither is Reaper or any of the other wonderful sequencers that legions of diehard fans always insist is the most reliable/best performing/overall greatest.


I've noticed an interesting thing. No matter what the product, the person using the product with a lot success will generally swear by it, and hold it above all others.

It doesn't matter what the DAW/product is; if he/she can use it the best, they assume that it must be the best.

Once again, the argument will always end in: A DAWs, a DAW, a DAW. I agree Digi, it would be nice if Cubase was a bit more careful with how it corraled plug-ins. Instead it seems to preferr free-range plugins a bit too much, and sometimes the cows won't come home. And your farm will crash.

Wow. Enough with the pastoral metaphors. Time to make some choons.


Posted by jupiterone on May-20-2007 02:50:

I just found out it's a plugin that I've been using that was causing the problems. It just happened again, might be a corrupt installation but luckily I took the advice and saved multiple files of the same track as backups. Good deal.

So now I just gotta clean up my plugin installations and fix the problem.


Posted by thoughtlessjex on May-20-2007 03:35:

It's happened to me twice. But both times I was able to fix the corrupted file, and reverse most of the damage, so I haven't really learned my lesson yet. I just need to get a more robust hard drive (preferably on a desktop computer) that I can save back-ups to.

I also want a pony.


Posted by mysticalninja on May-20-2007 03:48:

quote:
It's happened to me twice. But both times I was able to fix the corrupted file, and reverse most of the damage, so I haven't really learned my lesson yet. I just need to get a more robust hard drive (preferably on a desktop computer) that I can save back-ups to.


all you have to back up is the project file, which should be tiny. hd space shouldnt really be an issue for backing up.


Posted by Fledz on May-20-2007 07:37:

quote:
Originally posted by DJFreaq
I've noticed an interesting thing. No matter what the product, the person using the product with a lot success will generally swear by it, and hold it above all others.

It doesn't matter what the DAW/product is; if he/she can use it the best, they assume that it must be the best.

Once again, the argument will always end in: A DAWs, a DAW, a DAW. I agree Digi, it would be nice if Cubase was a bit more careful with how it corraled plug-ins. Instead it seems to preferr free-range plugins a bit too much, and sometimes the cows won't come home. And your farm will crash.

Wow. Enough with the pastoral metaphors. Time to make some choons.


Indeed. It's all personal preference.


Pages (2): [1] 2 »

Powered by: vBulletin
Copyright © 2000-2021, Jelsoft Enterprises Ltd.