Re: Errors in examples
David,
2012/2/6 David Kastrup d...@gnu.org:
\layout {
\context {
\Voice
\settingsFrom \voiceOne
}
}
The settingsFrom command looks useful and I vageuly recall you
announced it in the mailing list. However, I don't see it documented
or used in any snippet/example.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 3:08 PM Subject: Re: Errors in examples On Sun, Feb 05, 2012 at 02:43:45PM -, Phil Holmes wrote: In the source for http://lilypond.org/ly-examples/tab-example.png I get the following compile errors: Seems to me these really ought to compile clean? Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. - Graham Given the 2 chords/notes near the end, both with downstems, I think the only option is either use the ignore-collision override, or have the upper notes stem-up using voiceOne. It doesn't appear to be a famous piece of music - there's no title, etc., so I'd actually prefer the latter. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
On Mon, Feb 06, 2012 at 04:12:55PM -, Phil Holmes wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 3:08 PM Subject: Re: Errors in examples Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. Given the 2 chords/notes near the end, both with downstems, I think the only option is either use the ignore-collision override, or have the upper notes stem-up using voiceOne. It doesn't appear to be a famous piece of music - there's no title, etc., so I'd actually prefer the latter. ok, sure. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Graham Percival gra...@percival-music.ca writes: On Mon, Feb 06, 2012 at 04:12:55PM -, Phil Holmes wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 3:08 PM Subject: Re: Errors in examples Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. Given the 2 chords/notes near the end, both with downstems, I think the only option is either use the ignore-collision override, or have the upper notes stem-up using voiceOne. It doesn't appear to be a famous piece of music - there's no title, etc., so I'd actually prefer the latter. ok, sure. No. The real problem is that \voiceOne and/or \voiceTwo do not take hold for some reason. If they did, the example would just work fine. Probably something grace-related. Please let us find and fix the real problem instead of meddling with its symptoms. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Mon, Feb 06, 2012 at 04:12:55PM -, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Sunday, February 05, 2012 3:08 PM
Subject: Re: Errors in examples
Users aren't supposed to look at these, but sure, go ahead and fix
those warnings if you want. As long as the output looks the same,
push directly to staging.
Given the 2 chords/notes near the end, both with downstems, I think
the only option is either use the ignore-collision override, or have
the upper notes stem-up using voiceOne. It doesn't appear to be a
famous piece of music - there's no title, etc., so I'd actually
prefer the latter.
ok, sure.
No. The real problem is that \voiceOne and/or \voiceTwo do not take
hold for some reason. If they did, the example would just work fine.
Probably something grace-related.
Please let us find and fix the real problem instead of meddling with its
symptoms.
If you comment out the acciaccatura like
\partial 4. %{ \acciaccatura c16 \glissando %} cis8 e4
the whole piece gets through fine with the intended voicing. This is
really, _really_ fishy.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Monday, February 06, 2012 5:01 PM Subject: Re: Errors in examples Graham Percival gra...@percival-music.ca writes: On Mon, Feb 06, 2012 at 04:12:55PM -, Phil Holmes wrote: - Original Message - From: Graham Percival gra...@percival-music.ca To: Phil Holmes em...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 3:08 PM Subject: Re: Errors in examples Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. Given the 2 chords/notes near the end, both with downstems, I think the only option is either use the ignore-collision override, or have the upper notes stem-up using voiceOne. It doesn't appear to be a famous piece of music - there's no title, etc., so I'd actually prefer the latter. ok, sure. No. The real problem is that \voiceOne and/or \voiceTwo do not take hold for some reason. If they did, the example would just work fine. Probably something grace-related. Please let us find and fix the real problem instead of meddling with its symptoms. -- David Kastrup Good point - well spotted. I'll have another look tomorrow. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Monday, February 06, 2012 5:40 PM
Subject: Re: Errors in examples
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Mon, Feb 06, 2012 at 04:12:55PM -, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Sunday, February 05, 2012 3:08 PM
Subject: Re: Errors in examples
Users aren't supposed to look at these, but sure, go ahead and fix
those warnings if you want. As long as the output looks the same,
push directly to staging.
Given the 2 chords/notes near the end, both with downstems, I think
the only option is either use the ignore-collision override, or have
the upper notes stem-up using voiceOne. It doesn't appear to be a
famous piece of music - there's no title, etc., so I'd actually
prefer the latter.
ok, sure.
No. The real problem is that \voiceOne and/or \voiceTwo do not take
hold for some reason. If they did, the example would just work fine.
Probably something grace-related.
Please let us find and fix the real problem instead of meddling with its
symptoms.
If you comment out the acciaccatura like
\partial 4. %{ \acciaccatura c16 \glissando %} cis8 e4
the whole piece gets through fine with the intended voicing. This is
really, _really_ fishy.
--
David Kastrup
See Known Issues etc. in
http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns .
It's in the bug list somewhere
Ah yes. http://code.google.com/p/lilypond/issues/detail?id=630
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Phil Holmes m...@philholmes.net writes:
No. The real problem is that \voiceOne and/or \voiceTwo do not take
hold for some reason. If they did, the example would just work fine.
Probably something grace-related.
Please let us find and fix the real problem instead of meddling with its
symptoms.
Good point - well spotted. I'll have another look tomorrow.
In a nutshell:
\relative c'' { \voiceOne
\grace { c16 } \repeat unfold 16 c
}
does not work. Even more annoyingly, not even
\context Voice \with \settingsFrom \voiceOne
\relative c'' {
\grace { c16 } \repeat unfold 16 c
}
works. And not even
\relative c'' {
\grace { c16 } \repeat unfold 16 c
}
\layout {
\context {
\Voice
\settingsFrom \voiceOne
}
}
which should also cover implicitly generated voices has a chance to get
its settings through to _any_ note. There is something very rotten
going on here.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Errors in examples
In the source for http://lilypond.org/ly-examples/tab-example.png I get the following compile errors: tab-example.ly:43:26: warning: ignoring too many clashing note columns gis\4 d'\3 fis\2 2 b'\2\harmonic e\harmonic 2\fermata tab-example.ly:43:4: warning: ignoring too many clashing note columns gis\4 d'\3 fis\2 2 b'\2\harmonic e\harmonic 2\fermata tab-example.ly:42:22: warning: ignoring too many clashing note columns s4. d'\3 g\2 8 gis,\4 d'\3 fis\2 2\arpeggio ~ Seems to me these really ought to compile clean? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
On Sun, Feb 05, 2012 at 02:43:45PM -, Phil Holmes wrote: In the source for http://lilypond.org/ly-examples/tab-example.png I get the following compile errors: Seems to me these really ought to compile clean? Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
2012/2/5 Graham Percival gra...@percival-music.ca: On Sun, Feb 05, 2012 at 02:43:45PM -, Phil Holmes wrote: In the source for http://lilypond.org/ly-examples/tab-example.png I get the following compile errors: Seems to me these really ought to compile clean? Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel Well, I looked at it now. And at http://lilypond.org/ly-examples/tab-example-small.png There is a printed flag in measure 4. It should be transparent, I think. Perhaps it's possible to fix it in one go. Cheers, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message - From: Thomas Morley thomasmorle...@googlemail.com To: Graham Percival gra...@percival-music.ca Cc: Phil Holmes em...@philholmes.net; Devel lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 3:37 PM Subject: Re: Errors in examples 2012/2/5 Graham Percival gra...@percival-music.ca: On Sun, Feb 05, 2012 at 02:43:45PM -, Phil Holmes wrote: In the source for http://lilypond.org/ly-examples/tab-example.png I get the following compile errors: Seems to me these really ought to compile clean? Users aren't supposed to look at these, but sure, go ahead and fix those warnings if you want. As long as the output looks the same, push directly to staging. - Graham Well, I looked at it now. And at http://lilypond.org/ly-examples/tab-example-small.png There is a printed flag in measure 4. It should be transparent, I think. Perhaps it's possible to fix it in one go. Cheers, Harm Thanks. I'm suspicious of that spare flag too. If you'd like to update it so that it compiles clean and looks good, I would appreciate it and would get the updated version into the documents. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Il 05/02/2012 16:37, Thomas Morley ha scritto: Well, I looked at it now. And at http://lilypond.org/ly-examples/tab-example-small.png There is a printed flag in measure 4. It should be transparent, I think. Perhaps it's possible to fix it in one go. It compiles fine on 2.14.2 But there is also this warning: \once \override Flag #'transparent = ##t tab-example.ly: warning: not a grob name, `Flag' It seems to me that this override is not necessary: if you comment it out, the flag is not printed anyway. I can't test latest git version now (no time to compile it). The original snippet doesn't have that override: http://lsr.dsi.unimi.it/LSR/Snippet?id=633 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Federico Bruni fedel...@gmail.com writes: Il 05/02/2012 16:37, Thomas Morley ha scritto: Well, I looked at it now. And at http://lilypond.org/ly-examples/tab-example-small.png There is a printed flag in measure 4. It should be transparent, I think. Perhaps it's possible to fix it in one go. It compiles fine on 2.14.2 But there is also this warning: \once \override Flag #'transparent = ##t tab-example.ly: warning: not a grob name, `Flag' It seems to me that this override is not necessary: if you comment it out, the flag is not printed anyway. On 2.14.2. I can't test latest git version now (no time to compile it). The original snippet doesn't have that override: http://lsr.dsi.unimi.it/LSR/Snippet?id=633 Hardly surprising. From changes.tely: @item Flags are now treated as separate objects rather than as stem parts. @lilypond[fragment,quote,relative=2] \override Flag #'color = #red g8 @end lilypond It was added in 2.15.13 -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 4:46 PM Subject: Re: Errors in examples Federico Bruni fedel...@gmail.com writes: Il 05/02/2012 16:37, Thomas Morley ha scritto: Well, I looked at it now. And at http://lilypond.org/ly-examples/tab-example-small.png There is a printed flag in measure 4. It should be transparent, I think. Perhaps it's possible to fix it in one go. It compiles fine on 2.14.2 But there is also this warning: \once \override Flag #'transparent = ##t tab-example.ly: warning: not a grob name, `Flag' It seems to me that this override is not necessary: if you comment it out, the flag is not printed anyway. On 2.14.2. I can't test latest git version now (no time to compile it). The original snippet doesn't have that override: http://lsr.dsi.unimi.it/LSR/Snippet?id=633 Hardly surprising. From changes.tely: @item Flags are now treated as separate objects rather than as stem parts. @lilypond[fragment,quote,relative=2] \override Flag #'color = #red g8 @end lilypond It was added in 2.15.13 -- David Kastrup That's quite interesting. I only found the error because I was browsing the output of make doc wondering what to tackle next (in terms of getting rid of extraneous output) and saw the lilypond error. Continues to justify getting rid of the dross of make doc so that real errors can be seen. Would appreciate your looking at http://code.google.com/p/lilypond/issues/detail?id=2146 if you're able - this would help in the same way and, if fixed properly, would display Cyrillic characters where we say they are in the NR. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
2012/2/5 David Kastrup d...@gnu.org:
Federico Bruni fedel...@gmail.com writes:
Il 05/02/2012 16:37, Thomas Morley ha scritto:
Well, I looked at it now. And at
http://lilypond.org/ly-examples/tab-example-small.png
There is a printed flag in measure 4. It should be transparent, I
think. Perhaps it's possible to fix it in one go.
It compiles fine on 2.14.2
But there is also this warning:
\once \override Flag #'transparent = ##t
tab-example.ly: warning: not a grob name, `Flag'
It seems to me that this override is not necessary: if you comment it
out, the flag is not printed anyway.
On 2.14.2.
I can't test latest git version now (no time to compile it).
The original snippet doesn't have that override:
http://lsr.dsi.unimi.it/LSR/Snippet?id=633
Hardly surprising. From changes.tely:
@item
Flags are now treated as separate objects rather than as stem parts.
@lilypond[fragment,quote,relative=2]
\override Flag #'color = #red
g8
@end lilypond
It was added in 2.15.13
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
In order not to change other output I simply added \override
NoteColumn #'ignore-collision = ##t
Attached: file and png
I'm afraid that's all I can do currently.
Harm
\version 2.15.24
#(set-global-staff-size 22.45)
#(define (glissando::calc-extra-dy grob)
(let* ((original (ly:grob-original grob))
(left-bound (ly:spanner-bound original LEFT))
(right-bound (ly:spanner-bound original RIGHT))
(left-pitch (ly:event-property (event-cause left-bound) 'pitch))
(right-pitch (ly:event-property (event-cause right-bound) 'pitch)))
(if (and (= (ly:pitch-octave left-pitch) (ly:pitch-octave right-pitch))
(= (ly:pitch-notename left-pitch) (ly:pitch-notename right-pitch)))
(- (ly:pitch-alteration right-pitch) (ly:pitch-alteration left-pitch))
0 )))
% Hide fret number: useful to draw slide into/from a casual point of
% the fretboard.
hideFretNumber = {
\once \override TabNoteHead #'transparent = ##t
\once \override TabNoteHead #'whiteout = ##f
\once \override NoteHead #'transparent = ##t
\once \override Stem #'transparent = ##t
\once \override Flag #'transparent = ##t
\once \override NoteHead #'no-ledgers = ##t
}
\paper {
indent= #0
line-width= #180
}
upper= \relative c' {
\time 4/4
\key e \major
\set Staff.midiInstrument = #acoustic guitar (steel)
\set fingeringOrientations = #'(left)
\partial 4. \acciaccatura c16 \glissando cis8 e4
cis-1 g'-3 2 s8 \grace a16 ( \glissando b-2 8\3 ) d-1 ( b )
\override NoteColumn #'ignore-collision = ##t
e-3 \2 ( d-1 b ) \grace ais-2 16 ( \glissando a8 g ) s4.
s4. d'\3 g\2 8 gis,\4 d'\3 fis\2 2\arpeggio ~
gis\4 d'\3 fis\2 2 b'\2\harmonic e\harmonic 2\fermata
}
lower= \relative c {
\set fingeringOrientations = #'(left)
\partial 4. s4.
s4 e,4 s2
s2 s8 e'-3 4. ~
e4 \hideFretNumber \grace { b8 \glissando s4 } e-2 4\5 e,2 ~
e2 e'\6\harmonic
}
\score {
\new StaffGroup
\new Staff = guitar
\context Voice = upper guitar {
\clef G_8 \voiceOne
\override Glissando #'gap = #0.5
\override Glissando #'extra-offset = #'(-0.5 . 0)
\override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods
\override Glissando #'minimum-length = #4
\override Glissando #'extra-dy = #glissando::calc-extra-dy
\upper
}
\context Voice = lower guitar {
\clef G_8 \voiceTwo
\override Glissando #'bound-details #'right #'padding = #1
\override Glissando #'bound-details #'left #'padding = #0.2
\lower
}
\new TabStaff = tab
\context TabVoice = upper tab { \clef moderntab \voiceOne \upper }
\context TabVoice = lower tab { \clef moderntab \voiceTwo \lower }
\layout {
\context {
\Staff
\override StringNumber #'transparent = ##t
}
\context {
\TabStaff
\revert Arpeggio #'stencil
}
}
}
attachment: tab-example.png___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
On Sun, Feb 05, 2012 at 05:57:31PM +0100, Thomas Morley wrote: 2012/2/5 David Kastrup d...@gnu.org: Hardly surprising. From changes.tely: @item Flags are now treated as separate objects rather than as stem parts. @lilypond[fragment,quote,relative=2] \override Flag #'color = #red g8 @end lilypond Yes, and I remember Mike manually changing a bunch of files, then running convert-ly, then undoing his manual changes... or something. There was certainly something to do with Stem vs. Flag and transparency. In order not to change other output I simply added \override NoteColumn #'ignore-collision = ##t I'm not certain that's a great solution. Is there a good reason why they're colliding? - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
- Original Message - From: Graham Percival gra...@percival-music.ca To: Thomas Morley thomasmorle...@googlemail.com Cc: David Kastrup d...@gnu.org; lilypond-devel@gnu.org Sent: Sunday, February 05, 2012 5:21 PM Subject: Re: Errors in examples On Sun, Feb 05, 2012 at 05:57:31PM +0100, Thomas Morley wrote: 2012/2/5 David Kastrup d...@gnu.org: Hardly surprising. From changes.tely: @item Flags are now treated as separate objects rather than as stem parts. @lilypond[fragment,quote,relative=2] \override Flag #'color = #red g8 @end lilypond Yes, and I remember Mike manually changing a bunch of files, then running convert-ly, then undoing his manual changes... or something. There was certainly something to do with Stem vs. Flag and transparency. In order not to change other output I simply added \override NoteColumn #'ignore-collision = ##t I'm not certain that's a great solution. Is there a good reason why they're colliding? - Graham == From a quick look - they don't actually collide since their pitch is so different, but their columns collide, since there's no use of voice. Best solution would probably be to set the piece with voiceTwo and voiceFour , but IIRC that would offset the lower notes. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
2012/2/5 Phil Holmes m...@philholmes.net:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Thomas Morley thomasmorle...@googlemail.com
Cc: David Kastrup d...@gnu.org; lilypond-devel@gnu.org
Sent: Sunday, February 05, 2012 5:21 PM
Subject: Re: Errors in examples
On Sun, Feb 05, 2012 at 05:57:31PM +0100, Thomas Morley wrote:
2012/2/5 David Kastrup d...@gnu.org:
Hardly surprising. From changes.tely:
@item
Flags are now treated as separate objects rather than as stem parts.
@lilypond[fragment,quote,relative=2]
\override Flag #'color = #red
g8
@end lilypond
Yes, and I remember Mike manually changing a bunch of files, then
running convert-ly, then undoing his manual changes... or
something. There was certainly something to do with Stem vs.
Flag and transparency.
In order not to change other output I simply added \override
NoteColumn #'ignore-collision = ##t
I'm not certain that's a great solution. Is there a good reason
why they're colliding?
- Graham
==
From a quick look - they don't actually collide since their pitch is so
different, but their columns collide, since there's no use of voice. Best
solution would probably be to set the piece with voiceTwo and voiceFour ,
but IIRC that would offset the lower notes.
--
Phil Holmes
I added \voiceOne near the end of the first voice. Of course this
changes the stem-direction (which I'd prefer) but Graham told not to
change the output.
Harm
\version 2.15.24
#(set-global-staff-size 22.45)
#(define (glissando::calc-extra-dy grob)
(let* ((original (ly:grob-original grob))
(left-bound (ly:spanner-bound original LEFT))
(right-bound (ly:spanner-bound original RIGHT))
(left-pitch (ly:event-property (event-cause left-bound) 'pitch))
(right-pitch (ly:event-property (event-cause right-bound) 'pitch)))
(if (and (= (ly:pitch-octave left-pitch) (ly:pitch-octave right-pitch))
(= (ly:pitch-notename left-pitch) (ly:pitch-notename right-pitch)))
(- (ly:pitch-alteration right-pitch) (ly:pitch-alteration left-pitch))
0 )))
% Hide fret number: useful to draw slide into/from a casual point of
% the fretboard.
hideFretNumber = {
\once \override TabNoteHead #'transparent = ##t
\once \override TabNoteHead #'whiteout = ##f
\once \override NoteHead #'transparent = ##t
\once \override Stem #'transparent = ##t
\once \override Flag #'transparent = ##t
\once \override NoteHead #'no-ledgers = ##t
}
\paper {
indent= #0
line-width= #180
}
upper= \relative c' {
\time 4/4
\key e \major
\set Staff.midiInstrument = #acoustic guitar (steel)
\set fingeringOrientations = #'(left)
\partial 4. \acciaccatura c16 \glissando cis8 e4
cis-1 g'-3 2 s8 \grace a16 ( \glissando b-2 8\3 ) d-1 ( b )
e-3 \2 ( d-1 b ) \grace ais-2 16 ( \glissando a8 g ) s4.
\voiceOne {
s4. d'\3 g\2 8 gis,\4 d'\3 fis\2 2\arpeggio ~
gis\4 d'\3 fis\2 2 b'\2\harmonic e\harmonic 2\fermata
}
}
lower= \relative c {
\set fingeringOrientations = #'(left)
\partial 4. s4.
s4 e,4 s2
s2 s8 e'-3 4. ~
e4 \hideFretNumber \grace { b8 \glissando s4 } e-2 4\5 e,2 ~
e2 e'\6\harmonic
}
\score {
\new StaffGroup
\new Staff = guitar
\context Voice = upper guitar {
\clef G_8 \voiceOne
\override Glissando #'gap = #0.5
\override Glissando #'extra-offset = #'(-0.5 . 0)
\override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods
\override Glissando #'minimum-length = #4
\override Glissando #'extra-dy = #glissando::calc-extra-dy
\upper
}
\context Voice = lower guitar {
\clef G_8 \voiceTwo
\override Glissando #'bound-details #'right #'padding = #1
\override Glissando #'bound-details #'left #'padding = #0.2
\lower
}
\new TabStaff = tab
\context TabVoice = upper tab { \clef moderntab \voiceOne \upper }
\context TabVoice = lower tab { \clef moderntab \voiceTwo \lower }
\layout {
\context {
\Staff
\override StringNumber #'transparent = ##t
}
\context {
\TabStaff
\revert Arpeggio #'stencil
}
}
}
attachment: tab-example-rev.png___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Am 05.02.2012 18:51, schrieb Thomas Morley: [...] I added \voiceOne near the end of the first voice. Of course this changes the stem-direction (which I'd prefer) but Graham told not to change the output. IIRC, the definition for calc-extra-dy is included in the source as glissando::calc-tab-extra-dy and applied to tablature glissandos (glissandi?) by default, so you can omit these parts of the code. Regards, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Am 05.02.2012 20:16, schrieb Marc Hohl: Am 05.02.2012 18:51, schrieb Thomas Morley: [...] I added \voiceOne near the end of the first voice. Of course this changes the stem-direction (which I'd prefer) but Graham told not to change the output. IIRC, the definition for calc-extra-dy is included in the source as glissando::calc-tab-extra-dy and applied to tablature glissandos (glissandi?) by default, so you can omit these parts of the code. Arrrg, I should have read the *whole* file before posting rubbish; just ignore my previous post. Marc Regards, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
Il 05/02/2012 17:46, David Kastrup ha scritto: The original snippet doesn't have that override: http://lsr.dsi.unimi.it/LSR/Snippet?id=633 Hardly surprising. From changes.tely: @item Flags are now treated as separate objects rather than as stem parts. @lilypond[fragment,quote,relative=2] \override Flag #'color = #red g8 @end lilypond It was added in 2.15.13 Ok, I see. I've tested it on latest git version and it looks like the \override Flag fixes the problem reported by Thomas: http://lilypond.org/ly-examples/tab-example-small.png I wonder why the website image is wrong. git log Documentation/ly-example/tab-example.ly doesn't show the full history of the file (maybe because the directory has been renamed?) I'm wondering when that override was added. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
On 05/02/2012 5:25 PM, Federico Bruni wrote: I wonder why the website image is wrong. git log Documentation/ly-example/tab-example.ly doesn't show the full history of the file (maybe because the directory has been renamed?) This directory used to be Documentation/web/ly-examples -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in examples
On 05/02/2012 5:25 PM, Federico Bruni wrote: I wonder why the website image is wrong. git log Documentation/ly-example/tab-example.ly doesn't show the full history of the file (maybe because the directory has been renamed?) You may try with git log --follow -- Julien ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
