Multimeasure Rest behavior

• Oct 21, 2016 - 05:18

As noted in a previous post, I have a large work that I am ready to publish. In doing some preliminary work, I cut a sample part, and got a surprise on the multimeasure rest behavior. Here is what I have in the score......

4 measures of rest, a rehearsal mark, and then one more measure of rest.

What I expected to be produced in the part was a multimeasure rest for 4 measures, followed by the reheasal mark, and a single measure rest.

What actually was produced in the part was a multimeasure rest for 3 measures, a single measure rest, the rehearsal mark, and another single measure rest.

I have other places in the part where rests were produced correctly, so I am assuming at this point that it has something to do with how I wrote the score. Does anyone have an idea what error I might have made?

Jerry


Comments

Addendum -

This seems to be related to a System Text entry on the top part. I moved the entry, and the multimeasure rest behavior corrected itself. The interesting thing is that the System text entry does not appear in the part. I should think that it should be there, since it is marked as System in its scope.

Jerry

In reply to by tbdbitl

It is correct that system text would break the rest. The whole point of system text is to appear on all parts, and if that requires breaking a rest, so be it.

If you are seeing a case where system text is not appearing on some given part, it might be that you have attached two separate texts to the same measure, and there is a known issue with this when it comes to multimeasure rests. See #38941: Staff texts after the first are ignored in multimeasure rests

That's just a guess. As mentioned, we would need you to attach the score in order to help further.

In reply to by Marc Sabatella

Is there a way to copy and paste the particular pages from the score that are the source of the problem? The score is 580MB in size, and is not yet copyrighted, so I am somewhat reluctant to put the entire score online; at any rate I would expect that a file this size would exceed your download limits for the forum.

I attempted to provide the 2 pages in question, but the copy function (Ctrl-C - am using windows 10) would not copy the desired selection to the clip board. When I attempted to paste into a blank document, I kept getting the previous copy request.

Perhaps I am missing something, but the lack of scroll bars makes navigation in a score this side somewhat tedious to me - I find I must work in small chuncks of code all the time since I cannot see an easy way to highlight a section that exceeds what can be seen on a physical screen. I highlight a note to start, then try to move to the end of the section, and unfortunately the act of scrolling - grabbing a non-staff area and dragging - obliterates the anchor/highlight that I just established. Is there an approved way of doing this that I am missing?

Thanks.

In reply to by tbdbitl

Mouse wheel or corresponding touch pad gesture are how you navigate. Or, View / Navigator. You can also define and extend selections with standard shortcuts like shift+right. It's actually quite simple and less work than scroll bars.

Not sure why copy and paste isn't working for you - probably some simple oversight. Here again, we'd need you to attach the score in order to investigate.

I'm having trouble imagining a 500MB score - that would be something like a 15 hour long work for 100 instruments it seems based on my experience. Or maybe it's that you have included large images? What if you make a copy of the score, and in the copy delete the images? Or delete all but the affected measures.

As for copyright, bear in mind that there Nonsuch thing as "copyrighting" a work - OK R at least, there hasn't been since the 1980's. Ever since the Berne convention, works are protected by copyright in virtually all countries the moment they are "fixed in tangible form" (to use the phrase from the US law, but all countries have something similar).

Do you still have an unanswered question? Please log in first to post your question.