Re: duration and pitch in a function
Hi Paolo,
this compiles in 2.14.2 on my machine:
--snip--
\version 2.14.2
myFunction = #(define-music-function (parser location foobar) (ly:duration?)
(make-music 'SequentialMusic 'elements (list
(make-music 'EventChord 'elements (list
(make-music 'NoteEvent 'duration foobar 'pitch (ly:make-pitch 1 0 0))
))
))
)
{
\myFunction #(ly:make-duration 2 0 1 1) r4
}
--snip--
In your first message you wrote something about one note, that is repeated 3
times, while augmenting its length - if I did understand your question right.
I recommend the us of \displayMusic, to see, how notes are constructed in
scheme. Then you might have one argument (... foobar) (ly:music?), a function
that copies this note and changes its duration accordingly.
HTH
cheers, Jan-Peter
Am 08.12.2011 um 10:36 schrieb Paolo Prete:
I searched in extending manual for 2.15, but I did not find a solution for
my problem.
Shortly, given this fragment of code:
myFunction = #(define-music-function (parser location foobar) (ly:duration?)
#{
a ...how_can_I_use_$foobar_as_duration_??...
#})
\new Staff \myFunction ...how_can_I_pass_duration_??...
-
...which is the right syntax and which version of lilypond could I use?
Thanks
--- Gio 8/12/11, David Kastrup d...@gnu.org ha scritto:
Da: David Kastrup d...@gnu.org
Oggetto: Re: duration and pitch in a function
A: lilypond-user@gnu.org
Data: Giovedì 8 dicembre 2011, 07:59
Paolo Prete p4olo_pr...@yahoo.it
writes:
I need to create a function that
accepts some_pitch and some_duration as arguments and
prints the
following three notes:
1) some_pitch with some_duration
2) some_pitch with some_duration*2
3) some_pitch with some_duration*3
Should I use ly:duration as type of the argument two?
ly:duration? would be the predicate. And yes,
definitely.
I can't find documentation for that.
I use LilyPond 2.12.3 but I can upgrade it if
necessary...
If you upgrade, you will find both the functionality itself
as well as
the documentation.
I don't quite remember the version; it might be necessary
to take one of
the 2.15.x releases.
--
David Kastrup
___
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
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: duration and pitch in a function
Jan-Peter Voigt jp.vo...@gmx.de writes:
Hi Paolo,
this compiles in 2.14.2 on my machine:
--snip--
\version 2.14.2
myFunction = #(define-music-function (parser location foobar) (ly:duration?)
(make-music 'SequentialMusic 'elements (list
(make-music 'EventChord 'elements (list
(make-music 'NoteEvent 'duration foobar 'pitch (ly:make-pitch 1 0 0))
))
))
)
{
\myFunction #(ly:make-duration 2 0 1 1) r4
}
Yes, it would. Unfortunately, it would not compile with the current
version since the current version does not allow duration arguments to
be specified in anything but duration syntax (along with pitches, they
are one of two currently remaining special-cased argument types).
I really don't think that it is worth investing work into creating 2.14
sources if you want to have music functions meddling with durations and
other stuff in easily maintainable ways.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Single line percussion staff with automatic note splitting
Hi. I'm trying to make a single line percussion staff with automatic
note splitting.
The single staff is confusing but I got it working by following an
example in the documentation. I have this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
(The notes are just random values.)
That works, but when I try to add the code to enable automatic note
splitting things go wrong. Following the documentation again I modify
my source to this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
} {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
But now Lilypond exits with a segmentation fault.
This is Lilypond version 2.12.3, from the Ubuntu 10.04.3 LTS x86_64
repositories.
Am I doing something wrong?
Thanks a lot.
--bart
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Footnotes documentation
Le Dec 11, 2011 à 8:06 AM, David Kastrup a écrit :
m...@apollinemike.com m...@apollinemike.com writes:
Le Dec 10, 2011 à 9:18 PM, David Kastrup a écrit :
Why don't we have \footnote \default for autonumbering (just like with
\mark),
We could...I don't understand how \default works, so I'm not sure how
to make it work here, but a tutorial would get me on my way!
Have you read Scheme function usage in EG?
Nope - this certainly helps for \default.
Anyway, let's take a look at two contenders:
There is an optional argument before number-pair giving the symbol, and
an optional markup text before the footnote. So we do
footnote =
#(define-music-function (parser location grob-name offset text footnote)
((symbol? '()) number-pair? (markup?) markup?)
(_i Attach @var{text} at @var{offset} with @var{text} referring
to @var{footnote} (use like @code{\\tweak}))
(make-music 'FootnoteEvent
'automatically-numbered (not text)
'symbol grob-name
'X-offset (car offset)
'Y-offset (cdr offset)
'text (or text (make-null-markup))
'footnote-text footnote))
And there you are.
I still am having trouble seeing what grob this would footnote?
Here, '() gets set as the grob-name for footnote. So, if footnote worked like
parenthesize, it'd presumably have code like:
parenthesize =
#(define-music-function (parser loc arg) (ly:music?)
(_i Tag @var{arg} to be parenthesized.)
(if (memq 'event-chord (ly:music-property arg 'types))
;; arg is an EventChord - set the parenthesize property
;; on all child notes and rests
(for-each
(lambda (ev)
(if (or (memq 'note-event (ly:music-property ev 'types))
(memq 'rest-event (ly:music-property ev 'types)))
(set! (ly:music-property ev 'parenthesize) #t)))
(ly:music-property arg 'elements))
;; No chord, simply set property for this expression:
(set! (ly:music-property arg 'parenthesize) #t))
arg)
Which would footnote every note and rest in the chord (w/ some extra code to
make a music-property called footnote, etc.), and even if it just applied to
one event as in the ;; No chord, simply... case, this event may result in the
creation of footnotes on several grobs. I'm not sure how code could be written
that would discern one meaningful grob and footnote it. You could pick one at
random, but this seems like it wouldn't be a gain compared to specifying the
grob in the first place.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Stanza number placing question
Hi all, When the lyrics begin with a stanza number, the number doesn't take up space in the score (as it can be seen in the attached example). When the stanza number is in the middle of a line, the number does take up space, moving the notes apart from the previous bar line. This makes sense in most cases, but with no lyrics in the previous measure, it would look better to place the stanza number before the bar line. Is there a way to achieve this? You can see the difference in the center of the attached pictures, right after the repeat sign. Thank you in advance for your answers. Zoltan attachment: BWV436.pngattachment: BWV436lily.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: duration and pitch in a function
Thanks for that hint! I will keep that in mind for future development.
I actually use 2.14 for my allday work and create my extensions according to
that syntax, because I want to be able to produce sheets day by day without
stumbling over suprisingly upcoming changes.
I know, I should have a devel (2.15 ... 2.17 ...) on my machine to be prepared
for the next release.
Paolo's excercise would be solved differently by me: I would use a ly:music?
argument and copy and augment that. And I hope, ly:music? arguments will not be
broken in future releases ;-)
Cheers,
Jan-Peter
Am 11.12.2011 um 09:45 schrieb David Kastrup:
Jan-Peter Voigt jp.vo...@gmx.de writes:
Hi Paolo,
this compiles in 2.14.2 on my machine:
--snip--
\version 2.14.2
myFunction = #(define-music-function (parser location foobar) (ly:duration?)
(make-music 'SequentialMusic 'elements (list
(make-music 'EventChord 'elements (list
(make-music 'NoteEvent 'duration foobar 'pitch (ly:make-pitch 1 0 0))
))
))
)
{
\myFunction #(ly:make-duration 2 0 1 1) r4
}
Yes, it would. Unfortunately, it would not compile with the current
version since the current version does not allow duration arguments to
be specified in anything but duration syntax (along with pitches, they
are one of two currently remaining special-cased argument types).
I really don't think that it is worth investing work into creating 2.14
sources if you want to have music functions meddling with durations and
other stuff in easily maintainable ways.
--
David Kastrup
___
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: Footnotes documentation
m...@apollinemike.com m...@apollinemike.com writes:
Le Dec 11, 2011 à 8:06 AM, David Kastrup a écrit :
Anyway, let's take a look at two contenders:
There is an optional argument before number-pair giving the symbol, and
an optional markup text before the footnote. So we do
footnote =
#(define-music-function (parser location grob-name offset text footnote)
((symbol? '()) number-pair? (markup?) markup?)
(_i Attach @var{text} at @var{offset} with @var{text} referring
to @var{footnote} (use like @code{\\tweak}))
(make-music 'FootnoteEvent
'automatically-numbered (not text)
'symbol grob-name
'X-offset (car offset)
'Y-offset (cdr offset)
'text (or text (make-null-markup))
'footnote-text footnote))
And there you are.
I still am having trouble seeing what grob this would footnote?
I have no idea. I never used footnotes. I am just giving you a single
\footnote command that can do everything that your four footnote
commands did previously. Are you telling me you don't know what your
commands actually do?
Here, '() gets set as the grob-name for footnote.
That is the default if _no_ grob-name is given before the coordinates,
and this default corresponds to _not_ setting grob-name. Which is what
your footnote commands without Grob in their name do.
So, if footnote worked like parenthesize, it'd presumably have code
like:
I was in this case not talking about parenthesize any more since your
commands don't appear to bother about working on parts of a chord. They
would need to apply tweaks or articulations to do that, and that does
not appear supported in the backend. So just forget about that
parenthesize comments. The current proposal just mimics what your
commands do for now, since your commands work at the override level
rather than at the tweak level.
You could presumably let them also work at the tweak level (and that
would presumably be a good idea in order to footnote individual chord
notes), but that would require additional backend support, and I am
currently just talking about the frontend.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Footnotes documentation
Le Dec 11, 2011 à 10:59 AM, David Kastrup a écrit :
m...@apollinemike.com m...@apollinemike.com writes:
Le Dec 11, 2011 à 8:06 AM, David Kastrup a écrit :
Anyway, let's take a look at two contenders:
There is an optional argument before number-pair giving the symbol, and
an optional markup text before the footnote. So we do
footnote =
#(define-music-function (parser location grob-name offset text footnote)
((symbol? '()) number-pair? (markup?) markup?)
(_i Attach @var{text} at @var{offset} with @var{text} referring
to @var{footnote} (use like @code{\\tweak}))
(make-music 'FootnoteEvent
'automatically-numbered (not text)
'symbol grob-name
'X-offset (car offset)
'Y-offset (cdr offset)
'text (or text (make-null-markup))
'footnote-text footnote))
And there you are.
I still am having trouble seeing what grob this would footnote?
I have no idea. I never used footnotes. I am just giving you a single
\footnote command that can do everything that your four footnote
commands did previously.
OK, but it would be impossible to reduce it to this, as there is no way for it
to lead to LilyPond intelligently and predictably choosing a grob if no default
is provided. I will, however, look into using \default.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dynamics clashing with stem of cross-staff knee beam
Le Dec 10, 2011 à 12:12 AM, Xavier Scheuer a écrit : On 9 December 2011 23:40, m...@apollinemike.com m...@apollinemike.com wrote: Thanks for bringing this to my attention. This is one of those situations that falls into the uncertain desired output category. Shifting the dynamic to the left or right dissociates it from the note, and whiting it out covers up a good portion of the stem. Mmh, this is the same uncertain desired output that is preventing an automated solution in the case of DynamicText colliding with SpanBar? It'd be not-very-hard to drum up an automated solution, but what we're really missing are examples from the literature. If you have time to peruse scores from reputable editors and send us examples, we can work from that. Maybe if there is no standard best solution, LilyPond could at least emit a Warning: collision when it occurs, isn't it? I submitted a patch that does some collision avoidance in these cases - I'll keep you posted. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: duration and pitch in a function
Jan-Peter Voigt jp.vo...@gmx.de writes: Thanks for that hint! I will keep that in mind for future development. I actually use 2.14 for my allday work and create my extensions according to that syntax, because I want to be able to produce sheets day by day without stumbling over suprisingly upcoming changes. I know, I should have a devel (2.15 ... 2.17 ...) on my machine to be prepared for the next release. Paolo's excercise would be solved differently by me: I would use a ly:music? argument and copy and augment that. And I hope, ly:music? arguments will not be broken in future releases ;-) They will. My preferred newspeak for that is they will be unbroken, namely become much more consistent and versatile. But that means that there _will_ be changes in semantics for cases that are quite cumbersome to do currently. I manage to get my syntax changes through with very little collateral damage, and convert-ly covers by far the largest portion of it. I don't do disruptive changes without good reason, and not without convert-ly rules where applicable, and as a rule, none of them gets backed out again once it is in. So there are no surprisingly upcoming changes that you can avoid in the long run by sticking with 2.14, and there is very little backpedaling in development. There has been quite a bit of heat spent on the developer lists to arrive at semi-automatic procedures that make reasonably sure that the current development master is kept in working state. I can take credit for that only so far as those procedures were partly created to withstand the strain from my flow of patches (and particularly the strain from my accompanying abuse when it got disrupted). But the results naturally made it easier for everyone to contribute exciting and numerous improvements while minimizing disturbances on the development versions' quality. Personally I would not create my extensions according to 2.14 syntax because that is so awkward. If you do git diff release/2.14.2-1..origin lily/lily-lexer.cc you'll notice that \grobdescriptions, \key, \mark, \once, \partial, \relative, \skip, \time, \times, \transpose all have disappeared from the lexer. All of those are now music functions instead of being hardwired in the syntax. And that means that your own personal extensions could also provide comparable functionality with comparable syntax. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Footnotes documentation
m...@apollinemike.com m...@apollinemike.com writes:
Le Dec 11, 2011 à 10:59 AM, David Kastrup a écrit :
m...@apollinemike.com m...@apollinemike.com writes:
Le Dec 11, 2011 à 8:06 AM, David Kastrup a écrit :
Anyway, let's take a look at two contenders:
There is an optional argument before number-pair giving the symbol, and
an optional markup text before the footnote. So we do
footnote =
#(define-music-function (parser location grob-name offset text footnote)
((symbol? '()) number-pair? (markup?) markup?)
(_i Attach @var{text} at @var{offset} with @var{text} referring
to @var{footnote} (use like @code{\\tweak}))
(make-music 'FootnoteEvent
'automatically-numbered (not text)
'symbol grob-name
'X-offset (car offset)
'Y-offset (cdr offset)
'text (or text (make-null-markup))
'footnote-text footnote))
And there you are.
I still am having trouble seeing what grob this would footnote?
I have no idea. I never used footnotes. I am just giving you a single
\footnote command that can do everything that your four footnote
commands did previously.
OK, but it would be impossible to reduce it to this, as there is no
way for it to lead to LilyPond intelligently and predictably choosing
a grob if no default is provided.
Mike, be reasonable. My proposed change in syntax does _exactly_ with
one command what your currently defined four commands do. So of course
it _is_ possible to reduce the current state to this.
There is no point in writing
\footnoteGrob #'ScriptGrob #'(2 3) x y
if you can just make
\footnote #'ScriptGrob #'(2 3) x y
do the same without disturbing the function of
\footnote #'(2 3) x y
in any way.
Whether or not the current state makes sense is a question different
from the syntax. But you are not arguing against my proposed single
definition covering all four use cases above, but rather about the
deficiencies of the functionality called by the syntax. And I don't
touch that at all.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Single line percussion staff with automatic note splitting
Hello,
On 11 December 2011 09:00, Bart Nagel b...@tremby.net wrote:
Hi. I'm trying to make a single line percussion staff with automatic
note splitting.
The single staff is confusing but I got it working by following an
example in the documentation. I have this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
(The notes are just random values.)
That works, but when I try to add the code to enable automatic note
splitting things go wrong. Following the documentation again I modify
my source to this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
} {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
But now Lilypond exits with a segmentation fault.
In 2.14.1 it does but the message is more explicit (I don't know what
2.12.x message is perhaps the same?)
--snip--
GNU LilyPond 2.14.1
Processing `untitled.ly'
Parsing...
Interpreting music...
warning: cannot find property type-check for `bar-size' (backend-type?).
perhaps a typing error?
warning: doing assignment anyway
Segmentation fault
--snip--
So that is a clue. Although it is beyond me.
regards
--
--
James
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Single line percussion staff with automatic note splitting
At 2011-12-11 11:56:29 +, James wrote: In 2.14.1 it does but the message is more explicit (I don't know what 2.12.x message is perhaps the same?) --snip-- GNU LilyPond 2.14.1 Processing `untitled.ly' Parsing... Interpreting music... warning: cannot find property type-check for `bar-size' (backend-type?). perhaps a typing error? warning: doing assignment anyway Segmentation fault --snip-- So that is a clue. Although it is beyond me. Thanks for that. Hmm, I tried commenting out the line with the bar size override and I still get a segfault. So perhaps that warning is a red herring. --bart ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Single line percussion staff with automatic note splitting
Hi,
2011/12/11 James pkx1...@gmail.com:
Hello,
On 11 December 2011 09:00, Bart Nagel b...@tremby.net wrote:
Hi. I'm trying to make a single line percussion staff with automatic
note splitting.
The single staff is confusing but I got it working by following an
example in the documentation. I have this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
(The notes are just random values.)
That works, but when I try to add the code to enable automatic note
splitting things go wrong. Following the documentation again I modify
my source to this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
} {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
But now Lilypond exits with a segmentation fault.
In 2.14.1 it does but the message is more explicit (I don't know what 2.12.x
message is perhaps the same?)
--snip--
GNU LilyPond 2.14.1
Processing `untitled.ly'
Parsing...
Interpreting music...
warning: cannot find property type-check for `bar-size' (backend-type?).
perhaps a typing error?
warning: doing assignment anyway
Segmentation fault
--snip--
So that is a clue. Although it is beyond me.
regards
--
--
James
engraver-init.ly states, that the Note_heads_engraver is removed
from the DrumVoice per default. Instead the Drum_notes_engraver is
used.
But
\new DrumVoice
\with {
\remove Drum_notes_engraver
\consists Completion_heads_engraver
}
{
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
gives the same error. So I don't know if it's possible.
BTW in 2.14 t'bar-size was altered to 'bar-extent (expecting a pair).
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Single line percussion staff with automatic note splitting
2011/12/11 Thomas Morley thomasmorle...@googlemail.com:
Hi,
2011/12/11 James pkx1...@gmail.com:
Hello,
On 11 December 2011 09:00, Bart Nagel b...@tremby.net wrote:
Hi. I'm trying to make a single line percussion staff with automatic
note splitting.
The single staff is confusing but I got it working by following an
example in the documentation. I have this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
(The notes are just random values.)
That works, but when I try to add the code to enable automatic note
splitting things go wrong. Following the documentation again I modify
my source to this:
\version 2.12.3
#(define snaredrum '((snare default #t 0)))
\new DrumStaff \with {
\remove Note_heads_engraver
\consists Completion_heads_engraver
} {
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
But now Lilypond exits with a segmentation fault.
In 2.14.1 it does but the message is more explicit (I don't know what 2.12.x
message is perhaps the same?)
--snip--
GNU LilyPond 2.14.1
Processing `untitled.ly'
Parsing...
Interpreting music...
warning: cannot find property type-check for `bar-size' (backend-type?).
perhaps a typing error?
warning: doing assignment anyway
Segmentation fault
--snip--
So that is a clue. Although it is beyond me.
regards
--
--
James
engraver-init.ly states, that the Note_heads_engraver is removed
from the DrumVoice per default. Instead the Drum_notes_engraver is
used.
But
\new DrumVoice
\with {
\remove Drum_notes_engraver
\consists Completion_heads_engraver
}
{
\override Staff.StaffSymbol #'line-positions = #'( 0 )
\override Staff.BarLine #'bar-size = #2
\set DrumStaff.drumStyleTable = #(alist-hash-table snaredrum)
\drummode {
\time 4/4
sn2. sn16 sn2. sn2. sn4 sn16
}
}
gives the same error. So I don't know if it's possible.
Sorry, typo !!
Should be
BTW in 2.14 'bar-size was altered to 'bar-extent (expecting a pair).
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to put user ly files on OSX?
Xavier Scheuer x.sche...@gmail.com wrote in message news:CADGqHRejv58mbS=0vewfg4ejoc-go3drmspfrtxvt3qchv5...@mail.gmail.com... On 7 December 2011 02:58, huzzam clari...@huzzam.com wrote: Hi-- I'm fairly new to lilypond, and am starting to write my own ly files to include. I want to put them somewhere that will be accessible easily from any score (user defaults). The only place I've so far been able to find to put them is inside the lilypond application package itself (/Applications/Lilypond.app/Contents/Resources/share/lilypond/current/ly). This obviously is annoying when I upgrade lilypond, as I have to dig in there and copy my files to the new one. Is there some place I can put them so that I can still just \include asdf.ly (without a path), but which is not inside the package itself? Something along the lines of ~/Library/lilypond or /usr/share/lilypond? There is not such features in LilyPond yet (but I'd love this too). Denis made a similar request on lilypond-devel a few days ago. http://lists.gnu.org/archive/html/lilypond-devel/2011-12/msg00073.html No developer replied at the moment; I hope one will say something about it. Then I suppose it could be added to the tracker (cc: to bug-lilypond) as a new feature request. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com Added to the tracker. See other message in newsgroup about this for the issue number. -- Phil Holmes Bug Squad ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Single line percussion staff with automatic note splitting
Hi again, to make it work, the Drum_notes_engraver should be exchanged with something like a Completion_drum_notes_engraver. Though, AFAIK a Completion_drum_notes_engraver doesn't exist. Perhaps you may want to make a feature request for this. Best, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Incorrect bar placement
Hello,
I am a relatively new lilypond user. I am working on a score and 62 measures
into the score, the bar placement is incorrect when I include a run of 16th
notes, as follows:
staffFlute = \new Staff {
\time 2/4
\set Staff.instrumentName = Flute
\set Staff.midiInstrument = flute
\key d \major
\clef treble
\relative c' {
%. (61 measures of other music)
c4-^ \acciaccatura d8 c4-^\trill \grace {b16 [cis]}
b16 \ (a g fis) e \ (d c b) %this is the measure that does not
print correctly - only 7 16th notes print in this measure
}
When I input this particular sequence, only 7 16th notes print in the measure
and the last 16th is printed in the following measure, screwing up the
placement of the subsequent measures. Previous to this, the placement of
similar runs was correct.
I would appreciate any guidance with how to fix this issue. Thanks very much.
Naomi
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Incorrect bar placement
On 11 December 2011 15:38, Naomi Gage nlg...@aol.com wrote:
Hello,
I am a relatively new lilypond user. I am working on a score and 62
measures into the score, the bar placement is incorrect when I include a run
of 16th notes, as follows:
staffFlute = \new Staff {
\time 2/4
\set Staff.instrumentName = Flute
\set Staff.midiInstrument = flute
\key d \major
\clef treble
\relative c' {
%. (61 measures of other music)
c4-^ \acciaccatura d8 c4-^\trill \grace {b16 [cis]}
b16 \ (a g fis) e \ (d c b) %this is the measure that does not print
correctly - only 7 16th notes print in this measure
}
When I input this particular sequence, only 7 16th notes print in the
measure and the last 16th is printed in the following measure, screwing up
the placement of the subsequent measures. Previous to this, the placement
of similar runs was correct.
I would appreciate any guidance with how to fix this issue. Thanks very
much.
Hello,
If I compile the piece of code you gave I get the expected output, i.e.
8 16th notes. So I guess the issue is elsewhere.
In measure 61, are you sure you do not mean to use an \afterGrace ?
c4-^ \acciaccatura d8 \afterGrace c4-^\trill { b16[ cis] }
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Incorrect bar placement
On 12/11/2011 2:38 PM, Naomi Gage wrote:
Hello,
I am a relatively new lilypond user. I am working on a score and 62
measures into the score, the bar placement is incorrect when I include
a run of 16th notes, as follows:
staffFlute = \new Staff {
\time 2/4
\set Staff.instrumentName = Flute
\set Staff.midiInstrument = flute
\key d \major
\clef treble
\relative c' {
%. (61 measures of other music)
c4-^ \acciaccatura d8 c4-^\trill \grace {b16 [cis]}
b16 \ (a g fis) e \ (d c b) %this is the measure that does not
print correctly - only 7 16th notes print in this measure
}
When I input this particular sequence, only 7 16th notes print in the
measure and the last 16th is printed in the following measure,
screwing up the placement of the subsequent measures. Previous to
this, the placement of similar runs was correct.
I would appreciate any guidance with how to fix this issue. Thanks
very much.
Naomi
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Naomi,
You didn't say which version you're using. I ran it in v2.14 and could
not reproduce the output you describe. What happens if you try just
this snippet? Does it come out wrong? If not, I would suggest looking
earlier in the input to see if there is something nudging everything
over a 1/16th note's worth.
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Incorrect bar placement
Hello,
On 11 December 2011 14:38, Naomi Gage nlg...@aol.com wrote:
Hello,
I am a relatively new lilypond user. I am working on a score and 62
measures into the score, the bar placement is incorrect when I include a
run of 16th notes, as follows:
staffFlute = \new Staff {
\time 2/4
\set Staff.instrumentName = Flute
\set Staff.midiInstrument = flute
\key d \major
\clef treble
\relative c' {
%. (61 measures of other music)
c4-^ \acciaccatura d8 c4-^\trill \grace {b16 [cis]}
b16 \ (a g fis) e \ (d c b) %this is the measure that does not print
correctly - only 7 16th notes print in this measure
}
When I input this particular sequence, only 7 16th notes print in the
measure and the last 16th is printed in the following measure, screwing up
the placement of the subsequent measures. Previous to this, the placement
of similar runs was correct.
I would appreciate any guidance with how to fix this issue. Thanks very
much.
I think there is probably something before this 'sequence' that might be
causing what you are seeing.
You don't say what version of LilyPond you are using but when I compile:
\version 2.14.1
{
\time 2/4
\set Staff.instrumentName = Flute
\set Staff.midiInstrument = flute
\key d \major
\clef treble
\relative c' {
c4-^ \acciaccatura d8 c4-^\trill \grace {b16 [cis]}
b16\ (a g fis) e \ (d c b)
}
}
It all looks fine.
Your literal example is missing a '}' before the final one (closing the
'\new Staff {') but even so it would not compile without error anyway.
Also your last crescendo is un-terminated (again LP posts a warning but
still compiles) and this doesn't seem to make any difference in the output.
So with these inconsistencies in your posted example I am suspecting that
when you said:
...Previous to this, the placement of similar runs was correct.
that whatever you did afterwards had an effect.
Regards
--
--
James
attachment: screenshot.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
how to make a songbook
Hi all, I've been using LilyPond for some time now, always to make lead sheets, or single- and multiple-page individual songs, mostly for church use. I now have quite a store of Christmas carols and similar which I'd like to do up into a booklet, perhaps printed ;landscape on letter or legal paper. I don't need to get fancy with page numbers or anything like that, as long as all my booklets are printed the same. It occurs to me that if I could import them into OpenOffice I could re-size them and arrange them there with a minimum of fuss -- I did that a few years ago (version 2.5.x), but I can't remember what I did there. How does one make a lily output suitable to import into OOo? (PNG?) I use 2.15.19 on a Windoze XP Pro laptop or 2.13.x on a PC-BSD desktop, with LilyPondTool on jEdit. -- Fr. Gordon Gilbert Penetanguishene, ON ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center NoteColumn
Hi Harm, On Sat, Dec 10, 2011 at 3:42 PM, Thomas Morley thomasmorle...@googlemail.com wrote: Hi David, thanks for doing this! I did the next step to simplify the definition, with defining read-out. Yes, this condenses the function quite a bit. Thinking about the problem some more, I came up with a way to find the grobs to either side of the note column without creating and manipulating alists. I take the filtered list of grobs you created with read-out, then sort it directly by X-coordinate in ascending order; the bounding grobs are then adjacent in the list. I get the same results with your examples. I didn't work out all the conditions so I'm sure it's easily breakable :) -David center-note-column-13.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to make a songbook
Il 11/12/2011 22:53, Father Gordon Gilbert ha scritto: Hi all, I've been using LilyPond for some time now, always to make lead sheets, or single- and multiple-page individual songs, mostly for church use. I now have quite a store of Christmas carols and similar which I'd like to do up into a booklet, perhaps printed ;landscape on letter or legal paper. I don't need to get fancy with page numbers or anything like that, as long as all my booklets are printed the same. I would use just Lilypond. I made simple books just using \include and lilypond. It occurs to me that if I could import them into OpenOffice I could re-size them and arrange them there with a minimum of fuss -- I did that a few years ago (version 2.5.x), but I can't remember what I did there. How does one make a lily output suitable to import into OOo? (PNG?) I quickly tried OooLily once, more than a year ago. Anyway the good news is that it can handle Lilypond code directly, you don't need to run lilypond before, as explained here: http://ooolilypond.sourceforge.net/ Don't know if you have to copy and paste or if you can also include an external file. Another option is Scribus: http://docs.scribus.net/index.php?lang=enpage=renderframes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to make a songbook
Le Dec 11, 2011 à 11:14 PM, Federico Bruni a écrit : Il 11/12/2011 22:53, Father Gordon Gilbert ha scritto: Hi all, I've been using LilyPond for some time now, always to make lead sheets, or single- and multiple-page individual songs, mostly for church use. I now have quite a store of Christmas carols and similar which I'd like to do up into a booklet, perhaps printed ;landscape on letter or legal paper. I don't need to get fancy with page numbers or anything like that, as long as all my booklets are printed the same. I would use just Lilypond. I made simple books just using \include and lilypond. To do this, you can check out http://lilypond.org/doc/v2.15/Documentation/notation/multiple-scores-in-a-book Cheers, MS___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Appoggiatura appears between two repeats
http://old.nabble.com/file/p32957263/Untitled.jpg
What I want is for the appoggiatura to be on the same side of the double bar
line as the D#. What I wrote looks something like what is below (at the
end). As you can see I've put the volta repeats only into the top part. Up
until now it's worked fine for everything. I don't think the \bar |. is
causing the problem, because taking it out doesn't help. The piece begins
with a quaver partial bar, but that's resolved in the first alternative. Any
help would be good.
Thanks
George
voiceOne =
\key g \major
\time 6/8
\clef treble
\relative c'' {
\repeat volta 2 {
...notes...
}
\alternative {
{ ...more notes... }
{ d32 \repeatTie cis b16 c8-. ais b4 r8 }
} \bar |.
\repeat volta 2 {
R1*3/4
...more notes...
}
\alternative {
{ ...more notes... }
{ ...more notes... }
}
}
voiceTwo =
\key g \major
\time 6/8
\clef treble
\relative c'' {
...notes...
b8 e!-. cis b8 r fis' |
\appoggiatura d8 dis8. b32( cis dis e fis16) a8. dis,!32 e fis
g a16 |
...more notes...
}
\score {
\new PianoStaff {
\context Staff = voiceOne{
\context Voice = voiceOne \voiceone
}
\context Staff = voiceTwo{
\context Voice = voiceTwo \voiceTwo
}
}
\layout{}
}
--
View this message in context:
http://old.nabble.com/Appoggiatura-appears-between-two-repeats-tp32957263p32957263.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Appoggiatura appears between two repeats
On 12 December 2011 00:30, George_ georgexu...@gmail.com wrote: http://old.nabble.com/file/p32957263/Untitled.jpg What I want is for the appoggiatura to be on the same side of the double bar line as the D#. What I wrote looks something like what is below (at the end). As you can see I've put the volta repeats only into the top part. Up until now it's worked fine for everything. I don't think the \bar |. is causing the problem, because taking it out doesn't help. The piece begins with a quaver partial bar, but that's resolved in the first alternative. Any help would be good. See NR 1.2.6 Special rhythmic concerns Grace notes Known issues and warnings [The example shown in the documentation is the same as your issue.] This can be remedied by inserting grace skips of the corresponding durations in the other staves. http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns.html#grace-notes I.e. in your voice one (first staff) add a \grace s8 before your R2. of measure 18. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 1.9.4 (beta)
Hi Will!
After install in /usr/local/
ia have this problem with midi.
I use Mandriva 2011/jackd/fluidsynth.
parser: class 'ly.lex.lilypond.ParseMusic'
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/frescobaldi_app/qmidi/player.py,
line 61, in run
self.timer_start_playing()
File /usr/lib/python2.7/site-packages/frescobaldi_app/midifile/player.py,
line 314, in timer_start_playing
self._output.reset()
File /usr/lib/python2.7/site-packages/frescobaldi_app/midifile/output.py,
line 54, in reset
self.reset_controllers()
File /usr/lib/python2.7/site-packages/frescobaldi_app/midifile/output.py,
line 79, in reset_controllers
send(event.ControllerEvent(c, event.MIDI_CTL_RESET_CONTROLLERS, 0))
File /usr/lib64/python2.7/contextlib.py, line 24, in __exit__
self.gen.next()
File /usr/lib/python2.7/site-packages/frescobaldi_app/midifile/output.py,
line 113, in sender
self.send_events(l)
File /usr/lib/python2.7/site-packages/frescobaldi_app/midifile/output.py,
line 135, in send_events
self.output.write(l)
File /usr/lib/python2.7/site-
packages/frescobaldi_app/portmidi/__init__.py, line 206, in write
self._output.Write(data)
File /usr/lib/python2.7/site-
packages/frescobaldi_app/portmidi/ctypes_pypm.py, line 112, in Write
_check_error(err)
File /usr/lib/python2.7/site-
packages/frescobaldi_app/portmidi/ctypes_pypm.py, line 189, in _check_error
PortMIDI-ctypes error [{0}]: {1}.format(err_no, err_msg))
MidiException: PortMIDI-ctypes error [-9994]: PortMidi: `Invalid MIDI message
Data'
QObject::setParent: Cannot set parent, new parent is in a different thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
python: xcb_io.c:221: poll_for_event: asserzione (((long) (event_sequence) -
(long) (dpy-request)) = 0) non riuscita.
Annullato
--
oiram/bin/selom
Da ognuno secondo le proprie capacità ad ognuno secondo i propri bisogni!___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to make a songbook
Good news! Right after I posted that request, I finally found the entry I wanted to make PNG files, and have been merrily compiling my various songs and doing the png command in LilyPondTool (the Console is handy for this), and pasting the PNGs in a OOo document, with the apparent ability to resize them as I need. I did go to the reference you suggested, and will carefully digest that. If my OOo experiment doesn't work as I hope, I'll go to that method next. I also looked at OOoLilyPond, and couldn't make head nor tail of it, so gave that up as a lost cause. Also looks as if it's not well supported -- especially compared to LilyPondTool. Thanks for that, Bertalan! Blessings, Gordon+ Fr. Gordon Gilbert Penetanguishene, ON, Canada ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Appoggiatura appears between two repeats
Damn. Really should have seen that. Thanks. Xavier Scheuer wrote: On 12 December 2011 00:30, George_ georgexu...@gmail.com wrote: http://old.nabble.com/file/p32957263/Untitled.jpg What I want is for the appoggiatura to be on the same side of the double bar line as the D#. What I wrote looks something like what is below (at the end). As you can see I've put the volta repeats only into the top part. Up until now it's worked fine for everything. I don't think the \bar |. is causing the problem, because taking it out doesn't help. The piece begins with a quaver partial bar, but that's resolved in the first alternative. Any help would be good. See NR 1.2.6 Special rhythmic concerns Grace notes Known issues and warnings [The example shown in the documentation is the same as your issue.] This can be remedied by inserting grace skips of the corresponding durations in the other staves. http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns.html#grace-notes I.e. in your voice one (first staff) add a \grace s8 before your R2. of measure 18. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- View this message in context: http://old.nabble.com/Appoggiatura-appears-between-two-repeats-tp32957263p32957770.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 1.9.4 (beta)
Op Mon, 12 Dec 2011 01:15:56 +0100 Mario Moles mario-mo...@libero.it schreef: Hi Will! After install in /usr/local/ ia have this problem with midi. I use Mandriva 2011/jackd/fluidsynth. Traceback (most recent call last): File /usr/lib/python2.7/site-packages/frescobaldi_app/qmidi/player.py, It looks like you have old frescobaldi_app module in /usr! The 1.9.4 version should not error out on invalid MIDI messages. please remove old directory /usr/lib/python2.7/site-packages/frescobaldi_app/ -- Wilbert Berendsen (http://www.wilbertberendsen.nl) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to make a songbook
Father Gordon Gilbert fatherg...@gmail.com writes: Good news! Right after I posted that request, I finally found the entry I wanted to make PNG files, and have been merrily compiling my various songs and doing the png command in LilyPondTool (the Console is handy for this), and pasting the PNGs in a OOo document, with the apparent ability to resize them as I need. Apparent is the correct term for resizing bitmaps. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
