Am Sun, 1 Mar 2026 16:24:38 -0500 schrieb Dan Eble <[email protected]>:
> On 2026-03-01 15:36, Benkő Pál wrote: > > sort of published example: > > https://www.karlheinzstockhausen.org/orchestra_finalisten_english.htm > > shows that Stockhausen used an equally tempered tempo scale, and > > didn't use trailing zeroes: > > 23.75 25 26.75 28.25 30 31.75 33.5 35.5 37.5 40 42.5 45 > > 47.5 50 53.5 56.5 60 63.5 67 71 75 80 85 90 > > 95 101 107 113.5 120 127 134 142 150 160 170 180 208 > > Thanks, Pál. These options spring to mind: > > A. Change the default formatter to round to the nearest 1/4 bpm > instead of 1 bpm. This is easy to describe and to test. Users of > midi2ly might see fractional parts that they didn't before. 2.24 > didn't support input of non-integer tempo counts, so old scores > should not be a problem. Those who want other behavior would still > have to provide their own formatter. > > B. Add context property tempoCountPrecision with default 1. People > using Stockhausen's scale would set it to 1/4 instead. Others who > want more precision could set 1/1000 or whatever. Maybe some people > who don't like odd numbers would want 2. :) > > Thoughts? I'm willing to prepare a patch for either, though B would > require more time and we're getting close to branching for 2.26. Hello, I expect someone will ask quite soon to choose the decimal mark, too (i.e. point or comma, or even a centered point) for the output of the metronome speed in high resolution. And yes, as I'm from Germany, I would prefer to set the comma, too, and I can read it better when written with a comma. ArnoldTheresius
