Dear list!
I’m trying to add different midiExpressions to a staff with two voices on
different midi channels. The problem I have is that \set midiExpression only
seems to work if placed before the first note of a voice. Subsequent \set-s
don’t appear in the output midi file. The following \set
On 2/6/19, Karlin High wrote:
> I got the LilyPond app extracted from .tar.bz and it opens and runs.
Greetings Knut,
I’ve received reports from two FreeBSD users that the x86_64 installer
doesn’t work.
- One said that the binary isn’t recognized as an "amd64" arch (he’s
using FreeBSD 12.0 on a c
On Mon, Feb 11, 2019 at 6:17 AM Valentin Villenave
wrote:
>
> I’ve received reports from two FreeBSD users that the x86_64 installer
> doesn’t work.
> - One said that the binary isn’t recognized as an "amd64" arch (he’s
> using FreeBSD 12.0 on a core i7).
I saw the same thing; apparently FreeBSD
Hi Andrew,
How about changing the stencil once, e.g.:
%%%
\version "2.19.82"
\layout {
indent = 0
ragged-right = ##t
}
STclef = {
\once\override Staff.Clef.stencil =
#(lambda (grob)
(let ((glyph (ly:grob-property grob 'glyph-name)))
(cond
((equal? g
is there a way of automagically adding some volume increase ("accent")
in MIDI output to any note that happens to start on the first beat in
a bar?
It seems a well-defined enough request to me so that it should be
perfectly possible to do this in scheme, but I'm afraid this exceeds
my very
Lukas-Fabian Moser writes:
>> is there a way of automagically adding some volume increase
>> ("accent") in MIDI output to any note that happens to start on the
>> first beat in a bar?
>>
>> It seems a well-defined enough request to me so that it should be
>> perfectly possible to do this in schem
Thanks for the explanations!
Your idea is good. The infrastructure is not there. We probably should
have something like make-translator for stuff that just translates
events and/or meddles with context properties.
So you probably need to work on the music expressions for now similar to
how art
Lukas-Fabian Moser writes:
> Thanks for the explanations!
>> Your idea is good. The infrastructure is not there. We probably should
>> have something like make-translator for stuff that just translates
>> events and/or meddles with context properties.
>>
>> So you probably need to work on the m
Hi Pierre,
Marvellous. Works nicely in a quick try out. I'll put it to industrial use
test it further.
This is one of those functions that would be good as a snippet on LSR.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.
