Re: ChordNames on Staff

2019-02-07 Thread Robert Hennig
uot;) ;; Staff needs to be named equal to this #{ \override ChordName.Y-offset = #-1 #} #{ \revert ChordName.Y-offset #}) #}) \score { \new StaffGroup << \new ChordNames = "chrds-up" %% keep it alive! \chordmode { s1*8 } \new Staff =

Re: ChordNames on Staff

2019-02-07 Thread Thomas Morley
ing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user Here a different approach. _If_ it works (and you really should test it, I did only the provided examples) it looks much cleaner, imho. \version "2.19.82" gotoCtx = #(define-music-function (strg)(s

Re: ChordNames on Staff

2019-02-07 Thread David Kastrup
Robert Hennig writes: > Hi Valentin, > thank you for sharing your lilypond wisdom. > I have learned a lot already :). > (\denies "Voice" had not removed the note heads) It would basically just state that no Voice contexts can be anchored directly under the given context type. If LilyPond

Re: ChordNames on Staff

2019-02-07 Thread Robert Hennig
Hi Valentin, thank you for sharing your lilypond wisdom. I have learned a lot already :). (\denies "Voice" had not removed the note heads) For my problem to switch from up and down setting the chord names I will stick to Arons solution in this fashion: chordsUp = { \override

Re: ChordNames on Staff

2019-02-07 Thread Valentin Villenave
On 2/7/19, Robert Hennig wrote: > The second Solution from Valentin looks like what I would prefer but > it prints the chord notes too, which is not was I'm looking for (only > Chord Names). Huh. Have you added \denies "Voice" like I did? It should prevent any notes (or rests) from being

Re: ChordNames on Staff

2019-02-07 Thread Robert Hennig
\override ChordName.extra-offset = #'(0 . -1) \alias ChordNames } \context { \Staff \accepts "ChordsOnStaff" } } << \new ChordNames \chordmode { c1 s1 s1 c1 } \relative c' { c2 e2 \context ChordsOnStaff \chordm

Re: ChordNames on Staff

2019-02-06 Thread Kieren MacMillan
Hi Valentin, > I can think of two ways: > > \new ChordNames \with { > \consists Staff_symbol_engraver > } \chordmode { > c1 > } Ooh, that’s clever. =) K. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info

Re: ChordNames on Staff

2019-02-06 Thread Valentin Villenave
On 2/6/19, Robert Hennig wrote: > I would like to print the ChordNames casually directly on the staff, Not > above the staff. Using extra-offset works if there are no other objects > which adjusts the spacing. What is the proper way to get the ChordNames > fixed to the staff? Greetings, I can

Re: ChordNames on Staff

2019-02-06 Thread Aaron Hill
ra-offset = #'(0 . -3.5) c1 } s1%^"Text" You need to change the nonstaff-relatedstaff-spacing so that the baselines between the ChordNames and Staff align. The key is setting padding to a large enough negative number, which permits the stencils to overlap. You will still need

ChordNames on Staff

2019-02-06 Thread Robert Hennig
Dear lilypond community, I would like to print the ChordNames casually directly on the staff, Not above the staff. Using extra-offset works if there are no other objects which adjusts the spacing. What is the proper way to get the ChordNames fixed to the staff? I would like to create lead sheets

Re: How to adjust space between ChordNames and Staff?

2017-01-12 Thread Thomas Morley
2017-01-12 21:13 GMT+01:00 Risto Vääräniemi <risva...@gmail.com>: > Hi all, > > The spacing between ChordNames and Staff seems a bit tight by default. I've > been trying to adjust it but I haven't figured out the right magic words > yet. The IR says *) that there should b

How to adjust space between ChordNames and Staff?

2017-01-12 Thread Risto Vääräniemi
Hi all, The spacing between ChordNames and Staff seems a bit tight by default. I've been trying to adjust it but I haven't figured out the right magic words yet. The IR says *) that there should be nonstaff-nonstaff-spacing.padding and nonstaff-relatedstaff-spacing.padding available and I have

Re: ChordNames in Staff context

2013-11-01 Thread David Kastrup
Robert Schmaus robert.schm...@web.de writes: Hi Keith, thanks for your reply! May I ask what the reasons were for removing that technique? Probably, no-one watching the changes knew that this was a technique. that would be a pity! LilyPond can't support everything which people consider

Re: ChordNames in Staff context

2013-10-14 Thread Robert Schmaus
really know about those engravers). let me reply to that, that whatever the internal conflict was which the removal of that technique tried to solve, the actual result of having Staff accept ChordNames was quite outstanding. all musicians who I play with always were in awe about the quality of my

Re: ChordNames in Staff context

2013-10-13 Thread Keith OHara
Robert Schmaus robert.schmaus at web.de writes: The compiling resulted in hundreds of errors (after applying convert-ly). It took some time to figure out, that the problem was the statement \context { \Staff \accepts ChordNames } in the score block. A google search turned