Re: changing the default midi instrument "permanently"

[Robert Schmaus]

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 instrument in a Voice/Staff sometimes results in that
instrument being used also for other Voices (even in different scores or
files!) as a default, if nothing else is specified.

However, for just that reason, I've checked the Staff/GrandStaff &
midi/layout combinations outside the editor (in MacOS) where that
"instrument-memory" doesn't exist for sure. And I'm pretty sure I was
thorough ... but if I did miss something, I'd hate to cause a stir.

It's high time to finally install VirtualBox and some Linux variation to
be able to use Frescobaldi ... 



On Mon, Mar 18, 2013, at 09:16 AM, David Kastrup wrote:
> Robert Schmaus <address@hidden> 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 ...
> 
> I am somewhat surprised.  It should matter.  midiInstrument is read by
> the Staff_performer, and short of overrides at Staff level (which are
> established by TabStaff and DrumStaff to guitar and drums,
> respectively), the setting at GrandStaff should be visible.
> 
> I have to admit that I don't really understand how midiChannelMapping
> plays into this right now.
> 
> -- 
> David Kastrup
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user