TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- Cubase crashing

Cubase crashing

Cubase users... do you find it crashes at all? I used SX3 (non legit) and got tired of it crashing; so I bought Cubase 4, and it has been even worse!

I've updated to the latest version, but it still shits itself constantly. I'm using the same plugins etc. as I was using in FL, which never crashed on me once in the last 3 years.

Do any of you guys find it to be temperamental like this? Or is it just me?! Ive had 3 different computers, and Cubase has been like this on all three. I'm a computer technician too, so its not like I'm doing something stupidly wrong.

Cubase 3.1 has never ever crashed on me once (or well.. almost), and ive been using it for years..

What kind of crash is it?

I have two problems:

1. Sometimes when I close cubase, I get an error screen pop up. However, if I close the project first, THEN quit Cubase, no problems!

2. Open pool, go to import a wav, try to preview the wav... NO SOUND. This happens to me with the play button in the pool window too. It doesn't ALWAYS happen, but at least 60-70% of the time.

I do have 2 cracked plugins... However I never had any problems with them in FL!

quote:

Originally posted by echosystm I have two problems: 1. Sometimes when I close cubase, I get an error screen pop up. However, if I close the project first, THEN quit Cubase, no problems! 2. Open pool, go to import a wav, try to preview the wav... NO SOUND. This happens to me with the play button in the pool window too. It doesn't ALWAYS happen, but at least 60-70% of the time. I do have 2 cracked plugins... However I never had any problems with them in FL!

I also have the preview error bug, but when i import samples.. it wont preview.. i dont use preview in pool, but i think its the same thing. and it always happens if i change the ASIO driver in a project or something. So whenever i change it, i have to load up Cubase again.

I have also experienced some problems in the past with closing the whole thing.. so i always save, close the project and then close Cubase.

So only tip i can give u on the preview thingy is to switch to the right ASIO driver, close Cubase and reopen it, however its very strange its behaving like this one 3 different computers.

Looks to me like there is a plugin interfering with Cubase, i only use a small amount of plugins.. like vanguard, ravity, trilogy, atmosphere and omhboyz delay thats about it (expect for a couple of small ones) and i never crash.

quote:

2. Open pool, go to import a wav, try to preview the wav... NO SOUND. This happens to me with the play button in the pool window too. It doesn't ALWAYS happen, but at least 60-70% of the time.

That happens if for some reason when your asio driver resets itself, and what you need to do is hit f4 and make sure your setting in VST connection are the same as last time. The thing to do is save your main settings under some name, and if you're running a problem like this all you have to do is pull down the correct preset. I have my as STUDIO 2007, and if my asio driver is reset, I just pull that down and everything is how it should be.


And Subtle - always close cubase project first, well save it, than close it, and after that close Cubase. The problem with the error is ussually generated by some of the plugins / vsti intruments that don't like cubase being closed before them. It generates memory errors.. It dosn't screw your project or anything like that. But I suggest you close the program properly, this probably will avoid more serious problem.

I can't really say my sx crashes, It's running really stable at all times. The only time it did when i loaded up some freeware plug to try and for some reason it crashed. I than deleted the plugin, and the problem was gone..

quote:

Originally posted by DJDIRTY And Subtle - always close cubase project first, well save it, than close it, and after that close Cubase.

Thats what i do

Cool to know about that ASIO thingy, im going save a setting there, immedietly.. its very annoying when preview is gone. cheers

cubase crashes all the time, its a joke of a sequencer, you should get ableton live, echosystm.

quote:

Originally posted by asdfg cubase crashes all the time, its a joke of a sequencer, you should get ableton live, echosystm.

Ableton uses 150mb of RAM when its idle with nothing loaded. It's even more of a joke.

If I were to leave Cubase... it would be for Reaper, nothing else. Anyway, those solutions listed above fixed my probs! Thanks guys! :P

quote:

Originally posted by asdfg cubase crashes all the time, its a joke of a sequencer, you should get ableton live, echosystm.

Troll-tard-alert!


Anyway. Glad you got it working echo.

Hi Echo,

Been using C4 for a while with not one crash. I'm using PC with dual core and 2 GB ram. I also use the Virus TI as my S/C. Also using 2xuad-1 cards and POCO.

I know there is a few bugs still in it so I hope these get sorted on the next update.

IMHO it's stable for me.

quote:

