Custom Chords behavior subject again
I've been working with custom chords xml file for quite some time, and yet, I still scratch my head when something goes weird. I'm afraid my herpes zoster is coming back because of that. lol. Here's the thing: every time I need to do some repair in the xml file, I have to: 1-save the music with any different chord style available and apply the changes, 2-choose the xml style i'm working on and save it again, 4- close the program, 5- open it again and voila - my newer changes are there now. It took me a good amount of time to figure that out, but that's Ok. Now, the problem - my custom chord xml is working like a charm in musescore v.2, but it refuses to cooperate in v.3. Some changes are there but others, not. Please, anybody could explain what is going on with this weirdness? I'll provide the files later if needed. Thanks.
Comments
Here some pics. It seems to me, according to the v.3 image, musescore is not recognizing the changes, but the font typing only.
And this image below is the weirdest thing that happened so far. Both Chords were typed F#m7(11). Consider that the custom "m" is a glyph I added to the font, because I simply don't like to read a chord with a "M" upper case kind of.
Update: in one of my several tries, I ended up changing the xml version numbers.
" ?xml version="3.0" encoding="UTF-8"? "
" museScore version="3.0.0" "
I wonder if it has anything to do with my problem. After I changed it back to the original number, which was "1", everything started to work again. I probably did something stupid here...
In reply to Update: in one of my several… by Toninho Zemuner
Should be
In reply to Should be <?xml version="1… by Jojo-Schmitz
Thanks JoJo. I’ll try that later. How can I make my xml text appears in the message just like yours?
In reply to Thanks JoJo. I’ll try that… by Toninho Zemuner
Enclosing it with
<xml>
...
<\xml>
In reply to Enclosing it with <xml> ... by Jojo-Schmitz
Thank you.
In reply to Should be <?xml version="1… by Jojo-Schmitz
Hey Jojo and Marc, I found out that I cannot mess with xml files while I'm working on a score that is already in progress. I don't know why, but Musescore refuses to accept the new changes this way. However, when I start a new score, all my changes are correctly there. Go figure.
In reply to Hey Jojo and Marc, I found… by Toninho Zemuner
Have you tried to change the chord symbols file in an open score to something else then to the one you are editing to force a reload?
In reply to Have you tried to change the… by mike320
Yes, that is what I do all the time. I also found out that some of the changes, like font size or font itself, WILL reflect on reload. It seems to me that part of the code, when loaded to a score, stays IN the score, and there is nothing you can do to revert that.
In reply to Yes, that is what I do all… by Toninho Zemuner
indeed, custom chord files get baked into the score
In reply to indeed, custom chord files… by Jojo-Schmitz
In other words, according to what you said, testing a custom chord file requires lots of wasted scores and time.
In reply to In other words, according to… by Toninho Zemuner
Maybe try testing by editing the score itself (save as MSCX). The whole custom chord facility is there for advanced users who don't mind hacking, but it's not really "supported" because we know it isn't easy and the details may well change. Some day I do hope to see us add a user interface o allow these sort of customizations more directly.
In reply to Maybe try testing by editing… by Marc Sabatella
Funny, I started knowing nothing about xml in this forums. And you, Marc, always helped me to get to the other side. Today, you are kind of pushing me again. 😂. Hacking here I go. Thanks so much for doing what you do.
In reply to indeed, custom chord files… by Jojo-Schmitz
I don't use chord symbols, so I'll ask what I would try myself if I did. Can you right click a chord, select all similar elements, the use 'Reset to text style" in the inspector to change the style?