For printing a score (all parts on a page) you can pad the Marimba part with hidden rests,
As David said, you will have to pad the score so each measure contains the same number of "beatlets".
the music looks fine
I think what you need to do is decide where the system breaks happen, (or force them where you want them) and add a bar line at those points in all staves.
NWC can handle reasonable polymeters, but this goes way beyond reasonable. I doubt that any notation software can make sense of it.
NWC can handle reasonable polymeters, but this goes way beyond reasonable.
I take this back. NWC does not support mismatched barlines well enough to be useful for polymeter. Polyrhythm is tedious, but can usually be made to work.
I've used it to notate polymetric music with changing meters that were not a whole lot less complex than the ones in the OP's example.
Nonsense. Frybyte wants polymeter, not polyrhythm. I made the same mistake. Took an hour or so of trying to rewrite the song as polyrhythm for me to realize this.The file attached to the main topic is rather short of "looking fine." Sustain Pedals that preserve width, 'Increase spacing for longer notes', and a dearth of Spacers are not signs that you care much about how the song appears. At least you don't have staff metrics set to 26pt, although 19 rather than 18 is a curious choice.As you say, you don't post here often, but attaching a song using fonts that most of us do not have is not friendly.Sounds good, but the song attached is so bizarre that that is not possible. NWC can handle reasonable polymeters, but this goes way beyond reasonable. I doubt that any notation software can make sense of it.
NWC will not allow a beam across a barline. I suppose that if you find it acceptable to have notes that clearly should be beamed to be unbeamed, you might be able to make things work.
Attached is a simple polymeter. As of NWC 2.51a, system breaks cannot be added to it that will produce an acceptable Print Preview.
You're kidding, right? Beams across barlines are among the first thing most of us learn to use layers for.
the second example (Topic 8818 rg01b) works - as long as you add the extra sysbreak after the final bar.
I've also attached a real-world example
It's not April 1st, is it?
in view or print it's a mess and unperformable.I'm wondering if there is a work around?
Only difficulty was getting lined up bars to break the lines: LilyPond won't break in the middle of a bar, so there are some dummy bar lines. I definitely _won't_ break in the middle of a note!
How easy is it for LP to preserve the accidental state across those hidden barlines? The issue doesn't arise in Unsure until m17, so I can't tell from the pdf. I can see that the accidental problem will be different from NWC's since all accidentals are specified.
Page created in 0.043 seconds with 24 queries.