Originally posted by echosystm I have two problems: 1. Sometimes when I close cubase, I get an error screen pop up. However, if I close the project first, THEN quit Cubase, no problems! 2. Open pool, go to import a wav, try to preview the wav... NO SOUND. This happens to me with the play button in the pool window too. It doesn't ALWAYS happen, but at least 60-70% of the time.

I've had these problems on occasion (SX 3, I won't touch 4). I believe that both of them are actually related to flaky ASIO drivers.

It used to be that when I closed Cubase it would shoot up to 100% CPU, not good when the program sets its process priority to High. At the time it was a single-core machine so I couldn't even open the task manager to kill it. However, that only happened with my E-MU card, it's never happened since I switched over to the MOTU interface. And I guess it wouldn't really matter now that I'm on a dual-core machine.

You should know that the previewing from the file browser or the pool uses the "audition" track (usually hidden) for its sounds. If you don't hear anything out of your previews, check that audition track and see where it's routed. Again, when I was on my E-MU, this happened frequently and it was because Audition was routed to a different ASIO strip and that strip would just die. Never happened on my current rig.

The crash-on-exit thing is definitely a Cubase bug, bad drivers or not. Cubase IS buggy as hell, in general. The preview issue though, I think that particular one is not Steinberg's fault. Doesn't happen in Fruityloops because there is no audition track.

quote:

Originally posted by DigiNut I've had these problems on occasion (SX 3, I won't touch 4). I believe that both of them are actually related to flaky ASIO drivers. It used to be that when I closed Cubase it would shoot up to 100% CPU, not good when the program sets its process priority to High. At the time it was a single-core machine so I couldn't even open the task manager to kill it. However, that only happened with my E-MU card, it's never happened since I switched over to the MOTU interface. And I guess it wouldn't really matter now that I'm on a dual-core machine. You should know that the previewing from the file browser or the pool uses the "audition" track (usually hidden) for its sounds. If you don't hear anything out of your previews, check that audition track and see where it's routed. Again, when I was on my E-MU, this happened frequently and it was because Audition was routed to a different ASIO strip and that strip would just die. Never happened on my current rig. The crash-on-exit thing is definitely a Cubase bug, bad drivers or not. Cubase IS buggy as hell, in general. The preview issue though, I think that particular one is not Steinberg's fault. Doesn't happen in Fruityloops because there is no audition track.

I'm using an Audiophile 24/96 at the moment. Aren't they pretty much the most stable drivers ever? C4 doesn't seem to have an audition track, it just mutes all channels and goes through the master and bypasses the fx... I think.

I'm confident the exit error was as DJDirty said, and the plugins were causing memory errors. The errors I get ARE memory errors, and they don't happen when I quit the way he said. But yeah, it probably is a bug, I should be able to quit normally

Almost every fatal program error involves reading or writing the wrong memory. There are many different mistakes that can lead to that, but the fact that it's a "memory" error doesn't necessarily tell you anything. It could certainly be a plug-in problem though, wouldn't surprise me one bit.

You're describing the same problem I had, where it wouldn't happen if I closed the project first. Sounds like in my case it was an infinite loop, whereas in yours it was an invalid memory access. I guess it stands to reason that two different plugins could have caused similar but subtly different problems. Hard to say whether it's truly a plug-in doing this, or if it's Cubase not handling an unexpected condition caused by a plug-in.

I thought M-Audio had a pretty bad reputation driver-wise, but maybe that was just a few cranky customers. The most stable drivers are probably the Pro Tools drivers though.

quote:

Originally posted by DigiNut I thought M-Audio had a pretty bad reputation driver-wise

Oh they do... !

Anything firewire or USB, you might as well pre-emptively book yourself into an asylum. The delta series has been around since the dawn of time though, and are supposed to be really stable.

quote:

Originally posted by echosystm Oh they do... ! Anything firewire or USB, you might as well pre-emptively book yourself into an asylum. The delta series has been around since the dawn of time though, and are supposed to be really stable.

I used an Audiophile 24/96 for years; never gave me any grief, only got rid of it when I upgraded to the MotU.

A friend now has the Audiophile; never got any complaints from him about it either.

quote:

Originally posted by Rusty O'Hara I used an Audiophile 24/96 for years; never gave me any grief, only got rid of it when I upgraded to the MotU. A friend now has the Audiophile; never got any complaints from him about it either.

Same here, works MUCH better than my terratec 6 fire I used to have.
I'm having this error too if I don't close the file first . Sometimes I just forget. Anyway, nothing too serious and autosaving is 10 minutes but I only needed that once since I bought the upgrade.

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