[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Midi block gives errors with bar number checks

From: Carl Sorensen
Subject: Re: Midi block gives errors with bar number checks
Date: Wed, 27 Nov 2019 15:14:25 +0000
User-agent: Microsoft-MacOutlook/

´╗┐On 11/27/19, 7:20 AM, "lilypond-devel on behalf of James Lowe" 
<lilypond-devel-bounces+c_sorensen=address@hidden on behalf of address@hidden> 

    On Wed, 27 Nov 2019 10:51:15 +0100 (CET), 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
    Do we need an @knownissue in the Notation Reference?

I believe that @knownissue is the correct way to deal with this, unless we are 
going to go all out and remove \barNumberCheck from the midi performers.

We shouldn't spend a lot of time documenting the current behavior, since it's 
not consciously designed, but rather an unanticipated result.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]