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??
Much appreciated!
| Attachment | Size |
|---|---|
| septet_homage.mscz | 44.61 KB |
| septet_homage_to_older_music_3m_20s.xml | 913.48 KB |
| septet_homage_to_older_music_3m_20s.pdf | 216.39 KB |
Comments
I downloaded your xml file, then simpy opened it in Musescore. The formatting needs a bit of work, particularly your explanatory introduction, but everything seems to be there and playback sounded convincing.
In reply to I downloaded your xml file,… by Brer Fox
Why the HECK didn't I do what you did??? I did the same, changed all the instruments over to a different .SF2 soundfont, all works great!! Thanks alot for a KISS example.
I do get the desire to copy/paste from an imported score to a fresh one, to be sure you are starting with completely "fresh" defaults. But sometimes it's just not feasible or worth the effort, and scores that include time signature changes or other things that don't copy are going to be problematic. Any reason to not just work directly with the imported score rather than messing with all this copying?
But if you do for what reason choose to do the copy, then yes, best to set up all the meter changes before doing the copy/paste. Even without the tuplet issues, also, your note values will be off if you don't do this. Consider, notes that should have fit within a measure will likely now be broken up with ties across barlines, and fixing the time signature later won't undo that. So even without tuplets, it's just not a good idea. And then, tuplets just make it flat out impossible to do the copy in the first place unless you get incredibly luck and they all just happen to fit within the wrong measures as well as the right ones. So definitely set up the meter changes first before attempting a copy.
And also, when you do the copy, no need to laboriously do each staff one at a time - just Ctrl+A to select all and copy it all at once.
In reply to I do get the desire to copy… by Marc Sabatella
(Marc Sabatella) Any reason to not just work directly with the imported score rather than messing with all this copying?
I took the exceptionally long, tedious way. As (Brer Fox) pointed out, it worked fine with the least migration labor.
(Marc Sabatella) But if you do for what reason choose to do the copy, then yes, best to set up all the meter changes before doing the copy/paste.
I will definitely remember this. Thanks!
(Marc Sabatella) And also, when you do the copy, no need to laboriously do each staff one at a time - just Ctrl+A to select all and copy it all at once.
This ALSO I'll try, and remember. I've got maybe 23 scores to migrate. I got so absolutely fed-up with Finale and their constant paid-upgrade path, MuseScore is turning out to be a God-send.
Much appreciated both you guy's quick help! I wish I could email you your favorite beer or pizza.