musescore 4 CLI --score-transpose does nothing?
Hi team,
I have a script that does a bit of processing on my scores, part of which is CLI transposition with the following invocation:
> mscore myfile.mscz --score-transpose '{"mode": "by_interval", "direction": "up", "transposeInterval": 4, "transposeKeySignatures": true}'
It works fine with MuseScore 3, but it seems that the mscz produced by MuseScore 4 isn't transposed at all, though everything seems to work fine. Inside the encoded mscz output I can find a "MercyMercyMercy_transposed.997894.mscx" file, which content is exactly identical to the mscx in my original mscz.
Am I doing something wrong? I have tried with a freshly-compiled musescore, master branch and with MuseScore 4.1.1, they behave just the same.
I am attaching my original file (MercyMercyMercy.mscz) and the produced mscz (tmp_conductor.mscz).
Thanks for your help!
| Attachment | Size |
|---|---|
| MercyMercyMercy.mscz | 32.45 KB |
| tmp_conductor.mscz | 31.65 KB |
Comments
TLA de-obfuscator:
CLI = command-line interface
https://www.techtarget.com/searchwindowsserver/definition/command-line-…
Did you manage to solve this? I have the exact same problem. Using 4.3.1 and today's nightly build, and all of the returns the same .mscz file, completely ignoring the --score-transpose options (i am also using -o score.pdf on the CLI)
In reply to Did you manage to solve this… by opinsky
Hi, I haven't been able to solve this, and I'm quite baffled at the lack of reaction. I'm still stuck with version 3 for the time being.
In reply to Hi, I haven't been able to… by brassdom
Thanks for the prompt answer. I hope this gets fixed soon. Have you had success in downgrading songs from 4.x to 3.x?
In reply to Thanks for the prompt answer… by opinsky
Yes: I've exported them into MXML and imported them into musescore 3, and it worked perfectly fine.
In reply to Hi, I haven't been able to… by brassdom
What does this script do that MU4 doesn't? just wondering.
In reply to What does this script do… by bobjp
It is not a script - is just the ability to transpose a file from the CLI (command line interface). Many people that have a large library of scores that need to be transposed to instruments in different tuning (Bb for clarinets, Eb for Sax Alto, etc) rely on this feature, that can be done manually, but would be much much easier if automated.
In reply to It is not a script - is just… by opinsky
I only called it a script because the OP did. So it is a batch processor?
In reply to I only called it a script… by bobjp
I didn't call it a script, and it's not "batch processing" per se. I have used this "ability" in a set of instructions (using a scripting language, see https://en.wikipedia.org/wiki/Scripting_language) that I've called a "script" to process multiple files, so the whole script does batch processing. I hope I made it clearer :-)
Just adding to say that, I'm also having the same issue, as of 4.4.0.
Also filed an issue in the repository.
FWIW, I think I've fixed this. PR here.