Best Way to Hide Systemic Barline (Only) Between Players?

I’m making some analysis examples in which I’d like to “float” a 0-line staff showing composite rhythm over piano music.

Am I correct in thinking that one can either “have it all” (in my case, piano brace + “dangling” systemic barline) or hide everything, but not anything in the middle?


Is this a case in which I’d either need to use obscuring boxes or export it to a PDF editor with the ability to edit lines? Anyone have a nifty technique for such cases?

What about high notes in another voice with hidden ledger lines?

3 Likes

Interesting idea, thanks.

My initial stab at it produced this mess:

A few details:

  • each piano staff will have (constantly) up-stem and down-stem voices, i.e., four discrete voices on the grand staff
  • I want to show stemlets above/below rests and beams grouped per ♩
  • The high voice (preferably stems-down) has numbers attached as lyrics and in several cases asterisks added as a custom playing technique

I might be notating 112 ♩s of music in this way. I’ll keep playing, but do you know readily how you might make that all work in a less-than-“forever” ( :slightly_smiling_face:) way?

Indeed, I didn’t look closely enough at your screenshots! My solution is probably far from ideal when there’s so much information going on at once…

1 Like

I appreciate your creative thinking, time and generosity, @charles_piano!

2 Likes

Here’s a new approach:

  • I zoomed to 500%
  • then slightly indented each system so that…
  • added and resized blank text frames in Engrave Mode could cover the “dangling” systemic barline

Ultimately this will probably prove easier to do in the app to which I export the slices rather than in Dorico, where I had to experiment with fractions of a millimeter for the bottom of each frame (in addition to the manual system indenting).

Still, I thought I’d add this.

1 Like

It’s possible to edit the beams in Engrave mode.

Jesper

Here with 5 voices

1 Like

I was doing a bit of that just to try it. Maybe if I started from the top down (high “floating” notes) as V1-up things would have been a bit less messy…? What are the voices in your upper staff, just out of curiosity?

Here’s the file, I had to lower the beam of the “Blue” voice 16:s in Engrave mode.

Jesper

many voices.dorico (545.5 KB)

1 Like

Many thanks, @jesele!

My instinct is that with the relative complexity of the piano music in my examples this would be rather time-consuming. Am I misguided in that hunch?

1 Like

No, you’re not, you have to edit all the beams in Engrave mode for upstem voice 1 in the treble staff. (Blue) Sorry, no better suggestion right now. Bedtime.

Jesper

1 Like

With a zero-line staff, a cutaway upbeat, and tick barlines for the zero-line staff. (I know, not very good, and better to edit the pdf)

Jesper

2 Likes

@jesele I think we woke up with the same idea — I was just doing that :grin:

2 Likes

But of course. Great minds… :grinning_face:

Jesper

1 Like

Silly me, but what about using a rhythmic cue? :thinking:

That’s the best solution @YourMusic.Pro Edit: Or not. It creates the same problem as with a voice with hidden ledger lines.

Jesper

Yeah, but this has always been an issue with rhythmic cues and really is on the team to fix…

As you can see, this goes way back, and even got a reply from @dspreadbury :

or here:

Yes, I know. Too bad.

Jesper

Just when one has gotten so accustomed to the generosity of this forum’s members, a special interaction comes along to strengthen one’s gratitude! Thank you all for the thought, effort, and time you put into this.

2 Likes

For my current project I think I’ll stick with the approach I outlined above. Manually moving system indents (3 ✕ opt + shift + arrow) for maybe 6 pages, then exporting my slices to Keynote, where white boxes can be placed to obscure the dangling systemic barlines quite easily, seems like the most efficient method at this point.

Of course, the ability to show/hide systemic barlines between players would be a handy addition for the dev team to consider for possible future implementation (feature-request).

1 Like