copy/ paste trouble

• Jul 7, 2014 - 15:55

Writing a score in 9/8 with multiple instruments. When I copy/ paste the new copy is not same as orig. Notes overlap measures, there are wrong rests in measures, one measure copied with no rests and musescore won't let me write in it. Some notes are tied whereas they were dotted. Does anyone know what's going on?


and also check the nominal and actual durations in measure properties. (Right click on an empty spot in a measure to access measure properties.)

Be sure you are pasting the copied 9/8 measures into measures having the same time signature and/or measure durations.
Posting the score itself (or the problem section) would be the best way forward.


In reply to by john brady

I'm here again...55 meas into piece and copy paste is again malfunctioning the same way...incorrect measures of time, ties where there were none, note values overlapping different measures. I don't know what to do about this. Also, when I save this to PDF, it doesn't save the whole page. Part is cropped off.

In reply to by Marc Sabatella

Thanks. The partial score is posted in my profile. I've since redone it but need to know what happened. In that score, I selected the first note in piccolo (I think it was a rest), shift+select last note in bassoon. Now all is blue outlined, hit copy. Move to blank meas. to paste and hit paste. That was my process. This score was to work thru the beginning accompanying notes to a movement and I've now redone it on another score. I had a similar problem there but found that, if I transfer the parts one at a time, it works ok. I don't know why. Thanks for your help.

In reply to by john brady

Well, it's pretty obvious just from looking at the score that it is already corrupt - lots of measures with wrong number of beats. I can't say how that happened, but indeed, most of the things I've seen that lead to corruption involve copy and paste. Usually somthing complicated - irregular meters like 5/4, multiple voices, triplets pasted across barlines, etc.

In reply to by john brady

Once it happens - once the score is already corrupt - it's too late to start thinking about avoid copy & paste. If the score is corrupt, it is because some *previous* copy & paste operation corrupted it. All you can do at that is completely delete the corrupt measures, insert new ones, and re-enter the content.

As for avoiding corruption, copy & paste is normally safe. Hard to say what went wrong here. I don't offhand see any of the things that I know have caused corruption in the past.

In reply to by john brady

No, I mean, in the corrupt score, delete the corrupt measure itself. Not the copy you made of it, but the original corrupt measure. And not just delete the *contents* of the measure, but the entire measure (Ctrl+Del), which is why you then need to insert a new measure to replace it. The new measure will not be corrupt. If you delete all corrupt measures in this way, you can save a score that is already corrupt.

I have this exact same problem from time to time when I'm creating the main score for a complete wind band with around 25 instrument types.

There seem to be nothing wrong with the measure properties as you can see at:…

These errors appear suddenly after using copy and paste from one instrument to other instrument. And sadly cannot be undone/ solved - or I haven't find out yet…

It's very frustrading when arranging such a complete score. For me it not a solution to delete the corrupt measure because very often I already created a couple of staff lines ahead for other instruments. And what I found out is that the problem most of the time comes from a measure in front. Somehow this one seem to mess-up the amount of time in one of the next.

At the moment I duplicate the instrument and copy & paste the good part, after testing which measure is making trouble. Finally delete the old staff and continue again. Not ideal because you cannot copy stuff like dynamics, lines etc.

I hope this issue of musescore will be solved one day, or does somebody know a better solution?

In reply to by bmvkelderman

I don't understand what you mean about deleting the corrupt measure not being a sooution. It does work, whether you've created a music in subsequent measures or not. You do lost the content of the *current* measure for other instruments, so maybe that's what you mean, but you can always re-enter it. Should usually be a *lot* less work than that what I think you are describing as a workaround.

Anyhow, assuming you are using MuseScore 1.3, I would say "most" of the known causes of corruption have indeed been fixed for 2.0. But no doubt some remain and new ones have probably appeared. Meanwhile, if you want to see such problems fixed, the best thing you could possibly do is help us figure out what led to the problem, and if you can find a way to reproduce it on command, post the score and the steps to reproduce.

In reply to by Marc Sabatella

Hi Marc,

As mentioned before the problem is that the "corrupt measure" is not always the trouble maker.
Especially when you have whole notes in more measures, you cannot see it directly.

Re-enter 25 instruments with all specific dynamic, notes and relations with measures in front or after etc. is for sure more work comparing to creating a new instrument and copying a part of a staff.

But I'am glad you proposed to try 2.0 and will do so, thanks.

I find I've got to delete the whole copy/ paste and redo to new measures, usually be writing the individual notes. To re- copy/ paste seems to just duplicate the problem. I haven't seen that any certain 'consistent action' leads to this problem e.g. when I do such and such, the corruption happens. I'm also noticing that in my last movement of this piece, when I delete and then re- enter a different note, it sometimes doesn't sound on playback. To get it to sound I've found that I can usually put a dynamic loudness marking at the new note to get it to 'play' and then remove the marking later. The movement is over 15 minutes long and for full orchestra and I'm wondering if this is somehow a function of size?

In reply to by john brady

Size itself wouldn't be the problem, but whatever the problem is, the bigger the score, the more likely it will contain whatever it is that *is* the problem.

If you are using 1.3, I can tell you that copy and paste involving tuplets and/or multiple voices were biggest sources of corruption. in my experience. Not that *all* copy & paste involving these things would cause corruption, but various specific cases involving on or the other or both.

Do you still have an unanswered question? Please log in first to post your question.