I just discovered that Cubase 14 is as horrible as Cubase 13 in some scenarios. Not always the cancellation token value is picked up. There is an easy reproduction scenario that you guys may want to checkout:
Download the official demo project by Dom Siglas (it is a Cubase 9.5 project but nevermind) There’s a simple chord track in there. Select two chords not near to each other. Double click on the first one. Have fun reproducing! (tested Cubase 14, Windows 11 latest, i9, 64G RAM)
Good question. I am not sure yet. If I feel like it I might try to take a deep dive into it. Right now I rather do something else, though. Sorry.
I could believe that it is triggered especially by highlighting many chords (let’s say you copy the chords) and I usually have color tones or bass tones different from root. I guess taht will add complexitie to the task
Here is me repdocuing it with a very simple chord progression, highlighting only 4 chords
Are you using version 14.0.32 on Windows x86 (not Windows on Arm)?
Seen this many times. On 14 Mac I have been able to eventually abort, but that wasn’t always the case. I think I mostly see it occur when trying to copy sections (verses / choruses etc) of chords - it’s very easy to double click when working quickly and there’s still a bunch of chords highlighted.
Yes, the latest version Cubase Pro 4.0.32 on Windows 10 Pro 64-bit, fully patched. Apure DAW computer I had purpose built by scan.co.uk with a 12core i9 (coffee lake)
With a Steinberg UR824 interface. I often have several plugins running and sometimes experience stability issues that I don’t know where they’re coming from, but I think this bug is reproducible on many systems. It would help me if I could disable this feature (or the double-click handler for multi-selection).
The problem is that I absolutely need to double-click a single chord in order to quickly modify / set it by banging in a new one on my MIDI keyboard (fastest workflow). I don’t want to have to think about whether I have multiple chords selected and worry about crashes, when harmonizing that#s probably one of the worst times to happen.
Thanks for the detailed feedback. Let’s see if we can raise awareness for this issue.
I bet it is triggered by multiple chords, I find based on your screenshots with D + G (no tensions) the number of 20269 possible chord progressions quite hilarious 
.
Are these like chord progressions with (e.g.) 6 different chords where these 2 chords are anywhere within the sequence (but in the given order D first, then G at some stage later)? or is it just calculating any chord progressions that could continue or contain the D-G change within? I don’t think I will ever find out because so far I only cancelled or crashed Cubase, but I would still be interested in the reasoning. I know that threaded programming is hard, but I am hoping they will eventually at least fix the “Abort” feature. Or allow us to close cubase when something is stuck so that we can save.
Usually I can rely on the backup every 12 mins, but I had the problem after creating a fresh project (in a folder), mapping out chords from a demo, but hadn’t saved the project name yet (bad habit, I know).
This is completely the same issue I met with. The first time I encountered this was back to earlier this year, with Cubase 14 Pro. And several same issues happened next with other projects. I have to consider not using the Chord track now, since it only helps me to mark or function as tips.
Same problem here. Abort button doesnt fix it.
Any news on Cubase 15?
