Re: Tempo marks & modifications

Many thanks for this which worked like a charm.Apologies for the delay in replying caused by a misconfiguration of my settings. Michael On Fri, 27 Jun 2025 at 14:40, Kieren MacMillan wrote: > Hi Michael, > > > I am making a reduction of a Berg song & trying to horizontally align > tempo indicati

Re: Tempo marks & modifications

Hi Michael, > I am making a reduction of a Berg song & trying to horizontally align tempo > indications (langsamer etc) & modifications (rit etc). The example shows two > ways I have tried: the first using a text spanner for the rit; the second > placing the rit after \tempo. The results could

Re: \tempo \markup \rhythm

Mark Knoop writes: > At 20:20 on 14 May 2025, James Harkins wrote: >> \tempo \markup { \rhythm { 8 } = \rhythm { 8 } } > >> Lilypond does not like it one bit: > >> ./common/globals.ily:139:28: error: wrong type for argument 1. Expecting >> music, found (ly:make-duration 3) >> \tempo \markup

Re: \tempo \markup \rhythm

At 20:20 on 14 May 2025, James Harkins wrote: > \tempo \markup { \rhythm { 8 } = \rhythm { 8 } } > Lilypond does not like it one bit: > ./common/globals.ily:139:28: error: wrong type for argument 1. Expecting > music, found (ly:make-duration 3) > \tempo \markup { \rhythm >

Re: \tempo \markup \rhythm

On Wed, 14 May 2025 20:20:41 +0800 James Harkins wrote --- > I said (in a "globalxxx" variable): > > globalChorale = { > \numericTimeSignature > \key ef \major > \time 7/4 s4*14 > \time 5/4 s4*5 > \time 7/4 s4*21 > \time 5/4 s4*5 > \time 7/4 s4*7 > \tempo \markup { \rhythm

Re: Tempo changes and spanners

I really appreciate your work on that! It's also a very instructive example to emulate, I imagine. One quick question -- is this "lattice" idea I'm doing (maintaining a separate voice with nothing but tempo and spaces that gets munged into the parts) a bad idea for any reason? Would I ever run int

Re: Tempo changes and spanners

Am Di., 23. Juli 2024 um 23:52 Uhr schrieb Tom Brennan : > > Hi all > > I'm notating a sonata for a cello and piano, and I would like to produce > three "artifacts" (products?) from this: > > 1. A solo cello part (a typical single staff representation) > 2. A "study score" where all staves are equ

Re: Tempo formatting question.

Ah, thank you and Jean A. for this. Works perfectly! Hwaen Ch'uqi On 2/8/24, Knute Snortum wrote: > On Thu, Feb 8, 2024 at 8:26 AM Hwaen Ch'uqi wrote: > >> Greetings, >> >> I would like to indicate a metronome mark of "Prestissimo" > note tied to dotted quarter note>=96. How may I do this? I a

Re: Tempo formatting question.

On Thu, Feb 8, 2024 at 8:26 AM Hwaen Ch'uqi wrote: > Greetings, > > I would like to indicate a metronome mark of "Prestissimo" note tied to dotted quarter note>=96. How may I do this? I am using > version 22.04. Thank you for any help! > Jean A. helped me with this a while back. Here's what I

Re: tempo marks floating number

Sorry, copying error: to avoid confusion, the numbers should be 90.86/4 = 22.715 > 22 jan. 2024 kl. 22:22 skrev Leo Correia de Verdier > : > > Hi Jacopo! > > I think > \set Timing.tempoWholesPerMinute = #(ly:make-moment 24.715) % that is 98.86/4 > should work for the midi output. At least it

Re: tempo marks floating number

Hi Jacopo! I think \set Timing.tempoWholesPerMinute = #(ly:make-moment 24.715) % that is 98.86/4 should work for the midi output. At least it accepts floats. Combining it with Michael’s solution for the markup should get you the complete \tempo I might have heard sometime in the past that tempo

Re: tempo marks floating number

On Mon, Jan 22, 2024 at 9:33 AM Jacopo Greco d'Alceo wrote: > How can I simply write a bpm in floating number in lilypond (e.g.*♩ = > 90.86 ) *? > It seems that \tempo accept only integers. > thanks > You can do pretty much any markup with the \tempo command. Two ways you can do this are either:

Re: Tempo marking doesn't avoid cross-staff slur

>> This issue belongs into the group of the many cross-staff problems. >> AFAICS, we don't have this particular case covered, so please file >> an issue in the LilyPond tracker. > > For reference, it's : https://gitlab.com/lilypond/lilypond/-/issues/6688 Thanks! Werner

Re: Tempo marking doesn't avoid cross-staff slur

On Thu, Jan 11, 2024 at 4:40 AM Werner LEMBERG wrote: > > > I found a weird behavior -- I don't know if it's worthy of an issue > > or not, but here it is: > > > > The tempo marking will not avoid a slur that goes from staff to > > staff. Here is a snippet that shows the problem, and I've attach

Re: Tempo marking doesn't avoid cross-staff slur

> I found a weird behavior -- I don't know if it's worthy of an issue > or not, but here it is: > > The tempo marking will not avoid a slur that goes from staff to > staff. Here is a snippet that shows the problem, and I've attached > an image of it: [...] This issue belongs into the group of

Re: Tempo vs. markup

On Sun, Mar 12, 2023 at 5:36 AM Valentin Petzel wrote: > Hello Ralph, > > while Pierre’s solution works with some adaptation I think your approach > is > wrong. > > Tempo is something that is created at the Score level, while TextScripts > are > created at the Staff level. This means that it shou

Re: Tempo vs. markup

Hello Ralph, while Pierre’s solution works with some adaptation I think your approach is wrong. Tempo is something that is created at the Score level, while TextScripts are created at the Staff level. This means that it should be expected for TextScripts to be closer to the Staff. Rather use t

Re: Tempo vs. markup

Hi Ralph, Try: \version "2.24.0" \relative c' { \time 3/4 \tweak outside-staff-priority #0 \tempo \markup { \concat { ( \smaller \general-align #Y #DOWN \note {2} #1 " = " \smaller \general-align #Y #DOWN \note {4} #1 ) } } d4^\markup\italic{ar

Re: Tempo Mark with letter

Thanks for the quick and helpful response, Jean! All the best, Ralph __ Ralph Palmer Seattle USA (he, him, his) palmer.r.vio...@gmail.com On Sat, Mar 4, 2023 at 10:29 AM Jean Abou Samra wrote: > Le samedi 04 mars 2023 à 10:16 -0800, Ralph Palmer a écrit : > > Greetings - > > I'm running L

Re: Tempo Mark with letter

Le samedi 04 mars 2023 à 10:16 -0800, Ralph Palmer a écrit : > Greetings - > > I'm running LilyPond 2.24.0 under Frescobaldi 3.2 and Ubuntu 22.04.2 LTS. > > I'm trying to get a tempo indication similar to the included screenshot (I > couldn't figure out how to include the screenshot as an attach

Re: tempo indication without parentheses

Thank you.  I'm sure I could make definition in my shortcuts file but as I mentioned in the other part of this thread the extra set of curly brackets works fine. Thank you all for your work on this, Paul On 12/17/22 6:23 PM, Valentin Petzel wrote: Hello Paul, formatting of the Metronome Ma

Re: tempo indication without parentheses

Hello Paul, formatting of the Metronome Marks is done by a function taking the event and the context given by the context property metronomeMarkFormatter. If we look into ly/engraver-init.ly we see the default behaviour: metronomeMarkFormatter = #format-metronome-markup The scheme function for

Re: tempo indication without parentheses

Thank you, Here's what I have in one of my files of shortcuts: #(define-markup-command (MM layout props dura beats) (ly:duration? string?)   (interpret-markup layout props    (markup     #:tiny #:raise 0.4 (#:note dura up)     #:tiny "="     #:tiny beats   ))) Paul

Re: tempo indication without parentheses

Dear Paul, I wasn't able to find any vanilla lilypond options to do that for you. Of course I assume that you were talking about a situation in which you have text followed by the quarter=number tempo, because just `\tempo 4 = 120` does display without parenthesis. The best I could find was

Re: tempo markup problem

Le 11/08/2022 à 03:11, Craig Dabelstein a écrit : Hi all, I know this is not difficult but I just can't get it to work. I want the tempo to look like: Allegro moderato die *[image of crotchet] *etwa 108 M.M. I have this so far: \tempo \markup \left-column { "Allegro moderato"            

Re: tempo markup problem

Have a look at LSR 1138. Andrew

Re: Tempo arguments

Jean Abou Samra writes: > Le 18/07/2022 à 00:35, David F. a écrit : >> \tempo 4 = 90 >> >> How is tempo able to take ‘4 = 90’ as an argument? Is this >> hardwired into the language or can any function take ‘x = y’ as an >> argument? > > It is hardwired. Music functions cannot take arguments with

Re: Tempo arguments

Le 18/07/2022 à 00:35, David F. a écrit : \tempo 4 = 90 How is tempo able to take ‘4 = 90’ as an argument? Is this hardwired into the language or can any function take ‘x = y’ as an argument? It is hardwired. Music functions cannot take arguments with '='. Jean

Re: tempo

But... with lyx-latex dont work...🙁 Il 23/05/21 17:02, Thomas Morley ha scritto: Am So., 23. Mai 2021 um 10:31 Uhr schrieb Mario Moles : Yes, I saw! Thank you. But I have to figure out how to enter these commands: \override Flag.stencil = #old-straight-flag \override NoteHead.transparent = ##t

Re: tempo

Wow! Wow! Wow! Wow! Wow! Thank you so mach. 😎 Il 23/05/21 17:02, Thomas Morley ha scritto: #(define-markup-command (ezscore layout props mus) (ly:music?) #:properties ((size 0)) (interpret-markup layout props #{ \markup { \score { \new RhythmicStaff { $mus

Re: tempo

Am So., 23. Mai 2021 um 10:31 Uhr schrieb Mario Moles : > > Yes, I saw! Thank you. But I have to figure out how to enter these commands: > \override Flag.stencil = #old-straight-flag > \override NoteHead.transparent = ##t > > Il giorno sab 22 mag 2021 alle ore 18:22 Mark Stephen Mrotek > ha scrit

Re: tempo

Yes, I saw! Thank you. But I have to figure out how to enter these commands: \override Flag.stencil = #old-straight-flag \override NoteHead.transparent = ##t Il giorno sab 22 mag 2021 alle ore 18:22 Mark Stephen Mrotek < carsonm...@ca.rr.com> ha scritto: > Mario, > > Look at > https://lsr.di.unim

RE: tempo

Mario, Look at https://lsr.di.unimi.it/LSR/Item?id=574 Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Mario Moles Sent: Saturday, May 22, 2021 1:35 AM To: lilypond-user@gnu.org Subject: tempo Hi lilyponders! How to m

Re: tempo

Hi Mario, with \tempo https://lilypond.org/doc/v2.22/Documentation/notation/displaying-rhythms#metronome-marks I don't understand the sign before the = in your image... Cheers Michael Am 22.05.21 um 10:35 schrieb Mario Moles: > Hi lilyponders! > > How to make this? Like \markup ? Or other? > >

Re: Tempo marking with 2 notes

Indeed, I had missed that portion of the documentation.. I was able to adapt it and make it work. Thank you! -Ahanu On Mon, May 10, 2021, 22:13 Peter Chubb wrote: > > "Ahanu" == Ahanu Banerjee writes: > > > Ahanu> Can anyone provide a simple way to make a tempo marking like > Ahanu> this:

Re: Tempo marking with 2 notes

> "Ahanu" == Ahanu Banerjee writes: Ahanu> Can anyone provide a simple way to make a tempo marking like Ahanu> this: "♩= 𝅗𝅥 " ? Something like this? \version "2.22.0" \score { \new Staff { \time 3/4 r2.^ \markup { \note {2.} #UP

Re: Tempo marking with 2 notes

On 2021-05-10 6:41 pm, Ahanu Banerjee wrote: Hello, Can anyone provide a simple way to make a tempo marking like this: "♩= 𝅗𝅥 " ? You should be able to adapt LSR 574 [1] to achieve that. [1]: https://lsr.di.unimi.it/LSR/Item?id=574 -- Aaron Hill

Re: Tempo marking with 2 notes

Please disregard, I missed the answer in the documentation.. thanks On Mon, May 10, 2021 at 9:41 PM Ahanu Banerjee wrote: > Hello, > > Can anyone provide a simple way to make a tempo marking like this: "♩= 𝅗𝅥 > " ? > > Thanks, > -Ahanu >

Re: Tempo markings placement for trio music

Thank you very much! Rachel On Apr 30, 2021, at 11:21 AM, Xavier Scheuer mailto:x.sche...@gmail.com>> wrote: On Fri, 30 Apr 2021 at 19:55, Rachel Green mailto:rg4...@outlook.com>> wrote: > > Hi, > For trios, I would like all the tempo markings to occur both above all parts > (as seen above th

Re: Tempo markings placement for trio music

Thanks! Rachel > On Apr 30, 2021, at 11:19 AM, Kevin Barry wrote: > > Hi Rachel, > > You can make this work by adding the engraver to the staff you want it > to print above (in this case the harp's upper staff). Based on your > example the code might look something like this: > > \new Sta

Re: Tempo markings placement for trio music

Just what I needed! Rachel > On Apr 30, 2021, at 11:06 AM, Jean Abou Samra wrote: > > > Le 30/04/2021 à 19:17, Rachel Green a écrit : >> Hi, >> For trios, I would like all the tempo markings to occur both above all parts >> (as seen above the flute in the example below) but also right above th

Re: Tempo markings placement for trio music

On Fri, 30 Apr 2021 at 19:55, Rachel Green wrote: > > Hi, > For trios, I would like all the tempo markings to occur both above all parts (as seen above the flute in the example below) but also right above the harp part. When I add a tempo marking to the harp part, it places it above the flute part

Re: Tempo markings placement for trio music

Hi Rachel, You can make this work by adding the engraver to the staff you want it to print above (in this case the harp's upper staff). Based on your example the code might look something like this: \new Staff \with { \consists Mark_engraver \consists Metronome_mark_engraver

Re: Tempo markings placement for trio music

Le 30/04/2021 à 19:17, Rachel Green a écrit : Hi, For trios, I would like all the tempo markings to occur both above all parts (as seen above the flute in the example below) but also right above the harp part. When I add a tempo marking to the harp part, it places it above the flute part, bu

Re: Tempo marking per staff

Thank you, I tried option 2 and it works perfectly... and I learned about tagging :) On 2021-01-22 14:42, Kieren MacMillan wrote: Hi there, How do I place tempo marks above a particular staff rather than a system as a whole, please? I have parts that speed up during an ensemble piece for a

Re: Tempo marking per staff

Hi there, > How do I place tempo marks above a particular staff rather than a system as a > whole, please? > > I have parts that speed up during an ensemble piece for a few measures, and > would like to see the tempo mark above the staff for that part rather than > above the system as is conve

Re: tempo spanners

FWIW in the meanwhile I managed to improve the appearance of my metronome markings by centering them, and by not hiding but omitting the tempo markings for the MIDI: \relative c'' { \override TextSpanner #'(bound-details left text) = "rit." \override TextSpanner #'(bound-details right text) = \ma

Re: tempo spanners

here a MWE \relative c'' { \override TextSpanner #'(bound-details left text) = x \override TextSpanner #'(bound-details right text) = x \override TextSpanner #'(bound-details left-broken text) = ##f \override TextSpanner #'(bound-details right-broken text) = ##f %\override TextSpanner.to

Re: tempo spanners

Actually, I just noticed that if the new tempo is supposed to appear in a new system after the accel., the new tempo is not shown with this code. Any other ideas on how to properly write an aligned accel. with a new tempo? Am Mi., 9. Sept. 2020 um 10:38 Uhr schrieb Martín Rincón Botero < martinrin

Re: Tempo markings & partcombine

On 2019-06-10 5:28 am, Michael Seifert wrote: What I’d like is for the tempo markings to show up (at most) once per staff in the score, even on combined staves; but the tempo markings should show up in each individual part when it’s produced. Right now, partcombine leads to both of the “rit.” m

Re: Tempo markings & partcombine

Hello Michael, two strategies are helpful here: 1) use \tempo and \mark for any structural information shared by all staves. I even defined an \agogicMark command for things like "rit." and "a tempo" in order to have a separate category with the proper text formatting (see attachment) 2) a

Re: Tempo declaration on different staves

Hi Vaughan, > Putting the clef where it is a bit idiosyncratic, but it lets me do things > like have a trombone part use bass clef in the score and tenor clef in the > part. Related: I have started to think of "clef" as presentation-layer [as opposed to content-layer] data. Therefore, as soon

Re: Tempo declaration on different staves

On 23-9-2018 15:49, Kieren MacMillan wrote: Of course, a lot of it is simply personal preference/style, so there’s no big need to change if you don’t agree with my reasoning! I was just offering a possible improvement. Cheers, Kieren. Thanks for explaining. I'll think about it. There's

Re: Tempo declaration on different staves

On Mon, 24 Sep 2018 at 04:25, Simon Albrecht wrote: > On 18.09.2018 21:10, Kieren MacMillan wrote: > > Here’s one way. (Note that I also <<>>'ed the \global variable into > each*staff* context in the score, rather than into each note variable > definition; personally, I think that is better codi

Re: Tempo declaration on different staves

On 18.09.2018 21:10, Kieren MacMillan wrote: Here’s one way. (Note that I also <<>>'ed the \global variable into each*staff* context in the score, rather than into each note variable definition; personally, I think that is better coding style, for many reasons.) I for my part don’t feel like

Re: Tempo declaration on different staves

p.s. >> In the rewrite Kieren gave of Bernhard's score the global variable is still >> included at the voice level. And, yes, I would likely move the \global variable to the staff level(s) — or even score, if the type of global information warranted/allowed — though I didn’t go that far in my

Re: Tempo declaration on different staves

Hi all, > In the rewrite Kieren gave of Bernhard's score the global variable is still > included at the voice level. So, it seems that less typing is not the reason. No, less typing is not the reason. Here are three of the more important reasons I prefer late-stage combination: 1. It’s less li

Re: Tempo declaration on different staves

On 23-9-2018 08:41, arnepe wrote: hello Auke, (/bear with me, I'm not a programmer and may not know the correct terminology/) one reason would be that "voice" is a child of "staff": definitions in "staff" are inherited by "voice", plus the benefit of less typing... cheers Arne Hello Arne, I

Re: Tempo declaration on different staves

hello Auke, (/bear with me, I'm not a programmer and may not know the correct terminology/) one reason would be that "voice" is a child of "staff": definitions in "staff" are inherited by "voice", plus the benefit of less typing... cheers Arne -- Sent from: http://lilypond.1069038.n5.nabble.co

Re: Tempo declaration on different staves

On 18-9-2018 21:10, Kieren MacMillan wrote: (Note that I also <<>>'ed the \global variable into each *staff* context in the score, rather than into each note variable definition; personally, I think that is better coding style, for many reasons.) I'm intruiged. What would those 'many reas

Re: Tempo declaration on different staves

Hi Bernhard, > Please show me how to deal with different tempo declarations on different > staves. Here’s one way. (Note that I also <<>>'ed the \global variable into each *staff* context in the score, rather than into each note variable definition; personally, I think that is better coding st

Re: Tempo & Markup

Malte Meyn-3 wrote > Looks like I should get issue 5215 done soon > (https://sourceforge.net/p/testlilyissues/issues/5215/). I haven’t had > much time for LilyPond the last few weeks, hopefully it gets better soon. Oh, I just watched your code, it is amazing! Those options would be very welcomed

Re: Tempo & Markup

On 04/05/18 12:34, foxfanfare wrote: > But I was wondering if I could be able to write a small function for it. > Is it possible to change the default command "2 = 76-84" so it will take > my own markup preferences? Almost certainly ... I do the same thing with the header block on my music. Brass

Re: Tempo & Markup

Am 04.05.2018 um 13:34 schrieb foxfanfare: Is it possible to change the default command "2 = 76-84" so it will take my own markup preferences? Looks like I should get issue 5215 done soon (https://sourceforge.net/p/testlilyissues/issues/5215/). I haven’t had much time for LilyPond the last

Re: Tempo Alignment Questions

On Mon, Jan 15, 2018 at 1:46 AM, Xavier Scheuer wrote: > On 14 January 2018 at 16:36, Jay Anderson wrote: > > > > Right. I want a more general solution. It gets annoying to have to > > tweak the same tempo in the score and different parts. With the > > accidental issue for instance the object i

Re: Tempo Alignment Questions

On 14 January 2018 at 16:36, Jay Anderson wrote: > > Right. I want a more general solution. It gets annoying to have to > tweak the same tempo in the score and different parts. With the > accidental issue for instance the object is on the page so I assume > there is some way to tell it to align w

Re: Tempo Alignment Questions

On Sat, Jan 13, 2018 at 9:53 PM, Shane Brandes wrote: > \override Score.MetronomeMark.extra-offset = #'(x . -y) that will do > it you will have to iterate a few guesses to get what you want. > Right. I want a more general solution. It gets annoying to have to tweak the same tempo in the score

Re: Tempo Alignment Questions

\override Score.MetronomeMark.extra-offset = #'(x . -y) that will do it you will have to iterate a few guesses to get what you want. Shane On Sat, Jan 13, 2018 at 11:34 PM, Jay Anderson wrote: > I'm unable to find them at the moment, but I've seen threads discussing > general overrides for temp

Re: tempo percentage

Gianmaria Lari writes: > On 27 November 2017 at 10:30, David Kastrup wrote: > >> Any reason you don't take the previous working code, just replacing >> ly:moment-mul with ly:moment-add (and factor with value if you want more >> readable code, but for the first attempt you can skip this)? >> > >

Re: tempo percentage

On 27 November 2017 at 10:30, David Kastrup wrote: > Gianmaria Lari writes: > > > On 27 November 2017 at 09:32, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > > >> > Another question. It would be also useful to have a function that > >> > increase the tempo by a certain quantity (

Re: tempo percentage

Gianmaria Lari writes: > On 27 November 2017 at 09:32, David Kastrup wrote: > >> Gianmaria Lari writes: >> > >> > Another question. It would be also useful to have a function that >> > increase the tempo by a certain quantity (instead of a certain >> > factor). >> > >> > I tried to modify the p

Re: tempo percentage

On 27 November 2017 at 09:32, David Kastrup wrote: > Gianmaria Lari writes: > > > On 27 November 2017 at 07:39, Gianmaria Lari > > wrote: > > > >> > >> On 27 November 2017 at 00:24, David Kastrup wrote: > >> > >>> Gianmaria Lari writes: > >>> > >>> > On 8 November 2017 at 18:15, David Kastrup

Re: tempo percentage

Gianmaria Lari writes: > On 27 November 2017 at 07:39, Gianmaria Lari > wrote: > >> >> On 27 November 2017 at 00:24, David Kastrup wrote: >> >>> Gianmaria Lari writes: >>> >>> > On 8 November 2017 at 18:15, David Kastrup wrote: >>> > >>> >> Gianmaria Lari writes: >>> >> >>> >> > Talking abou

Re: tempo percentage

On 27 November 2017 at 07:39, Gianmaria Lari wrote: > > On 27 November 2017 at 00:24, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > On 8 November 2017 at 18:15, David Kastrup wrote: >> > >> >> Gianmaria Lari writes: >> >> >> >> > Talking about midi, is there any way to to reduce or

Re: tempo percentage

On 27 November 2017 at 00:24, David Kastrup wrote: > Gianmaria Lari writes: > > > On 8 November 2017 at 18:15, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > >> > Talking about midi, is there any way to to reduce or increase the > tempo > >> of > >> > some measures by a certain pe

Re: tempo percentage

Gianmaria Lari writes: > On 8 November 2017 at 18:15, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > Talking about midi, is there any way to to reduce or increase the tempo >> of >> > some measures by a certain percentage instead of setting it to an >> absolute >> > value? >> > >> > F

Re: tempo percentage

On 8 November 2017 at 18:15, David Kastrup wrote: > Gianmaria Lari writes: > > > Talking about midi, is there any way to to reduce or increase the tempo > of > > some measures by a certain percentage instead of setting it to an > absolute > > value? > > > > For example instead of: > > > > \tempo

Re: tempo percentage

On 9 November 2017 at 11:04, David Kastrup wrote: > Gianmaria Lari writes: > > > Thank you David & Mark! > > > > Mark's solutions looks simpler. Any disadvantages using it comparing to > > David'one? > > It doesn't do what you asked for, namely setting the tempo in relation > to the _current_ te

Re: tempo percentage

Gianmaria Lari writes: > Thank you David & Mark! > > Mark's solutions looks simpler. Any disadvantages using it comparing to > David'one? It doesn't do what you asked for, namely setting the tempo in relation to the _current_ tempo rather than some fixed tempo. That makes it simpler because it

Re: tempo percentage

Thank you David & Mark! Mark's solutions looks simpler. Any disadvantages using it comparing to David'one? Thank you, gianmaria On 8 November 2017 at 18:15, David Kastrup wrote: > Gianmaria Lari writes: > > > Talking about midi, is there any way to to reduce or increase the tempo > of > > som

Re: tempo percentage

Gianmaria Lari writes: > Talking about midi, is there any way to to reduce or increase the tempo of > some measures by a certain percentage instead of setting it to an absolute > value? > > For example instead of: > > \tempo 4=100 a b c d > \tempo 4=110 e f g a > > > something like > > \tempo 4=1

Re: tempo percentage

At 14:14 on 08 Nov 2017, Gianmaria Lari wrote: >Talking about midi, is there any way to to reduce or increase the >tempo of some measures by a certain percentage instead of setting it >to an absolute value? > >For example instead of: > >\tempo 4=100 a b c d >\tempo 4=110 e f g a > > >something like

Re: Tempo Indication

"Mark Stephen Mrotek" writes: > David, > > K 331 was composed in 1783, the variations in 1799, so Beethoven might > (should) have known it > So delicious to discover all of the "behind the scenes" elements of this > music! Ok, I looked at your link. It's definitely not a March, being in 3/8. On

RE: Tempo Indication

16 8:35 AM To: Mark Stephen Mrotek Cc: 'lilypond-user' Subject: Re: Tempo Indication [Sort of already wrote that in private communication, sorry for the duplication] David Kastrup writes: > "Mark Stephen Mrotek" writes: > >> Hello, >> >> >>

Re: Tempo Indication

[Sort of already wrote that in private communication, sorry for the duplication] David Kastrup writes: > "Mark Stephen Mrotek" writes: > >> Hello, >> >> >> >> Admittedly my inquiry is not directly related to the use of Lilypond. Yet >> the members of this list are the most knowledgeable to a

RE: Tempo Indication

: David Kastrup Cc: Mark Stephen Mrotek ; lilypond-user Subject: Re: Tempo Indication Hi Mark, I guess it means "not seriously, like a folk song, much lighter than a Beethoven piece". My personal opinion. The whole variations are pretty funny (http://petrucci.mus.auth.gr/imglnks/

Re: Tempo Indication

Hi Mark, I guess it means "not seriously, like a folk song, much lighter than a Beethoven piece". My personal opinion. The whole variations are pretty funny ( http://petrucci.mus.auth.gr/imglnks/usimg/2/28/IMSLP51439-PMLP16877-WoO_73.pdf ). Cheers, Pierre 2016-08-18 7:17 GMT+02:00 David Kastrup

Re: Tempo Indication

"Mark Stephen Mrotek" writes: > Hello, > > > > Admittedly my inquiry is not directly related to the use of Lilypond. Yet > the members of this list are the most knowledgeable to answer. > > > > A Beethoven piano variation has the tempo marking "alla Austriaca." > > > > Would someone please

Re: tempo and different staves

Solved. Sorry for the noise m > Il giorno 23 apr 2016, alle ore 08:03, matpen3@gmail ha > scritto: > > Hi David, > > thanks. > > I’d like to have tempos above the voice staff and above the piano part, so, > reading manuals and forums, it seems you have to remove them from score and > assi

Re: tempo and different staves

Hi, I don't know why that matters, but you can omit the line \consists "Metronome_mark_engraver" in the pianostaff \with block and put it in the \with block of the upper ("right") Staff. That works for me. Cheers, Joram ___ lilypond-user mailing lis

Re: tempo and different staves

Hi David, thanks. I’d like to have tempos above the voice staff and above the piano part, so, reading manuals and forums, it seems you have to remove them from score and assign to single staves. m > Il giorno 23 apr 2016, alle ore 07:58, David Kastrup ha > scritto: > > "matpen3@gmail" wr

Re: tempo and different staves

"matpen3@gmail" writes: > Hi all, > > is there a reason why tempos aren’t assigned to the staves, after > removing them from score? I'd ask the person who removed them from the score. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu

Re: Tempo equivalence markup

Hi Andrew, I'm not sure to understand what you're looking for. A more precise description or a teeny example would have been helpful. Anyway, here's something I've done i order to look-like your picture: \version "2.19.31" my-tempo = \markup { %% Left arrow: \overlay { \arrow-head #X #LE

Re: Tempo equivalence markup

Hello Robert, I use the following, but I don’t know how to add the arrows: \version "2.19.30" \relative { \clef "bass" \key c \major \numericTimeSignature\time 4/4 \tempo \markup { \concat { "le double plus lent " \smaller \general-align #Y #DOWN \note #"4" #1 " = "

Re: Tempo equivalence markup

I've done something similar using an ossia staff some time ago. That's definitely a way. My solution (which was for drums) looked like this (I can't tell you right now, where I got the arrowed slur commands from - but that's probably easy to find): FullDrums = << \new DrumStaff = "main" << \

Re: tempo as REAL number

dak: > jan writes: ... > > \tempo 4 = 82.3 > > produces the error. > > "syntax error, unexpected REAL" > > Since in midi tempo definitions are of type float > > They aren't. They are exact fractions. > > > I wonder if there is a reason for Lilypond to restrict the tempo to > > integers. If

Re: tempo as REAL number

jan writes: > Hi, > > i did not expect the tempo definition in Lilypond to be required to be an > integer. > > For instance > > \tempo 4 = 82.3 > > produces the error. > > "syntax error, unexpected REAL" > > Since in midi tempo definitions are of type float They aren't. They are exact fract

Re: Tempo spanners

Hi Dominic, > Thanks, Kevin - that appears to work perfectly! Hmmm… When I try it, in the second score, the baselines of the tempo mark and the “rall” are not consistent. Is that actually what you want? Cheers, Kieren. ___ Kieren MacMillan, composer www:

Re: Tempo spanners

Anyway, it would be more confortable to have a "TempoTextSpanner", as proposed in this issue: https://code.google.com/p/lilypond/issues/detail?id=3176 Philippe -- View this message in context: http://lilypond.1069038.n5.nabble.com/Te

Re: Tempo spanners

Hi Dominic, > Thanks, Kevin - that appears to work perfectly! Hmmm… When I try it, in the second score, the baselines of the tempo mark and the “rall” are not consistent. Is that actually what you want? Cheers, Kieren. ___ Kieren MacMillan, composer www:

  1   2   3   >