Re: Midi block gives errors with bar number checks

2019-11-27 Thread Peter Toye
Carl, I've been thinking about this, and my guess is that LP uses the bar number to calculate the beat clock. And when there are repeats, MIDI bar number != engraving bar number, so it goes wrong. This is presumably why the MIDI generator in LP doesn't handle repeats, and to make it do so would

Re: Midi block gives errors with bar number checks

2019-11-27 Thread Martin Tarenskeen
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 out

LSR Snippet 318

2019-11-27 Thread Malte Meyn
Hi list, I’m not sure where to post an LSR bug report but maybe the people responsible for the LSR read this list? Snippet 318 (http://lsr.di.unimi.it/LSR/Item?id=318) states that \parenthesize for notes works only inside chords. That’s not correct, the following works as expected in 2.12.3

Re: Midi block gives errors with bar number checks

2019-11-27 Thread 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'