Marc,
There is one use case where I wished that I could set the multi-measures
manually: copying only a few instruments from the full score into
MuseScore.
Scenario 1:
You get an orchestral trumpet part in D but your trumpeters are not good
enough to transpose from sight. This is common in the educational
setting, but I've even redone parts for musicians in professional
orchestras. When you get to a multi-measure rest, you have to leave
multiple blank measures (that are easy to miscount). It also creates a
visual difference between the part you are copying to what you see on
the screen (which makes errors more common).
Scenario 2:
You want to make editorial/artistic changes to section of the score.
Perhaps your changes only affect the brass section, so you only input
that section of the score in to MuseScore rather than the full score.
When you get to a multi-measure rest, you have the same problems as
scenario 1 above.
There are ways to use MuseScore as it currently exists for these
scenarios. For example you could add the multi-measures at the very end
after you've added all the notes (by inserting exactly the number of
measures you need for each multi-measure rest). However, making multiple
passes on input is something I try to avoid since it is so prone to
mistakes.
In summary, the current implementation of multi-measure rests is ideal
when you are working with full scores. But manually setting
multi-measure rests is ideal when you are working with only part of a
full score.
David
On 3/14/2016 9:00 PM, Marc Sabatella wrote:
> That sounds much *harder* to me, not easier at all. How is going to
> all that trouble easier than just pressing "M"? Or, better yet,
> having created automatically for you when you generate parts from your
> scores? They break autmatically at double bars and other significant
> events, so the "specific" mutlimeasure rests normally happen
> completely automatically, and in cases where for some unusual reaosn
> you want to break a multimeasure rest but *not* have a double bar or
> other marked there (this is very rare), you can do this as well, via
> Measure Properties.
>
> I'd recommend you maybe ask about how to use multimmeasure rests on
> the forum, and then I think you'll probably find the system actually
> does work extremely well, and you'll be able to find more suitable
> GSoC project. That's my personal opinion, anyhow.
>
> On Mon, Mar 14, 2016 at 6:47 PM Joyce Yom <
[hidden email]
> <mailto:
[hidden email]>> wrote:
>
> Hello!
>
> My name is Joyce Yom, and I'm a sophomore studying Computer
> Science at Rensselaer Polytechnic Institute. I only heard about
> GSOC just a few days ago, otherwise I would have contacted
> MuseScore a LOT earlier.
>
> I do not have much experience with Qt, but I have extensive
> experience with C++, which is what I prefer to code in.
>
> I was wondering if for my project, I could implement an easier way
> to notate multiple measure rests.Currently, the only way to
> implement these is adding them in at the end by checking the box
> for "Create multimeasure rests" under the Style menu, or to create
> split measure rests, clicking on the start of the measure where
> you want to split, go to measure properties, and check "break
> multimeasure rest".
>
> I feel that this is very inconvenient regardless because firstly,
> this method isn't very apparent and easy to find (unless you do
> some Googling), and while it can be convenient in that it's
> automated for you, there isn't a manual setting for multimeasure
> rests either.
>
> I would like to propose implementing an additional method for
> multimeasure rests, in which you can give two inputs, the measure
> number where the rest starts and the measure number to which you
> rest, and it creates a multimeasure rest for you, and another
> where you can select multiple empty measure, and go under Measure
> Properties in order to concatenate them all into on single
> multimeasure rest.
>
> This can be a kinda picky thing to nitpick at, but I feel like It
> would make something a lot easier if you are creating a score
> based off of something handwritten, and the composer is very
> specific about measure rests, for whichever reason. I also feel
> like this way is more natural, rather than going under the style
> menu. I was surprised there wasn't a Rest option under Palettes!
>
> I hope to hear feedback!
>
> Sincerely,
> Joyce
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
>
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140_______________________________________________> Mscore-developer mailing list
>
[hidden email]
> <mailto:
[hidden email]>
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
>
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140>
>
> _______________________________________________
> Mscore-developer mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer