Beam problem
I can't manage to get beams between the pairs of notes as in the original printed music below. I think the problem stems from the fact that the beams start from half way through the beat. I've attached the original measure, and my best kludge in MuseScore, where I replace one of the beams by a slur. Any suggestions?
| Attachment | Size |
|---|---|
| serenata_beam_original.png | 63.17 KB |
| serenata_beam_ms.png | 9.99 KB |
Comments
See http://musescore.org/en/handbook/beam
In reply to See by Jojo-Schmitz
Thanks Jojo, but I had read that. It seems like one should be able to do it, but I can't. Can you actually do it? I don't think you need the mscz, but fwiw, It's measure 37 in the file at:
http://musescore.com/user/142755/scores/170844
The only way I can do it is a kludge: add a 2nd voice with the two problematic chords in it, with rests everywhere else. Then set the rests invisible. The beam works fine in the second voice, without the adjacent notes that cause problems.
These days I avoid kludges and cleverness (in programming, MuseScore, everything). If no one can show me how to do it with the official mechanisms I'll use the workaround in the png I attached in the original post.
In reply to Thanks Jojo, but I had read by MikeN
I assume it's only the over-the-bar beam you are having trouble with - the rest work just fine following the instructions in the Handbook. Unfortunately, that'a limitation in the current version of MuseScore; certain over-the-bar combinations don't work, and that includes one where you are trying to beam to only a single note at the end of the previous bar. You could probably fake it using multiple voices if you needed to. Looks like this is fixed for 2.0 - see #20648: beaming across barline not working under needed circumstance.
Ah, it seems you can either have the 3rd and 4th note beamed or the 5th and 1st of next measure or have a beam over all 4 notes
In reply to Ah, it seems you can either by Jojo-Schmitz
Yes, that's what I found, Jojo.
I downloaded a nightly just now (mar 18) and I could put the beams exactly as I wanted. Thanks for that suggestion, Marc. I often find "beam start" and "beam middle" a little tricky at first, but with a few clicks it works.
However, I'll wait till a stable 2.0 comes out, as there were funny things happening (piano staves jumping from 3 cm apart to 8 cm apart, text changing size from very small to large) as is proper for a pre-release...
Thanks for your help and suggestions.
In reply to Yes, that's what I found, by MikeN
Right, I definitely would be recommending 2.0 releases to actually *use*. But it's worth playing with. And if you find issues, reporting them. My guess is the first issue is a simple misunderstanding - MuseScore now supports the idea of minimum and maximum distance between staves rather than the old system where it was either minimum or they were fully stretched to fill the page. As for text, there are currently some fairly major changes in text handling underway, so what you are seeing is probably a side effect of that work not being completed. but it doesn't hurt to report anyhow. Ideally, separate threads for each issue, int he Technology Preview forum.
In reply to Right, I definitely would be by Marc Sabatella
Marc meant to say "Right, I definitely would NOT be recommending 2.0 releases to actually *use*. But it's worth playing with."
I've been using it a lot for the past few days and it's getting quite good, much more stable.
In reply to Marc meant to say "Right, I by schepers
Ouch - bad typo on my part!
Yes, things had been looking good, then destabilized a while while some fairly significant changes were introduced, but now they are indeed stabilizing again.