| Author |
 Topic 
|
one man bland
Location: Canada
Posts: 2
|
 Posted - Sun Mar 02, 2003 12:23 pm
|
|
|
is this a problem anyone is aware of? i tried scouring the forums here for any hint of what i'm mentioning, but came up with nothing. basically, i've been recording and piecing together songs here at home using cool edit for years, and i've never had this problem.
i have a session file that will open, but forces cool edit to close basically as soon as i try to do anything with it. this is only happening with this one specific session, and i have no problems when editing any others.
there aren't a lot of tracks really, basically only two guitars, and a few tracks of drums that are looped.
this is driving me nuts, as every time i try to open this session, it just crashes the program alltogether. i've tried reinstalling the program (ver. 2.0 btw), resaving the session on a different drive, renaming the wavs, moving the files, you name it.. nothing is working.
please, any help is much appreciated.
|
|
jonrose
Location: USA
Posts: 2901
|
|
Posted - Sun Mar 02, 2003 1:25 pm
|
|
|
I think I can safely conclude that the session file is corrupted.
This will not be an easy fix, depending on what modifications you've already done to it, but here is one thing that will solve this.
If you can open the session, grab a pencil and try noting all your tweaks (if any), and write down the actual start-times of all your waveblocks (that is, if they're not all sitting at 0:00.000), then close the session.
If you're feeling the need to be safe, then by all means, reboot.
:)
Now open an empty CEP session. Right click / Insert your wave blocks (your audio files) in their respective tracks (or you can find and insert them using the organizer window).
Obviously, if you've done a lot of tweaking work within the corrupted session, you will have some work ahead of you to recreate all of that, but at least the new session file will be clean, with just your base audio files inserted.
Now save your new session file with a new filename (Save As...).
Good luck!
Best... -Jon
_________________
 |
|
|
|
jonrose
Location: USA
Posts: 2901
|
|
Posted - Sun Mar 02, 2003 1:38 pm
|
|
|
P.S.
If you suspect a particular function of causing the crash, try saving your work in a series of .ses (session) files, with slightly different file names. Session files are small and contain only data about the session, so size isn't an issue. Then if you run into a problem or corruption, you can step back one file and at least get back to where you were the day before.
(Saving different sessions is also a good way to easily save alternate mixes for client-review!)
-J
_________________
|
|
|
|
Minor
Posts: 69
|
|
Posted - Sun Mar 02, 2003 8:50 pm
|
|
|
yeah it could be just a little idiosyncracy of the program, today i was recording my band and stuff, and i'd delete a track and hit stop afterwards and it would crash every time. it took me about 2 minutes to realize it always exploded after i hit stop, so yeah. i dunno if that was a help or not....
_________________
AFI's Sing The Sorrow: In music stores everywhere! Check it out! |
|
|
|
one man bland
Location: Canada
Posts: 2
|
|
Posted - Mon Mar 03, 2003 3:16 pm
|
|
|
|
i ended up just biting the bullet and rearranging all the wav files in a new session. it's a shame i did so much cutting up and rearranging originally, because otherwise it wouldn't have taken so damn long, and i would have just done it that way from the start. i haven't had any problems with the new session so far, so it looks ok i guess. thanks for the help guys
|
|
| |
Topic
|
All Forums
forced close in xp