[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames |
Date: |
Thu, 26 Mar 2015 10:14:39 +0000 |
Comment #1 on issue 4330 by address@hidden: No midi with ChordNames
https://code.google.com/p/lilypond/issues/detail?id=4330
The old code from performer-init.ly was
\context {
\type "Performer_group"
\consists "Staff_performer"
\accepts ChordNameVoice
\defaultchild ChordNameVoice
\name ChordNames
}
\context {
\Voice
\name ChordNameVoice
}
Obviously there was some effort to rename Voice to ChordNameVoice and
making this the defaultchild os ChordNames.
Is there any need for it or would it be sufficient to add
\defaultchild Voice
to ChordNames directly?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/26
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames,
lilypond <=
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/26
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/26
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/29
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/29
- Re: [Lilypond-auto] Issue 4330 in lilypond: No midi with ChordNames, lilypond, 2015/03/31