How to change bar numbers?
Hi there, I'm doing an analysis on a vocal solo for uni but my score starts halfway through the actual song so I want to start the score from bar 30 or around abouts so the first bar will say 30 but it won't let me. How do I do it?
Thanks in advance,
Harry
Comments
"Add to measure/bar number" in the properties for the measure/bar: https://musescore.org/en/handbook/measure-operations#properties
In reply to "Add to measure/bar number"… by jeetee
What'd be nice is that this "Add to measure/bar number" instead of making the bar "3" becoming the bar "4" (and labelled accordingly)(with Add to measure/bar number=1) it counts the bar "3" as being "3-4" so that it keeps labelling bar "3" as "3" and the next bar becomes bar "5".
In reply to What'd be nice is that this … by parkingb
You'd get that effect by not changing bar 3, but adding 1 to bar 4 instead, wouldn't you?
In reply to You'd get that effect by not… by jeetee
Indeed. But... my point is more about semantic than technicity.
If, e.g. One merge two bars (3+4) in order to have a cross bars tuplet, then semantically it is bar 3 that must count as 2 bars. Today it counts as 1 one bar but one to tweak the bar 4 by moving it one 1 bar.
Meaning that if you for any reason work in some bar, you must reflect that impact in the next bar. And not in the bar causing the effect.
In OO programming, I'd write:
bar(i).startIndex=bar(i-1).endIndex+1
bar(i).endIndex=bar(i).startIndex+bar(i).length
In the current situation
bar(i).startIndex=bar(i-1).startIndex+bar(i).addition
bar(i).endIndex=bar(i).startIndex
In reply to Indeed. But... my point is… by parkingb
I understand, but I wouldn't base the common terminology or behavior of a feature on the fact that it can be used as part of a workaround of a different issue (not supporting cross-bar tuplets).
Where the OOP comparison misses the ball is that it assumes
endIndexis an actual property, while it is not.As for tuplets crossing barlines, often other workarounds are possible as well, which don't require the merging of a bar, such as the one here:
https://musescore.com/user/2605606/scores/7725047
In reply to I understand, but I wouldn't… by jeetee
Those merged bars aren't indeed easy, because they can't be copy/paste easily.
![4-3tuplet.png]( "4-3tuplet.png")
However, I tried your trick with my own case and (although I'm pretty creative) I couldn't manage to apply it to my tuplet:
I want to write that 4:3 tuplet on the eight from the 1st bar and the quarter of the 2nd one?
In reply to Those merged bars aren't… by parkingb
It all comes down to math in the end ;-)
1) You need a common base duration that'll allow you to make equal subdivisions across the 3/8th range and regroup them in the 4:3 ratio. For you this means you need 12 equal subdivisions; 4 before the barline and 8 after, which each resulting end note taking up 3 of those subdivisions.
2) All that is then left is some tuplet ratio hocus pocus to make the displayed durations you want (1/8ths and the 4:3 ratio marking)
https://musescore.com/user/2605606/scores/9001460
In reply to It all comes down to math in… by jeetee
8-O
Thanks for spending some much effort on this point... But I don't see me spending so much time for every cross-bar tuplet I want to write. Let's imagine I change me mind in the tuplet's duration, form, ... What a rework... I think I'll keep merging bars when necessary (with the disadvantages of it) until MS4/5/6 allows natively for cross-bars tuplets.
(BTW I really like the way you're presenting your examples. I'll reuse this if I ever need to help someone or demonstrate something)
In reply to 8-O Thanks for spending some… by parkingb
Now you've got me wondering about whether the mathematics model for this could be made into a plugin which perhaps could do the "heavy lifting" for these type of tuplets.
You'd be required to select the range (total real duration), the ratio and quite possibly the smallest subdivision you'd want enabled (to ensure the crossing tied note gets the intended written duration).
In reply to Now you've got me wondering… by jeetee
I'd be a nice plugin indeed. However, sometime I wonder if the time spent a building plugins (like my DurationEditor, that took me a hell of a time) would not be better spent at bringing those functionality natively in MuseScore.
In reply to I'd be a nice plugin indeed… by parkingb
In this case, it might.
For TempoChanges for example, the plugin was more of a "bring this sooner" attempt combined with a faster testing cycle.
If one can invest the time to make it natively, that should be preferred imho; but it is an eternal trade-off between available time and effort...
In reply to Indeed. But... my point is… by parkingb
There is another method of modifying bar numbers which may be more appropriate for this use case. You can tick "Exclude from bar count" in the measure properties of the second of your merged bars. That seems to satisfy both the technicity and semantics. It also better reflects what you are doing. If you merge two bars to appear as if they are one, then only one of them should be taken into account in the numbering.
In reply to There is another method of… by SteveBlower
At the contrary, I'd like to have the merge bars appear as 2 bars. Because they are merged just in order to be able to write the cross-bar tuplet.