I manually created some Scale Events in the Chord Track, (and disabled both Adaptive Voicings and Automatic Scales just in case they were going to interfere with my settings). I closed the project down, and when I reopened it the scales were different.
I re-created the problem but this time I also manually created markers with THE SAME INFORMATION to make sure I didn’t lose the data a second time.
When I reopened the project the Chord Track scales had been corrupted again. Attached is a screenshot of the differences. Before I closed and reopened the project the two tracks in the image contained EXACTLY the same information.
I cannot find the post right now, but I saw something like this before – scales being changed to the wrong mode. It stopped happening when I edited the scales in the scale assistant. I think I just got rid of most except for the Greek modes and other common modes
I’ve raised a Support Ticket with Steinberg (oh, come on now, don’t laugh, you never know). I might try doing what you suggest, but I don’t fancy always being unsure if my data’s still going to be there when I come back.
Yes, but there’s more. Before I did, I spent half an hour trying to recreate the original problem, and couldn’t. I tried editing some notes in the keyboard line I have, playing the song at various points, basically anything I could think of to make the chord track be upset, and it remained uncorrupted each time I restarted Cubase (proper restart, not just reopening the project.)
So, I’ve followed your suggestion - it’s cleaner not having all of that stuff there anyway, but I don’t know why the problem happened in the first place. I’ll be interested to see if Steinberg offer any intelligence, and if they do I’ll post it here.
I’ll mark your post as a solution, though, since I’m happy to accept that your fix alone was enough to make the problem go away. Thanks for your time.
That’s great. I’ve seen a few other posts for the same problem – I think it’s the result of changes made between versions. Good to know the fix can be accomplished simply by editing the scales.
I have edited the used scales in the scale assistant and I have also deleted the unused scales from there but, in my project, all scale events keep being changed quite randomly after restarting Cubase. Therefore, I would not consider this issue solved.
it wasn’t easy but I hope I have reliable repro-steps here:
System: Windows 10, Cubase 11.0.10
Create an empty project and create a chord track in it.
In the chord track inspector, untick the “Automatic Scales” option.
Make sure the “Show Scales” option is activated.
Now, create the following three scale events:
bar 1: “D Dorian”
bar 2: “E Phrygian”
bar 3: “F Lydian”
Select the first scale event (“D Dorian”) - this is crucial!
Save the project under a new name and quit Cubase.
Start Cubase again and reopen the saved project.
What you expect: The chord track contains exactly the scale events you created.
What you can actually see: The mode of some of the events has changed. Most often, I’m getting “D Dorian”, “E Dorian” and “F Dorian” but your experience may vary.
I’m curious whether you can reproduce this. Please, let me know
Hi, I thought I’d just put a quick update to say that the problem wasn’t fixed after all. I have also fully deleted all the scales I could even remotely classify as superfluous.
6 weeks in and still no reply from Steinberg to my support query, but I fully expect them to (eventually) say “reinstall Cubase and delete all of your preferences” - it seems to be their stock reply. I’m not prepared to do that, so I have abandoned the Chord Track.
Sorry for my very late reply, Steve. Thanks for your file but, unfortunately, it does not solve the problem for me. The scale events are still being randomly changed after re-opening the project. And I have experienced this behaviour on two computers with different update history - which does not rule out the possibility of corrupt preferences completely, however, it makes the hypothesis less probable, I suppose.
Just bumping this thread to say that this issue still persists in Cubase 11.0.20. Of course, it’s understandable since Martin reported it on April 6 and Cubase 11.0.20 was built on March 26 but I’m just letting everyone know
