Logic Pro Bug in cross-staff beaming combined with clef changes?


I have used the very useful information here to add cross-staff beaming to a 2-staff piano part. Today though I ran into what seems like a bug. I have a measure in which I split the part between the staves and beamed them for clarity, and at this point I am partway through moving the notes to the lower staff:
Screenshot 2024-06-16 at 9.58.18 AM.png

Because most of the notes are above the bass clef, I added a treble clef as shown - but it is ignored! If I click on the notes in the left hand, I get C3 and F1, respectively. I then tried to move the treble clef to a better location after the C2-natural in the left hand - but Logic will not allow me to place the clef *anywhere else* in the bar!
Is this some odd order-of-operations issue, or just a bug?
Closely related to this is that if I select the F4 and C#4 in the third beat and use the command to move them to the staff below, nothing happens.

Much appreciated!
1) I now understand that if I hide the LH staff rests in the Staff Style, I can place my own quarter-note rest above, and then the clef change after that. BUT, the clef does nothing (the notes following it do not change location).
2) I see that for the third beat, the notes are *already* cross-beamed. The problem here is the same as (1) - treble clef ignored.

As a retired programmer, I would guess this is because the cross-beamed notes "belong" to the RH staff, and the LH clefs are therefor ignored.
Upvote 0
This was the result of choosing to move the selected notes to the staff below the voice. You can see that the lower staff is set to treble clef, but the notes are mapped in as if that staff were still in bass clef.
Screenshot 2024-06-29 at 10.10.35 AM.png
Upvote 0
I did a quick test - I had no problem adding a treble clef in the left hand staff, and the notes relocated correctly (Logic 11.0.1). However, when I go through the process you linked to, I get the same ignoring of the treble clef - or any clef for that matter. My guess is the coding is not set up for this, it expects notes of the left hand to be lower.
- Doug
Upvote 0
Workaround for this is to chop the region and duplicate/create a new staff style with the required clefs (would still need to hide rests in staff style). You are correct in post #2 above: staves are unaware of one another: accidentals, rests, clefs etc. so as far as cross-staff notation goes in logic, best to think of it like pencil and paper where you have to manually check and notate accidentals. See below: new region with clef change where all notes C# but lower stave requires missing accidental to be added manually…
Screenshot 2024-07-09 at 11.31.51.png

However, one major problem with this workaround is that it won't work mid-beam…(see below)
Last edited:
Upvote 0
Incidentally, the chop/change region/staffstyle method is the Swiss-army-knife workaround for many logic issues BUT problems arise when score items span the region break e.g. tied notes (or even mid-note in a polyphonic staff), 8ve higher/lower lines, slurs etc. Usually all can be fixed using workarounds but some situations (e.g. mid-beam cross-staff clef change ) will require muting display notes and having hidden playback notes, so at a certain point it may seem not worth the trouble…

So this is a MAJOR candidate for a score editor feature request i.e. the ability for successive regions to "see into" and effect one another e.g. should be possible for a score item (like a tied-note, 8ve line, slur etc.) to extend into the next region.
Last edited:
Upvote 0