Andrew Bernard writes:
Hi David,
That's one view, but I have been using LilyPond for professional
engraving for years and I am now moving into MIDI for generation
of
MIDI as the principal end output, for film scores and so on.
That's a
valid musical compositional use case. The engraved score
Hi Andrew,
On Wed, Oct 28, 2020 at 5:03 PM Andrew Bernard wrote:
>
> Hi David,
>
> That's one view, but I have been using LilyPond for professional
> engraving for years and I am now moving into MIDI for generation of
> MIDI as the principal end output, for film scores and so on. That's a
> valid
Hi David,
That's one view, but I have been using LilyPond for professional
engraving for years and I am now moving into MIDI for generation of
MIDI as the principal end output, for film scores and so on. That's a
valid musical compositional use case. The engraved score is _not_
always the principa
> I think the fact that a person is using Lilypond means they want a
> properly-printed score, and making the effort to print a nice
> score implies a planned live performance. Which (in my mind)
> allows Lilypond’s MIDI into the “mere proof of concept” category.
In my opinion, every feature that
David Kastrup writes:
Marc Shepherd writes:
According to the documentation, the default behavior of the
MIDI block is
not to “unfold” repeats (other than those that are explicitly
\repeat unfold).
If you want repeats unfolded inside of a MIDI block, you have
to requote
the music within the
Marc Shepherd writes:
> According to the documentation, the default behavior of the MIDI block is
> not to “unfold” repeats (other than those that are explicitly \repeat unfold).
> If you want repeats unfolded inside of a MIDI block, you have to requote
> the music within the MIDI block, nested i
