Re: moving rests relative cues
Thanks to Jean's correction about quotedCueEventTypes here is a MWE that
shows why there is still a collision.
\version "2.23.5"
aa = \relative{ f'4->( 4 d4 4) f4->( 4 d4 4->) }
\addQuote qaa \aa
bb = \relative{
\set Score.quotedCueEventTypes = #'(note-event rest-event tie-event
articulation-event
beam-event tuplet-span-event
dynamic-event slur-event)
\cueDuring qaa #up R1
<< { \cueDuring qaa #up s1 } { \voiceOne R1 } >>
}
\score{
\new Staff \new Voice \bb
}
Paul
On 12/13/21 16:37, Jean Abou Samra wrote:
Le 14/12/2021 à 00:19, Paul Scott a écrit :
On 12/13/21 16:03, Jean Abou Samra wrote:
How about:
\version "2.22.1"
aa = \relative { f'4 4 4 4 }
\addQuote qaa \aa
\relative{
<< { \cueDuring qaa #down s1 } { \voiceOne R1 } >>
}
I need to understand voices better. My real problem has articulation
over the notes which your solution doesn't seem to see.
OK, I am at loss here.
\version "2.22.1"
<<
{ R1 }
\\
{ c'1 }
\\
{ e''4 4 4 4 }
>>
Why does this make colliding output? Does
anyone see if I am missing something?
I had tried adding the articulations to my MWE and didn't get them to
show up with quotedEventTypes.
You are using \cueDuring. The property for
that would be quotedCueEventTypes.
Best,
Jean
Re: moving rests relative cues
On 12/13/21 16:37, Jean Abou Samra wrote:
Le 14/12/2021 à 00:19, Paul Scott a écrit :
On 12/13/21 16:03, Jean Abou Samra wrote:
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
(Snip)
OK, I am at loss here.
Your solution was fine for my MWE. My actual situation has articulation
which collides with the rest. I was having trouble quickly providing a
MWE which showed this. I will try to provide a more complete MWE.
\version "2.22.1"
<<
{ R1 }
\\
{ c'1 }
\\
{ e''4 4 4 4 }
>>
Why does this make colliding output? Does
anyone see if I am missing something?
No collisions with the above. See my comments few lines up.
I had tried adding the articulations to my MWE and didn't get them to
show up with quotedEventTypes.
You are using \cueDuring. The property for
that would be quotedCueEventTypes.
I will look into this. quotedEventTypes has seemed to work for both
cues and quotes.
Sorry if I wasn't clear,
Paul
Best,
Jean
Re: moving rests relative cues
Le 14/12/2021 à 00:19, Paul Scott a écrit :
On 12/13/21 16:03, Jean Abou Samra wrote:
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Paul
\version "2.23.5"
aa = \relative{ f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative{
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score{
\new Staff \bb
}
How about:
\version "2.22.1"
aa = \relative { f'4 4 4 4 }
\addQuote qaa \aa
\relative{
<< { \cueDuring qaa #down s1 } { \voiceOne R1 } >>
}
I need to understand voices better. My real problem has articulation
over the notes which your solution doesn't seem to see.
OK, I am at loss here.
\version "2.22.1"
<<
{ R1 }
\\
{ c'1 }
\\
{ e''4 4 4 4 }
>>
Why does this make colliding output? Does
anyone see if I am missing something?
I had tried adding the articulations to my MWE and didn't get them to
show up with quotedEventTypes.
You are using \cueDuring. The property for
that would be quotedCueEventTypes.
Best,
Jean
Re: moving rests relative cues
On 12/13/21 16:03, Jean Abou Samra wrote:
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Paul
\version "2.23.5"
aa = \relative{ f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative{
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score{
\new Staff \bb
}
How about:
\version "2.22.1"
aa = \relative { f'4 4 4 4 }
\addQuote qaa \aa
\relative{
<< { \cueDuring qaa #down s1 } { \voiceOne R1 } >>
}
I need to understand voices better. My real problem has articulation
over the notes which your solution doesn't seem to see.
I had tried adding the articulations to my MWE and didn't get them to
show up with quotedEventTypes.
Thank you,
Paul
Re: moving rests relative cues
On 12/13/21 15:57, Kieren MacMillan wrote:
Hi Paul,
I'm trying to move rests associated with cues. The first measure shows the
problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Does this solution suit?
Yes. Thank you!
%%%
\version "2.23.5"
aa = \relative { f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative {
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score {
\new Staff \bb
}
cc = \relative {
\override Staff.MultiMeasureRest.staff-position = #2
\voices 2,1 << { \cueDuring qaa #down s1 } \\ { R1 } >>
}
\score {
\new Staff \cc
}
%%%
Note: If you're doing a lot of this "tweaking", you should really look into the
edition-engraver. =)
I'll look at it. Thanks,
Paul
Cheers,
Kieren.
[j...@abou-samra.fr: Re: PNG/EPS output doesn't work anymore in 2.23.6?]
On Mon, Dec 13, 2021 at 11:48:41PM +0100, Jean Abou Samra wrote: [...] > I don't understand what's going on at all. It all > happens as if you were calling lilypond with wrong > quoting as > > lilypond -dbackend="eps myfile.ly" Haha, in fact, you hit the nail right on the head (without realizing it). :-) It turns out to be entirely my fault after all: I have a wrapper shell script that forwards to a local copy of lilypond (because I'm using a local copy of guile-1.8 that I didn't want to conflict with the distro's version), but I used the wrong forwarding for arguments: export LD_LIBRARY_PATH=/usr/src/guile-1.8/lib /usr/src/lilypond/bin/lilypond "$*" where in the second line, I should have written "$@" instead. This bug went unnoticed because I usually only invoke lilypond with the single .ly file as argument. But now when I need to pass additional arguments to it, the "$*" smushes all the arguments into one where lilypond expected multiple arguments, thus generating the observed mysterious error message. Changing it to "$@" fixed the problem. Thanks a bunch, and sorry for wasting everyone's time with something that isn't lilypond's fault at all. T -- "I'm running Windows '98." "Yes." "My computer isn't working now." "Yes, you already said that." -- User-Friendly
Re: moving rests relative cues
Le 13/12/2021 à 23:34, Paul Scott a écrit :
I'm trying to move rests associated with cues. The first measure
shows the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Paul
\version "2.23.5"
aa = \relative{ f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative{
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score{
\new Staff \bb
}
How about:
\version "2.22.1"
aa = \relative { f'4 4 4 4 }
\addQuote qaa \aa
\relative{
<< { \cueDuring qaa #down s1 } { \voiceOne R1 } >>
}
Best,
Jean
Re: moving rests relative cues
Hi Paul,
> I'm trying to move rests associated with cues. The first measure shows the
> problem. The second measure shows the attempted solution.
> Changing #down to #up is not reasonable in my real complex score.
> TIA for any7 help,
Does this solution suit?
%%%
\version "2.23.5"
aa = \relative { f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative {
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score {
\new Staff \bb
}
cc = \relative {
\override Staff.MultiMeasureRest.staff-position = #2
\voices 2,1 << { \cueDuring qaa #down s1 } \\ { R1 } >>
}
\score {
\new Staff \cc
}
%%%
Note: If you're doing a lot of this "tweaking", you should really look into the
edition-engraver. =)
Cheers,
Kieren.
moving rests relative cues
I'm trying to move rests associated with cues. The first measure shows
the problem. The second measure shows the attempted solution.
Changing #down to #up is not reasonable in my real complex score.
TIA for any7 help,
Paul
\version "2.23.5"
aa = \relative{ f'4 4 4 4 4 4 4 4 }
\addQuote qaa \aa
bb = \relative{
<< { \cueDuring qaa #down s1*2 } { R1 d''1\rest } >>
}
\score{
\new Staff \bb
}
Re: Multiple identical articulations on one note
Hello Ahanu, how about this:
{ _- _- _- }
Cheers,
Valentin
Am Montag, 13. Dezember 2021, 22:29:24 CET schrieb Ahanu Banerjee:
> Hello,
>
> What is the easiest way to put multiple identical articulations on one
> note? I am trying to put a tenuto marking both above and below the same
> note in a passage.
>
> (Context: this is for a cello; the main bowing is above the notes, and
> there is an alternative bowing below the notes.)
>
> Thanks,
> -Ahanu
signature.asc
Description: This is a digitally signed message part.
Re: PNG/EPS output doesn't work anymore in 2.23.6?
Here's the output: GNU LilyPond 2.23.6 (running Guile 1.8) command line options: "((backend . eps test.ly) (gs-api . #f) )": In procedure scm_i_lreadparen in expression (dynamic-wind swaports thunk ...): : #:1:18: in pair: missing close paren I'm using the latest git master (just updated this morning). Running on Linux (debian/testing), not compiling with Cairo. Should I rollback git to the latest release to see if it makes a difference? --T On Mon, Dec 13, 2021 at 10:37:17PM +0100, Jean Abou Samra wrote: > Le 13/12/2021 à 20:54, Jean Abou Samra a écrit : > > #(display (ly:command-line-code)) > > > Silly me. It should print nothing at all since the error is > occurring before LilyPond even starts parsing the file. > Rather, try to change scm/lily.scm by applying the attached > patch (`git apply show-command-line-code.patch`). > > Thanks, > Jean > > > diff --git a/scm/lily.scm b/scm/lily.scm > index c5c905b3ca..89563d9e2c 100644 > --- a/scm/lily.scm > +++ b/scm/lily.scm > @@ -436,6 +436,8 @@ messages into errors.") >(ly:set-option 'debug-gc-object-lifetimes #f)) > (else)) > > +(ly:message "command line options: ~s" (ly:command-line-options)) > + > (for-each (lambda (x) > (ly:set-option (car x) (cdr x))) >(with-input-from-string (ly:command-line-options) read)) > @@ -846,6 +848,7 @@ PIDs or the number of the process." > > (define-public (lilypond-main files) >"Entry point for LilyPond." > + (ly:message "command line code: ~s" (ly:command-line-code)) >(eval-string (ly:command-line-code)) >(if (ly:get-option 'help) >(begin (ly:option-usage) -- Freedom: (n.) Man's self-given right to be enslaved by his own depravity.
Re: PNG/EPS output doesn't work anymore in 2.23.6?
Le 13/12/2021 à 20:54, Jean Abou Samra a écrit : #(display (ly:command-line-code)) Silly me. It should print nothing at all since the error is occurring before LilyPond even starts parsing the file. Rather, try to change scm/lily.scm by applying the attached patch (`git apply show-command-line-code.patch`). Thanks, Jean diff --git a/scm/lily.scm b/scm/lily.scm index c5c905b3ca..89563d9e2c 100644 --- a/scm/lily.scm +++ b/scm/lily.scm @@ -436,6 +436,8 @@ messages into errors.") (ly:set-option 'debug-gc-object-lifetimes #f)) (else)) +(ly:message "command line options: ~s" (ly:command-line-options)) + (for-each (lambda (x) (ly:set-option (car x) (cdr x))) (with-input-from-string (ly:command-line-options) read)) @@ -846,6 +848,7 @@ PIDs or the number of the process." (define-public (lilypond-main files) "Entry point for LilyPond." + (ly:message "command line code: ~s" (ly:command-line-code)) (eval-string (ly:command-line-code)) (if (ly:get-option 'help) (begin (ly:option-usage)
Multiple identical articulations on one note
Hello, What is the easiest way to put multiple identical articulations on one note? I am trying to put a tenuto marking both above and below the same note in a passage. (Context: this is for a cello; the main bowing is above the notes, and there is an alternative bowing below the notes.) Thanks, -Ahanu
Re: PNG/EPS output doesn't work anymore in 2.23.6?
Le 13/12/2021 à 17:58, H. S. Teoh a écrit : According to the usage manual, in order to get PNG output: lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly But lilypond 2.23.6 aborts with this: : In procedure scm_i_lreadparen in expression (dynamic-wind swaports thunk ...): : #:1:18: in pair: missing close paren What am I doing wrong? P.S. I compiled lilypond with guile 1.8.8, don't know if that's related? T I cannot reproduce this, whether compiling with Guile 1 or Guile 2. Are you using the latest Git revision? There have been heavy changes around the output backends and a bug of this kind might have slipped through before being corrected in a later commit. If it still doesn't work, - What is your OS? - Are you compiling with Cairo or not? (If you don't know, it's not with Cairo.) - What is printed if you put this in the file? #(display (ly:command-line-code)) Best, Jean
PNG/EPS output doesn't work anymore in 2.23.6?
According to the usage manual, in order to get PNG output: lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly But lilypond 2.23.6 aborts with this: : In procedure scm_i_lreadparen in expression (dynamic-wind swaports thunk ...): : #:1:18: in pair: missing close paren What am I doing wrong? P.S. I compiled lilypond with guile 1.8.8, don't know if that's related? T -- Food and laptops don't mix.
Re: Crescendo after custom dynamic marking
> c): Add \dynamic know and later find a special name for Harm's > dynamic engine. (d) You add now `\dynamic` in a first MR. Eventually, Harm's stuff gets applied in another MR under the same name, extending your stuff.[*] IMHO there is no necessity to provide `convert-ly` rules between development versions, especially since the LilyPond's current micro version is still a single digit. Werner [*] Under the assumption that this actually makes sense.
