Re: Problems with tempo in 15/8 time
On Tue, Sep 19, 2023 at 8:06 AM Jean Abou Samra wrote:
> So the first question is how do I get the two notes closer. I've attached
> the LilyPond source and a screenshot of my attempts.
>
>
> You can do
>
> \rhythm {
> \override Score.SpacingSpanner.spacing-increment = 0.5
> 4.~ 4
> }
>
>
> Secondly, what's the best way to get the MIDI to play at the correct
> tempo? I'd like to do something like \tempo 5*8 = 69 but of course that
> doesn't work. Right now I have \tempo 8 = 345, which is 69 times five but
> is that the best way to do it?
>
>
> I actually don't see any technical reason why \tempo 8*5 = 69 should be
> rejected. (I just tested the parser change and it didn't seem to cause
> trouble).
>
> Anyway, this works:
>
> \tempo $#{ 8*5 #} = 70
>
Thanks Jean, those solutions work great.
Re: Problems with tempo in 15/8 time
> So the first question is how do I get the two notes closer. I've attached the
> LilyPond source and a screenshot of my attempts.
You can do
\rhythm {
\override Score.SpacingSpanner.spacing-increment = 0.5
4.~ 4
}
> Secondly, what's the best way to get the MIDI to play at the correct tempo?
> I'd like to do something like \tempo 5*8 = 69 but of course that doesn't
> work. Right now I have \tempo 8 = 345, which is 69 times five but is that the
> best way to do it?
I actually don't see any technical reason why \tempo 8*5 = 69 should be
rejected. (I just tested the parser change and it didn't seem to cause trouble).
Anyway, this works:
\tempo $#{ 8*5 #} = 70
Best,
Jean
signature.asc
Description: This is a digitally signed message part
Re: problems with \tempo
I'm sorry to top post. My outlook online email client doesn't work well with
the Liypond mailer, and my desktop Outlook client is broken right now.
Have you looked at the lilypond log file? Your snippet creates errors.
var/folders/q5/88k2s1717qv1v7rq4tqz53k8gn/T/frescobaldi-5i3u1hok/tmpc7w_p6ze/document.ly:4:28:
error: not a note name: …
\tempo "Allegro" 2 = 200
… 400 … 600
/var/folders/q5/88k2s1717qv1v7rq4tqz53k8gn/T/frescobaldi-5i3u1hok/tmpc7w_p6ze/document.ly:4:30:
error: not a duration
\tempo "Allegro" 2 = 200 …
400 … 600
/var/folders/q5/88k2s1717qv1v7rq4tqz53k8gn/T/frescobaldi-5i3u1hok/tmpc7w_p6ze/document.ly:4:34:
error: not a note name: …
\tempo "Allegro" 2 = 200 … 400
… 600
/var/folders/q5/88k2s1717qv1v7rq4tqz53k8gn/T/frescobaldi-5i3u1hok/tmpc7w_p6ze/document.ly:4:36:
error: not a duration
\tempo "Allegro" 2 = 200 … 400 …
600
You have improper lilypond code.
The code below should give you accelerating tempo in midi (but it does it in
steps, not continuously).
theMusic = \relative {
\tempo "Largo" 4 = 50
c''4 c c c |
\tempo "Allegro" 2 = 200
c2 c
\set Score.tempoHideNote = ##t
\tempo 2 = 400
c c |
\set Score.tempoHideNote = ##t
\tempo 2 = 600
c c c c |
}
Carl
From: lilypond-user
on behalf of Mario Bolognani
Sent: Wednesday, March 16, 2022 10:20 AM
To: Knute Snortum
Cc: lilypond-user
Subject: Re: problems with \tempo
Many thanks Knute,
using your snippet in this way:
theMusic = \relative {
\tempo "Largo" 4 = 50
c''4 c c c |
\tempo "Allegro" 2 = 200 … 400 … 600
c2 c c c |
}
nothing changes. The midi output of “Allegro” is not going progressively faster.
Mario
Mario Bolognani
mario.bologn...@gmail.com
> Il giorno 16 mar 2022, alle ore 15:46, Knute Snortum ha
> scritto:
>
> As always, a small, working example will help diagnose the problem and
> demonstrate to us what is going wrong. For instance, this snippet
> works fine for me:
>
> %%%
> \version "2.22.2"
>
> theMusic = \relative {
> \tempo "Largo" 4 = 50
> c''4 c c c |
> \tempo "Alegro" 4 = 120
> c4 c c c |
> }
>
> \score {
> \new Staff \theMusic
> \layout {}
> \midi {}
> }
> %%%
>
> --
> Knute Snortum
>
>
> --
> Knute Snortum
>
>
>
> On Wed, Mar 16, 2022 at 1:47 AM Jacques Menu wrote:
>>
>> Hello Mario,
>>
>> The \midi block is your friend:
>>
>> \book {
>> \score {
>> <<
>>
>> \new Staff = "Part_POne_Staff_One"
>> \with {
>> }
>> <<
>> \context Voice = "Part_POne_Staff_One_Voice_One" <<
>> \Part_POne_Staff_One_Voice_One
>>>>
>>>>
>>
>>>>
>>
>> \layout {
>> \context {
>> \Score
>> autoBeaming = ##f % to display tuplets brackets
>> }
>> \context {
>> \Voice
>> }
>> }
>>
>> \midi {
>> \tempo 16 = 360
>> }
>> }
>>
>> }
>>
>>
>> Le 16 mars 2022 à 05:08, Mario Bolognani a écrit
>> :
>>
>> I’m using LilyPomd 2.20 with Frescobaldi 3.1.3 on a MacBook M1 with MacOSX
>> Monterey (last version). With \time 3)1 and \tempo \breve (or breve.) = xx
>> the midi output seems not responding to \tempo changes. Any suggestion?
>>
>> Many thanks
>>
>>
>> Mario Bolognani
>> mario.bologn...@gmail.com
>>
>>
>>
>>
Re: problems with \tempo
Many thanks Knute,
using your snippet in this way:
theMusic = \relative {
\tempo "Largo" 4 = 50
c''4 c c c |
\tempo "Allegro" 2 = 200 … 400 … 600
c2 c c c |
}
nothing changes. The midi output of “Allegro” is not going progressively faster.
Mario
Mario Bolognani
mario.bologn...@gmail.com
> Il giorno 16 mar 2022, alle ore 15:46, Knute Snortum ha
> scritto:
>
> As always, a small, working example will help diagnose the problem and
> demonstrate to us what is going wrong. For instance, this snippet
> works fine for me:
>
> %%%
> \version "2.22.2"
>
> theMusic = \relative {
> \tempo "Largo" 4 = 50
> c''4 c c c |
> \tempo "Alegro" 4 = 120
> c4 c c c |
> }
>
> \score {
> \new Staff \theMusic
> \layout {}
> \midi {}
> }
> %%%
>
> --
> Knute Snortum
>
>
> --
> Knute Snortum
>
>
>
> On Wed, Mar 16, 2022 at 1:47 AM Jacques Menu wrote:
>>
>> Hello Mario,
>>
>> The \midi block is your friend:
>>
>> \book {
>> \score {
>><<
>>
>> \new Staff = "Part_POne_Staff_One"
>> \with {
>> }
>> <<
>>\context Voice = "Part_POne_Staff_One_Voice_One" <<
>> \Part_POne_Staff_One_Voice_One
>>
>>
>>\layout {
>> \context {
>>\Score
>>autoBeaming = ##f % to display tuplets brackets
>> }
>> \context {
>>\Voice
>> }
>>}
>>
>>\midi {
>> \tempo 16 = 360
>>}
>> }
>>
>> }
>>
>>
>> Le 16 mars 2022 à 05:08, Mario Bolognani a écrit
>> :
>>
>> I’m using LilyPomd 2.20 with Frescobaldi 3.1.3 on a MacBook M1 with MacOSX
>> Monterey (last version). With \time 3)1 and \tempo \breve (or breve.) = xx
>> the midi output seems not responding to \tempo changes. Any suggestion?
>>
>> Many thanks
>>
>>
>> Mario Bolognani
>> mario.bologn...@gmail.com
>>
>>
>>
>>
Re: problems with \tempo
As always, a small, working example will help diagnose the problem and
demonstrate to us what is going wrong. For instance, this snippet
works fine for me:
%%%
\version "2.22.2"
theMusic = \relative {
\tempo "Largo" 4 = 50
c''4 c c c |
\tempo "Alegro" 4 = 120
c4 c c c |
}
\score {
\new Staff \theMusic
\layout {}
\midi {}
}
%%%
--
Knute Snortum
--
Knute Snortum
On Wed, Mar 16, 2022 at 1:47 AM Jacques Menu wrote:
>
> Hello Mario,
>
> The \midi block is your friend:
>
> \book {
> \score {
> <<
>
> \new Staff = "Part_POne_Staff_One"
> \with {
> }
> <<
> \context Voice = "Part_POne_Staff_One_Voice_One" <<
> \Part_POne_Staff_One_Voice_One
> >>
> >>
>
> >>
>
> \layout {
> \context {
> \Score
> autoBeaming = ##f % to display tuplets brackets
> }
> \context {
> \Voice
> }
> }
>
> \midi {
> \tempo 16 = 360
> }
> }
>
> }
>
>
> Le 16 mars 2022 à 05:08, Mario Bolognani a écrit :
>
> I’m using LilyPomd 2.20 with Frescobaldi 3.1.3 on a MacBook M1 with MacOSX
> Monterey (last version). With \time 3)1 and \tempo \breve (or breve.) = xx
> the midi output seems not responding to \tempo changes. Any suggestion?
>
> Many thanks
>
>
> Mario Bolognani
> mario.bologn...@gmail.com
>
>
>
>
Re: problems with \tempo
Hello Mario,
The \midi block is your friend:
\book {
\score {
<<
\new Staff = "Part_POne_Staff_One"
\with {
}
<<
\context Voice = "Part_POne_Staff_One_Voice_One" <<
\Part_POne_Staff_One_Voice_One
>>
>>
>>
\layout {
\context {
\Score
autoBeaming = ##f % to display tuplets brackets
}
\context {
\Voice
}
}
\midi {
\tempo 16 = 360
}
}
}
> Le 16 mars 2022 à 05:08, Mario Bolognani a écrit :
>
> I’m using LilyPomd 2.20 with Frescobaldi 3.1.3 on a MacBook M1 with MacOSX
> Monterey (last version). With \time 3)1 and \tempo \breve (or breve.) = xx
> the midi output seems not responding to \tempo changes. Any suggestion?
>
> Many thanks
>
>
> Mario Bolognani
> mario.bologn...@gmail.com
>
>
>
