You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a simple example from a score (string quartet template). The rests, accent and stave text all have X and Y offsets applied:
Here is the Violin I part:
Note that:
X and Y offsets to text are reset
X and Y offsets to rests and articulation are SCALED to the new stave size (score size/part size, in this case 1.3/1.75, so scaled by a factor of 0.743)
The former I can accept, at least for now (the position of text may need to be changed anyway, with possibly different text sizes and radically different layout etc) but the latter makes NO sense. The offsets of items directly attached to notes, or to rests (which need to have specific positions on the stave) should not change!
I haven't tested yet all types of item to see how their behaviour may differ.
It turns out this isn't about generating parts per se: it happens whenever the spatium size is changed (which will often happen when parts are generated).
Platform information
This is in MU4, but the behaviour is inherited from 3.6 or earlier.
The text was updated successfully, but these errors were encountered:
oktophonie
changed the title
[MU4 Issue] Nonsensical behaviour of offsets when generating parts
[MU4 Issue] Nonsensical behaviour of offsets when changing stave size
Jan 22, 2023
Describe the bug
Here's a simple example from a score (string quartet template). The rests, accent and stave text all have X and Y offsets applied:
Here is the Violin I part:
Note that:
The former I can accept, at least for now (the position of text may need to be changed anyway, with possibly different text sizes and radically different layout etc) but the latter makes NO sense. The offsets of items directly attached to notes, or to rests (which need to have specific positions on the stave) should not change!
I haven't tested yet all types of item to see how their behaviour may differ.
It turns out this isn't about generating parts per se: it happens whenever the spatium size is changed (which will often happen when parts are generated).
Platform information
This is in MU4, but the behaviour is inherited from 3.6 or earlier.
The text was updated successfully, but these errors were encountered: