Thanks for testing. On which version of MS did you fail to reproduce the issue? Maybe some code was updated that deprecated this problem since 3.5 and we can close it?
3.5.0 currently reside on my machine still, but an old 3.4.2 checked quickly with a new piano grand staff + placement of fretboard diagrams + export to uncompressed musicxml + opening of that file results in no diagrams.
Update: Tried this on 3.6.0 and I too didn't have a problem, so it looks like this was solved somewhere between 3.5.x and 3.6 and should be closed (PR wasn't linked with any code updates at github.com)
Comments
Relates to #270643: [EPIC] MusicXML import/export issues
Please attach an example file, the issue does not reproduce for me.
In reply to Please attach an example… by Leon Vinken
Thanks for testing. On which version of MS did you fail to reproduce the issue? Maybe some code was updated that deprecated this problem since 3.5 and we can close it?
3.5.0 currently reside on my machine still, but an old 3.4.2 checked quickly with a new piano grand staff + placement of fretboard diagrams + export to uncompressed musicxml + opening of that file results in no diagrams.
Update: Tried this on 3.6.0 and I too didn't have a problem, so it looks like this was solved somewhere between 3.5.x and 3.6 and should be closed (PR wasn't linked with any code updates at github.com)
3.5.0 is outdated since quite a while, there 3.5.1, 3.5.2, 3.6 and, as of yesterday, 3.6.1
3.6 currently (end of Jan 2021) performs the export/import task without issue.
See #303623: Fretboard diagrams are not exported to MusicXML ?
But also #316504: [MusicXML import] [3.6.0 regression] several strings are incorrectly shown as unplayed
In reply to Thanks for testing. On which… by worldwideweary
I tested on 3.6.0.
Fits the closed issue which claims it fixed in 3.6.0