Thanks a lot for your help!
Moving the Midi_control_change_performer did the trick (I was unaware of its
existence).
A MWA that actually works is then:
\version "2.19.82"
\score {
\new Staff <<
\new Voice \relative c''' {
\set midiExpression = #.1
\voiceOne
g1
\se
On Mon, 2019-04-15 at 23:36 +0200, Leo Correia de Verdier wrote:
> Dear list!
>
> Can any of you check this for possible mistakes so I can rule out
> myself as source of error before I send it in as a bug report?
>
> Love
> /Leo
To make the changes to the MIDI expression level have effect, you'
On 4/15/19, 3:36 PM, "Leo Correia de Verdier"
wrote:
Dear list!
Can any of you check this for possible mistakes so I can rule out myself as
source of error before I send it in as a bug report?
Love
/Leo
> 11 feb. 2019 kl. 11:14 skrev Leo Correia de Ve
Dear list!
Can any of you check this for possible mistakes so I can rule out myself as
source of error before I send it in as a bug report?
Love
/Leo
> 11 feb. 2019 kl. 11:14 skrev Leo Correia de Verdier
> :
>
> Dear list!
>
> I’m trying to add different midiExpressions to a staff with two
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
