Re: Could something be done about the way the list of MIDI instrument names is presented?

# [132]Staff symbol # [133]Ossia staves # [134]Hiding staves o [135]1.6.3 Writing parts # [136]Instrument names # [137]Quoting other voices # [138]Formatting cue notes

Re: Could something be done about the way the list of MIDI instrument names is presented?

Am 01.01.2022 um 14:30 schrieb Petr Pařízek: Michael wrote: > are you familiar with GitLab or do you have an account at least? > It would be nice if you could summarize your enhancement proposal and > add it to the issue tracker directly: > https://gitlab.com/lilypond/lilypond/-/issues I

Re: Could something be done about the way the list of MIDI instrument names is presented?

Michael wrote: > are you familiar with GitLab or do you have an account at least? > It would be nice if you could summarize your enhancement proposal and > add it to the issue tracker directly: > https://gitlab.com/lilypond/lilypond/-/issues I confess that I don't know what GitLab is, nor do I

Re: Could something be done about the way the list of MIDI instrument names is presented?

Pařízek: Hi all, this list of MIDI instrument names would deserve some reformatting or even rewriting. I'm saying this as someone who has never read this before. https://lilypond.org/doc/v2.23/Documentation/notation/midi-instruments The following things are all true at the same time, which makes

Re: Manipulating instrument names and staff group names

Hi Jean, > 3. I believe you are a bit quick in believing you >will never, ever be able to write C++ code ;-) I didn’t say I wouldn’t be *able* to write C++ code… I said > but very little chance of ever C++-ing ;-) My prediction was more about my likely enthusiasm and commitment than my

Re: Manipulating instrument names and staff group names

Le 08/11/2021 à 21:13, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Am Sonntag, dem 07.11.2021 um 15:59 -0500 schrieb Kieren MacMillan: Hi Jonas, "Defect" is for problems within the "core program", which means either C++ or Scheme. I would argue that those two are not

Re: Manipulating instrument names and staff group names

Hi Kieren, A blatant counter-example is in the person of Harm. So C++ and Scheme *are* [as I first suggested] separable? There's lots of stuff one can do in Scheme alone. But it seems to me to be a non-trivial task in general to decide a priori whether, given a feature request or bug

Re: Manipulating instrument names and staff group names

Am Sonntag, dem 07.11.2021 um 15:59 -0500 schrieb Kieren MacMillan: > Hi Jonas, > > > "Defect" is for problems within the "core program", > > which means either C++ or Scheme. I would argue that those two are not > > really separable in most cases > > Does that mean for someone like me — with a

Re: Manipulating instrument names and staff group names

Hi Harm, > Start slowly, maybe with a markup-command you would like to have Okay! I’ve got one: I’d like to become an official #'style in TimeSignature. (This hasn’t been done yet, right?) Thanks, Kieren. Kieren

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Hi Carl, > As far as I can see, this is desirable, but certainly not low-hanging fruit. As I qualified, that’s from the metric of “motivation” (which was what Jean implied should be the main metric!). > If you could come up with a an algorithm that would allow me to Do The Right > Thing given

Re: Manipulating instrument names and staff group names

Hi Jean, >>> "Defect" is for problems within the "core program", >>> which means either C++ or Scheme. I would argue that those two are not >>> really separable in most cases >> Does that mean for someone like me — with a fighting chance of Scheme-ing, >> but very little chance of ever C++-ing —

Re: Manipulating instrument names and staff group names

Am So., 7. Nov. 2021 um 22:30 Uhr schrieb Jean Abou Samra : > > Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : > > Hi Jonas, > > > >> "Defect" is for problems within the "core program", > >> which means either C++ or Scheme. I would argue that those two are not > >> really separable in most

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

On 11/7/21, 12:46 PM, "lilypond-devel on behalf of Kieren MacMillan" wrote: Obvious “low-hanging fruit” [at least from the perspective of motivation]: I want — nay, need! — the part combiner to Do The Right Thing™: effectively unlimited voice inputs, no problem with quotes and

Re: Manipulating instrument names and staff group names

Jean Abou Samra writes: > Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : >> Hi Jonas, >> >>> "Defect" is for problems within the "core program", >>> which means either C++ or Scheme. I would argue that those two are not >>> really separable in most cases >> Does that mean for someone like me

Re: Manipulating instrument names and staff group names

Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : Hi Jonas, "Defect" is for problems within the "core program", which means either C++ or Scheme. I would argue that those two are not really separable in most cases Does that mean for someone like me — with a fighting chance of Scheme-ing, but

