- I put an midi event on the Chord Track to show me the chords.
- I dragged the Chords on the Chord Track to a a different Instrument Track to edit the chords.
- The Chord ‘boxes’ are still highlighted (not all that I copied but some, see pict)
- I started playback
- I highlighted the midi event created from the Chord Track with the mouse
- I hit enter on my Computer Keyboard to open the Midi Event in the Editor.
- I did not see the Chord Track ‘boxes’ were still highlighted.
- An Info Window comes up, it says something like: searching for “chord progressions”.
- I hit the cancel box in the Info Window.
- Nothing happens, it says >100000 chord progressions found
- It is frozen now, I force close using the Task Manager.
- Lucky me I only lost 5min of work. But while I was waiting to see if Cubase would unfreeze in the search process, Cubase played my loop, over and over and over…
- My Wife comes in and says she will now divorce me, the cat started to scream, and then it started to rain…
Cubase 13.0.50, Windows 10
OK, maybe not 13, but 1-12 happened…
Hi,
Can you reproduce the freeze, or did it happen only once?
If you can reproduce it, I believe, it would be project related. Then it would be nice to get the project. And we would need the *.dmp file.
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the 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 hard disk.
-
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 behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
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 exceptions 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 a similar service, please.
I was able to reproduce it, kinda.
Just selected a Chord Track ‘box’, then selected a Midi Event.
The Message box opens up and starts to search for Chord Progressions. It stopped at some 600000+.
But after a couple of minutes the Chord Editor box opened. Unresponsive for another minute or so. Then it went back to normal.
I wasn’t playing Cubase this time, it was stopped and it reached the 600k+ faster and gave me the Chord Editor after a couple of minutes, not the looooong freeze like first time.
It won’t do this any more.
Hi,
Sorry, could you be more precise with the description?
Do you mean the Chord Event on the Chord Track (is there any Chord selected, or is it the default X?) and the MIDI Part?
How can any message kind of message appears after just selecting a MIDI Part? Did you drag and drop the Chord Event over to the MIDI Track?
Yes, the Chord Track. The ‘box’ has notes, not just an ‘X’, PLEASE SEE PICTURE.
Please see Item #6 in original post, ‘I HIT ENTER’
Hi,
When I drag and drop a Chord Event over to the MIDI Track, then just the Chord Event remains selected, not the MIDI Part. Therefore if I press Enter, the floating Chord Event editor appears, not the Key Editor.
Yes, that is the behavior I normally see as well.
Except today, as I tried to show above in my first post in the picture. I got the message box instead and it searched for ‘chord progressions’ as you can see in the picture.
First time it got stuck at some 100000, second time it went to 600000.
Hi,
As far as I can see, you are using the divided Track list. The Chord Track is in the top list, the MIDI Track is most probably in the bottom list. Where is the focus, once you press Enter? Is it in the top- or bottom list?
Focus moves to the bottom list as a select a Midi Event in the Bottom list. I hit Enter and the Chord Assistant open up. It has always done so for as long as I have had Cubase.
Hi,
Yes, I can confirm, if the Chord Event is selected in the top list and MIDI Part is selected in the bottom list, even if the focus is in the bottom list, the Chord Editor floating window appears, instead of opening the Key Editor.
This is a known and already reported issue.
But I’m not aware of a freeze.
Good to hear the first issue is already known. It is an unnecessary annoyance tbo.
As far as the Chord Assistant window process froze:
Well, it is apparently doing some library search for chord progressions. For some reason it got stuck the first time and the second time, after some time, it says it found >600000 (makes no sense). Should be pretty easy for your programmers to look at this process and see if they can understand what it was trying to do that made it freeze. Can be too hard since I screen printed the progress window that comes up in this process.
Good luck!
Hi,
Could you try the ProcDump thing to get a DMP file, please?
I was able to replicate this problem ONCE, but only once. I’m still working on the same project, haven’t closed Cubase. I won’t happen again.
