creating a second layer
Please forgive the newbie question, but there's something very simple I'm trying to do that I can't for the life of me figure out how to manage.
I just installed MuseScore for the first time, and my first project is to produce a usable choral score from a MIDI file produced by another program. I imported the MIDI file and started making adjustments (beaming, accidental choice, and so on) and everything was proceeding pretty smoothly.
However, one of the things I want to do involves adding a second layer, consisting of a quarter rest and a quarter note, to an existing 2/4 measure containing a half note. The measure contains a time signature because the piece changes signature almost every bar. When I try following the instructions given in the tutorial and the handbook for going into note entry mode, the insertion point is set to the previous barline, and the new notes are inserted before the time signature. I can't for the life of me figure out how to get the notes to be inserted after the signature, or alternatively how to move the signature back to the start of the measure after the notes are entered. It's driving me sort of nuts. What am I missing?
I'd appreciate any help anyone could give.
Comments
Try this:
1. Drag a 2/4 time signature to an *empty* measure (e.g. where you want the time signature to change to 2/4). The measure should display a half rest (empty).
2. Click on the half rest (turns blue), press N to enter note entry mode. The (blue) cursor should appear *after* the 2/4 time signature but *before* the half rest.
3. Enter the half note - e.g. press 6, then C to enter a C half note.
4. Read about 'voices' (you call them 'layers') here:
http://musescore.org/en/handbook/voices
You must enter both the quarter rest, by pressing 0 (zero), and the remaining quarter note as a different voice. The cursor in note entry mode will change color depending on the active voice.
5. While in note entry mode, you can move the cursor backward/forward using left arrow/ right arrow.
If you need further assistance, please mention what version of MuseScore and what operating system you are using.
Attaching the MuseScore file (.mscz), or an excerpt showing the actual problem, is also the best thing you can do for 'custom tailored' help.
Regards, and welcome aboard.
In reply to Try this: 1. Drag a 2/4 time by Jm6stringer
Thanks for the reply. I had tried most of the steps you mention, without success. What finally worked was to abandon the file entirely and reimport from the MIDI file. After this the voice editing tools worked as documented and I was (more or less) easily able to do what I wanted.
I suspect that something I'd done while editing the file the first time through put the file (or the software) into an odd state that caused the voice editing tools to misbehave, but I don't think I'm up for taking the time necessary to try to reproduce the problem. If it crops up again I'll preserve the file and upload it as you suggest.
In reply to Thanks for the reply. I had by ghicks
If you enter notes into a voice other than the default (1), then delete the notes, then delete the rests that are created when you delete the notes, you get "holes" in your score that cannot easily be filled again. Perhaps that is what happened. Anyhow, glad you're up and running now!
In reply to Thanks for the reply. I had by ghicks
Good work!
If you are using MuseScore 1.3, be aware that in some instances scores can become corrupt. Copy/paste of triplets and/or different time signatures in a score can sometimes be problematic. Oftimes one can just insert new measure(s) and delete the corrupted section.
Also, for your information, bugs will no longer be fixed in MuseScore 1.3. All new development is geared toward MuseScore 2.0, which is currently in its second (and hopefully last) beta release.
See:
http://musescore.org/en/node/42051
and
http://musescore.org/en/handbook/comparison-stable-prerelease-and-night…
So, if something consistently (i.e. reproducible) goes wrong in MuseScore 1.3, give the beta version a try to see if the bug is fixed in the new version.
Regards.