Strange selection bug after MusicXML import
After importing a MusicXML score generated in SmartScore 64, I noticed that 50% of the measures were selecting as partial ranges (e.g. I click on a single measure and it also selects the start of the next measure).
I am not sure if this is related, but due to an inability to accurately read tuplets and tremolos, SmartScore often increased the measure duration in order to accommodate notes (which I am correcting in Musescore).
This is a minor nuisance, as it interrupts the parts of my workflow involving operations to entire measures (e.g. repeat, ties, etc.)
Comments
I figured it out.
SmartScore 64 created mid-measure barlines that threw off Musescore's measure calculations. Deleting them and fixing the note/measure mismatches fixed the issue.
Could you attach an example MusicXML file produced by SmartScore that illustrates the behaviour ? That would assist in providing a structural solution in MuseScore.
In reply to Could you attach an example… by Leon Vinken
Here is the xml import from SmartScore. Please keep in mind that I did a lot of clean-up after importing it into MuseScore.