Re: Manipulating instrument names and staff group names

Hi Jonas, > "Defect" is for problems within the "core program", > which means either C++ or Scheme. I would argue that those two are not > really separable in most cases Does that mean for someone like me — with a fighting chance of Scheme-ing, but very little chance of ever C++-ing — there are

Re: Fwd: Manipulating instrument names and staff group names

Am Sonntag, dem 07.11.2021 um 11:07 -0500 schrieb Kieren MacMillan: > > > 2. Is there a tag/label on GitLab which identifies all and only > > > those issues which don’t (or at least shouldn’t likely) require > > > any C++ work? > > > > There isn't. We had Frog in the past (good for beginners, > >

Re: Manipulating instrument names and staff group names

Hi Jean, > On Nov 6, 2021, at 4:20 PM, Jean Abou Samra wrote: > >> #1034 seems safe, there's no actual "programming" involved, as far as I can >> see. > > The NR appendix is autogenerated, so you'd need to add > a new optional keyword argument to define-music-function > like #:category for

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Le 07/11/2021 à 20:45, Kieren MacMillan a écrit : Hi Jean, The problem for both of these is that often, investigating what the bug is and how it might be fixed is the main part of the work. So if you have a good idea of what language is required and how hard it is, you're close enough to a fix

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Hi Jean, > The problem for both of these is that often, > investigating what the bug is and how it > might be fixed is the main part of the work. > So if you have a good idea of what language > is required and how hard it is, you're > close enough to a fix that it's worth it > to actually prepare

Issue difficulty tags (was: Manipulating instrument names and staff group names)

contribute code directly to the codebase!! So… first bit of business, carried over from a -user thread: From: Jean Abou Samra mailto:j...@abou-samra.fr>> Subject: Re: Manipulating instrument names and staff group names Date: November 6, 2021 at 4:08:15 PM EDT To: Kieren Mac

Fwd: Manipulating instrument names and staff group names

… first bit of business, carried over from a -user thread: > From: Jean Abou Samra mailto:j...@abou-samra.fr>> > Subject: Re: Manipulating instrument names and staff group names > Date: November 6, 2021 at 4:08:15 PM EDT > To: Kieren MacMillan <mailto:kieren_macmil...@sympatico.ca&

Re: Proposal: Automatically adjusting indents for instrument names

. It will increase the indent and short-indent of a score to fit all of its instrument names and instrument short names. This is a great idea (and a feature I've been missing for quite some time). In the current version, subsequent systems get a positive short-indent even

Re: Proposal: Automatically adjusting indents for instrument names

Hi Johannes, I 'd like to propose the enhancement below to LilyPond. It will increase the indent and short-indent of a score to fit all of its instrument names and instrument short names. This is a great idea (and a feature I've been missing for quite some time). In the current version

Proposal: Automatically adjusting indents for instrument names

Hi there, for programatically produced scores I've found it to be a nuisance that indents for somewhat longer instrument names had to be tuned by hand. And I guess LilyPond beginners will wonder why in the face of so much perfection longer instrument names simply get cut off. I 'd like

Re: Instrument names

the first instrument name, then set the indent according to that unless the user manually sets an indent? I think that will fix 99% of the instrument names off the left-hand side of the page problems. - Graham ___ lilypond-devel mailing list lilypond

Re: Instrument names

- Original Message - From: Graham Percival gra...@percival-music.ca To: Keith OHara k-ohara5...@oco.net Cc: lilypond-devel@gnu.org Sent: Friday, July 27, 2012 12:48 PM Subject: Re: Instrument names On Thu, Jul 26, 2012 at 02:32:42AM +, Keith OHara wrote: Phil Holmes email

Re: Instrument names

-- Phil Holmes - Original Message - From: Phil Holmes m...@philholmes.net To: Graham Percival gra...@percival-music.ca; Keith OHara k-ohara5...@oco.net Cc: lilypond-devel@gnu.org Sent: Friday, July 27, 2012 2:41 PM Subject: Re: Instrument names - Original Message - From

Re: Instrument names

- Original Message - From: Keith OHara k-ohara5...@oco.net To: lilypond-devel@gnu.org Sent: Thursday, July 26, 2012 3:32 AM Subject: Re: Instrument names Phil Holmes email at philholmes.net writes: I've done the looking into the code that I can manage. I know that indents

