Re: partcombine & killCues

2020-01-23 Thread Aaron Hill
On 2020-01-23 8:00 pm, Aaron Hill wrote: \tag #'cueName <>_\markup \tiny \italic "Bsn." \cueDuring #"bassoon" #DOWN { R1} If you need to use instrumentCueName or would simply prefer not to use text scripts, then you can do this: \cueDuring #"bassoon" #DOWN { \tag #'cueName

Clef change placement

2020-01-23 Thread Daniel Rosen
>From Elaine Gould's "Behind Bars" (p. 9): > Where an instrument rests for more than a system, it is usual to return it to > its commonest clef... Place > the clef change at the end of the system after the player has finished: this > is the least disruptive position > as regards spacing. It is

Re: partcombine & killCues

2020-01-23 Thread Aaron Hill
On 2020-01-23 7:37 pm, Michael Seifert wrote: However, I can’t seem to get killCues to work correctly in combination with partcombine. It creates stray notation below the system in the full score, which is both unsightly and causes the systems in the full score to be over-compressed.

partcombine & killCues

2020-01-23 Thread Michael Seifert
Hey there folks, I’m trying to prepare a score and parts for a concerto using Lilypond, and I can’t figure out how to make partcombine and killCues work nicely together. My goal is to have individual parts for the orchestra, containing cues for the solo instrument; and also

Re: Odd Behaviour: \break after \repeat

2020-01-23 Thread David Wright
On Thu 23 Jan 2020 at 21:03:40 (+0100), sir.teddy.the.fi...@gmail.com wrote: > […] > Test Test, Test, Te -- st } > […] > When I compile this, Lilypond outputs this weird double-hyphen as if it > actually inserts an empty syllable where there should be none. > > Strangely, if I remove the

Re: Beams over rests and concaveness

2020-01-23 Thread Gilberto Agostinho
Hi Carl, Thank you so much for the reply, I will report this in the bugs subforum. Also, thanks for the workaround, I will use it for the moment being. Best, Gilberto -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: Scheme function evluates only once

2020-01-23 Thread Thomas Morley
Am Do., 23. Jan. 2020 um 22:47 Uhr schrieb Urs Liska : > But let me take the opportunity to introduce you to Amir who I think > has never posted on the LilyPond lists so far. German Forum? https://lilypondforum.de/index.php/topic,214.msg1333.html Cheers, Harm

Re: Scheme function evluates only once

2020-01-23 Thread David Kastrup
Urs Liska writes: > Hi, > > I intended to write about the same, but when I came back home to switch > the computer back on David had already replied, although in clearer > words than I would have done. Since I only quoted the Guile manual, any clarity has to be credited to the people writing

Re: Scheme function evluates only once

2020-01-23 Thread Urs Liska
Hi, I intended to write about the same, but when I came back home to switch the computer back on David had already replied, although in clearer words than I would have done. But let me take the opportunity to introduce you to Amir who I think has never posted on the LilyPond lists so far. For

Re: Scheme function evluates only once

2020-01-23 Thread David Kastrup
Amir Teymuri writes: > Hi, > > this is just a nonsense exercise for me to get to know LilyPond better! > I can't figure out why in the following the #(rnd-col) is evaluated only > once and not upon each compilation of my ly file? The first time i > compile this i will get the four colors

Odd Behaviour: \break after \repeat

2020-01-23 Thread sir.teddy.the.first
Hi everyone, please consider the following snippet: \version "2.19.83" melody = \relative c'' { r2. r4. e | %T69 a,4. fis4.~ fis a | %T70 g1. } words = \lyricmode { Test Test, Test, Te -- st } struct = { \time

Scheme function evluates only once

2020-01-23 Thread Amir Teymuri
Hi, this is just a nonsense exercise for me to get to know LilyPond better! I can't figure out why in the following the #(rnd-col) is evaluated only once and not upon each compilation of my ly file? The first time i compile this i will get the four colors displayed: (0.5 0.5 0) (0.5 0 1.0) (0.5

Workarounds for issue #5538

2020-01-23 Thread Daniel Rosen
Does anyone have any ideas for a workaround for Issue #5538 "bendAfter broken by chords"? (https://sourceforge.net/p/testlilyissues/issues/5538/) DR

Re: Beams over rests and concaveness

2020-01-23 Thread Carl Sorensen
On 1/23/20, 7:48 AM, "Gilberto Agostinho" wrote: Hi everyone, It seems that the beam concaveness value is ignored when beaming over rests, in the case of a single note with a single rest. This happens with and without stemlet. See the code and score below, the groups

Beams over rests and concaveness

2020-01-23 Thread Gilberto Agostinho
Hi everyone, It seems that the beam concaveness value is ignored when beaming over rests, in the case of a single note with a single rest. This happens with and without stemlet. See the code and score below, the groups marked with an asterisk should have been flat (+inf.0 concaveness): \version

Beams over rests and concaveness

2020-01-23 Thread Gilberto Agostinho
Hi everyone, It seems that the beam concaveness value is ignored when beaming over rests, in the case of a single note with a single rest. This happens with and without stemlet. See the code and score below, the groups marked with an asterisk should have been flat (+inf.0 concaveness): \version