Re: OT: Strange tempo indication

Am 29. Juni 2016 02:08:26 MESZ, schrieb Andrew Bernard : >Hi Simon, > >I looked at the complete score for Urs. Each piece either has >' T.' or ' Solo' where is the tempo, and only >at the start. It's almost certainly 'tutti', as Urs can now confirm. I think Simon didn't object to your interpre

Re: OT: Strange tempo indication

Hi Simon, I looked at the complete score for Urs. Each piece either has ' T.' or ' Solo' where is the tempo, and only at the start. It's almost certainly 'tutti', as Urs can now confirm. Andrew On 29 June 2016 at 05:53, Simon Albrecht wrote: > On 28.06.2016 13:15, Urs Liska wrote: >> >> "T."

Re: Reducing space between lyric lines

On 29.06.2016 00:39, Br. Gabriel-Marie | SSPX wrote: So, I'm trying to force my music onto one page. If I can reduce the space between lyric lines then I might be able to get it. Hi Gabriel, have a look at these manual pages:

Reducing space between lyric lines

So, I'm trying to force my music onto one page. If I can reduce the space between lyric lines then I might be able to get it. I've been playing with this override: \layout{ \context { \Lyrics \override VerticalAxisGroup #'minimum-Y-extent = #'(1 . 1.8) }

Re: Set Stanza for every staff

Thanks you all for your time! It looks right now! On 6/28/2016 5:26 PM, lilypond-user-requ...@gnu.org wrote: \layout { \context { \Lyrics \override InstrumentName.X-offset = 2 \override InstrumentName.font-size = 0 \override InstrumentName.font-series = #'bold }

Re: Set Stanza for every staff

Well, that does indeed number every line, but it places the number outside the borders of the lyric text. Set Stanza made the number inline with the lyrics. Set Stanza: 1. lyr- ic instrumentname 1. lyric So, I'm trying to fix the alignment. I'd like to do it in the \layout bra

Re: Set Stanza for every staff

Am 29.06.2016 um 00:08 schrieb Thomas Morley: 2016-06-28 23:40 GMT+02:00 Br. Gabriel-Marie | SSPX : In my music I have been using \set stanza = "1. " to get line numbering for the lyrics. But this only numbers the beginning of the lyric's line. I can manually insert that to get the numbering

Re: Set Stanza for every staff

2016-06-28 23:40 GMT+02:00 Br. Gabriel-Marie | SSPX : > In my music I have been using > \set stanza = "1. " > to get line numbering for the lyrics. But this only numbers the beginning > of the lyric's line. > I can manually insert that to get the numbering to appear within the lyric > line, but wh

Set Stanza for every staff

In my music I have been using \set stanza = "1. " to get line numbering for the lyrics. But this only numbers the beginning of the lyric's line. I can manually insert that to get the numbering to appear within the lyric line, but what I need is for it to appear at the start of each lyric as it

Re: OT: Strange tempo indication

On 28.06.2016 13:15, Urs Liska wrote: "T." refers to Tutti, but not as part of the tempo but as a performance indication. It's tutti choir vs. solo voice. That's also why it is typeset differently (italics vs. upright). Somewhat confusing is that it's also in the instruments. I don’t think so.

Re: #(define (bookGenerator please))

Simon Albrecht writes: > On 28.06.2016 00:52, Thomas Morley wrote: >>> How can I make my function be more "indentable" by using, for >>> example, curly braces e.g. \bookGenerator { stuff } ? >> No idea what you mean. > > The point is, with the current coding you write > > \bookGenerator > \scores

Re: #(define (bookGenerator please))

On 28.06.2016 00:52, Thomas Morley wrote: How can I make my function be more "indentable" by using, for example, curly braces e.g. \bookGenerator { stuff } ? No idea what you mean. The point is, with the current coding you write \bookGenerator \scores "violinI" %\header {instrument = "Violin

Re: OT: Strange tempo indication

Urs Liska writes: > Am 28.06.2016 um 13:01 schrieb David Kastrup: >> Urs Liska writes: >> >>> I'm wondering about the "T." in a 18th century print. The file is too >>> large to attach here, so please view at >>> https://git.openlilylib.org/bfsc/kayser/issues/3. >>> >>> First I thought it referre

Re: OT: Strange tempo indication

Am 28.06.2016 um 13:03 schrieb Urs Liska: > > Am 28.06.2016 um 13:01 schrieb David Kastrup: >> Urs Liska writes: >> >>> I'm wondering about the "T." in a 18th century print. The file is too >>> large to attach here, so please view at >>> https://git.openlilylib.org/bfsc/kayser/issues/3. >>> >>>

Re: OT: Strange tempo indication

Am 28.06.2016 um 13:01 schrieb David Kastrup: > Urs Liska writes: > >> I'm wondering about the "T." in a 18th century print. The file is too >> large to attach here, so please view at >> https://git.openlilylib.org/bfsc/kayser/issues/3. >> >> First I thought it referred to the tenors, but it's o

Re: OT: Strange tempo indication

Urs Liska writes: > I'm wondering about the "T." in a 18th century print. The file is too > large to attach here, so please view at > https://git.openlilylib.org/bfsc/kayser/issues/3. > > First I thought it referred to the tenors, but it's obviously not > related to that. It's in all the parts, a

Re: OT: Strange tempo indication

Am 28.06.2016 um 12:06 schrieb David Kastrup: > Urs Liska writes: > >> I'm wondering about the "T." in a 18th century print. The file is too >> large to attach here, so please view at >> https://git.openlilylib.org/bfsc/kayser/issues/3. > > You need to sign in or sign up before continuing. > So

Re: Strange tempo indication

Requires a sign in to view. -- Phil Holmes - Original Message - From: Urs Liska To: lilypond-user Sent: Tuesday, June 28, 2016 10:56 AM Subject: OT: Strange tempo indication I'm wondering about the "T." in a 18th century print. The file is too large to attach here, so p

Re: OT: Strange tempo indication

Urs Liska writes: > I'm wondering about the "T." in a 18th century print. The file is too > large to attach here, so please view at > https://git.openlilylib.org/bfsc/kayser/issues/3. You need to sign in or sign up before continuing. -- David Kastrup _

Re: scheme-function to provide value for \include

Urs Liska writes: > Am 28.06.2016 um 11:05 schrieb David Kastrup: >> Urs Liska writes: >> >>> Hi all, >>> >>> I am surprised that \include refuses to accept a string that isn't >>> passed literally but through a scheme-function: >>> >>> \version "2.19.43" givePath = #(define-scheme-function ()()

OT: Strange tempo indication

I'm wondering about the "T." in a 18th century print. The file is too large to attach here, so please view at https://git.openlilylib.org/bfsc/kayser/issues/3. First I thought it referred to the tenors, but it's obviously not related to that. It's in all the parts, and I've also seen it with other

Re: Decaying squiggle

Hi Jacques, Indeed yes. The complexity comes in when you realise that once you have the function and it’s derivative - that is the easy part - you need to compute a set of bezier spline segments that approximate the function in order to use them in Postscript path creation. This is decidedly Not S

Re: scheme-function to provide value for \include

Am 28.06.2016 um 11:05 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> I am surprised that \include refuses to accept a string that isn't >> passed literally but through a scheme-function: >> >> \version "2.19.43" givePath = #(define-scheme-function ()() >> "some/path/that/will/

Re: #(define (bookGenerator please))

Pierre-Luc Gauthier writes: > Greetings, > > Sorry about the late follow up (about 7 months later). > > The orchestra I work with came down to a halt for the summer and I now > have some time to set stuff up for the next season. > > Many thanks to you Urs and David; your explanations certainly he

Re: Decaying squiggle

Hello Andrew, Look at the bottom of page 4 and beginning of page 5 of: http://web.mit.edu/6.02/www/s2007/lab2.pdf They show how to draw a decaying wave with: y_damped = sin(2*pi*330*t).*exp(-t/tau); I guess this could be done in Scheme, couldn’t it? JM > Le 23 juin 2016 à 13

Re: scheme-function to provide value for \include

Urs Liska writes: > Hi all, > > I am surprised that \include refuses to accept a string that isn't > passed literally but through a scheme-function: > > \version "2.19.43" givePath = #(define-scheme-function ()() > "some/path/that/will/probably/not/be/found.ily") #(display (givePath)) > \inclu

Re: Multiple rhythms in same score

> Le 24 juin 2016 à 14:29, Stephen MacNeil a écrit : > > Hi Don > > I see this a lot, (in guitar music -- typically vocals are added) the two > typical ways are 1. use small notes eg 2. use the same size notes. I can > post examples if you need. > > >>I'm guessing that the answer is "no" s

Re: scheme-function to provide value for \include

2016-06-28 9:23 GMT+02:00 Urs Liska : > Hi all, > > I am surprised that \include refuses to accept a string that isn't passed > literally but through a scheme-function: > > \version "2.19.43" givePath = #(define-scheme-function ()() > "some/path/that/will/probably/not/be/found.ily") #(display (give

scheme-function to provide value for \include

Hi all, I am surprised that \include refuses to accept a string that isn't passed literally but through a scheme-function: \version "2.19.43" givePath = #(define-scheme-function ()() "some/path/that/will/probably/not/be/found.ily") #(display (givePath)) \include \givePath I would of course ex