I can't reproduce this in a currently nightly, but it might depend on more specifics. Please attach your actual score we can verify if the problem still exists. And if so, then please report it on GitHub.
I think this is an issue already present in MS3. It ocurrs when in the Inspector you set a high number (> 1) in the Spread of the arpeggio. It´s very clear when you set a number bigger than, say, 5. That´s why I posted -with no answer- this: https://musescore.org/en/node/335053.
Comments
I can't reproduce this in a currently nightly, but it might depend on more specifics. Please attach your actual score we can verify if the problem still exists. And if so, then please report it on GitHub.
In reply to I can't reproduce this in a… by Marc Sabatella
I think this is an issue already present in MS3. It ocurrs when in the Inspector you set a high number (> 1) in the Spread of the arpeggio. It´s very clear when you set a number bigger than, say, 5. That´s why I posted -with no answer- this: https://musescore.org/en/node/335053.
If I´m wrong put the blame on my bad english.
here is the file i've been working on, I re-wrote the song without the arpeggios so they do sound a little out of place.