Re: Instrument names

Phil Holmes wrote Tuesday, July 24, 2012 4:28 PM I'd like to look at fixing 766. Could someone suggest the best way to go about this, please? One option would seem to be to calculate the length of the text of the instrument names, and set the indent on the score equal to that plus a bit

Instrument names

I'd like to look at fixing 766. Could someone suggest the best way to go about this, please? One option would seem to be to calculate the length of the text of the instrument names, and set the indent on the score equal to that plus a bit. Is this the best way? It seems to me that a system

Re: Documentation NR 1.6.3 Instrument Names

I looked at the docu of ... a quite old ... version, because I once downloaded it completely so that I had it completely offline with working all cross-references. For 2.13.11 I didn't find a possibility to download such complete docu-packet. For 2.12.3 there is a tar.bz. So I'll

Documentation NR 1.6.3 Instrument Names

In the NR of version 2.11.57 I found: Instrument names may be changed in the middle of a piece: \set Staff.instrumentName = First % \set Staff.shortInstrumentName = one c1 c c c \break c1 c c c \break \set Staff.instrumentName = Second % \set Staff.shortInstrumentName

Re: Documentation NR 1.6.3 Instrument Names

On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: In the NR of version 2.11.57 I found: Why are you look at that version? It's an UNSTABLE DEVELOPMENT version, which normal people should not be using. Instrument names may be changed in the middle of a piece: \set

Re: Documentation NR 1.6.3 Instrument Names

Graham Percival graham at percival-music.ca writes: On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: In the NR of version 2.11.57 I found: Why are you look at that version? It's an UNSTABLE DEVELOPMENT version, which normal people should not be using. I used this version in the

Re: Documentation NR 1.6.3 Instrument Names

PS I looked at the docu of this version, because I once downoaded it completely so that I had it completely offline with working all cross-references. For 2.13.11 I didn't find a possibility to download such complete docu-packet. For online use the automatic language selection is really

Re: Documentation NR 1.6.3 Instrument Names

On 2/4/10 4:15 PM, Werner mey@web.de wrote: Graham Percival graham at percival-music.ca writes: On Thu, Feb 04, 2010 at 09:25:01PM +, Werner wrote: In the NR of version 2.11.57 I found: Why are you look at that version? It's an UNSTABLE DEVELOPMENT version, which normal

Re: Documentation NR 1.6.3 Instrument Names

On 4 February 2010 23:35, Carl Sorensen c_soren...@byu.edu wrote: I think that Werner has found a regression. See Notation Reference 1.6.3 for 2.12.  When the instrument name is changed, the first staff after the change shows instrumentName, and succeeding staffs show shortInstrumentName.

Re: different sizes for instrument names (Staff vs. PianoStaff)

Mats Bengtsson schrieb: The simple explanation is that the fontSize property is handled by the Font_size_engraver, which by default lives in the Staff context. Since the PianoStaff instrument names are typeset at the PianoStaff level, it means that the value of fontSize isn't used, then. One

different sizes for instrument names (Staff vs. PianoStaff)

