Re: Midi block gives errors with bar number checks

[Nikolai Hedler]

For what it's worth, I'm one of those users who makes use of the MIDI
output from LilyPond frequently, and while I have not needed to mess with
bar numbers on the MIDI side, I have found it's repeat support serviceable
aside from D.C./D.S. being unsupported. Unfortunately, in my current
project, I'm unable to use your trick of making separate blocks and
assembling them differently in the MIDI score than in the layout score.

- Nikolai

On Wed, Nov 27, 2019, 04:51 Martin Tarenskeen <address@hidden>
wrote:

>
>
> On Wed, 27 Nov 2019, Peter Toye wrote:
>
> > I'm not sure how many LP user use the MIDI output anyway, given its
> restrictions. Personally, I use it for proof-reading only, so lack of
> repeats isn't an issue.
>
> I use MIDI output mainly for proofreading, but at occasions where I need
> better MIDI output I always create separate scores for layout{} and
> midi{}. In the midi-only version I copy/paste all music in the correct
> order instead of using any repeat instructions. Also suitable for complex
> Da Capo / Segno / Coda types of repeats. If I arrange my music in blocks
> using variables and use my favorite texteditor it really isn't that much
> extra work and it is a usable workaround for Lilypond's restrictions.
>
> Sometimes even \unfoldRepeats doesn't do the trick.
>
> --
>
> MT
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>