|
I feel like crying.... (pg. 2)
|
View this Thread in Original format
| mysticalninja |
| one of my tracks wouldnt open anymore in cubase SX2 once it got too complex. i upgraded to SX3 and it opens fine. |
|
|
| TVG |
| Yeah, I have SX2. Maybe I'll try and get someone with SX3 to open it and re-save it. |
|
|
| mysticalninja |
| i'd do it for you but i dont think that will help. SX3 opens files different, it loads everything for a minuete before opening the file instead of trying to do it all at once. if you want you can IM me, my aim is EEIIXXXXX ... i have a different file that ill send you that should fix it :o |
|
|
| Reactance |
We all learn from this !!
***** ALWAYS MAKE A BACK UP COPY OF UR TRACK ******
:) |
|
|
| nhibberd |
| I had similar problems a while back. But now that I have an audio PC I have absolutely no problems. I think a lot of problems occur becouse XP has so much bull running in the background that takes up half your memory and CPU. |
|
|
| Chronosis |
| quote: | Originally posted by nhibberd
But now that I have an audio PC |
What's that? |
|
|
| dj jasonF |
^^
dedicated pc for audio applications
| quote: | Originally posted by TVG
I read somewhere that it was a known bug in Cubase when the track had over a certain amount of memory used. This track did have a lot of stuff. Could be the same for FL I donno. |
or maybe its just compability problems or bad plugins. it happened when i had 200-300 plugins and used alot of different ones in the same project. in fl that is, but my guess is that it can happen in all programs |
|
|
| DigiNut |
Look guys-
It's got nothing to do with the operating system.
It's got nothing to do with background processes.
It's got nothing to do with the sequencer version.
It's got nothing to do with the project complexity.
The only thing I've noticed about Cubase is that if you're using an assload of memory (we're talking more than a gigabyte here), it WILL sometimes crash WHILE saving. The resulting file will be 0 bytes and completely unusable, and if you saved it over your original project file, that original is gone.
However, memory is just one thing that can cause a crash. VST and DX compatibility issues are probably the #1 reason for crashes.
Regardless, happens. I'm sure we've all at one point had MS Word crash on us while writing a long essay. Every non-trivial program is going to crash and burn at some point, and unfortunately it may sometimes be before you've saved or even WHILE you are saving. Even if it doesn't crash, what if the power goes out or your CPU spontaneously combusts? All you can do is try to minimize the chances of data loss: save early, save often, and save multiple versions. It's just good practice to do this even if you never have a crash (what if you messed something up without realizing it and need to see what something was like 3 days ago?)
|
|
|
| Reactance |
Also a possibility that we all overlooked:
Is the pc running an illegal copy of cubase sx? If yes then asked your self is the machine connected to the internet Yes | NO
If your answer is No then your solution to your problem is mentioned above, if no then the possibilities are endless.Cubase sx may and I speak under correction may be communicating with the server online ever think of that and just think what they can do ? Im a software developer I know these things are very much possible and happening people don’t tell the end user everything.
Don’t over look what I mentioned I think in my experience its better to have ur machine off from the internet keeps u safer!
Anyway that my 2 cents
;) |
|
|
| ichabod |
I have had exactly this problem loads of times. It seem to happen when a track gets to a certain level of complexity?!? (or could it be realted to a plugin?) Anyway, I found a workaround... try it out and see if it works for you too:
Open Cubase thenbeofre opening your track,open another older track that doesn't cause the crash. Now leave this one open then open the the problem track. You can then close the first track. This works 90% of the time for me... |
|
|
| mysticalninja |
| quote: | Originally posted by Reactance
Also a possibility that we all overlooked:
Is the pc running an illegal copy of cubase sx? If yes then asked your self is the machine connected to the internet Yes | NO
If your answer is No then your solution to your problem is mentioned above, if no then the possibilities are endless.
Cubase sx may and I speak under correction may be communicating with the server online ever think of that and just think what they can do ? Im a software developer I know these things are very much possible and happening people don’t tell the end user everything.
Don’t over look what I mentioned I think in my experience its better to have ur machine off from the internet keeps u safer!
Anyway that my 2 cents
;) |
You are stupid.
Not a possibility. |
|
|
| Reactance |
mysticalninja
Are what i call a lamer,
Defined as a person who steals software and dont understand a thing of the underling area of it.U ARE THE FOOL |
|
|
|
|
