Okey, I ve tried a slightly different command on my previous macro and it seems to be working.
Instead of "DELETE MUTED TRACKS ", I’ve used “DISABLE ALL MUTED TRACKS”.
I am giving the whole procedure again:
FIRST SAVE YOUR PROJECT!!!
Then go on EDIT tab, select KEY COMMANDS
select SHOW MACROS, select NEW, name it and select it
Add the following commands to your created macro:
CHANNEL & TRACK VISIBILITY - AGENTS: SHOW ALL CHANNELS/TRACKS
EDIT - SELECT ALL ON TRACKS
PROCESS PROJECT LOGICAL EDITOR - MUTE TRACKS OF SELECTED EVENTS OR PARTS
PROCESS PROJECT LOGICAL EDITOR - DISABLE ALL MUTED TRACKS
FILE - QUIT
C12 will then prompt you to save your project select NO and that’s it.
At least a few times I have seen that the EuCon is shown in the dialog that cause the spinning ball. On this cases I dont think I have seen it break any settings but it suggest that I use backup copy even if I started the exit with a save.
Sorry but I read the post from Mr. Matthias_Quellmann on this thread and I quote:
Of course, this is not a direct vote on the Cubase development backlog. There are a lot of factors that influence the decision what improvements the next Cubase version will introduce. But ideas or suggestions that are discussed and supported widely by the community, will definitely be considered by the team.
The actual voting mechanism in the forum is close to useless - so it doesn’t really get used to track the popularity of anything. Each person gets 4 votes total and when you’ve used your 4 you can’t vote on anything else unless you remove a vote from something else and reuse that vote.
I can’t even imagine what a limited voting scheme like that might be useful for.
Voting for bugs that is crash types is silly. It should be fixed ASAP. Voting for new features is a good idea. And having a limitation make the need for thinking about priority. Otherwise there will be people that vote for everything.
I kind agree but…
A version or two crashing because of 3rd party vsts let’s say it’s acceptable up to some point.
All versions since v.7 crashing on exit is something different.
I don’t even use the same vst’s as I did on v.7. Not a single one.
Not even the same windows version and bits, and upgraded all to vst3 also since v.11
But the problem remains no matter what.
I 've said it before but fwiw my Protools and Sequoia are not crashing with the same plugins…
I don’t want to spend time/energy finding what the problematic vst’s are and troubleshoot by removing each one,etc, and then find replacement vst’s for those. and lose the money spent and spend again for new ones which might have the same issue etc, etc.
I want an error free vst host to use the vsts that I like working with.
Vst protocol was released by steinberg and should have been the leader in hosting vst’s error free.
As mentioned in another thread Bitwig Studio i.e. found a way to do it with its plugin sandboxing solution.
If a plugin crashes, only that plugin crashes and shows a Reload button in place of the plugin window.
Sorry for long post and waving the flag but it’s kind of frustrating dealing again and again in everyday basis with the same old issues after all these years.
I am with Cubase since VST 3.5 version and I always looked the other way for major issues it may had because truth is that is a powerful tool that makes modern producing a lot easier and always the pros are massively a lot more than the cons.
But for me issues like this one, or the drops of the audio engine when adding channels/vsts etc in 2022 are unacceptable.
yes - Cubase 11.4, v11.41, v12.0, and v12.10 - when I work on the project no problems - when I shut it down it crashes Cubase every time without a crash dump - and when I restart Cubase I get the options to choose safe startup
Generate a DMP file and share it via Dropbox or similar service, please.
Use Microsoft ProcDump utility to generate a DMP file, please.
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your harddisk.
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder.
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behavior (see next step).
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exeptions and the option -t terminations of the application.
Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or similar service, please.
