First of all sorry for not reading myself through the whole thread, so my problem may have been mentioned before.
For me Cubase 6.0 was working perfectly but the latest update 6.05 causes a crash on exit (100%). Nevertheless projects can be saved and re-opened without any problem. Also the free Alchemy player GUI won’t show up, instead just a black nothing. Therefore I decided to go back to the 6.0 version.
I have been running Cubase 6 on Windows 7 64 bit without any trouble for some time suddenly it hangs on closing 80% of the time. I have tried everything suggested in this posting and it still happens. I suspect it is since I upgraded to 6.05. I haven’t tried rolling back to 6.00.
What disappoints me is there doesn’t appear to be any response from Steinberg. Come on guys I have been a loyal user since the MIDI only days. I can’t afford to loose the time it takes me to reboot every time I change projects. We need you to acknowledge that there is a problem and to fix it.
For the record it tends to happen more frequently on the larger projects, it does it with projects using standard Cubase plug-ins only. Some times I have to close using task manager; sometime I have to reboot the whole operating system.
I am running an Intel® Core™ i5CPU 760 @280Ghz 280Ghz RAM 3.00GB
Windows professional with Service pack 1 and an M-Audio Project mix Firewire audio interface and control surface
Never had any problems like hanging on exit in Cubase 6 on Win7 eiter 64-bit nor 32-bit. I Run them both for about one year now on a dedicated i7-920 studio PC.
Just upgraded to 6.5. Still crashes on exit every time!
That’s sad news!
Since 6.05 didn’t work for me I’d appreciate, if more people on here share their experiences with the upgrade 6.5.
I have been using Cubase 6.0.0 - 6.0.5 x64 everyday for work on my W7 x64 i7 2600k system since last May. I have never seen it hang on exit, not even once.
I just upgraded to 6.5 and am still having a crash/freeze on exit. It does not happen every time, but when it happens it is annoying, since I have to force shut down Cubase (task manager) and when re-opening I will give me a ‘ASIO driver open failure’ message, so I have to reboot altogether.
I can’t believe how little response there is from Steinberg on this matter.
This thread is over a year old and Steinberg does not even seem to acknowledge the problem.
In this whole thread there are like only 3 or 4 responses from Steinberg ? Really?!?! Very disappointing in my opinion.
Indeed! Under these circumstances I’m not even sure, if I should install the “bugfix update” 6.06 (that will most probably crash my working 6.0 version, funny isn’t it?) let alone upgrading to 6.5.
my 6.5 works but I could have preferred a no synths update but to have the crash/exit issue and REAL PROBLEMS shown some more love from the developers and, maybe more so, the ones in charge. It doesn’t work that way, I know, but it would look good and felt even better.
in Germany (population app. 80 million) a survey with 2.000 test persons qualifies as representative.
Therefore a poll with more than 400 participants, of which almost 50 % claim to have a problem with the software, is something I’d call at least “significant”.
Hardly. First of all, people with no problem at all are less represented in this group since they’re more likely not to bother. Or aren’t active in the forum at all. Plus, this poll here spreads over more than a year, and 5 Cubase updates. I myself had the problem a couple of times in the beginning, but haven’t in a very long time. Not saying Steinberg shouldn’t take this seriously, but if they can’t reproduce and there is no reproduceable case it’s hard to fix, if not impossible.
I have posted several times in this thread already. Originally, the idea that running the app ‘as admin’ was a good one - b/c it seemed to work. But it only worked short term, probably related to what is coming next.
I have found something interesting. There are stretches where I will launch and close Cubase several times a day. With all this closing and opening, the sample editor raster gets screwed up. So to alleviate this, I frequently delete my defaults.xml file, and replace it with a back up. Well, I have never had a hang with a fresh defaults.xml file - and furthermore, Cubase seems to be fine for a certain amount of launches/closes after replacing the xml. I dont have a number, but it is more than just a few. After a certain amount of launches/closes, then it will all of a sudden hang. Then the next three or four times it wont, then it will. And back and forth. Until, I delete the defaults.xml file, and replace it with the back up. Then, no hangs for many launches/closes.
Maybe some of you want to try this. Start from scratch: delete your defaults.xml file, launch Cubase, let a new defaults.xml get created, and set everything to the way you like it (pref and key command files, ‘always on top’, etc). Close Cubase (all of the changes you just made need to be written to the defaults.xml file - that happens when you close Cubase) and immediately make a copy of the newly created defaults.xml file. Place that copy in another folder, and leave it there as a b/u - don’t move nor delete it. When you experience a hang, let Cubase close completely (gone from the TM), and then delete the defaults.xml file that Cubase uses (from the app data folder), and c&p the b/u. And see if you experience any hangs over the next several launches/closes. If it takes a while to experience a hang, this is a step in the right direction. If that’s the case, when you finally do experience a hang - repeat the process: delete the defaults.xml file from the app data folder, and c&p the b/u again. And see if you experience any hangs over the next several launches/closes.
I’d be interested to see anyone’s findings.
Just upgradet to 6.5. Now every time I close the app I get a runtime error.
Well, I’d say, if a Steinberg production manager calls up here asking for information regarding trouble with 3rd party plug-ins, that suggests that they already have an idea about possible error sources.
All I’m saying is that a significant amount of people (once again it’s a sample that obviously shows a trend, at least for the “universe” called Steinberg forum) have a significant problem with one crucial feature of the software, that is to say closing the programme, getting an error message and eventually losing data, on its creation people may have wasted an awful lot of time and passion!
Just an official statement would be a nice gesture.
Having an idea is not exactly a reproduceable case, and ofcourse they know in which direction to look, as Chris Beuermann already wrote about earlier in this thread: http://www.steinberg.net/forum/viewtopic.php?f=19&t=3291&start=200#p91208
You can’t know whether it is significant or not, even for the forum, and you certainly can’t say there is ‘obviously’ a trend. Again: 5 Cubase versions and more than a year.
still hanging on exit here for nearly 1 minute every time
No amount of arguing is going to deny the fact that the crash/freeze on exit is an issue for some users. If it isn’t for you, that’s good on you, but for many others - myself included - it is an issue. It is not just one or two users who are experiencing it, but many more. And I do think Steinberg should show more response in the matter, at least acknowledge the possibility of this being a bug and show that they are looking into it and working towards a solution. From the very few responses Steinberg has offered in this thread, it has not become obvious to me that they acknowledge the possibility of a bug leave alone that they are looking into it or working towards a solution.
You’re right on the mark, dude!