Mass copy-paste into empty score gives rise to "tuplet cannot cross bar..." But is it meter changes??
I am migrating my compositions originated in Finale 2016 to Musescore. I first dump to .XML from Finale, then use that to bring the score into Musescore. On my Musescore account, I have so far migrated 2 scores without any problem. NOTE: those 2 scores have NO METER CHANGES.
Files attached: "septet_homage" is the migration work-in-progress. The .PDF and .XML files came from Finale.
1) created an empty Musescore file with only a cover page and empty, throw-away measures (1 stave).
2) created empty staves in Musescore matching the instrumentation in the original score.
3) deleted the empty, throw-away measures (1 stave).
4) opened the .XML source score.
5) going one stave at a time, used Ctrl-Shift-End to mark (and Ctrl-C copy) one entire instrument's measures.
6) pasted Ctrl-V into the matching stave/instrument Musescore work-in-progress file.
This worked for 3 staves, no problem. Then I started getting "tuplet cannot cross bar" errors. I scoured the source .XML file for TIES, eliminating any obvious. The same error kept coming back.
Then I noticed that a METER CHANGE at measure 57 does NOT get propagated when Copy/Paste is used across ALL the measures of ONE stave/instrument. The attached source .XML and .PDF files have the change from 2/4 to 6/8. The attached work-in-progress file has no meter change at measure 57.
(I've tried to insert a meter change at measure 57 in the work-in-progress score. This FAILS with the "tuplet cannot..." error. So I can't repair the work-in-progress score, at least I can't see how to do that.)
Maybe this is the way Copy/Paste works in Musescore. This migration is 114 measures. I REALLY don't want to transcribe 7 instruments over 114 measures.
I'm not sure where to go... Do you savvy people think if I set up 114 EMPTY measures in the target Musescore file -- with meter changes matching the source -- this will allow the Copy/Paste to work, and then not produce the "tuplet cannot cross bar..." errors? Which MAY NOT really be the actual problem??