I’m going to use this thread as an opportunity to really shine the spotlight on some major issues that this program has.
My biggest gripe right now is that when I go to save a user preset after I have worked for quite some time already to build a perfect chord set, that when you now load that preset, that it does not recall the inversions of chords that you had set which I find is absolutely ridiculous and laughable, that it hasn’t even been implemented when to me this seems like such a basic function. For me, chord inversions are one of the most important aspects of building tension in music. If I spend some hours working on a set with many inversions, I save and then reload the preset at a later date, I can no longer even remember what I had done. What makes matters even worse, is that when you open up the circle of fifths page and then click on the chord that you would like to change into an inversion, the menu at the top to change that chord to an inversion doesn’t even appear! The only work around to this is to delete that chord and replace it with the same chord, and then you can now change it into an inversion, what the hell?
Another issue with inversions is that when you are viewing the guitar chords for the chords in your chord track, they too, will not display the chord as an inversion, what?
Don’t get me wrong, I really want to love this program, but to me, it has been released in an unfinished state. There are just way too many things wrong with this program, that I end up just giving up in frustration because of all of the things I cannot do and then with all of the bugs on top of that.
I was unable to reproduce the issues you’ve described on my M1 Mac. I added inversions to several chords, saved as a preset, and upon reloading the preset, the inversions were retained. I also tested cross-DAW – saving in Logic and opening in Ableton Live – as well as in standalone, and in all cases the inversions were preserved.
I’m also able to access the inversion controls on the Circle of Fifths page without issue.
I’d recommend rebooting your machine if you haven’t already. If the issue persists, please let us know with a bit more detail about your setup, for example, your DAW, OS version, and whether you’re using Scaler in standalone or as a plugin. Cheers
Hello Steven, thank you for the welcome and also thank you for taking the time to try and replicate the issues I have been having; it’s greatly appreciated.
It is interesting that it is working for you and it is a possibility that the problem lies in that I am on a windows based machine compared to your apple device. I took a couple hours this evening to do some extensive testing on this matter and my results are negative.
I am currently running on a windows based laptop using:
Windows 11 Home 64bit, version 24H2
AMD Ryzen 5 7520U with Radeon Graphics 2.80 GHz
I tested using both the standalone version and the DAW hosted version inside of Cubase Pro 14.
Issues persisted using both versions.
I restarted my laptop after doing updates and I created a quick chord progression within the standalone version with the cadence being an inversion and I saved it, reloaded one of my user presets and reloaded the chord progression I had created and for whatever reason, it decided to save that inversion.
I then loaded up two of the ones I had saved from before, changed certain chords to inversions, saved over them, didn’t work, I even redid the process, saved them as new presets, still no luck.
I created more progressions with inversions from scratch, still nothing.
Also, the issue where I can no longer change those chords back to inversions in the circle of fifths page unless I delete the chord and replace it with the same chord, and then I’m able to change the inversion still persists.
I tried doing this in both the standalone version and inside of Cubase.
I also have Scaler3 installed on my main computer at home which is a windows based machine running Windows 10, the issues are also present on that machine. Unfortunately, I can’t give you the specs of that machine right now as I am out of town for work.
Hi @Khepera. I wanted to chime in to say we have been unable to reproduce your reported issue where chord inversions are not saved, but would like to clarify a few details if you don’t mind.
First, when you say:
are you referring to Scaler 3 global presets saved via the preset browser at the top of the screen? Or are you talking about saving user chord sets? Either way, chord inversions should be saved, however there are notable differences between the two cases.
When saving a global Scaler 3 preset, all aspects of Scaler 3 are saved in their current state. This includes chord/motion modifiers such as octave and inversion.
When saving user chord sets, only the selected main track chords are saved in their current state. Whilst this does include inversions e.g. C maj to C maj / E, this does not change the displayed values of any other parameters in Scalar 3. So the chord notes themselves should be the same as when you saved the chord set, and the chords should sound the same, however Scaler 3 parameters such as the inversion controls on the circle of fifths page or sidebar modifiers on the arrange page won’t necessarily reflect this.
Either way, let’s say you save a global preset or a user chord set which includes the chord C maj / E with notes: E, C, E, G. Are you saying when you recall this preset or user chord set, that chord is now labeled simply as C maj and contains only the notes: C, E, G? Or something similar to this?
I’m referring to what is titled ‘Main Presets’ in the top bar beside the arrange tab.
I opened up the program again and tried more testing, my results are still negative. I tried building a set of chords using inversions and saved them as chord sets this time and when I load the chord sets, they still don’t retain their inversion status, infact it’s worse when they are loaded, I saved the cadence as a sharp chord inversion and when I loaded the chord set, it for whatever reason loaded the cadence as a flat chord; a D# is NOT the same as an Eb.
What I have also discovered is that, if I build a chord set with inversions on the main track, and then close the program without saving and then reopen the program, it will load up the main track I was just working on, Scaler will remember every chord, except the chord I had set to an inversion.
Hi @r3coil , thank you for sharing this issue that you are having with me, even though what you are doing is slightly different, it seems as though we are both having the issue of not being able to change the inversion of a chord because the option to just straight up disappears.