Saving segment positions with MuseScore 3 leads to elements with sx attributes being mostly 0
Steps to reproduce:
- execute musescore export job with .spos as target
- sx distance is always 0
Original thread: https://musescore.org/en/node/307253
I actually had feedback by mail from the original user complaining about it and am waiting for a file 'without the issue' to check what is expected. Also have a copy of their code exploiting the data (end of https://musescore.org/en/node/311914 )
But I'm pretty sure the line computing the sx value as: "sx *= ndpi;" coupled with an issue in the voice related algo above would be the region to watch for fix. https://github.com/musescore/MuseScore/blob/3f4894ec3f734f4af6f720195f6…
Will try to fix/pr today.