Hello, while working with lilypond I discovered that changes of the font size are treated differently between Staff and PianoStaff. Consider the following snippet: \version 2.13.4 stuff = \relative c { c4 d e f g a b c } \score { \new Staff = Staff \with { \override StaffSymbol

Re: different sizes for instrument names (Staff vs. PianoStaff)

The simple explanation is that the fontSize property is handled by the Font_size_engraver, which by default lives in the Staff context. Since the PianoStaff instrument names are typeset at the PianoStaff level, it means that the value of fontSize isn't used, then. One solution is to add

Re: centering of instrument names

-name::calc-min-distance-to-support, which goes through all the instrument names and finds the minimum distance necessary between any instrument name and any grob in its support. The nicer way to get the same effect would be to create an InstrumentNameColumn grob that is the X-parent of all

Re: centering of instrument names

instrument-name::calc-combined-delimiters-offset with instrument-name::calc-min-distance-to-support, which goes through all the instrument names and finds the minimum distance necessary between any instrument name and any grob in its support. The nicer way to get the same effect would be to create

Re: centering of instrument names

inside System_start_text::get_stencil (), but can be switched off if a user wants to revert to the existing behaviour using side-support-elements? I wouldn't worry about preserving the existing behaviour. Anyway, with your patch, individual instrument names can be adjusted by tweaking

Re: centering of instrument names

if a user wants to revert to the existing behaviour using side-support-elements? This would allow the correct use of padding for individual instrument names and would get rid of the simple closure for X-offset. I was hoping to be able to make use of the option in Side_position_interface

Re: centering of instrument names

2009/5/24 Kieren MacMillan kieren_macmil...@sympatico.ca: Can the instrument name blob take advantage of a vertical skyline (profile?) the way the rest of the notation (notes, etc.) take advantage of a horizontal skyline? That would certainly solve the problem precisely, without having to

Re: centering of instrument names

2009/5/20 Francisco Vila paconet@gmail.com: Maybe it's not that easy. If the right padding is intended to put the stencil to the rightmost side, the problem is that the extent of the brace (if any) is unknown at this moment. And let's not forget that braces can have different sizes from

Re: centering of instrument names

. The InstrumentName has to be attached to the left edge of the VerticalAxisGroup (i.e., the Staff), so the only way to position it is to apply padding on its right hand side; this moves it away from the system. In order to prevent collisions between instrument names and PianoStaff braces

Re: centering of instrument names

2009/5/23 Joe Neeman joenee...@gmail.com: If I understand this correctly, you're suggesting that we pad each instrument name according to the largest (wrt X-extent) SystemStartXXX. That's basically it, though the extent would be that of the greatest number of stacked delimiters: for example,

Re: centering of instrument names

On Sat, 2009-05-23 at 23:38 +0100, Neil Puttock wrote: 2009/5/23 Joe Neeman joenee...@gmail.com: If I understand this correctly, you're suggesting that we pad each instrument name according to the largest (wrt X-extent) SystemStartXXX. That's basically it, though the extent would be that

Re: centering of instrument names

On 5/23/09 6:48 PM, Joe Neeman joenee...@gmail.com wrote: On Sat, 2009-05-23 at 23:38 +0100, Neil Puttock wrote: 2009/5/23 Joe Neeman joenee...@gmail.com: If I understand this correctly, you're suggesting that we pad each instrument name according to the largest (wrt X-extent)

Re: centering of instrument names

of the VerticalAxisGroup (i.e., the Staff), so the only way to position it is to apply padding on its right hand side; this moves it away from the system. In order to prevent collisions between instrument names and PianoStaff braces, the system start delimiters are added as side-support-elements of each

Re: centering of instrument names

. The InstrumentName has to be attached to the left edge of the VerticalAxisGroup (i.e., the Staff), so the only way to position it is to apply padding on its right hand side; this moves it away from the system. In order to prevent collisions between instrument names and PianoStaff braces

centering of instrument names

Hello, I think instrument names were recently implemented in a centered column by default. I would like to help improving this because the exact location of every name is at first well computed but finally wrongly typeset, as the braces are not taken into account. Currently, names of staves

Re: centering of instrument names

2009/5/19 Francisco Vila paconet@gmail.com: I think instrument names were recently implemented in a centered column by default. I would like to help improving this because the exact location of every name is at first well computed but finally wrongly typeset, as the braces are not taken

Re: centering of instrument names

2009/5/20 Valentin Villenave v.villen...@gmail.com: Are you referring to http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=b12cf25401fa3007c58593fdf1e05acf7e8aaeb6 ? Yes, thank you. It is a perfect starting point. Do you agree it needs a slight retouch? -- Francisco Vila. Badajoz

Re: centering of instrument names

On Tue, May 19, 2009 at 10:09 AM, Francisco Vila paconet@gmail.com wrote: Hello, I think instrument names were recently implemented in a centered column by default. I would like to help improving this because the exact location of every name is at first well computed but finally wrongly

Re: centering of instrument names

2009/5/20 Patrick McCarty pnor...@gmail.com: On Tue, May 19, 2009 at 10:09 AM, Francisco Vila paconet@gmail.com wrote: Hello, I think instrument names were recently implemented in a centered column by default. I would like to help improving this because the exact location of every name

Re: [PATCH] Re: Vertical position of cue instrument names

, which changes the defaults for InstrumentSwitch to more sensible values: -) outside-staff-priority set to 500 -) staff-padding reduced to 0.5 -) left-aligned on the note (actually, in the hand-engraved scores that I have, most fo the cue instrument names are neither center-aligned nor left

Vertical position of cue instrument names

It seems that cue instrument names (set via Voice.instrumentCueName) are always placed bottom-aligned at the same vertical position, even if they collide with accents/notes and also if there would be enough space to place them lower (closer to the staff). Attached is an example displaying

Re: Vertical position of cue instrument names

- From: Reinhold Kainhofer [EMAIL PROTECTED] To: LilyPond Development lilypond-devel@gnu.org Sent: Sunday, May 04, 2008 12:23 PM Subject: Vertical position of cue instrument names It seems that cue instrument names (set via Voice.instrumentCueName) are always placed bottom-aligned at the same

Re: Geting the list of MIDI instrument names

, I'm already using this for the midi instrument names (which would be 3 pages otherwise). I certainly wouldn't mind using a snippet like this for the relevant appendix section... although I agree that shades of gray aren't interesting. Could you tweak the snippet to exclude all grays

Re: Geting the list of MIDI instrument names

as a stream designator resolves to (current-output-port). Substitute #t with (current-error-port) to send the list to standard error. Well, you are right that it can be done simpler: #(map (lambda (x) (format #t ~s~% (car x))) instrument-names-alist) However, the missing #t is not a bug, rather

Re: Geting the list of MIDI instrument names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 21. Februar 2008 schrieb Ralf Mattes: However, the missing #t is not a bug, rather a missing optimization. format without a stream designator returns the formatted string, so in this case one really needs a display. However, if

Re: Geting the list of MIDI instrument names

2008/2/21, Reinhold Kainhofer [EMAIL PROTECTED]: Don't ask me how it is done, but at least that's how it works in lilypond: lilypond -e '(display (string-list (format abc~sdef )))' be careful with format; there are 2 routines: simple-format (the default, implemented in C; format is

Re: Geting the list of MIDI instrument names

Greetings everybody, I haven't completely understood the whole discussion, but I'd just like to know if there's a way to print the MIDI instruments list in the PDF output, and not as a stderr message like Mats suggested; this way I could add a cool snippet to the LSR alongside with tricks to

Re: Geting the list of MIDI instrument names

\header { title = Creating the list of all supported midi instruments } % We need to load the scheme file containing the definitions #(ly:load midi.scm) % Code for lilypond 2.11: % We apply a lambda function to the list (instrument-names-alist) of instrument definitions % That function simply creates

Re: Geting the list of MIDI instrument names

On Fri, 22 Feb 2008 00:33:38 +0100 Reinhold Kainhofer [EMAIL PROTECTED] wrote: BTW, I also created a similar scheme function displaying all x11 colors (including a filled box of that color), but didn't submit it to the LSR, because it takes a while to format and creates 21 pages of output

instrument names not always properly centered in .40

Hello, I've seen that in .40 instrument names are centered by default; however, there is some problem because the longest name does not set the width of the column where the names are centered in (see sample and preview) \version 2.11.40 \new Staff {\set Staff.instrumentName = Violin I c'1} \new

Re: Geting the list of MIDI instrument names

with (current-error-port) to send the list to standard error. Well, you are right that it can be done simpler: #(map (lambda (x) (format #t ~s~% (car x))) instrument-names-alist) However, the missing #t is not a bug, rather a missing optimization. format without a stream designator returns

Re: instrument names not always properly centered in .40

Le 20 févr. 08 à 18:07, Francisco Vila a écrit : Hello, I've seen that in .40 instrument names are centered by default; however, there is some problem because the longest name does not set the width of the column where the names are centered in (see sample and preview) The documentation

Re: Geting the list of MIDI instrument names

Op dinsdag 19 februari 2008, schreef Mats Bengtsson: Reinhold Kainhofer wrote: Of course, the lilypond-way is much better than my pure-scheme code... Yes and no! If you use ly:message, the printouts will appear on stderr (or in the .log file if you use lilypond -dgui ...) and will be mixed

Geting the list of MIDI instrument names

Hi, I'm looking for a stable way to get the list of supported MIDI instrument names from LilyPond, by running lilypond -e with a scheme expression to do just that (and not print a regular ps/pdf file). It's for my plugin that could offer a nice help window to quickly assign a midi instrument

Re: Geting the list of MIDI instrument names

that function... That also means that I can now easily create a table of all available x11-colors with scheme! #(map (lambda (entry) (ly:message (car entry))) instrument-names-alist) Of course, the lilypond-way is much better than my pure-scheme code... Cheers, Reinhold

Re: Geting the list of MIDI instrument names

Reinhold Kainhofer wrote: Of course, the lilypond-way is much better than my pure-scheme code... Yes and no! If you use ly:message, the printouts will appear on stderr (or in the .log file if you use lilypond -dgui ...) and will be mixed with some other printouts, whereas if you use

Re: Geting the list of MIDI instrument names

On Tue, 19 Feb 2008 17:31:41 +0100, Reinhold Kainhofer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 19. Februar 2008 schrieb Wilbert Berendsen: I'm looking for a stable way to get the list of supported MIDI instrument names from LilyPond, by running lilypond -e

Re: Geting the list of MIDI instrument names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 19. Februar 2008 schrieb Wilbert Berendsen: I'm looking for a stable way to get the list of supported MIDI instrument names from LilyPond, by running lilypond -e with a scheme expression to do just that (and not print a regular ps/pdf

Re: Geting the list of MIDI instrument names

))) instrument-names-alist) which produces the list on stderr. /Mats Wilbert Berendsen wrote: Hi, I'm looking for a stable way to get the list of supported MIDI instrument names from LilyPond, by running lilypond -e with a scheme expression to do just that (and not print a regular ps/pdf file

