Jean Abou Samra writes:
> When you say "tackle the resulting parser conflicts", that means
> "add precedences to solve them by making interpretation choices",
> not "solve them in a way that always does what the user might intend",
> right? As I understand it, there is a shift/reduce conflict on
Hi David,
On 27/06/2022 21:07, David Kastrup wrote:
Before looking for a possible following `=`
LilyPond has to have made a decision what type the token/expression
coming before that has. It cannot look at the type of a #... expression
before deciding to look for `=` but it can (and will) look
\shiftDurations (that would be a sensible
feature request, right?),
Go open an issue.
I did: <https://gitlab.com/lilypond/lilypond/-/issues/6366>
so I tried this:
%%%
\version "2.23.9"
durationShiftOne = #-1
{
\tempo #(ly:make-duration
[…]
Can I make that
). Unfortunately \tempo isn’t affected by
\shiftDurations (that would be a sensible feature request, right?),
Go open an issue.
so I tried this:
%%%
\version "2.23.9"
durationShiftOne = #-1
{
\tempo #(ly:make-duration (+ 3 durationShiftOne)) = 152
\shif
> halved/doubled). Unfortunately \tempo isn’t affected by
>>> \shiftDurations (that would be a sensible feature request, right?),
>>
>> Go open an issue.
>>
>>
>>> so I tried this:
>>> %%%
>>>
Jean Abou Samra writes:
> Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
>> Hello everyone,
>>
>> I’m trying to encode a piece such that I can switch whether or not
>> durations will be shifted (note values
>> halved/doubled). Unfortunately \tempo isn’t aff
Le 27/06/2022 à 20:10, Simon Albrecht a écrit :
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values halved/doubled). Unfortunately
\tempo isn’t affected by \shiftDurations (that would be a sensible
feature request
Hello everyone,
I’m trying to encode a piece such that I can switch whether or not
durations will be shifted (note values halved/doubled). Unfortunately
\tempo isn’t affected by \shiftDurations (that would be a sensible
feature request, right?), so I tried this
Le 29/07/2021 à 05:23, Kees van den Doel a écrit :
Is there a way to do a \shiftDurations of 2/3?
I have a voice with almost all dotted minims and semibreves {c2. c1. }
in 6/2 and want to change to 2/2 and use \scaleDurations to make it fit.
I would not be surprised by "no" as there
Is there a way to do a \shiftDurations of 2/3?
I have a voice with almost all dotted minims and semibreves {c2. c1. } in
6/2 and want to change to 2/2 and use \scaleDurations to make it fit.
I would not be surprised by "no" as there are a few "minim semiminim" like {e2
d4 c2
Found it! It's a known bug (no. 4362).
https://sourceforge.net/p/testlilyissues/issues/4362/
The bug has been logged since 2015. I'm amazed I hadn't noticed it before.
> On 4 Jul 2019, at 22:08, Graham King wrote:
>
> Corrected MWE (it turns out that \shiftDurati
Corrected MWE (it turns out that \shiftDurations is irrelevant; it is the
dotted breve that is misbehaving):
\version "2.19.82"
{
\time 3/1
c'\longa. % should give \breve. ~ \breve.
\time 3/2
c'\breve. % works as expected
}
\layout {
\context {
Is there a way to make the following MWE generate a dotted breve tied to a
dotted breve, rather than breve~semibreve~breve~semibreve ?
I would prefer not to abandon the use of shiftDurations or state "c'1. ~ 1." if
these things are avoidable, for weak reasons to do with my
13 matches
Mail list logo
