Cross Staf Beaming Bug and Tuplet Question
Hi all,
just new to MuseScore and absolutely love it. I'm teaching a subject at Music College in Belgium called "Musical Application Software". They used to teach the basics of Sibelius, but now we've switched to MuseScore and we're trying to achieve the same results.
Untill now, that all seemed possible, but as the scores become more complex, it gets a little harder :)
I'm trying to transcribe Chopin's Prelude No 14, Opus 28. A bit complex since there are a lot of "hidden" second voices, merging with the first voice in the left hand. MuseScore handled that surprisingly well, but now I'm stuck in bar three with the cross-staff beaming.
I've seen this bug being reported here (http://musescore.org/en/node/4668) on the 14the of February 2010, almost a year ago and wonder if it's still in. When I double click the beam and drag it down (as to not have the beam between the staves), the "second beam" of the 16th notes is positioned underneath the first beam (while of course this souldn't happen).
Is there a workaround for this problem?
Second question: you say the septolete in the last bar: it's made up of 16th notes. To me this seems logical, since they replace one quarter note, but all the "original" scores I've found online display this septolete as a septolete of 8th notes... While mathematically incorrect, I wonder (why they did it this way, but let's forget that question for now :-)) if there's a way I can change the 16th notes to 8th notes?
Two problems, any ideas?
Thanks in advance!
Curls
| Attachment | Size |
|---|---|
| Chopin - Original Score.png | 50.91 KB |
| PreludeNo14.mscz | 3.12 KB |
Comments
Hi already once again,
just managed to solve the last problem (regarding the septolete that should be in eight notes). Look around a bit and found out about measure operations. Changed the "actual measure" to 5/4 and made a septolete of the last two beats. Pretty incredible, don't think Sibelius is capable of doing this in such an elegant way :-)
But I'm still left with the wrong cross-beam. Would be great if this one could be solved also!
Thanks in advance!
C
In 1.0 at least, you can force a tuplet to be something other than what might musical sense using notes>-tuplets->other. If you want to cram 7 eighth notes into the space normally taken up by two, as was done in the Chopin example, you'd just enter 7 and 2 in the boxes within the dialog that appears. This strikes me as preferable to messing with measure properties for this purpose.
The cross-staff beaming still looks broken in this case, though.
In reply to In 1.0 at least, you can by Marc Sabatella
Hi Marc,
thanks for the tuplet hint, is indeed a better way of working than measure properties.
Too bad about the cross staff beam though... Any other suggestions about that one?
In reply to Tuplet, cool. Beam, still uncool :) by Curls_On_Keys
The beam one is a hard bug. It looks solved for the next major release. I will try to see if we can fix it in the next minor one.
The only ugly solution I can think about now is to hide the bad beam with a white image and add a thick line to make a normal one... but it's very very ugly.
In reply to The beam one is a hard bug. by [DELETED] 5
Keep in mind that the cross-staff notation of this example isn't the only way of depicting this passage. In the numerous traditionally engraved editions I've seen from major music publishers, it's done in various alternative ways that include (1) use of ledger lines, and (2) inserting a clef change that reassigns the lower staff to the treble clef.
I understand that if the point of this exercise is to reproduce an engraved score exactly, these alternative methods won't help you. Still, I thought it might be worth pointing out; I know from using many categories of productivity software that it's wiser to bend to accommodate the limitations of the program rather than simulate something via a workaround that's not implemented in the present feature set.
In reply to The beam one is a hard bug. by [DELETED] 5
Since cross staff beaming is not an option because of the beam bug, I tried the same trick than http://musescore.org/en/node/8717 Together with some invisible rest and notehead, I manage to engrave the measure. To have a good playback, one can change the velocity of a given note. (note properties -> velocity -> user / 0)