Re: forcing a specific notehead glyph
Am 01.04.2013 05:56, schrieb luis jure: on 2013-03-31 at 16:50 Neil Puttock wrote: This should just be `0'. hi neil, i'm sorry, but i don't quite understand how to modify the function suggested by harm to address the problem you mention. IIUC, he proposed that you remove the last line in the cited example and replace it by the digit '0', like this: ;; If laThin-NoteHead for bassdrum is detected, ;; change duration-log, else default. (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum)) (ly:grob-set-property! grob 'duration-log 0) should become ;; If laThin-NoteHead for bassdrum is detected, ;; change duration-log, else default. (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum)) 0 the rest of the function remains unaffected. HTH, Marc best, lj ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cross-voice arpeggio moves accidental away from notehead
Nick Payne-3 wrote See example below. The chord across two voices has the accidental next to the notehead. Add an arpeggio and the accidental and arpeggio both get spaced away to the left. How do I move the accidental back next to the notehead? thanks, Nick I've added https://code.google.com/p/lilypond/issues/detail?id=3289colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary to the tracker! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Cross-voice-arpeggio-moves-accidental-away-from-notehead-tp143711p143715.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
Alberto Simões-2 wrote
Hello
Although I can add manually text binding it to a note with
^\markup{...}, how can I add an annotation to be placed exactly in the
center of the page, between two staves?
The manual refers a Separate Text, but it is placed between scores,
and I would like to keep the score (it is the same music, just a note).
do you mean something like
\score{ … }
\markup { … }
\score{ … }
?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Kind-of-title-beetween-staves-tp143709p143716.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
Urs Liska-4 wrote Is it possible to refer to a staff relative to the current staff and not by its name? So, is it possible to write something like \change Staff = previous/next or higher/lower instead of \change Staff = Explicit-name-of-staff inside a PianoStaff? I'd be interested in creating a generic command like \staffUp or \staffDown. hi Urs seems logical - in a two stave score you can only change up or down depending on where you actually are and LilyPond should be able to detect that! are you proposing to build such a command or would you like to add a feature request?! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Refer-to-a-staff-relatively-not-by-name-tp143705p143717.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
2013/4/1 Eluze elu...@gmail.com:
Alberto Simões-2 wrote
Hello
Although I can add manually text binding it to a note with
^\markup{...}, how can I add an annotation to be placed exactly in the
center of the page, between two staves?
The manual refers a Separate Text, but it is placed between scores,
and I would like to keep the score (it is the same music, just a note).
The regression test ‘context-mod-with.ly’ in
http://lilypond.org/doc/v2.17/input/regression/collated-files.html
uses a nice trick to put titles to staves using different
\mark\markup{} . I found it useful for labeling staves.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
help in adapting lilypond to new notation
Hi, Would anybody be willing to adapt the lilypond software so that we can see the musical scores in the CEST system ? In the link bellow you can find a summary of the system. http://wwwae.ciemat.es/~fernand/musicacest/summary_cest_system.doc (spanish : http://wwwae.ciemat.es/~fernand/musicacest/Cursillo%20Seminario%20C%20N%20corregido.doc) Best, Juan Pablo ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
On 31 March 2013 22:36, Urs Liska li...@ursliska.de wrote: Is it possible to refer to a staff relative to the current staff and not by its name? So, is it possible to write something like \change Staff = previous/next or higher/lower instead of \change Staff = Explicit-name-of-staff inside a PianoStaff? I'd be interested in creating a generic command like \staffUp or \staffDown. Best Urs I have a piece for four keyboards where a motif that changes staff note-by-note makes its way through all of the keyboards. Something like this would be useful... If there are normally a limited number of keyboards in any one piece, maybe the following pseudo-code might work: function ChangeStaff() current = GetCurrentStaff() if current == PianoOneRH then newStaff = PianoOneLH elseif current == PianoOneLH then newStaff = PianoOneRH elseif current == PianoTwoRH then newStaff = PianoTwoLH elseif current == PianoTwoLH then newStaff = PianoTwoRH end SetCurrentStaff(newStaff) end It would depend on the name of the current staff being available to Scheme, which I don’t imagine would be a problem. Vaughan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Suppressing an accidental inside a chord
On a different topic you helpfully suggested:
On Tue, 2013-03-26 at 12:58 +0100, Urs Liska wrote:
You can use
suppressAccidental = {
\once \override Accidental #'stencil = ##f
}
I notice this can't be used on notes inside chords - I've been looking
at
http://lilypond.org/doc/v2.16/Documentation/notation/visibility-of-objects
but I don't see any clues there - is a different sort of syntax needed
to suppress the accidental in this case or can suppressAccidental be
changed to work on this
ces'' \suppressAccidental dis'''
as well? (I am using the current stable LilyPond)
Richard
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
Eluze elu...@gmail.com schrieb: Urs Liska-4 wrote Is it possible to refer to a staff relative to the current staff and not by its name? So, is it possible to write something like \change Staff = previous/next or higher/lower instead of \change Staff = Explicit-name-of-staff inside a PianoStaff? I'd be interested in creating a generic command like \staffUp or \staffDown. hi Urs seems logical - in a two stave score you can only change up or down depending on where you actually are and LilyPond should be able to detect that! are you proposing to build such a command or would you like to add a feature request?! If it is possible to retrieve the necessary information (i.e. current, previous and next staff context) I'll give it a try. If it isn't I'll post a feature request on bug-lilypond. Of course I'm also talking about PianoStaves with more than two staves in it. BTW does \change Staff work only in the context of a PianoStaff (can't check that ATM)? Best Urs Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Refer-to-a-staff-relatively-not-by-name-tp143705p143717.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
on 2013-04-01 at 08:20 Marc Hohl wrote:
the rest of the function remains unaffected.
ok, now i see. for the benefit of the archives, i confirm that the full
example below works to perfection with lilypond-2.17.15. no errors, and
the output is exactly what i wanted.
thank you all!
lj
\version 2.17.15
alwaysPrintWholeLaThinBassDrum =
\override NoteHead #'duration-log =
#(lambda (grob)
(let* ((style (ly:grob-property grob 'style))
(grob-probs (ly:grob-properties grob))
(cause (assoc-get 'cause grob-probs))
(drum-type (ly:prob-property cause 'drum-type)))
(if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
0
(note-head::calc-duration-log grob
#(define mydrums
'(
(bassdrum laThin #f -1)
(hihat laThin #f 1)
))
\new DrumStaff
\with {
\override StaffSymbol #'line-count = #2
drumStyleTable = #(alist-hash-table mydrums)
\alwaysPrintWholeLaThinBassDrum
}
\drummode { bd8 bd bd4 bd2 | hh8 hh hh4 hh2 }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Suppressing an accidental inside a chord
2013/4/1 Richard Shann richard.sh...@virgin.net
On a different topic you helpfully suggested:
On Tue, 2013-03-26 at 12:58 +0100, Urs Liska wrote:
You can use
suppressAccidental = {
\once \override Accidental #'stencil = ##f
}
I notice this can't be used on notes inside chords - I've been looking
at
http://lilypond.org/doc/v2.16/Documentation/notation/visibility-of-objects
but I don't see any clues there - is a different sort of syntax needed
to suppress the accidental in this case or can suppressAccidental be
changed to work on this
ces'' \suppressAccidental dis'''
as well? (I am using the current stable LilyPond)
Richard
inside a chord you need to use \tweak
you find some examples in the Learning Manual (lilypond.org seems down at
the moment)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
Thanks for the idea, but I'm looking for a generic solution tha doesn't rely on given staff names. Best Urs Vaughan McAlley vaug...@mcalley.net.au schrieb: On 31 March 2013 22:36, Urs Liska li...@ursliska.de wrote: Is it possible to refer to a staff relative to the current staff and not by its name? So, is it possible to write something like \change Staff = previous/next or higher/lower instead of \change Staff = Explicit-name-of-staff inside a PianoStaff? I'd be interested in creating a generic command like \staffUp or \staffDown. Best Urs I have a piece for four keyboards where a motif that changes staff note-by-note makes its way through all of the keyboards. Something like this would be useful... If there are normally a limited number of keyboards in any one piece, maybe the following pseudo-code might work: function ChangeStaff() current = GetCurrentStaff() if current == PianoOneRH then newStaff = PianoOneLH elseif current == PianoOneLH then newStaff = PianoOneRH elseif current == PianoTwoRH then newStaff = PianoTwoLH elseif current == PianoTwoLH then newStaff = PianoTwoRH end SetCurrentStaff(newStaff) end It would depend on the name of the current staff being available to Scheme, which I don’t imagine would be a problem. Vaughan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
2013/3/31 Neil Puttock n.putt...@gmail.com On 31 March 2013 12:05, Thomas Morley thomasmorle...@googlemail.com wrote: Hi, I downloaded 2.17.15 this morning and tried to compile my code, again: no problem. Perhaps some copy/paste error? To be sure, I've attached the file. Your code does naughty things inside a callback. I should have seen the problem myself :( LilyPond turns a blind eye to such things unless you're compiling with optimising disabled. I don't know anything about optimising. Searching the archives, it seems that optimising is enabled in every released version. IIUC, it could be disabled for compiling LilyPond from master. How to do, i.e what should I type? I found no hint in our manuals. alwaysPrintWholeLaThinBassDrum = \override NoteHead #'duration-log = #(lambda (grob) (let* ((style (ly:grob-property grob 'style)) (grob-probs (ly:grob-properties grob)) (cause (assoc-get 'cause grob-probs)) (drum-type (ly:prob-property cause 'drum-type))) ;; If laThin-NoteHead for bassdrum is detected, ;; change duration-log, else default. (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum)) (ly:grob-set-property! grob 'duration-log 0) This should just be `0'. Yep. Cheers, Neil Thanks, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
Eluze wrote
Alberto Simões-2 wrote
Hello
Although I can add manually text binding it to a note with
^\markup{...}, how can I add an annotation to be placed exactly in the
center of the page, between two staves?
The manual refers a Separate Text, but it is placed between scores,
and I would like to keep the score (it is the same music, just a note).
do you mean something like
\score{ … }
\markup { … }
\score{ … }
or you can add such a monstrous construct like
\version 2.17.15
\new Staff \relative f {
c1
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
c
}
inside a \score { }
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Kind-of-title-beetween-staves-tp143709p143731.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
It's not obvious, but this page should help: http://lilypond.org/doc/v2.17/Documentation/contributor/compiling-regression-tests -- Phil Holmes - Original Message - From: Thomas Morley To: Neil Puttock Cc: lilypond-user Sent: Monday, April 01, 2013 1:01 PM Subject: Re: forcing a specific notehead glyph 2013/3/31 Neil Puttock n.putt...@gmail.com On 31 March 2013 12:05, Thomas Morley thomasmorle...@googlemail.com wrote: Hi, I downloaded 2.17.15 this morning and tried to compile my code, again: no problem. Perhaps some copy/paste error? To be sure, I've attached the file. Your code does naughty things inside a callback. I should have seen the problem myself :( LilyPond turns a blind eye to such things unless you're compiling with optimising disabled. I don't know anything about optimising. Searching the archives, it seems that optimising is enabled in every released version. IIUC, it could be disabled for compiling LilyPond from master. How to do, i.e what should I type? I found no hint in our manuals. alwaysPrintWholeLaThinBassDrum = \override NoteHead #'duration-log = #(lambda (grob) (let* ((style (ly:grob-property grob 'style)) (grob-probs (ly:grob-properties grob)) (cause (assoc-get 'cause grob-probs)) (drum-type (ly:prob-property cause 'drum-type))) ;; If laThin-NoteHead for bassdrum is detected, ;; change duration-log, else default. (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum)) (ly:grob-set-property! grob 'duration-log 0) This should just be `0'. Yep. Cheers, Neil Thanks, Harm -- ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
On 01/04/13 13:02, Eluze wrote:
Eluze wrote
Alberto Simões-2 wrote
Hello
Although I can add manually text binding it to a note with
^\markup{...}, how can I add an annotation to be placed exactly in the
center of the page, between two staves?
The manual refers a Separate Text, but it is placed between scores,
and I would like to keep the score (it is the same music, just a note).
do you mean something like
\score{ … }
\markup { … }
\score{ … }
or you can add such a monstrous construct like
\version 2.17.15
\new Staff \relative f {
c1
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
c
}
inside a \score { }
Yep, monstruous, but probably that is what I want.
Or I am not yet used to how \score works :-)
Thank you
Alberto
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
2013/4/1 Phil Holmes m...@philholmes.net ** It's not obvious, but this page should help: http://lilypond.org/doc/v2.17/Documentation/contributor/compiling-regression-tests -- Phil Holmes - Original Message - *From:* Thomas Morley thomasmorle...@googlemail.com *To:* Neil Puttock n.putt...@gmail.com *Cc:* lilypond-user lilypond-user@gnu.org *Sent:* Monday, April 01, 2013 1:01 PM *Subject:* Re: forcing a specific notehead glyph 2013/3/31 Neil Puttock n.putt...@gmail.com LilyPond turns a blind eye to such things unless you're compiling with optimising disabled. I don't know anything about optimising. Searching the archives, it seems that optimising is enabled in every released version. IIUC, it could be disabled for compiling LilyPond from master. How to do, i.e what should I type? I found no hint in our manuals. Hi Phil, thanks for the hint. Meanwhile I tried: harm@harm-laptop ~/lilypond-git/build (master)$ ../configure --disable-optimising [skipping the output] harm@harm-laptop ~/lilypond-git/build (master)$ make [skipping the output] Though, while compiling the code with this built I couldn't reproduce the error Luis reported. What am I missing? -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
On 01/04/13 13:26, Alberto Simões wrote:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
Hmms, this doesn't seem to work with version 2.16...
Cheers
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
custom articulation inside custom drumstaff
hello list, i have yet another question regarding the definition of a custom drumstaff, and it is how to add a custom articulation. it's actually two questions, the first one is how to make custom articulations available inside #define mydrums(). i managed to do that adding a custom articulation in script.scm, but somehow i fail to see how to put the definition in a separate file that i could include (script.scm will be rewritten every time i install lilypond) the second question later, if i manage to solve this... best, lj ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
On 01/04/13 13:41, Alberto Simões wrote:
On 01/04/13 13:26, Alberto Simões wrote:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
Hmms, this doesn't seem to work with version 2.16...
Changed to:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber #'stencil = ##f
\override StaffSymbol #'line-count = #0
\override TextScript #'staff-padding = #'()
\override KeySignature #'stencil = ##f
\override Score.Clef #'stencil = ##f
}
s1 -\markup{Ao Prefácio} \bar
\startStaff
\break
\cadenzaOff
but doesn't work. Just some empty space at the top.
Cheers
ambs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
On 01/04/13 13:43, Alberto Simões wrote:
On 01/04/13 13:41, Alberto Simões wrote:
On 01/04/13 13:26, Alberto Simões wrote:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
Hmms, this doesn't seem to work with version 2.16...
Changed to:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber #'stencil = ##f
\override StaffSymbol #'line-count = #0
\override TextScript #'staff-padding = #'()
\override KeySignature #'stencil = ##f
\override Score.Clef #'stencil = ##f
}
s1 -\markup{Ao Prefácio} \bar
\startStaff
\break
\cadenzaOff
but doesn't work. Just some empty space at the top.
Going in the multiple \score use :)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
on 2013-04-01 at 14:33 Thomas Morley wrote: Though, while compiling the code with this built I couldn't reproduce the error Luis reported. What am I missing? i'm afraid i can't be of much help, i'm building lilypond on a gentoo linux using an ebuild (a script used by gentoo to fetch sources, configure, compile and install packages). looking at the ebuild i see that it uses these configure options: --disable-documentation --disable-optimising --disable-pipe more than that i don't know, tut mir leid... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Kind of title beetween staves
Alberto Simões-2 wrote
On 01/04/13 13:43, Alberto Simões wrote:
On 01/04/13 13:41, Alberto Simões wrote:
On 01/04/13 13:26, Alberto Simões wrote:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber.stencil=##f
\override StaffSymbol.line-count=#0
\override TextScript.staff-padding=#'()
\override KeySignature.stencil=##f
\override Score.Clef.stencil=##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
Hmms, this doesn't seem to work with version 2.16...
Changed to:
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber #'stencil = ##f
\override StaffSymbol #'line-count = #0
\override TextScript #'staff-padding = #'()
\override KeySignature #'stencil = ##f
\override Score.Clef #'stencil = ##f
}
s1 -\markup{Ao Prefácio} \bar
\startStaff
\break
\cadenzaOff
but doesn't work. Just some empty space at the top.
Going in the multiple \score use :)
___
lilypond-user mailing list
lilypond-user@
https://lists.gnu.org/mailman/listinfo/lilypond-user
well, you should post the whole code that doesn't compile! otherwise it's
not possible to trace an error.
for earlier versions you may write
\new Staff \relative f' {
c1
\cadenzaOn
\stopStaff
\break
\once {
\override Score.BarNumber #'stencil =##f
\override StaffSymbol #'line-count =#0
\override TextScript #'staff-padding =#'()
\override KeySignature #'stencil =##f
\override Score.Clef #'stencil =##f
}
s1 -\markup text \bar
\startStaff
\break
\cadenzaOff
c1
}
which runs perfectly with 2.16.…
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Kind-of-title-beetween-staves-tp143709p143742.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RemoveEmptyStaves and the ambitus_engraver
I'm not top posting.
It seems that \RemoveEmptyStaves doesn't play very well with the
ambitus_engraver.
In this example, I'm trying to get the treble staff removed in the
first two systems, and appear with an ambitus on the third.
It is removed correctly in the first system. But reappears in the
second. If I comment out the line (*), then the staves are removed as
needed, but the ambitus is too of course.
---
\version 2.17.11
\paper { ragged-right = ##t }
\layout {
\context {
\type Engraver_group
\name MainSequence
\accepts Voice
\consists Ambitus_engraver %% (*)
\override AmbitusNoteHead.break-visibility = ##(#f #t #t)
\override AmbitusLine.break-visibility = ##(#f #t #t)
\override AmbitusAccidental.break-visibility = ##(#f #t #t)
}
\context {
\Staff
\accepts MainSequence
\override VerticalAxisGroup.remove-empty = ##t
\override VerticalAxisGroup.remove-first = ##t
}
}
\new ChoirStaff
\new Staff \relative c' {
\clef treble
\skip 1*8
\new MainSequence {
\repeat unfold 2 { e1 e'1 }
}
\bar |.
}
\new Staff \relative c {
\clef bass
\repeat unfold 4 {e1} \break
\repeat unfold 4 {e1} \break
\repeat unfold 4 {e1}
}
---
It looks as if the ambitus is keeping the system alive. I can't get it
to work by setting keepAliveInterfaces in the staff context either.
Has anyone any ideas?
Thanks for any help
Roman
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Suppressing an accidental inside a chord
Thank you - that worked nicely. Denemo now has a hide accidental
command :)
Richard
On Mon, 2013-04-01 at 11:50 +0200, Federico Bruni wrote:
2013/4/1 Richard Shann richard.sh...@virgin.net
On a different topic you helpfully suggested:
On Tue, 2013-03-26 at 12:58 +0100, Urs Liska wrote:
You can use
suppressAccidental = {
\once \override Accidental #'stencil = ##f
}
I notice this can't be used on notes inside chords - I've been
looking
at
http://lilypond.org/doc/v2.16/Documentation/notation/visibility-of-objects
but I don't see any clues there - is a different sort of
syntax needed
to suppress the accidental in this case or can
suppressAccidental be
changed to work on this
ces'' \suppressAccidental dis'''
as well? (I am using the current stable LilyPond)
Richard
inside a chord you need to use \tweak
you find some examples in the Learning Manual (lilypond.org seems down
at the moment)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\relative { } in 2.17.15
Hi, I thought I had followed the discussion about \relative without startpitch. I liked the idea and started using it. In 2.17.15 this feature no longer seems to work. I get an error. What did I miss? Thanks, Paul Scott ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
Urs Liska-4 wrote
Of course I'm also talking about PianoStaves with more than two staves in
it.
BTW does \change Staff work only in the context of a PianoStaff (can't
check that ATM)?
it should work with any staff-grouper
here is an example where the melody jumps from one staff to the other -
and it does not need to be the nearest (up or down)!
\new ChoirStaff
\new Staff = 1 { \clef treble_8 s1 * 6 }
\new Staff = 2 { \clef treble s1 * 6 }
\new Staff = 3 { \clef alto s1 * 6 }
\new Staff = 4 \relative f {
\clef bass c4 d e f
\change Staff = 3 g' a h c
\change Staff = 2 g a h c
\change Staff = 1 g, a h c
\change Staff = 3 g a h c
\change Staff = 4 g a h c
}
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Refer-to-a-staff-relatively-not-by-name-tp143705p143746.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
Paul Scott-4 wrote Hi, I thought I had followed the discussion about \relative without startpitch. I liked the idea and started using it. In 2.17.15 this feature no longer seems to work. I get an error. What did I miss? yes, it's mandatory to use a pitch after \relative, see https://code.google.com/p/lilypond/issues/detail?id=3245colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary or http://lilypond.1069038.n5.nabble.com/Proposed-new-available-and-recommended-behavior-of-relative-td142217.html I believe the behavior of \relative in this version is being tested. Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/relative-in-2-17-15-tp143745p143747.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
On Mon, Apr 01, 2013 at 10:09:24AM -0700, Eluze wrote: Paul Scott-4 wrote Hi, I thought I had followed the discussion about \relative without startpitch. I liked the idea and started using it. In 2.17.15 this feature no longer seems to work. I get an error. What did I miss? yes, it's mandatory to use a pitch after \relative, see It's not mandatory in 2.17.14. It works quite well. Paul https://code.google.com/p/lilypond/issues/detail?id=3245colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary or http://lilypond.1069038.n5.nabble.com/Proposed-new-available-and-recommended-behavior-of-relative-td142217.html I believe the behavior of \relative in this version is being tested. Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/relative-in-2-17-15-tp143745p143747.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
OK, thanks for the information.
And does anybody know how/if one can retrieve information about the existing
(staff) context? Some property accible by Scheme?
Eluze elu...@gmail.com schrieb:
Urs Liska-4 wrote
Of course I'm also talking about PianoStaves with more than two
staves in
it.
BTW does \change Staff work only in the context of a PianoStaff
(can't
check that ATM)?
it should work with any staff-grouper
here is an example where the melody jumps from one staff to the other
-
and it does not need to be the nearest (up or down)!
\new ChoirStaff
\new Staff = 1 { \clef treble_8 s1 * 6 }
\new Staff = 2 { \clef treble s1 * 6 }
\new Staff = 3 { \clef alto s1 * 6 }
\new Staff = 4 \relative f {
\clef bass c4 d e f
\change Staff = 3 g' a h c
\change Staff = 2 g a h c
\change Staff = 1 g, a h c
\change Staff = 3 g a h c
\change Staff = 4 g a h c
}
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Refer-to-a-staff-relatively-not-by-name-tp143705p143746.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
xml
hi all i'm really sorry if the thing i would like to discuss is a very discussed topic. i made a lot of searches on the net trying to understand if it is possible to export the lilypond score in order to import it in FInale or Sibelius (xml) I found just the Midi option which is trivial option because you loose a lot of informations. i tried with musescore, but i did't find the way. do you know if is possible to export and import form lilypond and FInale / SIbeliius? can you please help me? before i start to copy by hand my wonderful lilypond scores? thank you very much. Lorenzo ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
Paul Scott-4 wrote It's not mandatory in 2.17.14. It works quite well. but in 2.17.15 it is as the links I sent explain! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/relative-in-2-17-15-tp143745p143752.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: xml
I'm sorry to tell you that this isn't possible yet. It seems it wouldn't be too complicated to get at least the basic content (without LilyPond's superior layout quality) to xml. But it hasn't been done yet. Urs lorenzo bianchi lorenzo.bian...@lorbi.info schrieb: hi all i'm really sorry if the thing i would like to discuss is a very discussed topic. i made a lot of searches on the net trying to understand if it is possible to export the lilypond score in order to import it in FInale or Sibelius (xml) I found just the Midi option which is trivial option because you loose a lot of informations. i tried with musescore, but i did't find the way. do you know if is possible to export and import form lilypond and FInale / SIbeliius? can you please help me? before i start to copy by hand my wonderful lilypond scores? thank you very much. Lorenzo ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
On Mon, Apr 01, 2013 at 10:09:24AM -0700, Eluze wrote: Paul Scott-4 wrote Hi, I thought I had followed the discussion about \relative without startpitch. I liked the idea and started using it. In 2.17.15 this feature no longer seems to work. I get an error. What did I miss? yes, it's mandatory to use a pitch after \relative, see https://code.google.com/p/lilypond/issues/detail?id=3245colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary or http://lilypond.1069038.n5.nabble.com/Proposed-new-available-and-recommended-behavior-of-relative-td142217.html I believe the behavior of \relative in this version is being tested. So you believe the old (startpitch optional) behavior will be restored after the testing? Paul Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/relative-in-2-17-15-tp143745p143747.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: xml
ouh.. :( thank you Lorenzo On Apr 1, 2013, at 10:52 PM, Urs Liska wrote: I'm sorry to tell you that this isn't possible yet. It seems it wouldn't be too complicated to get at least the basic content (without LilyPond's superior layout quality) to xml. But it hasn't been done yet. Urs lorenzo bianchi lorenzo.bian...@lorbi.info schrieb: hi all i'm really sorry if the thing i would like to discuss is a very discussed topic. i made a lot of searches on the net trying to understand if it is possible to export the lilypond score in order to import it in FInale or Sibelius (xml) I found just the Midi option which is trivial option because you loose a lot of informations. i tried with musescore, but i did't find the way. do you know if is possible to export and import form lilypond and FInale / SIbeliius? can you please help me? before i start to copy by hand my wonderful lilypond scores? thank you very much. Lorenzo lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: custom articulation inside custom drumstaff
2013/4/1 luis jure l...@internet.com.uy
hello list, i have yet another question regarding the definition of a
custom drumstaff, and it is how to add a custom articulation.
it's actually two questions, the first one is how to make custom
articulations available inside #define mydrums().
i managed to do that adding a custom articulation in script.scm, but
somehow i fail to see how to put the definition in a separate file that i
could include (script.scm will be rewritten every time i install lilypond)
the second question later, if i manage to solve this...
best,
lj
Hi Luis,
below my approach.
Several comments in code, file and png attached.
Hope there are no problems, I tested it with 2.16.2 up to 2.17.16 from
latest master.
\version 2.16.2 %% and higher
%% Although, it is public I didn't manage to get full acces to
%% `default-script-alist´ from/scm/script.scm.
%% It is possible to modify the values, though, I couldn't create a new
entry.
%%
%% Anyway, working on a copy of `default-script-alist´ guarantees no
bleed-over.
#(define my-script-alist default-script-alist)
%% Some crazy stencils :)
#(define my-crazy-stil
;; A longish ellipse
(ly:stencil-in-color
(make-partial-ellipse-stencil 4 0.5 10 10 0.13 #t #t)
1 0 0))
#(define my-crazy-stil-2
;; A small hexagon
(let* ((th 0.1)
;; Value @code{6} returns a hexagon, try others.
(alpha-step (/ (* 2 PI) 6))
(alpha-start (/ alpha-step 2))
(radius 0.7)
(polypoints
(let loop ((alpha alpha-start))
(if ( alpha (* 2 PI))
'()
(cons (* (abs radius) (sin alpha))
(cons (- 0 (* (abs radius) (cos alpha)))
(loop (+ alpha alpha-step
(ly:make-stencil `(polygon ',polypoints ,th #f
%% Two alists with the name of the new articulation and its settings.
#(define my-wish-list-1
`(ellipse
. (
(avoid-slur . around)
(padding . 0.20)
(stencil . ,my-crazy-stil)
;(direction . ,DOWN)
(side-relative-direction . ,DOWN
#(define my-wish-list-2
`(hexagon
. (
(avoid-slur . around)
(padding . 0.40)
(stencil . ,my-crazy-stil-2)
;(direction . ,DOWN)
(side-relative-direction . ,DOWN
%% A macro setting the lists from above in the copy of
`default-script-alist´
%% I didn't manage to program some looping, mapping ... How to do?
%% For now, every new script has to be inserted in a single run.
#(define-macro (set-my-script-alist! ls-1 ls-2)
Creates a new key-value-pair, taken from ls-2, in ls-1
`(set! ,ls-1
(if (and (pair? ,ls-2) (pair? (cadr ,ls-2)))
(assoc-set! ,ls-1 (car ,ls-2) (cdr ,ls-2))
(begin
(ly:warning (_Unsuitable list\n\t~a \n\tdetected, ignoring. )
,ls-2)
,ls-1
#(set-my-script-alist! my-script-alist my-wish-list-1)
#(set-my-script-alist! my-script-alist my-wish-list-2)
%% from
http://lists.gnu.org/archive/html/lilypond-user/2013-04/msg9.html
alwaysPrintWholeLaThinBassDrum =
\override NoteHead #'duration-log =
#(lambda (grob)
(let* ((style (ly:grob-property grob 'style))
(grob-probs (ly:grob-properties grob))
(cause (assoc-get 'cause grob-probs))
(drum-type (ly:prob-property cause 'drum-type)))
;; If laThin-NoteHead for bassdrum is detected,
;; change duration-log, else default.
(if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
0
(note-head::calc-duration-log grob
%% A new drum-table
#(define mydrums
'(
(bassdrumlaThinellipse-1)
(hihat laThin hexagon 3)
))
%% To use the new scripts call them in \layout
\layout {
\context {
\Score
scriptDefinitions = #my-script-alist
}
}
\new DrumStaff
\with {
\override StaffSymbol #'line-count = #2
drumStyleTable = #(alist-hash-table mydrums)
\alwaysPrintWholeLaThinBassDrum
}
\drummode {
bd8 bd bd2. hh1 hh2 hh4 hh8 hh
}
%% To use in \notemode you may want to use:
ellipse = #(make-articulation ellipse)
hexagon = #(make-articulation hexagon)
%% Shortcuts.
%% TODO: How to create more shortcuts? I didn't test so far.
%% Below are redefined ones.
dashDash = ellipse
dashHat = hexagon
\relative c' {
c1\ellipse d^\ellipse
e\hexagon f^\hexagon
c'1-- d_-
e-^ f_^
}
\header {
title = New Scripts
subtitle = for
subsubtitle = \markup \column {
\\drummode and \\notemode
\vspace #2
}
}
HTH,
Harm
new-scripts.ly
Description: Binary data
attachment: new-scripts.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: forcing a specific notehead glyph
2013/4/1 luis jure l...@internet.com.uy on 2013-04-01 at 14:33 Thomas Morley wrote: Though, while compiling the code with this built I couldn't reproduce the error Luis reported. What am I missing? i'm afraid i can't be of much help, i'm building lilypond on a gentoo linux using an ebuild (a script used by gentoo to fetch sources, configure, compile and install packages). looking at the ebuild i see that it uses these configure options: --disable-documentation --disable-optimising --disable-pipe more than that i don't know, tut mir leid... I tried it with all of them. Though, I couldn't reproduce your error. -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: custom articulation inside custom drumstaff
on 2013-04-02 at 00:01 Thomas Morley wrote: below my approach. Several comments in code, file and png attached. like wow, this is indeed terrific! thank you! it'll take a while before i understand the code enough to adapt it to my needs, but this is a great start. Hope there are no problems, I tested it with 2.16.2 up to 2.17.16 from latest master. compiled perfectly here, with 2.17.15. thank you again! lj ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Refer to a staff relatively, not by name
2013/4/1 Urs Liska li...@ursliska.de
OK, thanks for the information.
And does anybody know how/if one can retrieve information about the existing
(staff) context? Some property accible by Scheme?
Hi Urs,
below a possibility, though, not sure if it is really helpful.
I'm using Eluze's example and
http://lists.gnu.org/archive/html/lilypond-user/2010-01/msg00668.html
Thanks Reinhold.
\verson 2.17.15
Helper functions, which simply print out the observed Music
in a nice format:
#(define (format-ctx engraver event)
(let* ((context (ly:translator-context engraver))
(ctx (ly:context-id context))
(ctx-name (ly:context-name context))
;(mus (ly:event-property event 'music))
)
(ly:message We are in \~a\ with name \~a\\n\n ctx-name ctx)
)
)
The actual engraver definition: We just install a listener.
ctxInfo =
#(list
(cons 'listeners
(list
(cons 'note-event format-ctx
\layout {
\context {
% I add this to the score, so all voices are caught. You can also only add
% the engraver to selected voices to get the statistics split down.
\Staff
\consists #ctxInfo
}
}
\new ChoirStaff
\new Staff = One \with { instrumentName = ctx 1 }
{ \clef treble_8 s1 * 6 }
\new Staff = Two \with { instrumentName = ctx 2 }
{ \clef treble s1 * 6 }
\new Staff = Three \with { instrumentName = ctx 3 }
{ \clef alto s1 * 6 }
\new Staff = Four \with { instrumentName = ctx 4 }
\relative f {
\clef bass c4 d e f
\change Staff = Three g' a b c
\change Staff = Two g a b c
\change Staff = One g, a b c
\change Staff = Three g a b c
\change Staff = Four g a b c
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
Paul Scott waterho...@ultrasw.com writes:
Hi,
I thought I had followed the discussion about \relative without startpitch.
I liked the idea and started using it.
Uh, you started using it? The previous behavior of \relative { ... }
was to be equivalent to \relative c' { ... }, so you have been using
something else.
In 2.17.15 this feature no longer seems to work. I get an error.
After using convert-ly, your \relative { ... } would have gotten changed
to \relative c' { ... } which corresponds to the previous meaning.
What did I miss?
Issue 3245 is still pending. It will likely appear in 2.17.16. Once it
does, using \relative { ... } will exhibit the new meaning.
In the mean time, you can use \relative f { ... } to emulate the
behavior of no starting pitch. Its sole disadvantage is one of
aesthetics: the f looks uncalled for but does the trick, being in the
middle of the unshifted octave.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \relative { } in 2.17.15
Eluze elu...@gmail.com writes:
Paul Scott-4 wrote
So you believe the old (startpitch optional) behavior will be restored
after
the testing?
no idea - I've got used to the optional start pitch myself (i.e. I
nearly never used a pitch with my laziness); I wouldn't mind if it
came back (also in the form of f' being the default, as discussed
other-where)
It would default to f rather than f'. convert-ly would change your old
sources to use \relative c' explicitly. Issue 3229 (not going to pass
anytime soon I guess) has a rather more tricky convert-ly rule which
changes almost everything to the new \relative { ... } form. I'll try
to give a way to use optional convert-ly rules (so that users may call
this converter on their own if they want to), but that is likely going
to take weeks.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
