[Bonehead]

This app is fantastic and well thought out!!!   However ... :-)

I do not have a foot pedal so I use the automatic scrolling, and the scroll settings can't allow for things like lengthy rests so over- or under-scroll while practicing or performing.

I'd like to propose a "measure" object.  As with links, you would assign a measure location by tapping just under the staff where measure numbers normally are located.  Assuming a similar visual as link, a transparent circle, but with an assigned measure number inside it.  The measure object would have these attributes and settings:

* measure number
* size of circle -- measure # size adjusted to fit inside
* transparency (and color?) of circle
* staff height above for scrolling/visibility purposes
* tempo -- time sig and bpm -- at this measure
* GOTO 1-4 (visits) measure number -- if assigned, next measure to go to per visit # of THIS measure.  Maybe could be arbitrary visits.  This can be used to handle repeats, coda jumps, etc.

This would allow for far better automatic scrolling control with the metronome:

* metronomic scrolling based on tempo and beat count between measures
* metronomic pulsing of current measure link object
* scrolling to use staff height to smoothly scroll down to GOTO links without displaying anything above the GOTO measure staff
* scrolling always keeps entire staffs visible

[BRX]

I like that. In part because I wanted to suggest something similar but haven't so far since Mike has so much on his docket and I simply forget about it if I don't post it when I think about it.

Your suggestion is much better thought out than mine would have been. I just additionally suggest a “stay at“ feature as one of the properties for rests, repeats so the beat ticks on and the scrolling stops for the needed time (if that wasn't implied with the visits).

[Bonehead]

I like that. In part because I wanted to suggest something similar but haven't so far since Mike has so much on his docket and I simply forget about it if I don't post it when I think about it.

Your suggestion is much better thought out than mine would have been. I just additionally suggest a “stay at“ feature as one of the properties for rests, repeats so the beat ticks on and the scrolling stops for the needed time (if that wasn't implied with the visits).

Thanks.  I probably should explain a bit more.  Nothing else should be needed for rest measures.  They're just multiple measures on a staff where you don't play but "the beat goes on."  I should have also described that a best practice would be to at least have a measure link at the first measure of every line.  For forward-moving music, the number of beats is just a multiple of the number of measures between one measure link object and the next.  So if you have Measure 1 marked (you probably should but might not have to, as it's a special case being at the start!) and the next line is marked Measure 10, and you're in 4/4 time, you have 36 beats in-between (i. e., on the first line).  Doesn't matter if there are rests.  :-)

The GOTO directive might seem a little odd having to be assigned at the next numbered measure after say a repeat so the beat goes through to the end of the measure with the repeat sign.  So, like this:  | x x x x : ||  (36) -- sorry, don't have a circle!  Measure 36 is after the measure with the repeat (four beats) and it MIGHT be on the next staff line.  Awkward but it should be workable.

What probably *should* be added to the original are niceties such as a configurable "pause" for fermatas and such.  That also might allow for ritardos rather than the complexity of having to fiddle with the actual metronome beat.