Note this is similar to but not the same as #14146: Bars with text shouldn't be part of multi bar rests. That issue involves explicitly placed staff text and the question of whether or not it should break a mm rest. In that case, yes, I would, and I'd also want the measure to not be part of *any* multimeasure rest. But in this case - rehearsal marks - it's OK to still include the measure in a multmeasure rest. Ideally it would start a new one, but in the real life case from which this example was derived, there was a double bar before the rehearsal mark so the break wasn't the problem. I just need to the rehearsal mark to display at the start of the multimeasure rest that this measure begins.
BTW, same exact comment applies to tempo text. They should probably to *break* multimeasure rests automatically, but in any case, assuming the break occurs for whatever reason (double bar, explicit break mm rest property set), tempo markings need to *display* at the start of the new multimeasure rest.
FWIW, I just completed a semi-significant arrangement and found this to be really the only significant regression compared to 1.3 in terms of not being able to get the desired results.
Comments
Forgot attachment as usual...
Note this is similar to but not the same as #14146: Bars with text shouldn't be part of multi bar rests. That issue involves explicitly placed staff text and the question of whether or not it should break a mm rest. In that case, yes, I would, and I'd also want the measure to not be part of *any* multimeasure rest. But in this case - rehearsal marks - it's OK to still include the measure in a multmeasure rest. Ideally it would start a new one, but in the real life case from which this example was derived, there was a double bar before the rehearsal mark so the break wasn't the problem. I just need to the rehearsal mark to display at the start of the multimeasure rest that this measure begins.
This worked as expected in 1.3.
BTW, same exact comment applies to tempo text. They should probably to *break* multimeasure rests automatically, but in any case, assuming the break occurs for whatever reason (double bar, explicit break mm rest property set), tempo markings need to *display* at the start of the new multimeasure rest.
FWIW, I just completed a semi-significant arrangement and found this to be really the only significant regression compared to 1.3 in terms of not being able to get the desired results.
This appears fixed (probably for a while now, but definitely as of 12/15/2013).
Automatically closed -- issue fixed for 2 weeks with no activity.