Saving doesn't honor invisibles
Hi,
When I make various items (such as braces, barlines) invisible, save the file and then re-open, the invisibles are visible again. On a multi-page composition this could get very tedious quickly!
I attach the file. The "correct output.png" shows you what the output looks like after I've made things invisible (good!) but the "invisibles.png" shows what the score looks like on re-opening. Note, also, the horizontal line artifacts that only disappear when I make a change such as moving a note or a frame etc.
Puzzled...Thanks for any help!
| Attachment | Size |
|---|---|
| Responses.mscz | 27.22 KB |
| invisibles.png | 124.21 KB |
| correct output.png | 131.63 KB |
Comments
See #33541: some elements can get marked invisible, but this doesn't get saved, so is lost on reload
In reply to See #33541: some elements can by Jojo-Schmitz
Are you saying that these can't be permanently made invisible on a saved score? If so, doesn't my real-world example of choral "preces and responses" show that it is a necessary function for this and other similar types of music?
See attached Rose responses typeset by Novello. The priest's intonations are bracket-less and with no initial barline. The brace etc start with the SATB section.
Is there a work-around that you could suggest?
In reply to Are you saying that these by bachstudies
Neither the visible property nor the color (I tried changing it to white) survives a reload, so the only remaining possibillity might be a white opaque Image placed carefully to cover those brackets and initial barlines.
It is possible to disable initial barlines, but then they are gon from the SATB part too
In reply to Neither the visible property by Jojo-Schmitz
Ouch. I hope that this is something that is thought about for a future version. I compose this sort of music regularly...It is rather sad to go through all the work of pressing v for line after line, page after page for PDF output to have it revert back in the actual file :(
My understanding now is that these are auto-generated lines. Could the software not at least honor the editing decisions if there was an option to lock the score in place? Do these elements need to be auto-generated if they are already present in the score?
In reply to Are you saying that these by bachstudies
Looks like you have simply made measures invisible. instead, you should be using Style / General / Hide empty staves. That way the initial measures - which are technically their own systems (horizontal frames split a line of music into two systems internally) will show with only one staff and hence no bracket. You can use a vertical spacer to control the relative position of the remaining staff.
BTW< sometimes more complex layouts might be easier to do my having two separate scores and then using the image capture tool (the camera icon at right of toolbar) to take snapshots of individual passages of one score to paste into the other.
In reply to Looks like you have simply by Marc Sabatella
Holy cow, why didn't I think of that, having used it myself on occasion.
One problem though; that then single staff moves up and alinges with the SA staff, no longer with the TB one.
Edit, I missed the hint about the spacver. with that it works!
In reply to Looks like you have simply by Marc Sabatella
Wow! Good call...Exactly what I needed. Now I'll try the spacer to get the staves aligned. OK, a cheeky ask...If, as it looks like, the hide empty staves did the trick, wouldn't it be really cool to allow the remaining staves to stay in place?
This is similar to the problem I have had with creating incipits for urtext editions of motets, which must show the original C-clefs and the ¢ time signature. I use a horizontal frame to separate the incipit from the start of the music (showing modern clefs and numeric time signatures), and, of course, after a horizontal frame, MuseScore automatically generate a new instance of the Long Instrument Name, which is unwanted. They can be made invisible, but that action cannot be saved so those instrument names re-appear every time the score is reopened.
However, nobody (I would think) prints a working copy of a score directly from the mscz file itself; so the problem is more of an annoyance than a major problem. What I have resigned myself to doing, until this anomoly is resolved, is to set all the unwanted visual elements as invisible, and then export the MuseScore file as a PDF before closing and re-opening the score. The resulting PDF will not show those invisible elements, so the working/performing print copy of the score will appear the way you want it.
In reply to This is similar to the by Recorder485
Agreed regarding printing, although for one-page pieces of music, I'll often print straight from Musescore when imposition isn't a concern.
I would definitely concur with the invisible property being an "anomoly". Marc offered great advice to help me solve the preces/responses intonation issue but I'm in the same position as you in that often I notate an incipit in choral music that I typeset. So far, I've been doing this in Sibelius but I've been slowly moving my typesetting to Musescore. I'm impressed with the output I've gotten on my choral preces and consider it easier and as visually appealing as what I could achieve in Sibelius (with a little bit of style-tweaking such as slightly thicker staff lines). Hurray for Musescore! However, the re-printing of the long instrument name would be annoying because I'd have to remember to make it invisible every time I edit and PDF the file. In the future I'd like to think I could share my scores in native format with choir members or a fellow composer without them having to re-do all the invisible tags when editing or printing.
Here's hoping!
In reply to Agreed regarding printing, by bachstudies
I don't run Sibelius at all, only MuseScore, so I can't evaluate the difference in the way they run. But I have filed an 'issue' in the Issue Tracker about this sort of thing, and I know that Marc is currently looking at ways to make those 'invisible' instructions savable for things like the instrument name.
In reply to I don't run Sibelius at all, by Recorder485
Great! One of the amazing things about a lot of open source software I use is that there are often multiple ways to crack the same nut. I hope that if instrument names can be kept invisible, so can beginning barlines, braces etc. For my purpose, Marc's is a very elegant solution using the horizontal frame and "hide empty staves" (with the minor detail of having to add spacers to each intonation to position in line with the lower stave) but I'd like to think my tweaking outside the box by making measures and various lines invisible would also work (especially as the PDF output is exactly what I want my score to look like). It seems to me (a non-programmer!) that if the information for these lines, instrument names and whatever else already exists in the file somewhere (along with any invisible or color properties), the software could skip the auto-generation of these items on loading...Then again, that may well break the universe for all I know ;)