Beam direction forcing not reported
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
Le forçage des sens de hampes n'est pas toujours reporté : elles
restent vues en automatique alors qu'elles sont forcées haut ou bas
(dans les ensembles de notes seulement, je crois)
In groups of notes, especially in scores coming from music scan or when you copy/paste between different clefs, the direction of beams stay forced but it's not reported into the inspector. If you force them again (with x for example), it still stays not reported.
Comments
Title talks about beam direction, text about stem direction, so which is it?
oops, i swear I read stem ;-)
What do you mean by 'stay forced', not automatic? That much is by design.
What do you mean by 'not reported by Inspector'?
I suspect confusion between beam and stem direction is the actual issue here. Right now, stem direction is ignored for beamed notes, the beam direction wins. Manually setting a stem direction will work only because it forces the beam to the same direction.
For me, then, this all works exactly as designed. If I force a beam up (by flipping a step), the Inspector does report the beam as being up (and the stem still as auto), and if I copy/paste this, I get exactly the same in the copy.
MusicXML is different because it does contain forced directions that may well be ignored. That is, if they conflict with each other, one will win, and the winner gets transferred to beam, at least it should.
If you have a specific case where you beleive there to be a proble, please attach the score and steps to reproduce. If it involves MusicXML import, please attach that file.