how to force instrument abbreviation
I used the Shift-{ feature to squeeze the horizontal size of some measures so that 4 measures fit on a line.
Yes this is ugly, but I want it to match the physical score I'm entering.
However, when I press Shift-{ enough times to make the measures fit, musescore spells out the instrument names rather than abbreviating them. Normally, this should only happen in the first measure of the score, not the first measure of a page. How can I fix this?
I'm using version 53d4ad2.
| Attachment | Size |
|---|---|
| Screen Shot 2018-12-20 at 20.07.58.png | 72.28 KB |
Comments
In the 1st measure and after a section break. From this picture we can't see what it is, so you'd need to share the score
your version 53d4ad2. is 2 years old... you should really upgrade to 2.3.2
In reply to In the 1st measure and after… by Jojo-Schmitz
No it's just a normal measure, no sections at all. I'll try to upload the score.
In reply to In the 1st measure and after… by Jojo-Schmitz
I thought I was using the beta version downloaded from https://musescore.org/en/download
am I not?
In reply to I thought I was using the… by jim.newton.562
Not, if it reports 53d4ad2, as that commit is 2 years old. And indeed:
this is definitly not a Beta, as that would have
<museScore version="3.01">In reply to Not it'll it reports 53d4ad2 by Jojo-Schmitz
What should it report if I'm using the beta download? I'm confused about which version my mac runs if I have several versions accidentally installed simultaneously.
In reply to What should it report if I'm… by jim.newton.562
In reply to First of all remove that… by Jojo-Schmitz
thanks for the conversion flow. is there a way to find "every score created with that old build" ?
In reply to thanks for the conversion… by jim.newton.562
MuseScore 3.0 RC will tell you...
In reply to MuseScore 3.0 RC will tell… by Jojo-Schmitz
Great!. I'll try it. Is there a link/url for MuseScoreSpecial-2018-09-20-0902-master-c07ed54-300-file-format.dmg ?
In reply to Great!. I'll try it. Is… by jim.newton.562
http://prereleases.musescore.org/macosx/nightly/
In reply to MuseScore 3.0 RC will tell… by Jojo-Schmitz
OK, i've downloaded and installed the compatibility version. But it is not clear to me now, how to ask it to find all the scores which it needs to convert. What do I need to do? I hope I don't need to one by one open up every score one by one and save them back to the same directory.
In reply to OK, i've downloaded and… by jim.newton.562
Maybe not every one, but sure where one the 3.0 RC (or betas) complains about. You've been warned back when you downloaded that development build...
In reply to Maybe not every one, but… by Jojo-Schmitz
Oh, I think I understand the flow. I need to run the compatibility version every time the beta version has trouble opening a score?
What should happen in the compatibility version? In my case it complains that the score is "corrupted" and allows me to ignore the corruption and open anyway.
So when I ignore, it seems to load fine. Then when I save it and try to open it in the beta version, it again complains that it is "corrupt", and allows me to ignore. When I press "ignore" it seems to load fine.
Is that what should normally happen? Or does that mean something else is wrong?
In reply to Oh, I think I understand the… by jim.newton.562
It means that you need to fix the corruption ASAP.
In reply to thanks for the conversion… by jim.newton.562
I wonder what the Mac user should expect when he downloads the beta version and installs it. I'm not an expert (as most mac users are not). But when I download the beta version, and then as ask the mac to run musescore, it only shows me one version. So I have believed for the past several months to be running the beta version, when in reality I was running some nightly build which as you point out is several years old.
I wonder whether I'm the only person that this has happened to?
In reply to I wonder what the Mac user… by jim.newton.562
Here are the applications matching "muse" which seem to be installed.
![Screen Shot 2018-12-22 at 13.27.27.png]( "Screen Shot 2018-12-22 at 13.27.27.png")
As can be seen from the text, I was assuming this version was from september 2018, but you say it is a couple of years old.
but here's what I see in the application launcher
![Screen Shot 2018-12-22 at 13.28.30.png]( "Screen Shot 2018-12-22 at 13.28.30.png")
In reply to What should it report if I'm… by jim.newton.562
I again downloaded the beta version and was able to start it. However, the beta version refused to load the score.
![Screen Shot 2018-12-22 at 12.29.37.png]( "Screen Shot 2018-12-22 at 12.29.37.png")
So I again ran the older version and exported musicxml, and that loaded in the beta version.
Now, I can't reproduce the instrument abbreviation problems. It seems for the moment that the problem is fix. That's good news.
In reply to I again downloaded the beta… by jim.newton.562
This gives me an interesting thought. It would be nice (although horribly difficult to implement), if there were a web service which given any musescore score, the user could upload it, and download the musicxml. The web service could look at which version the score was created with, and if it recognizes the version it could import it and export the musicxml. This would allow the user to recover most of the score, even some things are lost.
In reply to I again downloaded the beta… by jim.newton.562
That's why you'd need that 'compatibillity' build
Here is the score which exhibits the behavior.
To reproduce, place the cursor in measure 16, press CMD-{ a few times, then in measure 17 and press CMD-{ a few times.