The actual bow symbols are to be shown in the plugin's window rather than added to the score, aren't they? The text codes are just for development purposes. It's a pity that the plugin API does not give easy access to the relevant slur info so I'll have to code the workaround suggested by @elsewhere a few days ago.

Pizz/rest will be easy to fix but pedal I don't understand. Which bowed instruments have a pedal? (Maybe cello?) Is the pedal pressed instead of bowing a string or at the same time as bowing? Does it change the bowing direction?

I have just downloaded the score and the instrument appears to be piano rather than any bowed instrument. Am I missing something?

My results with articulate3.mscz do not match yours!

Good to know.

Just to clarify, in violin music, a slur by definition means ‘no bow change’.

Hi. I am back with my string-playerness :P
Bowing markings can be put inside a slur to indicate a smooth change of direction so that one would not run out of bow. This would be hard to program I think, but basically a bowing marking within a slur would interrupt and divide the slur at a given point.

Did some more tests:
onRun: {
console.time("109");
//var info = SymId.stringsDownBow
//var info = SymId.stringsUpBow
 var info = SymId.sixStringTabClef

    console.timeEnd("109");
    Qt.quit();
}// end on Run

Each of these info lines takes 5 sec on the first run, 0 sec thereafter. It must relate to reading something into memory, but 5 sec is an awful long time. The sixStringTabClef item is early in the table but does not run faster. Maybe we should ask Jojo Scmitz what he thinks about this...

Ok… who is an admin user? (Maybe we could leave that one up and make a new one for every x.x.0 major version?)

Updating on change is actually easy using onScoreStateChanged but switching it off is tricky. Recursion also has to get dealt with since the plugin can make score changes, (adding d,u,r), which triggers another onScoreStateChanged!

See https://musescore.org/en/node/364953
and https://musescore.org/en/node/320673#s43

Even after a plugin is closed its onScoreStateChanged continues to fire, presumably because the plugin engine is always running as a background process.

0.6.2 Adds dockable plugin, onClick bowing UI update and replaces d/u texts with down/up symbols.
I know why the bowing goes wrong after slurs and I need to redesign the slur retro fit algorithm to fix it.

Bowing 0.6.2.qml

Same. It appears to be working now. Maybe something like that happened. Would be nice to know what it is though.

Linked TAB causes problems and I have seen this in a score which was sent to me by email.

Random working/not working is like those pesky intermittent car faults which can be such a nuisance.

A very useful plugin. Thank you very much yonah_ag

Re: Wondering, was it only linked staves that caused the issue? Not unlinked staves?

It was both unlinked staves and linked TAB staves but they needed different fixes in the MusicXML.

(1) Unlinked staves generate separate parts with each part being a contiguous block of xml tags. The plugin's regex processing finds the end of the of the first part and deletes all further tags.

(2) Linked TAB scores are completely different as the TAB notes are mixed in with the standard notes rather than being a separate part. Measure 1 of standard notation comes first, followed by the same measure but in TAB; then measure 2 of standard is seen, followed by measure 2 in TAB - and so on, alternating through the part.

This apparently simple plugin turned out to be much trickier than expected. If I started this project over again I would do the whole mapping in a single pass of the MusicXML instead of making 2 partial maps and then knitting them together. Such is hindsight but it's been an interesting learning experience.

I'll wait a couple of days in case any other issues surface before releasing v1.0.

I recommended flashing or highlighting the bow direction symbol when the tracker shows succesive “same bow directions” within a slur. You opted to switch color with every stroke. This means that a down bow or up bow could alternate colors. Unfortunately this has the Stroop Effect on me (explained below.)

Wondering if you can assign a single color or all Down strokes and a single color for all Up strokes.

So then, on showing successive notes within a slur, possibly do one of the following:

• briefly show no stroke symbol, then show the current stroke symbol
• briefly show the stroke symbol at the same color as the background
• briefly show the stroke symbol with opacity (alpha transparency) = 0%
 

The Stroop Effect

The Stroop Effect (aka Stroop Test or Stroop Task) uses two basic challenges to illustrate conginitive interference.

When presented with an image like this:

    
... the person taking the test is to:

         a) go through the list naming the color of the font (i.e not say the written word)

          — or —

         b) go through the list saying the written word (i.e. not say the color of the word)

Yes, it could. The only proper fix is to process the score's jump structure.

A possible workaround could be to detect jump destinations which have no bowing symbol and add a red text to show that a bowing symbol is required. The user would then need to replace the red texts with the correct bowing symbol, (which could be set to invisible), before the mapping is marked as ready. As a consequence, the mapping process would need to detect these red texts so that it doesn't add another one where one already exists - although this could be seen as a 'feature' to draw attention to red texts which the user missed.

I'll go with that.

Can a score have a maximum of 1 coda?

Agreed. I thought of this cruel twist early on, and think I posted on it: An odd number of strokes within a repeat indeed produces the opposite bowing on the repeat pass .... assuming there's no explicit bowing indication to overcome it. That reality is bluntly paradoxical, like: "Everything I say is a lie. I'm lying."

Nevertheless the Bow Tracker plugin is still enormously helpful, and it could advertise itself as accurate only when repeat structures contain an even number of strokes.

Possibly the plugin could post an alert on "odd stoke" repeating situations—which could be quite helpful as it could may indicate a scorist's error!

Calculating forward, as if there was no repeat, would seem to be the only solution.

‘Fine’ at the very end does not make any sense. It is used in DC al Fine or DS a Fine. But I cannot imagine it would influence bowing.
If everything works fine I would still test an arpeggio & a slur into endings (voltas) (as mentioned above)
See https://musescore.org/en/handbook/3/repeats-and-jumps#first-second-endi…

Also need to comment out fid.write at line 313

I'll keep my eye on that! I think I've switched scores, mapped, and found the results were incorrect until I closed and reopened the plugin and then generate a new map.

It could be handy to have an "Auto-mat" checkbox, so the plugin:

a) produces a new map on score change (of course this presumed that the plugin can detect score change.) And remapping can't hurt, right?

b) possibly produces a new map when the plugin first opens

scorster