Eluze writes:
> David Kastrup wrote
>> Eluze <
>
>> eluzew@
>
>> > writes:
>>
>>> ..., but maybe I was confused by the fact that it works in the \with
>>> block...!
>>
>> A context modification in the music is applied to all outputs.
>>
>>> why can't midi items be read from the \layout block?
why I have to specify where it
goes myself!?
maybe the terms \layout and \midi should then be summarized in something
more neutral like \settings or \migr (for *mi*di and *gr*aphics)
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/changing-the-default-midi-instru
Eluze writes:
> David Kastrup wrote
>> Eluze <
>
>> eluzew@
>
>> > writes:
>>>
>>> it has no effect - why?
>>
>> Try placing that context definition in the \midi block rather than the
>> \layout block.
>
> thanks, that works (and I could have found myself, but maybe I was
> confused by the fact
act that it works in the \with block...)!
why can't midi items be read from the \layout block?
now I can integrate this in my -dinclude-settings
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/changing-the-default-midi-instrument-permanently-tp142924p14
Robert Schmaus writes:
> Before you (or anyone else) starts an investigation into this, let me
> (or someone else) double-check to be sure. I'm currently using Elysium
> (and Eclipse) to write LilyPond scores, and I did notice that there
> seems to exist something like a midi-instrument memory. M
Before you (or anyone else) starts an investigation into this, let me
(or someone else) double-check to be sure. I'm currently using Elysium
(and Eclipse) to write LilyPond scores, and I did notice that there
seems to exist something like a midi-instrument memory. Meaning that
changing the midi ins
Robert Schmaus writes:
>> Try placing that context definition in the \midi block rather than the
>> \layout block.
>>
>
> That was my first try too, but, again, it worked only when I used
> Staff instead of GrandStaff. And then it didn't matter if I placed it
> in the layout or in the midi block
Try placing that context definition in the \midi block rather than the
\layout block.
That was my first try too, but, again, it worked only when I used Staff
instead of GrandStaff. And then it didn't matter if I placed it in the
layout or in the midi block ...
Eluze writes:
> as I'm only writing guitar scores I'd like the midi instrument to always
> default to midiInstrument="acoustic guitar (nylon)"
>
> is there a way to do this?
>
> I know I can write
>
> \score {
> \new GrandStaff \with{ midiInstrument="acoustic guitar (nylon)"}
> <<
> \new
Hi Eluze,
It worked, when I replaced "GrandStaff" with "Staff", i.e.
\layout {
\context {
\Staff
midiInstrument = "acoustic guitar (nylon)"
}
}
Possibly, a GrandStaff doesn't have instrument properties ...
You could also outsorce that piece of code into a "general l
there a way to redefine/sort the instrument-names-alist as defined in
...\LilyPond\usr\share\lilypond\current\scm\midi.scm for this purpose?
thanks for any hints!
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/changing-the-default-midi-instrument-permanently-
11 matches
Mail list logo