Re: [patch] X-aligned instrument names

Le 11 févr. 08 à 02:41, Han-Wen Nienhuys a écrit : Sounds like a good idea. You could do the same with the other lines, if you would assume that there was a 'virtual' indent (don't change the line dimensions, but assume there is a global given space to align names with) Ok. Should I define a

[patch] X-aligned instrument names

Hi, The following patch add x-alignment support for instrument names: being given the amount of indentation, and the value of the self-alignment-X grob property, some padding is added to the right of the instrument name. \override Staff.InstrumentName #'self-alignment-X = #LEFT == instrument

Re: [patch] X-aligned instrument names

Le 10 févr. 08 à 16:35, Nicolas Sceaux a écrit : The following patch add x-alignment support for instrument names: being given the amount of indentation, and the value of the self-alignment-X grob property, some padding is added to the right of the instrument name. [...] I had a few thoughts

Re: [patch] X-aligned instrument names

-alignment support for instrument names: being given the amount of indentation, and the value of the self-alignment-X grob property, some padding is added to the right of the instrument name. \override Staff.InstrumentName #'self-alignment-X = #LEFT == instrument name aligned on the left margin

Re: instrument names in some contexts

Wilbert Berendsen wrote: Op maandag 10 december 2007, schreef Mats Bengtsson: Wilbert Berendsen wrote: Isn't it a good idea to add the instrument_name_engraver by default to the ChoirStaff, GrandStaff and StaffGroup contexts? Sure! There is a little issue with the

instrument names in some contexts (was: Re: Padding around instrument names)

2.11.30 \new ChoirStaff \relative \new Staff { c1 \break c1 } \new Staff { c1 \break c1 } \set ChoirStaff.instrumentName = Choir \set ChoirStaff.shortInstrumentName = Ch. does not print any instrument names. Isn't it a good idea to add the instrument_name_engraver by default

serious bug: split spanners and instrument names

I've added this to the Google item list also. Werner == \version 2.9.28 \header { texidoc = A split spanner moves the instrument name down which is wrong. } \relative { \set Staff.shortInstrumentName = foo

Re: Documentation addition: instrument names for PianoStaff, GrandStaff, etc.

Marcus Macauley wrote: I couldn't figure out how to add an instrument name to a GrandStaff, much less to a ChoirStaff or a StaffGroup. Kieren MacMillan (on lilypond-user) pointed me in the right direction, but the documentation could be updated to make this more obvious. So here is my

Documentation addition: instrument names for PianoStaff, GrandStaff, etc.

it. Append the following to 8.2.5 Instrument names (before See also and Bugs): --- Instrument names may also be added to groups of staves, such as PianoStaff, GrandStaff, ChoirStaff, or StaffGroup. For a PianoStaff, do something like: \new PianoStaff \set PianoStaff.instrumentName

\center-align in instrument names

Is this a bug, or am I doing something weird? \center-align works fine in Staff.instrument when I have a single instrument, but when I add a second instrument, the center of \center-align is lined up with the left side of the other instrument name. This results in half of the clarinetti running

Re: \center-align in instrument names

Graham Percival wrote: Is this a bug, or am I doing something weird? \center-align works fine in Staff.instrument when I have a single instrument, but when I add a second instrument, the center of \center-align is lined up with the left side of the other instrument name. This results in half