Chord Inversion

• Feb 7, 2023 - 23:37

Is there a quick way to move a chord up (i.e., the next inversion up)? I found some reference to a plugin 'Next Inversion' but it does not appear on the list for 4.0

Comments

Jojo-Schmitz

• Feb 8, 2023 - 08:41

You don't mean "New Retrograde", do you?

Ah, I see, https://musescore.org/en/project/next-inversion-replaces-all-chords-key…
That indeed hasn't (yet) beenported to 4.x.

Jojo-Schmitz

• Feb 8, 2023 - 08:49

Simply adding this near the start seems to be sufficient

   id: nextInversion
 
    Component.onCompleted : {
        if (mscoreMajorVersion >= 4) {
                   nextInversion.title = "Chord Inversion";
        }
    }

In addition to replacing Qt.quit(); with just quit();.

Jojo-Schmitz

• Feb 8, 2023 - 09:05

Try this

Attachment	Size
NextInversion.qml	20.29 KB

damuehlbauer@outlook.com

• Feb 8, 2023 - 17:59

Where do I place this in order for it to work? On the list of Plugins it says it is compatible with 4.x. I'm not a programmer, but I'd like to get this to work if possible. Thanks for your help. I have Windows 10.

Jojo-Schmitz

• Feb 8, 2023 - 18:08

Unfortunately https://musescore.org/en/handbook/4/plugins is still at its infancy, but check https://musescore.org/en/handbook/3/plugins and adjust for MuseScore 4

elsewhere

• Feb 8, 2023 - 18:41

The plugin author here. I don’t have MU4 installed, but in MU3: just place the qml file in your plugin directory (Documents\MuseScore3\Plugins). I always run the plugins from Plugins -> Plugin Creator. In the Plugin creator window choose File Open and Run.

Jojo-Schmitz

• Feb 8, 2023 - 18:52

There's no plugin creator in Mu4 and the folder to put plugins in is Documents\MuseScore4\Plugins. Once done, restart MuseScore, then enable that plugin via the plugin manager then run it from the plugins menu

damuehlbauer@outlook.com

• Feb 8, 2023 - 22:39

So, the only way I could get the Plugin to appear was to load the original MS 3.0 version in the ProgramFiles/MuseScore4/Plugin. It would load and be enabled. It just doesn't do anything. I tried making the edits suggested, but then it didn't even load. Looks like my only hope is that the originator decides to make a MS4 version someday. I did load it to MS3 and it works like a charm there.

elsewhere

• Feb 9, 2023 - 01:50

You may know this already, but maybe not…
You can go back and forth between MU3 & MU4: MU4 can open MU3 files, and if you export MU4 files to XML you can open them in MU3 (but XML does not export everything)
EDIT: and another thing: I hope you made the suggested changes in a plain text editor
EDIT2: MusicXML does some annoying things with chord symbols though. See https://musescore.org/en/node/344663

Jojo-Schmitz

• Feb 9, 2023 - 09:01

Jojo-Schmitz

• Feb 9, 2023 - 08:53

The Plugin I shared here and updated the original plugin page with, does work for Mu3 and Mu4

Edit 1: It does load and work in Mu3 and loads in Mu4, but indeed doesn't do anything there, sorry I didn't test that before.
So there got to be some internals that need more work

Edit 2: Actualy it does work, sort of, in Mu4's logs I found

2023-02-09T09:57:36.513 | INFO | main_thread | NotationProject | doSave: success save file: "C:/Users/(username)/AppData/Local/MuseScore/MuseScore4/new_project.mscz"

and indeed that new_project.mscz had the modifications/inversions in it.
That's not enough though to claim it being available for Mu4...

elsewhere

• Feb 9, 2023 - 09:45

Many thanks for your help & feedback Jojo!!
EDIT: I noticed there is no 'Quit' (at the end of OnRun) in the version you posted (and my Qt.Quit was already commented out by me). Could that be a problem?

Jojo-Schmitz

• Feb 9, 2023 - 10:37

I don't think so. But feel free to insert a plain quit(); there