My text disappears
Activating the multi-measure rest option, (Style/general/Create multimeasure rests) my text disappears.
Do you still have an unanswered question? Please log in first to post your question.
Activating the multi-measure rest option, (Style/general/Create multimeasure rests) my text disappears.
Do you still have an unanswered question? Please log in first to post your question.
Comments
What text disappeared? I don't see any text missing in your picture.
In general, best to post the actual score, not just a picture of it, and give precise steps to reproduce the problem.
In reply to What text disappeared? I by Marc Sabatella
The "Alto Sax Eb" is missing. But yes, for finding out why we'd need the score, not a picture of it.
And it is better to attache Images and files here directly, so they remain visible if found years later
In reply to The "Alto Sax Eb" is missing. by Jojo-Schmitz
The reason probably (I can reproduce so...) is because you have in the first measure:
1) Entering the text "Intro"
2) do "Escape"
3) and after this, making a second text operation by typing "Alto Sax Eb" (in bold character, no matter here)
Result: when you enable the mm rests, the second text entered (ie Alto Sax Eb) in this process is erased
- So, for avoiding this, you have just to enter the two words in the same/unique text operation (by Ctrl +T)
ie, enter "Alto Sax Eb" -> press "Enter" key -> enter "Intro" (see image below) and after this only, Escape:
![ex.jpg]( "ex.jpg")
For final result (after bold character change and better positionning)
![result.jpg]( "result.jpg")
- Or with your preferred layout:
![lay.jpg]( "lay.jpg")
![lay2.jpg]( "lay2.jpg")
And new final result:
In reply to The reason probably (I can by cadiz1
Interesting, so from 2 staff texts only the 1st is shown on an mm rest. Certainly ooks like a bug to me, worth being reported in the issue tracker
In reply to Interesting, so from 2 staff by Jojo-Schmitz
It's a known issue - #38941: Staff texts after the first are ignored in multimeasure rests
In reply to It's a known issue - #38941: by Marc Sabatella
Ouch... November 2014, almost two years, I confess that I did not remember at all! :)
(And not research either)
In reply to It's a known issue - #38941: by Marc Sabatella
Selecting a multy-rest part and double clicking the icon on the left, MuseScore crashes. Maybe that’s known as well ?
I had to go out of multy-rest mode, make the separation and go back into it.
In reply to The reason probably (I can by cadiz1
Better yet - don't use staff text for this; use the proper type of text - Instrument Name. Better still, let MuseScore take care of all of this for you - the transposition, the instrument name, and the Multimeasure Rests - by creating the score first and meeting MuseScore generated the parts for you, correctly and automatically, via File / Parts. You shouldn't be having to mess with any of these things manually.
In reply to Better yet - don't use staff by Marc Sabatella
That’s kind of a problem, when I start up, I don’t really know where I am going to end. I need to be able to make changes as I go along.
___ "Better still, let MuseScore take care of all of this for you" ___
Never have software taking care of stuff automatically, it always screws up, even Photoshop.
In reply to That’s kind of a problem, by Karel Van Tornhaut
Not sure what you mean about making changes as you go along - nothing about what I described prevents that. In fact, MuseScore's parts facility makes this far easier than doing it manually - changes to your score are automatically reflected in parts and vice verse.
As for screwing up, if you have a specific score and precise to reproduce a problem, please share them. But in general, MuseScore will do the job of generating parts from a score far more quickly, accurately , and completely than you would be to do yourself.
In reply to Not sure what you mean about by Marc Sabatella
"if you have a specific score and precise to reproduce a problem, please share them."
Thank you, I have already added some new tricks to my MuseScore knowledge thanks to this forum.
Never mind my ‘accidentals’ every now and then :-)
In reply to Not sure what you mean about by Marc Sabatella
Here you go, this is why you can’t rely on software doing things automatically for you. The first line should read 8 bars of rests.
In reply to Here you go, this is why you by Karel Van Tornhaut
Please share the score, not just an image of it
In reply to Please share the score, not by Jojo-Schmitz
Sorry 'bout this, here's the file :
Poliushko Polie.mscz
In reply to Sorry 'bout this, here's the by Karel Van Tornhaut
Having a change instrument instruction will break the multimeasure rest. (Not sure why it breaks at the end of the measure though? Break before makes sense, break after imo less so)
In reply to Having a change instrument by jeetee
“change instrument instruction”
This sounds like some hidden information. How do I find this 'change instrument instruction' and/or remove it ?
In reply to “change instrument by Karel Van Tornhaut
It's the text type you used to enter "Alto Sax Eb"
In reply to It's the text type you used by jeetee
Right ... this is weird.
In reply to Here you go, this is why you by Karel Van Tornhaut
This is *not* a part generated using the automatic facility I mentioned. had you used that facility, it would have worked. The problem is caused by your using the wrong type of text for the instrument name. You used an instrument *change* text instead of a part name. Instrument changes would not normally be placed on empty measures - they would be placed at the actual point of change. The part name, on the other hand, is added to the title frame and not attached to any specific measure.
Had you used the automatic facility, this and many more things would have been taken care of correctly. Not saying you have to do this, but this example is actually a good argument for why it is usually better to do things the way MuseScore was designed to be used.
In reply to This is *not* a part by Marc Sabatella
Why on earth did Steve Jobs die so soon ? He was the only one on this planet who could invent something without the need of a manual to use it.
In reply to Why on earth did Steve Jobs by Karel Van Tornhaut
If he was the only one, it's probably because it is so easy for everyone to figure out stuff that works intuitively for everyone else..
The aside, I also noted you're entering (although your text indicated for Alto Sax Eb) your score on a single Treble Piano staff. If you were to use an actual Alto Sax staff you'd get the partname (instrument) generation for free as well as automatically handled notation transposing required for that instrument.
How is writing a Sax part for a Piano staff more "intuitive" than just writing it for Alto Sax?
In reply to If he was the only one, it's by jeetee
Don't shoot the piano player Jeemee, i’m only using Musescore for a week now.
I’ve changed it into an alto sax staff in the main time. I discovered the ‘concert pitch’ button.
Here’s the latest version. If you have any remarks please let me know.
Poliushko Polie.mscz
In reply to Don't shoot the piano player by Karel Van Tornhaut
Apologies if I came across too cross, that was not my intention at all.
I assume the score is not yet finished? If not, the presence of the To Coda without any DC makes me wonder about what the expected playback order should be.
But if the score is still being composed and that part isn't written yet, no worries and keep on exploring MuseScore :)
In reply to Apologies if I came across by jeetee
It's ok, I can handle a punsh :-) Yes, the score is finished.
MuseScore can’t find the coda sign either. It is where the text ‘Alto sax Eb’ is.
Maybe it should be ‘Dal Segno Al Fine’ and replace the coda with a segno. I don’t really know the right way for doing this. The first 4 staffs should be replayed (with their repetitions) before continuing till the end. I tried several ways but MuseScore ignores them all, so I left it.
In reply to It's ok, I can handle a punsh by Karel Van Tornhaut
If you can walk me through the full desired playback order, I'll see if I can make it work for you.
Assume I know of nothing, so you'll have to say it in a format such as the following:
1-20
1-40
20-40
etc...
In reply to If you can walk me through by jeetee
It almost works. Dal segno al fine works, I forgot the ‘Fine’ word. DS with the segno works too. Unfortunately the second time Musescore ignores the repetitions.
17-24 twice
25-32 twice
17-24 twice
25-32 twice
33-69
Here’s the file : Poliushko Polie.mscz
Here’s Andre Rieu : https://youtu.be/qKCaH0KCWXg
In reply to It almost works. Dal segno al by Karel Van Tornhaut
So you'd need a jump with repeat, MuseScore doesn't have that yet.
In reply to So you'd need a jump with by Jojo-Schmitz
Ok, so it isn’t me :-)
Nice program btw, my love for it is growing crescendo.
In reply to Ok, so it isn’t me :-) Nice by Karel Van Tornhaut
There is an open feature request for this #8604: Better control of repeats and jumps for playback
In reply to There is an open feature by jeetee
And more specifically #56451: Add a property "with repeats" to jumps (like "D.S. al Coda")
In reply to The reason probably (I can by cadiz1
I have used the way around the problem as you explained. (See result in the attached file.)
La historia de mi vida.mscz
Thank you Cadiz1 for taken the time out.
In reply to The "Alto Sax Eb" is missing. by Jojo-Schmitz
--- "it is better to attache Images and files here directly, so they remain visible if found years later." ___
My mistake. I will do so in the future.
In reply to What text disappeared? I by Marc Sabatella
__ "What text disappeared? I don't see any text missing in your picture." --
I'm sorry to hear this.
In reply to __ "What text disappeared? I by Karel Van Tornhaut
Sorry, I was looking in the wrong place. I see it now. As mentioned, it's a known bug, but it only occurs here because you are not using the correct type of text.
In reply to Sorry, I was looking in the by Marc Sabatella
"Selecting a multy-rest part and double clicking the icon on the left, MuseScore crashes." Thanks for report.
Issue filed: #127281: Crash when adding line/section/page breaks by double-clicking on a multimeasure rest