% When input language is "deutsch" (German),
% Lilypond does not seem to print the default chord names
% given in the notation reference
%
https://lilypond.org/doc/v2.22/Documentation/notation/displaying-chords#customizing-chord-names
% The only workaround I have found was to use a different
ley
>
> thomasmorle...@gmail.com:
>
> > Am Sa., 12. März 2022 um 09:58 Uhr schrieb Ole V. Villumsen via
> >
> > bug-lilypond bug-lilypond@gnu.org:
> >
> > > % When input language is "deutsch" (German),
> > >
> > > % Li
\version "2.24.2"
\relative {
g'1 |
% The following has no effect.
\override Score.SpacingSpanner.strict-grace-spacing = ##t
\grace { a4 } g1 |
}
\relative {
% This works.
\override Score.SpacingSpanner.strict-grace-spacing = ##t
g'1 |
\grace { a4 } g1 |
}
As a consequence we
:28, Jean Abou Samra
wrote:
> Le dimanche 24 septembre 2023 à 09:21 +0000, Ole V. Villumsen via
> bug-lilypond a écrit :
>
>> \version "2.24.2"
>>
>> \relative {
>> g'1 |
>> % The following has no effect.
>> \override Score.Spacin
Hi,
Often, not always, when a slur ends on a note with the \prall\turn combination
(custom in baroque music), the prall and the turn are printed
colliding/overlapping in one spot rather than the turn above and the prall
below as they should. Please see the attachments.
Best regards, Ole
--
---
On Saturday, October 29th, 2022 at 08:08, Pierre Perol-Schneider
wrote:
> Hi Ole,
> I'd do:
>
> \relative c' {
> d'8( c\prall-\tweak avoid-slur #'outside \turn)
> }
>
> Cheers,
> Pierre
>
> Le sam. 29 oct. 2022 à 07:58, Ole V. Villumsen via bug-lilyp
A possible workaround is something like
d'8( c\prall-\tweak extra-offset #'(0 . 1.3)\turn)
/Ole
Sent with [Proton Mail](https://proton.me/) secure email.
--- Original Message ---
On Saturday, October 29th, 2022 at 07:01, Ole V. Villumsen
wrote:
> Hi,
> Often, not always, when a slur
---
On Saturday, October 29th, 2022 at 11:36, Kevin Barry wrote:
> On Sat, Oct 29, 2022 at 06:29:05AM +0000, Ole V. Villumsen via bug-lilypond
> wrote:
>
> > Thanks, Pierre! That looks good and isn’t so hacky as my own workaround.
> > I will do some further experimentation to see
:
> Is this not you want:
>
> \version "2.22.2"
>
> {
> \time 3/4
> \partial 4*2 % defines bar as holding two crotchets
> f'4 f' |
> \time 2/4
> R2 |
> R2 |
> }
>
> Paul
>
> From: Ole V. Villumsen via bug-lilypond
> To: "bug-lilypond@gnu
secure email.
--- Original Message ---
On Friday, October 28th, 2022 at 12:16, Paul Hodges wrote:
> There are only two crotchets between your 3/4 signature and your 2/4
> signature - what do you expect to happen?
>
> Paul
>
> From: Ole V. Villumsen via bug-lilypond
nt with [Proton Mail](https://proton.me/) secure email.
>
> --- Original Message ---
> On Friday, October 28th, 2022 at 12:16, Paul Hodges wrote:
>
>> There are only two crotchets between your 3/4 signature and your 2/4
>> signature - what do you expect to happen?
>>
I have found no really acceptable workaround for this bug. Please see the
attachments.
Thx
Ole
--
Ole V. Villumsen
Jelshøjvænget 13
DK - 8270 Højbjerg
Denmark
+45 - 86 27 29 26
Text +45 - 30 22 29 26
Sent with [Proton Mail](https://proton.me/) secure email.% In the output from this file, the
Hi Kevin,
Thank you for your input.
> If you use \partial at the beginning of a score it treats the resulting
> duration as the length of music preceding the first bar. This is how bar
> numbering generally works for upbeats/anacrusis.
Obviously confirmed.
> Partial expects to be given a
Hi Pierre,
Thank you, merci beaucoup! For my situation that is extremely helpful. The
documentation link too. I much prefer your solution over the ones by Paul, Mark
and Kevin pretending that the incomplete 3/4 measure is an upbeat, which it
isn’t. The way I read the documentation, in theory
,
Ole
Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, August 1st, 2023 at 20:46, Jean Abou Samra
wrote:
> Le mardi 01 août 2023 à 18:34 +0000, Ole V. Villumsen via bug-lilypond a
> écrit :
>
> > % Manual beams and cross-staff stems don’t seem t
;
>
> https://lilypond.org/doc/v2.25/Documentation/snippets/staff-notation_003a-cross-staff-stems
>
> -will
>
> On 8/1/23 15:22, Ole V. Villumsen via bug-lilypond wrote:
>
>> Hi Jean,
>> indeed. I retract my bug report.
>> Your solution works in the case where I
% Manual beams and cross-staff stems don’t seem to work together.
% Expected result: Shared stems across staves; beams above notes in upper staff
only.
% I have tried all possible combinations of specifying beams and \crossStaff in
the
% upper staff, the lower one and both. I always get
% Multiple slurs in a Voice work nicely on one staff, as described in NR.
%
https://lilypond.org/doc/v2.24/Documentation/notation/expressive-marks-as-curves#slurs
% Multiple slurs crossing over a line break are ugly and collide easily.
% I suppose modifying the shapes could be a workaround (I
oût 2023 à 20:38 +0000, Ole V. Villumsen via bug-lilypond a
> écrit :
>
>> % Multiple slurs in a Voice work nicely on one staff, as described in NR.
>> %
>> https://lilypond.org/doc/v2.24/Documentation/notation/expressive-marks-as-curves#slurs
>> % Multiple slurs cr
A suggestion for the Glossary in the documentation since I just learned that
percent repeats are called "Faulenzer" in colloquial German after I had sought
the word in vain in the Lilypond glossary and documentation. Or two
suggestions, really.
#1. The entry percent repeat
20 matches
Mail list logo
