| Author
|
Another Cubase problem
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 21, 2007 09:11
|
Hey guys, my Cubase SX 3 has been
acting up again, and this time the
problem is a really annoying one.
My recent project has reached about
5 minutes in length with a lot of
VSTs running...
when I try to save it gives me an error
saying
"the project is corrupt or needs too
much memory"
Im running on Windows XP with 2gb ram
and a dual core proccesor, I dont think
this should happpen, that and it never
lags while playing, and my CPU is only
working at 50% (so it sais).
Is there a way around this? |
|
|
shachar
Basic
Started Topics :
13
Posts :
402
Posted : Aug 21, 2007 10:47
|
had this before..altough the cpu reach only 50% it says the project needs too much memory...
didnt figure it out myself either.. try to copy the track into new folder and make backups |
|
|
|
Ghost Host
IsraTrance Junior Member
Started Topics :
27
Posts :
512
Posted : Aug 21, 2007 13:39
|
|
another solution: kill NI Kontakt or some VST's that using too much RAM
|
|
|
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 21, 2007 18:32
|
Would buying another gig of ram help? I wouldnt like to spend 80 dollars on something that could be fixed with just a patch or maybe fiddling with some options...
is there anyone here that has had this problem and has known how to solve it? :s
|
|
|
|
Ghost Host
IsraTrance Junior Member
Started Topics :
27
Posts :
512
Posted : Aug 21, 2007 19:01
|
sure thing more ram u got better perfomance would be, but win xp will see only 2.1-2.8GB from your 3GB as win xp is limited 
..once again back to the topic: get rid of hungry ram VST's like samplers, if u use NI Kontakt or Battery this can be solution (just bounce it to the wave)
|
|
|
|
Auralviolence
Started Topics :
0
Posts :
58
Posted : Aug 21, 2007 19:12
|
|
I don't think that this happens because of RAM. At first: make sure that you have last SX3 version installed (!!!), cause this bug is known with some of the first SX3 versions. Try to "save as" your project with all audiofiles and all included with the different name in different folder (better to another partition if possible), and try open this new project and work with it. |
|
|
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 21, 2007 19:32
|
Thanks for the posts guys, ill try both things just to make sure this doesnt happen again...
wi']['ch, I cant completely get rid of Battery as I am in love with it lol. Actually its because all of my percs are done with it, so when you say "bounce it to wave" what exactly do you mean? Turning it into audio instead of Midi?
As for Auralviolences post, I was considering saving in a dif. folder, so when I do this will it just be this simple? Or do I have to put other things I have used in this folder? For example, my VSTs are in Steinbergs VST folder and my samples are in my music folder...
Sorry if I made you guys read this much, its just that I want to do things right 
Thanks again!
|
|
|
|
mubali
Mubali
Started Topics :
71
Posts :
2219
Posted : Aug 21, 2007 20:23
|
I've had this same issue in Cubase a few times. I make it a point to save as in a new version, and the only time I get issues is when I do something I know I probably shouldn't have done, like removing a selected channel that was full of plugins, or trying to do a pitch shift on a chunk of audio I'm listening to at the same time.... I have far less ram than you guys do, and it's either the sampler (Kontakt) or it's my ram... but I used to do audio kick, but now I went back to using a sampler because sometimes a kick isn't gonna work like you thought when you first started the track, and I'd rather change it in the sampler than to have to redo all the audio... Currently it isn't that big of an issue because I always save new versions of the track each time I save, and it only really glitches when I knew that I shouldn't have tried that trick while it was playing...
 An Eagle may soar, but Weasels don't get sucked into jet engines. |
|
|
|
Ghost Host
IsraTrance Junior Member
Started Topics :
27
Posts :
512
Posted : Aug 21, 2007 21:16
|
Quote:
|
On 2007-08-21 19:32, l!l wrote:
so when you say "bounce it to wave" what exactly do you mean? Turning it into audio instead of Midi?
|
|
exactly ...saves CPU resurces too 
|
|
|
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 21, 2007 22:39
|
Tried the new folder thing, no luck, it starts to save it fine, but near the end it chokes up and gives me the same error.
As for the midi to audio trick with my Batteries, ill guess ill use that for now, since I just went to the computer store and told me that my computer had no more space for 3gb (since I was already using 2 slots for two sticks of 1 gb ram)BUT I went ahead and ordered 2 new sticks of 2gb ram, so ill have 4gb of ram total. so if that doesnt work I dont know what will lol
Still, if theres anyone with more tips on how I might be able to fix this, please post! I might be able to save some money hehe
Thanks to all whove helped |
|
|
|
Auralviolence
Started Topics :
0
Posts :
58
Posted : Aug 22, 2007 00:05
|
I'm sure on 100% that it's not RAM issue.
What version of Cubase SX is installed ? Does it 3.1.1.944 or lower ?
Do you use big samplers/romplers like spectrasonics software ? Many people have this trouble due to some of this big VSTi, I don't remeber what sure, I don't use this type VSTi's.
What VSTi's are in the project ? Try to remove suspicious VSTi's from rack and save your project without it.
If nothing helps - export your project to MIDI-file, export mixer settings, VSTi presets, and then create the new project))) And check for new versions of VSTi's that you use. I understand, that it very radical method, but there is a possibility that your project file *.cpr becomes corrupt - that is the main reason, why I advised to do "full save as" of your project to different folder. |
|
|
|
Auralviolence
Started Topics :
0
Posts :
58
Posted : Aug 22, 2007 00:08
|
Quote:
|
Or do I have to put other things I have used in this folder? For example, my VSTs are in Steinbergs VST folder and my samples are in my music folder |
|
No, you should not move the VSTPlugins folder. |
|
|
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 22, 2007 06:39
|
|
Thanks man, ill give this a try for sure! |
|
|
|
l!l
IsraTrance Junior Member
Started Topics :
17
Posts :
48
Posted : Aug 23, 2007 00:41
|
Still no luck. Im using the v3.1.1.944 version of Cubase SX3. The one by H20. I dont know if this is the one which has this bug.
Anyone? |
|
|
|
Auralviolence
Started Topics :
0
Posts :
58
Posted : Aug 23, 2007 01:19
|
Install last Nuendo 3.2.0.1128 and try to open your project there. If still no luck:
Read this topic, and try to do the similar things with VST used in your project:
http://forum.isratrance.com/viewtopic.php/topic/113787/forum/2
If not too:
Quote:
|
On 2007-08-22 00:05, Auralviolence wrote:
If nothing helps - export your project to MIDI-file, export mixer settings, VSTi presets, and then create the new project))) And check for new versions of VSTi's that you use. |
|
Or remove the vstplugins folder temporarily and "save as" project without it (it's easier than exporting MIDI-file, of course if it saves in your case).
Because it means that your project file becomes corrupt, and nothing will help. And it will be faster than trying to find other solutions, because no more solutions if *.cpr is corrupt:) Next time save some *.cpr/*.npr copies during your work on projects.
|
|
|
|
