Davide Liessi <[email protected]> writes: > Il 26/04/15 01.38, David Kastrup ha scritto: >> Davide Liessi <[email protected]> writes: >>> "\set Staff.midiInstrument = ..." has no effect when used inside a >>> RhythmicStaff. >> >> Minimal example exhibiting the problem, version number? > > \version "2.19.15" > \score { > \new RhythmicStaff { > %\set RhythmicStaff.midiInstrument = "flute" > %\set Staff.midiInstrument = "flute" > c > } > \midi { } > } > > If I uncomment the "\set RhythmicStaff..." line, the resulting MIDI > file contains the expected program change event setting the MIDI > instrument to flute. > If I uncomment the "\set Staff..." line, the resulting MIDI file > doesn't contain any program change events.
Should be fixed with commit bf8440d934cf7d31ea4649710a43fa720b7ef696 Author: Thomas Morley <[email protected]> Sun Feb 8 18:40:10 2015 Committer: Thomas Morley <[email protected]> Sun Mar 1 16:15:20 2015 Clean up inconsistencies in engraver-init.ly and performer-init.ly issue 4281 In performer-init.ly - let context-defs be copied when possible - add missing contexts for \accepts and \alias - delete settings for ChordNameVoice - add GregorianTranscriptionStaff, GregorianTranscriptionVoice, NoteNames, PetrucciStaff, PetrucciVoice - all contexts are written without quotation marks - accepted contexts are ordered alphabetically In engraver-init.ly - add FretBoards to the accepted contexts in StaffGroup - add NullVoice to the accepted contexts in RhythmicStaff - all contexts are written with quotation marks - accepted contexts are ordered alphabetically -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
