treat Rehearsal Mark string as Marker for "Jump to", "Play Until", "Continue at"
If rehearsal marks are already present, but want to add jumps to those rehearsal marks, then currently must add a Marker, name it, and set it to invisible (so doesn't overlap with rehearsal mark already present).
Alternativley, one can change the text style for "Repeat Text Left" (which is used by segunos/codas) to be identical to that of "Rehearsal Mark" style (so they have the same box and alignment), and then I can simply just use segunos for reherasal marks and change their text to what I want for rehearsal mark.
My feature request is to simply allow the text of Rehearsal Marks to be treated as a Marker which can be specified as the "Jump to", "Play Until", "Continue at" strings of Jumps.
Comments
interesting idea, this would basically turn rehearsal marks into markers, where the marker's label would get derived from the rehearsal mark's text.
Could actually even get extended to measure numbers.
Yes & yes. It would be nice to just type the measure number or rehearsal mark without any special tag character like # or $. Hopefully rehearsal marks arent named with a number and custom seguno names dont conflict with rehearsal mark names, but any naming conflicts could be resolved with priority of actual segunos, then rehearsal marks, then measure numbers.
How do we handle duplicated rehearsal mark and measure numbers?
Just have some default and document, like "Jumps to nearest" or "jumps to the farest" (I'd take the nearest for measure numbers and farest for rehearsal marks, as a 'resequence' then might still work). If that is not wanted: Garbage in Garbage out.
I would think duplicate rehearsal marks would be handled by the same internal logic that duplicate markers are handled. For instance, if I put two segnos in a chart, musescore currently labeles them both by the string "segno", and when playback reaches a D.S., musescore seems to by default jump to the first segno.
Regarding duplicate rehearsal marks, my other feature request would help the user notice them as being problematic, if those string get treated as invalid markers: https://musescore.org/en/node/67211 "Invalid strings for "Jump to", "Play Until", and "Continue at" should report error and/or displayed Red"