# Endless wait cursor when accidently double clicking two chord selection **URL:** \ **Category:** Cubase\ **Tags:** cubase-9, issue, cubase-15\ **Created:** [August 23, 2018, 10:08am UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076 "2018-08-23T10:08:41Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [August 23, 2018, 10:08am UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/1 "2018-08-23T10:08:41Z")
I had two chords from the chord track in “selected” mode, they had some 11 (unselected) chords in between them. I accidently double clicked on the first one. Mr. Theory from Cubase apparently tries to calculate all the possible chord progressions. (will it end?). I had a substantial amount of work done without saving the project (…) So I can only hope Cubase finishes at some point in time. Please add a time out timer or limit the amount of suggestions. One of minute calculations will be more than enough on a I5 or whatever machine. ---
**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\ **Post date:** [August 23, 2018, 7:28pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/2 "2018-08-23T19:28:07Z")
Hi, In this case probably limited count of results would be more useful, then a time. ---
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [August 25, 2018, 9:12am UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/3 "2018-08-25T09:12:45Z")
Well, It depends how long it will take to come up with the limited count of suggestions of course ---
**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\ **Post date:** [August 27, 2018, 9:28am UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/4 "2018-08-27T09:28:30Z")
Hi, I just tried on my system. The Chord Assistant appears immediately. Could you share your setup screenshot of the window, please? ---
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [September 12, 2018, 8:06pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/5 "2018-09-12T20:06:29Z")
Thx for thinking this over with me, apparently the project needs some complexity to encounter the issue. I can not reproduce it in a quick lab project either. That said I’ve made a movie that shows the thing with ease: [http://www.hamicast.nl/hans/cubase/hang\_due\_to\_chords.mp4](http://www.hamicast.nl/hans/cubase/hang_due_to_chords.mp4) Cubase 9.5, Windows 10 1803 fully patched, x64 ---
**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\ **Post date:** [September 13, 2018, 9:40am UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/6 "2018-09-13T09:40:45Z")
Hi, Thank you for the video. I build exactly the same chord progression, and now I can reproduce it. If I select just the X and C over one bar, it takes some seconds to open the Chord Editor. But if I do it over 2 bars, it already hangs. Reported to Steinberg (CAN-17821). ---
**Author:** ![EX1MUS](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ex1mus/32/176692_2.png) [@EX1MUS](https://forums.steinberg.net/u/EX1MUS)\ **Post date:** [July 27, 2025, 4:29pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/7 "2025-07-27T16:29:06Z")
Please address this behavior, Steinberg! It’s a major creative “flow” blocker! Selecting a bunch of chords, and then accidentally double-clicking results in Cubase generating thousands of chord progressions. If I Abort, Cubase becomes unresponsive, I have to Force Quit Cubase, and start again, losing my work! FIX: Chord generation should not be triggered until an approval “are you sure…?” dialog is clicked after accidentally double-clicking on chord progressions. ![Screenshot 2025-07-27 at 12.26.33](https://europe1.discourse-cdn.com/steinberg/original/4X/b/8/0/b80556147ea5e5ceb73cb7e6a778773bceb20a06.png) ---
**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\ **Post date:** [July 27, 2025, 5:12pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/8 "2025-07-27T17:12:19Z")
Can you make a screenshot with the chords on the chord track? I cannot replicate the issue. ---
**Author:** ![RealRaven](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/realraven/32/132970_2.png) [@RealRaven](https://forums.steinberg.net/u/RealRaven)\ **Post date:** [August 22, 2025, 1:52pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/9 "2025-08-22T13:52:38Z")
it’s August 2025! this happened to me a couple of times. the worst time is now, mapping out a new track, haven’t named it yet (only created the folder) and so there is no way to get back at my work. the worst thing is the dialog has a Cancel button, and I think clicking Cancel actually makes Cubase freeze. This is OUTRAGEOUS. it is very easy to trigger, because we double click a single chord to change it. If multiple chords in the track are selected then Cubase starts this anti-feature. I do not care that you think you can analyze chord changes, I just want to get on with my work. And I lose a full hour now and am embarrassed as well because I am on a collaboration session. This has been reported 7 years ago, and it’s REPRODUCABLE BEHAVIOR. If you CAN’T FIX it then give us an option to completely DISABLE this ANTIFEATURE. Steinberg, FIX THIS. At least, make it possible to shoot down Cubase and get a “please safe” prompt so we do not lose all our work. ---
**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\ **Post date:** [August 22, 2025, 6:39pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/10 "2025-08-22T18:39:36Z")
> [@RealRaven](#): > > This is OUTRAGEOUS. > > it is very easy to trigger, because we double click a single chord to change it. If multiple chords in the track are selected then Cubase starts this anti-feature. Sorry, I tried multiple times to replicate this behaviour (C14.0.32) by selecting and clicking 10 chords at the same. Nothing… everything works as expected. Can you provide some system specs, too @RealRaven and @EX1MUS since both Johnny and I can’t reproduce this behaviour? ---
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [August 22, 2025, 7:44pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/11 "2025-08-22T19:44:08Z")
Well Cubase 14 seems better in that you’re apparently able to cancel the ongoing search- thread: [https://www.hamicast.nl/hans/ytresources/chordlab\_cubase14.mp4](https://www.hamicast.nl/hans/ytresources/chordlab_cubase14.mp4) Cubase 13 is still horrible: [https://www.hamicast.nl/hans/ytresources/chordlab\_cubase13.mp4](https://www.hamicast.nl/hans/ytresources/chordlab_cubase13.mp4) I can reproduce it with _any_ project that has some _complexity_ and create a chord selection. > select a chord, select another chord double click on the first chord - seemingly (and there’s a score showing chords in there as well perhaps that influences it) Now I agree with @RealRaven that this is an anti-feature. The pro doesn’t need it at all, the beginner doesn’t want to check the 1000’s of progressions out that make no sense anyways. ---
**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\ **Post date:** [August 22, 2025, 8:06pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/12 "2025-08-22T20:06:53Z")
Okay, I tried to replicate it once again by following the exact steps shown in your video: 1. Chord track with 30 random chords and multiple tensions/bass notes for complexity 2. Select a chord somewhere near the start 3. Select another chord near the end with at least 10 chords in between 4. Double click on the first chord Still nothing here. What am I missing? I am on Cubase 14.0.32, too. Windows 10. ---
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [August 22, 2025, 8:12pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/13 "2025-08-22T20:12:03Z")
Try with a standard demo project of Cubase, create a chordtrack from audio perhaps, IDK I like reproduction before fixing as well - but hey after all this years it might be a good idea to have a look at the source code as well. If you don’t see it let AI help you. - Keep trying. ---
**Author:** ![ejocvx](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ejocvx/32/175662_2.png) [@ejocvx](https://forums.steinberg.net/u/ejocvx)\ **Post date:** [August 22, 2025, 8:13pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/14 "2025-08-22T20:13:44Z")
> [@Reco29](#): > > 30 random chords Perhaps you need real chord progression to start anyway not random. ---
**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\ **Post date:** [August 22, 2025, 8:23pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/15 "2025-08-22T20:23:38Z")
For starters, I believe you that you encounter this issue. The question is - which circumstances lead to this behaviour since it is not reproducable with any given ad hoc chord progression. I changed the chord progression in a way that there’s a tonal centre to it - still nothing. > [@ejocvx](#): > > I can reproduce it with _any_ project that has some _complexity_ and create a chord selection. Maybe you can upload a project here that just contains the bare minimum to reproduce this issue. ---
**Author:** ![EX1MUS](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/ex1mus/32/176692_2.png) [@EX1MUS](https://forums.steinberg.net/u/EX1MUS)\ **Post date:** [August 22, 2025, 8:33pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/16 "2025-08-22T20:33:11Z")
Thanks for trying to repro it. I notice you’re on Windows. Maybe it’s a Mac thing? I’m on Cubase 14.0.32 Build 342 on Apple Silicon, running MacOS 15.6 on an M3 Max MacBook Pro. ---
**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\ **Post date:** [August 22, 2025, 9:09pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/17 "2025-08-22T21:09:07Z")
That could be a thing. I remember reading this topic some time in the past and wasn’t able to reproduce the issue at all. I am on Windows, too. ---
**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\ **Post date:** [August 22, 2025, 9:15pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/18 "2025-08-22T21:15:43Z")
> [@EX1MUS](#): > > Maybe it’s a Mac thing? Hmm, unlikely since @ejocvx encountered this behaviour on his Windows rig in 2018: > [@ejocvx](#): > > Cubase 9.5, Windows 10 1803 fully patched, x64 ---
**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\ **Post date:** [August 22, 2025, 10:47pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/19 "2025-08-22T22:47:19Z")
Okay, I was able to get this behaviour, too, now. Good thing that the Abort button actually works. It basically lets you skip the dialog and go where you wanted to go in the first place. Not sure what happened on @RealRaven 's computer. ---
**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\ **Post date:** [August 22, 2025, 11:36pm UTC](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076/20 "2025-08-22T23:36:55Z")
What did you do differently now that you can reproduce this behaviour? Anything in particular? [Next page](https://forums.steinberg.net/t/endless-wait-cursor-when-accidently-double-clicking-two-chord-selection/113076.md?page=2)