Re: incomplete tuplets in non-standard time signatures

2020-12-02 Thread Michael Käppler
Am 02.12.2020 um 11:24 schrieb Michael Käppler: Am 02.12.2020 um 09:26 schrieb Michael Käppler: Am 30.11.2020 um 09:20 schrieb Michael Käppler: Am 30.11.2020 um 08:29 schrieb Lukas-Fabian Moser: Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property

Re: incomplete tuplets in non-standard time signatures

2020-12-02 Thread Michael Käppler
Am 02.12.2020 um 09:26 schrieb Michael Käppler: Am 30.11.2020 um 09:20 schrieb Michael Käppler: Am 30.11.2020 um 08:29 schrieb Lukas-Fabian Moser: Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905

Re: incomplete tuplets in non-standard time signatures

2020-12-02 Thread Michael Käppler
Am 30.11.2020 um 09:20 schrieb Michael Käppler: Am 30.11.2020 um 08:29 schrieb Lukas-Fabian Moser: Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad co

Re: incomplete tuplets in non-standard time signatures

2020-11-30 Thread Michael Käppler
Am 30.11.2020 um 08:29 schrieb Lukas-Fabian Moser: Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b06b1cc4f0ca33960c

Re: incomplete tuplets in non-standard time signatures

2020-11-29 Thread Lukas-Fabian Moser
Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c Author: Malte Meyn Date:   Sun Sep 29 10:10:35

Re: incomplete tuplets in non-standard time signatures

2020-11-29 Thread Jonas Hahnfeld via LilyPond user discussion
Am Sonntag, dem 29.11.2020 um 22:24 +0100 schrieb Michael Käppler: > Am 29.11.2020 um 21:09 schrieb Lukas-Fabian Moser: > > Hi Harm, > Hi Harm and Lukas, > > > > > I just filed a bug report > > > http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html > > > >

Re: incomplete tuplets in non-standard time signatures

2020-11-29 Thread Michael Käppler
Am 29.11.2020 um 21:09 schrieb Lukas-Fabian Moser: Hi Harm, Hi Harm and Lukas, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b

Re: incomplete tuplets in non-standard time signatures

2020-11-29 Thread Lukas-Fabian Moser
Hi Harm, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c Author: Malte Meyn Date:   Sun Sep 29 10:10:35 2019 +

Re: incomplete tuplets in non-standard time signatures

2020-11-29 Thread Thomas Morley
Am Fr., 27. Nov. 2020 um 17:21 Uhr schrieb 98123981293 1293812397123 : > > Dear list, > > On list thread Apr 6 2020, Harm provided a Scheme workaround for half-dashed > tuplet brackets in non-standard time signatures in version 2.20. However, in > using his solution in 2.21.6, if a /tempo marking

Re: incomplete tuplets in non-standard time signatures

2020-11-27 Thread 98123981293 1293812397123
Dear list, On list thread Apr 6 2020, Harm provided a Scheme workaround for half-dashed tuplet brackets in non-standard time signatures in version 2.20. However, in using his solution in 2.21.6, if a /tempo marking is included in *any* staff, I observe that, for the *first* staff in the score, the

Re: incomplete tuplets in non-standard time signatures

2020-04-06 Thread Thomas Morley
Am So., 5. Apr. 2020 um 19:59 Uhr schrieb 98123981293 1293812397123 : > > Dear list, > > In the following example, I would like to: > 1) In the first voice: make the tuplet line to the right of the number into a > dashed straight line. > 2) In the second voice: fix the appearance of the last tuple

incomplete tuplets in non-standard time signatures

2020-04-05 Thread 98123981293 1293812397123
Dear list, In the following example, I would like to: 1) In the first voice: make the tuplet line to the right of the number into a dashed straight line. 2) In the second voice: fix the appearance of the last tuplet in the measure so that the number does not clash with the bracket, and the bracket