So, you installed only cubase…and the one plug in that occasionally CRASHES mine on exit? I think you have your cuplrit. I never had a problem with Win7x64/c4.52/play2.
I have had issues with the 64bit Play3 in C6–but, that it…it’s the 64bit. That might be why it only occasionally crashes it–I don’t use the 64bit c6 much…and don’t use Play Everytime I use that…
Is anyone having this issue on either platform with the 32bit version of cubase?
i can confirm exatly what you have said “Z” now i have removed the five files (64 bit) i have no more close down error messages and no hanging what so ever , this has certainly cured my problem .
If i may add that if you wish to control those five files that are deleted al youy have to do is open the automap server and tick them to be automaped and you will still get a perfect shut down …
GREAT WORK “z” you’ve made my day … many thnks dude
I have also had the shutdown error many times with only three instances of 64-bit PLAY 3.X in operation. After reading the Steinberg response to this on their website I decided to turn off all my MIDI devices following closure of the Cubase file. I no longer have the shut-down issues and determined it was my Alesis MIDI controller in combination with PLAY that is the issue.
Given PLAY 4.X is just around the corner, maybe we can hope for VST3 (or even 3.5) compatibility, less memory demands and no crashing issues.
SOLVED! I originally had removed all Automap files on my C:drive (including the registry), but no dice. In a last ditch effort I manually searched again and found 1 automap file that never showed up in the search…because it was had a parenthesis around it like this: (Automap). Evidently the parenthesis stopped the windows search from spotting it…which must be a Windows 7 bug or something. All is well now!
I still find it strange that the first version of Cubase 6 had no problems originally with this, but it was only the first C6 update and everything since that did not like the (Automap) file.
I have the same issue, currently running Cubase 6.5.4 and get the Cubase Crash message from Windows 7.
I’m using a Novation Zero SL MKII , latest Automap version, I think it’s 4.5 . I will try to search for the (Automap) file you mentioned, and delete it, see what happens.
Oh… Have you tried to quit Automap before quitting Cubase 6.5 ? did that help ? I will try this and provide some feedback when I get a chance.
I have the exact same issue with the error message when exiting Cubase. It did not do this until I updated to 6.5.4, it shows up everytime. I uninstalled AutoMap, got rid of VSTs (Automap), etc. etc., as others have suggested. Still no luck. I think this is a bug related to the update and for those that may be using particular controllers. Nevertheless, the update is the catalyst for the problem.
No. The problem affects the updated version of Cubase. A catalyst is what affects some other process. In this case the process is affecting Cubase 6.x.x. Anyway that statement will probably not encourage a (Steinberg) programmer to do anything about it.
Whenever anything shuts down a computer or a program is usually a driver issue. Graphics or Audio I/F in this case.
Can you find an error log to post?
The Issue of the error message when quitting Cubase 6.5.4 on my system seems to have been caused by the Novation Automap application.
I deleted all automap related files, they usually attach to VSTs ,and other components in brackets, in the form of (Automap). I also uninstalled the Automap app. and decided to get rid of the Novation SL MKII desktop controller from my setup. All works fine now, no more error messages when quitting Cubase 6.5.4
I wish Steinberg would offer a new pro-quality control surface for Cubendo in the near future. I currently use my YAMAHA Motif XF7 keyboard, as a control surface for Cubase 6.5.4 (Motif XF faders, transport, jog-wheel, …etc. ) works great !
Well, as for me, I didn’t have the shut-down error in the first version of Cubase 6.5, but ever since I have updated to 6.54 (which I take it was supposed to FIX bugs, not create any), I too have the shutdown bug.
I.e., as soon as I try to shot down Cubase, Windoze informs me that the program cannot be shut down due to an error, and asks me if I want to force the shutdown (I’m on Win7, 64 bit version).
I take it from your post that Novation’s automap feature creates the conflict. Does this mean the choice is between using automap and suffering the shutdown error, or NOT using automap?
It is exactly the same with me -I also use Novation’s automap (as well as East-West’s ‘Play’ , which some have suggested might be the source of the conflict), but there was no problem until I updated to 6.54. It follows logically from this that it is not the plug-ins that are the source of the shutdown error, but the update to 6.54. Still, I will also try the suggestions that have been made regarding deletion of automap dll’s and subsequent reinstallation to see if that helps. Given your experience I fear that it won’t.
It follows logically from this that it is not the plug-ins that are the source of the shutdown error, but the update to 6.54
It also follows logically, computers being what they are, that chances are that after any given update some systems will experience crashes. If it happened to many thousands then what you say would be logical but as it’s just happening to a very few nobody can take that as a fact written in stone.
Try defragging your computer first. Basic system maintenance can heal many “problems”.
I see from that signature that you deduce from observed patterns. Don’t. We are hard wired to see patterns like faces in clouds, world takeover plots etc so try not to read too much into patterns.
Just because you are hit by a coconut while asleep under a coconut tree with a monkey perched on top doesn’t mean that the monkey threw it. (Professor Whatsisname)
Even I got same problem after my 6.5.4 update. But after deleting the automap dlls and deleting the data folder of the cubase and start cubase, everything set right.
I had this issue only with 64bit version of cubase and not cubase 32bit version.
Well I don’t have Automap and it’s still happening here. I’ve renamed my plugins folder to Vstplugins.old and it’s still doing it so can’t really blame an old plug in this time! Running Cubase 6.54 in Windows 7 64 bit ny the way. If this were hardware it would probably be considered not fit for purpose, It’s also doing the same in my dual boot installation of Windows 8 pro (32bit) (I’ve gone from a new clean installation of W7 (32bit) to W8 pro (32 bit) within a week). Sort it out Steinberg! This is not some cheap bit of software! Unacceptable!
What is the Steinberg tech support e-mail address?
I, too, get the same application crash box upon exit from the latest update of Cubase 6 when using Novation Automap. You’re telling me, Steinberg, that I have to stop using a program that worked flawlessly with your previous version of Cubase 6 because you can’t round up your software guys into a room and announce this known issue and have them write a fix for it? Unfreakin-believable. This issues has been going on since August and it’s still not fixed. You deflected and put the ball in Novation’s court to fix it? Their software worked perfectly with yours until your update. Now they want us to buy Version 7. Seriously, this is beyond unacceptable Steinberg. We pay top dollar for your product and you let a known bug/error like this continue on for several months without an update to fix this glitch? I see only one reply from any rep from Steinberg in this thread. This is a golden opportunity for you to step up to the plate and provide a quick-fix update in the form of a download for those who have invested in your products.
Btw, this is not a PLAY issue; I use their libraries extensively with no problem and when EastWest has a confirmed glitch in their stuff, they promptly provide a downloadable fix. This is not a Novation issue; their Automap program worked fine with earlier versions of Cubase 6 for months and months. This is not a Mac issue. Not a Windows issue. This is a Steinberg issue that has cropped up since the update this summer and has now gone on too long.
I too have same problem with cubase 6.5.4 and automap on mac osx ,i have tried every thing to resolve this issue, lets hope steinberg deal with this soon.
(Professor Whatsisname)
