Hi Timothy,
Am 20.09.2024 um 21:28 schrieb Timothy Lanfear:
You need
(markup #:override `(box-padding . ,myvalue) #:box text)
thanks a lot, that does the trick!
Cheers,
Klaus
On 20/09/2024 20:20, K. Blum wrote:
\version "2.24.3"
#(define-markup-command (dosomething layout props text) (markup?)
(let* ((myvalue 1))
(interpret-markup
layout props
; (markup #:override '(box-padding . 1) #:box text)) ; works
(markup #:override '(box-padding .
Dear community,
I try to use a variable instead of a simple hard-coded value (outside the MWE,
this would be the result of a calculation):
%---
\version "2.24.3"
#(define-markup-command (dosomething layout props text) (markup?)
(let* ((myvalue 1))
(inter
On Sat 03 Aug 2024 at 19:46:57 (-0300), Lucas Cavalcanti wrote:
> Hello. I'm transcribing a piece and I have come to need to use the
> "OneStaff" feature: I need to switch between multiple types of staff
> between this song. However, I'm facing a problem while input
Hello. I'm transcribing a piece and I have come to need to use the
"OneStaff" feature: I need to switch between multiple types of staff
between this song. However, I'm facing a problem while inputting lyrics:
the lyrics are aligned vertically with the OneStaff (as the refe
>> The Alain and Rachmaninov only have one fewer beam, so the beam
>> count between the groups is not appropriate for the lengths of the
>> subdivided groups, according to the Gould rules. Personally, I
>> think the Gould rules are correct, but two of the music publishers
>> in your example do no
On 04.07.24 19:00, Carl Sorensen wrote:
The Alain and Rachmaninov only have one fewer beam, so the beam count
between the groups is not appropriate for the lengths of the
subdivided groups, according to the Gould rules. Personally, I think
the Gould rules are correct, but two of the music publ
On 2024-07-04 09:09, Jason Yip - sripedia_getpgrp(a)slmail.me wrote:
On 2024-07-03 22:06, Werner LEMBERG - wl(a)gnu.org wrote:
Even though you want this special subdivision at just one point in
your example, do you have examples where this special subdivision
occurs at multiple points in the sam
On Wed, Jul 3, 2024 at 11:07 PM Werner LEMBERG wrote:
>
> OK, here are some scans that I've found. As you can see, this kind of
> subdivision is not so special as previously assumed.
>
> * Jehan Alain, trois danses – Deuils (for organ), (publisher: Leduc)
>
> * Prokofiev, piano sonata 7, op. 83,
On 2024-07-03 22:06, Werner LEMBERG - wl(a)gnu.org wrote:
Even though you want this special subdivision at just one point in
your example, do you have examples where this special subdivision
occurs at multiple points in the same beam? My former suggestion
acts as a offset of # of beamlets for eve
> I have thought of a probably better solution. Currently, if
> `minimumBeamSubdivisionInterval` > `maximumBeamSubdivisionInterval`,
> the algorithm basically pretends that `subdivideBeams` is false.
> What if I change the behavior of that case such that you can add
> `maximumBeamSubdivisionInterv
> This may be slightly less ugly, but it still requires a function
> call every place you want a beam subdivision:
Thanks!
Werner
On 2024-07-02 21:33, Werner LEMBERG - wl(a)gnu.org wrote:
My beam subdivision algorithm tries to strictly respect metric
values as subdivision is intended to ease readers' track of the
current measure position. Adding features that loosen that
strictness such as one to support your desired output
On Tue, Jul 2, 2024 at 10:48 AM Werner LEMBERG wrote:
>
> Folks,
>
>
> how can I easily create a beam subdivision as shown in the attached
> image using the current development version 2.25.18? The solution I
> came up with is extremely ugly...
>
>
> Werner
>
> This may be slightly less ugly
> My reading would be
>
> \version "2.24.3"
> \relative c'' {
> d4 r16 f d b g'4~ g16 a c a64 (g fis g) |
> }
>
> It corrects only one beaming "error", is more rhythmically
> consistent, and might be more in keeping with the context.
Thanks, but I'm not typesetting the sonata :-) It would be
ge-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
On Behalf Of Werner LEMBERG
Sent: Tuesday, July 2, 2024 9:33 PM
To: sripedia_getp...@slmail.me
Cc: lilypond-user@gnu.org
Subject: Re: beam subdivision problem
Hello Jason,
> > ```
> > {
> &g
Hello Jason,
> > ```
> > {
> > \once \set subdivideBeams = ##t
> > \once \set minimumBeamSubdivisionInterval = \musicLength 8
> > f'16 f'32
> > \set stemRightBeamCount = 2
> > f'
> > \set stemLeftBeamCount = 2
> >f' f' f' f'
> > }
> > ```
>
> Looks
Replying from my current email address since the one you cc'd me is
abandoned, wish I could update the git commits' email addresses without
breaking changes haha.
On 2024-07-02 09:47, Werner LEMBERG 'wl at gnu.org' wrote:
``` { \once \set subdivideBeams = ##t \once \set
minimumBeamSubdivisionI
Folks,
how can I easily create a beam subdivision as shown in the attached
image using the current development version 2.25.18? The solution I
came up with is extremely ugly...
Werner
```
{
\once \set subdivideBeams = ##t
\once \set minimumBeamSubdivisionInterval = \musicLength 8
Thank you, Jean. Of course! The broader issue for me is that I hadn't
grasped that it was actually a << {...} \\ {...} >> construction in the
newer, simpler format.
I'm so grateful for your help. I was going around in circles, knowing
that the solution had to be something straightforward.
> I've tried placing the new bar in 3 different places on the treble
> staff. In the current pdf, the first 2 are commented out and the third
> -- which I expected to work -- is active: placement after the >>.
> Somehow a spurious bar is inserted, but I don't know where it's coming from.
You
Thank you all ... I learned a lot fromt your answers Now I just have to
implement a solution.
Greetings
Morten
Lukas-Fabian Moser skrev den 2024-05-11 16:32:
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph
#"scripts.espr"
wrote:
On 12/05/2024 12:41, Archer Endrich wrote:
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for
chimes is added: i.e., another staff abov
On 12/05/2024 12:41, Archer Endrich wrote:
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for
chimes is added: i.e., another staff above t
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for chimes
is added: i.e., another staff above the piano's treble part a few bars
in a
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak self-alignment-X #-1.25 _\esp ~
a2 b4 4(
c1)-\tweak self-alignment-X #-0.5 _\esp
b2-\tw
Hi Mats,
> On May 11, 2024, at 11:51 AM, Mats Bengtsson wrote:
> I would rather do something like the following
I started down that path, but when I saw that the output was
I realized it would take far too much manual tweaking to make it visually
attractive, whereas my \esp version gives
with
On 2024-05-11 15:18, Kieren MacMillan
wrote:
Hi Morten,
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak self-al
Hi Morten,
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak self-alignment-X #-1.25 _\esp ~
a2 b4 4(
c1)-\tweak self-alignment-X #-0.5 _\esp
mor...@borchorst.eu skrev den 2024-05-11 11:40:
Dear list
I am trying to solve this problem about espressivos that stretches
over four beats. I have tried many versions but not seems to solve it
The c1 and the b4 c2 b4 bars work as I hoped for.
the b2 c2 bar and the a2~ a2 does not give the
Dear list
I am trying to solve this problem about espressivos that stretches
over four beats. I have tried many versions but not seems to solve it
The c1 and the b4 c2 b4 bars work as I hoped for.
the b2 c2 bar and the a2~ a2 does not give the wished for results.
Can anybody help
On Wed, May 1, 2024 at 10:55 PM Robert Garrigos wrote:
> Oh this is a bit embarrassing, such a basic error….. sorry, I never
> realized that the parenthesis needs to be right after the first note.
>
Nothing to be embarrassed about. It takes some getting used to.
--
Knute Snortum
anfear
> Sent: Wednesday, May 1, 2024 2:15 PM
> To: Robert Garrigos ; LilyPond Users
>
> Subject: Re: slurs problem with voices
>
> On 01/05/2024 21:57, Robert Garrigos wrote:
>>
>> Why is not the first example working? I tried with explicit voicing with the
>
, May 1, 2024 2:15 PM
To: Robert Garrigos ; LilyPond Users
Subject: Re: slurs problem with voices
On 01/05/2024 21:57, Robert Garrigos wrote:
Why is not the first example working? I tried with explicit voicing with the
same results.
Thanks.
Robert
The slur starts at the d2 so must be
On Wed, May 1, 2024 at 1:59 PM Robert Garrigos wrote:
> I have this music to engrave, note the slur:
> [...]
> Why is not the first example working? I tried with explicit voicing with
> the same results.
>
Slurs in LilyPond are "post events", meaning they always go *after* the
note. So if you
On 01/05/2024 21:57, Robert Garrigos wrote:
Why is not the first example working? I tried with explicit voicing with the
same results.
Thanks.
Robert
The slur starts at the d2 so must be placed with that note following the
pitch and duration,
{ d4 d2( | \hideNotes ef8)}
--
Timothy Lanfea
Hi Robert,
> I tried different approaches but cannot get that slur.
\version "2.25.14"
\language "english"
global = {
\key ef \minor
\time 3/4
}
\relative c' {
\clef treble
\global
<<
{ bf'4 cf2 \tweak staff-position #5.1 ~ | 8 8 r8 r8 }
\\
{ d4 d2( | \hideNotes ef8) }
I have this music to engrave, note the slur:
I tried different approaches but cannot get that slur. This is my code, with
two examples:
\version "2.25.14"
\language "english"
global = {
\key ef \minor
\time 3/4
}
first_example = \relative c' {
\clef treble
\global
<<
{bf'4 \once
Thank you Xavier!
You gave me the hint I needed.
I need to specify that the text spanner should start below (not
default, which is above).
Problem solved.
Ken
On Mon, Apr 22, 2024 at 1:18 PM Xavier Scheuer wrote:
>
> On Mon, 22 Apr 2024 at 21:48, Kenneth Wolcott
> wrote:
&
On Mon, 22 Apr 2024 at 21:48, Kenneth Wolcott
wrote:
>
> Hi;
>
> I've made a simple mistake but I can't figure out what I did wrong.
>
> At bar #36 the first text spanner starts. I think that's correct. But
> the piano articulation should be a bar earlier? But that also seems
> correct. How ca
On Sat, Mar 16, 2024 at 10:20 AM Hans Aikema
wrote:
>
>
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>
> Hi, Again -
>
> I've searched the Notation documentation and the LSR, and I cannot figure
> out how to solve t
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>> Hi, Again -
>>
>> I've searched the Notation documentation and the LSR, and I cannot figure
>> out how to solve this. It looks like a half note with an accent fol
Very short hairpins?
Phil
On 16/03/2024 16:27, Ralph Palmer wrote:
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot
figure out how to solve this. It looks like a half note with an accent
followed by a half note with the opposite figure. (You may have to
zoom in
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot figure
out how to solve this. It looks like a half note with an accent followed by
a half note with the opposite figure. (You may have to zoom in a bit!) I
can do the accent, and I seem to remember its opposite, but I c
Jean and Kieren -
Thank you both for pointing me in the right direction. Kieren, I actually
looked at Visibility of Objects, but somehow did not see \undo.
All the best,
Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
On Tue, Mar 12, 2024 at 7:51 AM Kieren MacMil
Hi Ralph,
> I cannot figure out how to revert or reverse "\omit TupletNumber". "\once
> \omit TupletNumber" does, in fact omit only the next tuplet number. However,
> if I use "\omit TupletNumber", it omits all folowing tuplet numbers, and I
> cannot find a command to restore the tuplet numbers
> I cannot figure out how to revert or reverse "\omit TupletNumber".
\undo \omit TupletNumber
Best,
Jean
signature.asc
Description: This is a digitally signed message part
Hello, again -
I cannot figure out how to revert or reverse "\omit TupletNumber". "\once
\omit TupletNumber" does, in fact omit only the next tuplet number.
However, if I use "\omit TupletNumber", it omits all folowing tuplet
numbers, and I cannot find a command to restore the tuplet numbers. Any
Thanks, Kieren -
Yes. My mistake. Still didn't quite do what I'd hoped, though, even when I
corrected it.
All the best,
Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
On Wed, Mar 6, 2024 at 7:42 PM wrote:
> Hi Ralph,
>
> Shouldn’t the d be 4. [not 4]?
>
> > bf
:8 } c4.*2/3:8 d4.*2/3:8 | c2.*2/3:8 b4.*2/3:8
> a4.*2/3:8
> }
>
> -William
>
> On 3/6/24 21:53, Ralph Palmer wrote:
> > Hi -
> >
> > Thanks for all your work and for your help to me over a number of years.
> >
> > I'm running into a problem
d for your help to me over a number of years.
I'm running into a problem I have no idea how to fix. I've looked at
tremolos in the Notation Reference and in the Snippet Repository, but
can't find a solution. I would appreciate any help. The first image is
the result of tremoloTrip
Hi Ralph,
Shouldn’t the d be 4. [not 4]?
bf2.:6 c4.:3 d4:3 |
Maybe I’m misunderstanding…?
Cheers,
Kieren.
Hi -
Thanks for all your work and for your help to me over a number of years.
I'm running into a problem I have no idea how to fix. I've looked at
tremolos in the Notation Reference and in the Snippet Repository, but can't
find a solution. I would appreciate any help. The fir
Hi lilyponders!
I have a problem with a frenched score. From a larger piece I'm creating
an excerpt for the choir and that shall be "frenched", aka voices that
have nothing to do are removed while they are silent.
As documented this is nicely done when I add a
\RemoveAl
to this problem.
The user only needs to enter pedal settings at the beginning of a passage,
which looks like:
<>\setHarpPedals { d c b e f g a }
Harp_pedal_engraver then listens for notes and automatically prints pedal
changes when new accidentals occur. Manually entered pedal changes (usi
That worked perfectly:
Emacs > Options > Customize Emacs > Options Matching > Lilypond > Lilypond
Lilypond Command > /usr/bin/lilypond
--include=/home/laurie/Lilypond/includes "${@}"
Thanks
Laurie Savage
https://www.queensofthewest.com/
The Latest Queens of The West clips
https://www.youtube.com
Laurie Savage wrote on 13.11.2023:
> Still I get errors like this:
> /home/laurie/Documents/Charts/Transpositions/Dear Old
> Stockholm/Dear-Old-Stockhom_Traditional.ly:3:10: error: cannot find file:
> `/home/Laurie/Lilypond/includes/jazzchords.ily'
>
> ...
>
> Any ideas?
I am not calling lilypon
Thanks for trying!
Laurie Savage
On Tue, 14 Nov 2023 at 20:59, David Kastrup wrote:
> Laurie Savage writes:
>
> > Thanks David,
> >
> > I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
> > any more easily so there isn't much advantage in tweaking it to behave
> with
> >
Laurie Savage writes:
> Thanks David,
>
> I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
> any more easily so there isn't much advantage in tweaking it to behave with
> my customised Include files. As for your question about where I found the
> documentation for the loca
Thanks David,
I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
any more easily so there isn't much advantage in tweaking it to behave with
my customised Include files. As for your question about where I found the
documentation for the location of my Includes: Options > Cust
On Tue 14 Nov 2023 at 07:04:39 (+1100), Laurie Savage wrote:
> Thanks, I should have spotted that.
So presumably the "cannot find file" error went away when you
corrected the full path "/home/Laurie/Lilypond/includes/jazzchords.ily"
but how about when you type only:
\include "jazzchords.ily"
D
Thanks, I should have spotted that. But I'm not sure why this setting
hasn't been picked up by Emacs lilypond mode:
Lilypond Include Path: String: /home/laurie/Lilypond/includes
State : SAVED and set.
LilyPond include path.
Groups: Lilypond
I don't want to type the full file path everyti
On Mon, Nov 13, 2023 at 02:45:26PM +1100, Laurie Savage wrote:
>I store my Includes file in a directory ~/Lilypond/includes but
>Lilypond mode cannot locate them even if I specify a full file name e.g
>\include
>"/home/Laurie/Lilypond/includes/jazzchords.ily"
>I set this in my ~
Hi,
I thought I'd give the Emacs Lilypond mode a try-out. I like Emacs and have
used it a lot for coding and writing in LaTeX in my past career. (No editor
wars please, VIM is good too but I'm less familiar with it!)
I store my Includes file in a directory ~/Lilypond/includes but Lilypond
mode ca
Thanks Jean, that worked!
It was a bigger drama than I expected--just about everything I can access
on this laptop (it's my work machine) is linked to the OneDrive folder,
meaning that silly bracket turned up everywhere. I managed to find a
high-level (and safe) folder to move it to though, and I'
Ouch, I think I see the cause. Could you move LilyPond to a folder whose full
path doesn't contain any parentheses and retry?
signature.asc
Description: This is a digitally signed message part
Apologies for not including the list--my usual client does that default,
but I'm not using my usual client!
Here's the .ly file as requested.
Cameron Horsburgh
On Wed, 11 Oct 2023 at 13:14, Jean Abou Samra wrote:
> Le mercredi 11 octobre 2023 à 13:03 +1030, Cameron Horsburgh a écrit :
>
> H
Hi,
That is a weird problem. Could you run LilyPond with the --ps option and send
the resulting PostScript file?
Thanks,
Jean
signature.asc
Description: This is a digitally signed message part
Hi all,
I've got LilyPond 2.24.2 running on Windows 11. It's installed as a local
installation in a folder in my OneDrive folder and I've never had a problem
with this setup before. My problem has only appeared since moving to a
Windows 11 machine though, so that might be relev
Thank you. It worked. С уважением,Виноградов Юрий.10.10.2023, 21:31, "Jean Abou Samra" :Le mardi 10 octobre 2023 à 21:16 +0300, Виноградов Юрий a écrit :Hello. Please help me to remove this collision at the beginning of the piece. So that everything starts smoothly.You need to insert grace skips (“
Le mardi 10 octobre 2023 à 21:16 +0300, Виноградов Юрий a écrit :
> Hello. Please help me to remove this collision at the beginning of the piece.
> So that everything starts smoothly.
You need to insert grace skips (“\grace { s8 }”) in each staff that does not
start with a grace note.
See
https:
The oldest bug of all, I believe!
Just put hidden ("s") appoggiaturas in the other parts and then everything will
line up.
Paul
From: Виноградов Юрий
To: "lilypond-user@gnu.org"
Sent: 10/10/2023 19:16
Subject: The problem of acciaccatura from the b
Hello. Please help me to remove this collision at the beginning of the piece. So that everything starts smoothly. С уважением,Виноградов Юрий.
Graham King writes:
> Many thanks David!
>
> (In the course of trying to convert the \note syntax, I discovered the
> existence of \note-by-number which solved 90% of my problem. Sorry for
> the confusing reference to \note.)
Well, \note-by-number #1 #0 #UP is essentially the s
Many thanks David!
(In the course of trying to convert the \note syntax, I discovered the
existence of \note-by-number which solved 90% of my problem. Sorry for
the confusing reference to \note.)
On Sun, 2023-09-17 at 00:38 +0200, David Kastrup wrote:
> Graham King writes:
>
> > I
Graham King writes:
> I'm trying to convert a naive Scheme function which has been broken by
> the new syntax for \note. Some arithmetic gives me the index (in this
> MNWE, 96) to a list of pairs, foo, from which I want to extract some
> markup.
>
> The 300-LOC proble
I'm trying to convert a naive Scheme function which has been broken by
the new syntax for \note. Some arithmetic gives me the index (in this
MNWE, 96) to a list of pairs, foo, from which I want to extract some
markup.
The 300-LOC problem seems to boil down to
> On Aug 27, 2023, at 11:55 PM, Werner LEMBERG wrote:
>
>
>>>> I do not think that my Times New Roman font is corrupted.
>>
>> Actually, I think it is: Most likely the font's 'post' table is
>> broken (i.e., it has a wrong PostScript name
> On 28 Aug 2023, at 08:49, Jean Abou Samra wrote:
>
>
>
>> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>>
>>
>>
>>> You might try to copy the affected font from macOS 14 to macOS 13 and
>>> check whether it works.
>>
>>
>> This bug has already been fixed in Homebrew. Please ju
> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>
>
>
>> You might try to copy the affected font from macOS 14 to macOS 13 and
>> check whether it works.
>
>
> This bug has already been fixed in Homebrew. Please just uninstall and
> reinstall LilyPond and it should go away.
Whoops,
> You might try to copy the affected font from macOS 14 to macOS 13 and
> check whether it works.
This bug has already been fixed in Homebrew. Please just uninstall and
reinstall LilyPond and it should go away.
Jean
> Jean did the analysis then, he can tell more.
D'oh, *I* did the analysis then :-)
https://gitlab.com/lilypond/lilypond/-/issues/6508
Werner
>>> I do not think that my Times New Roman font is corrupted.
>
> Actually, I think it is: Most likely the font's 'post' table is
> broken (i.e., it has a wrong PostScript name for glyph 'N').
> Normally, you won't see the problem at all becau
>> I am experiencing a very weird problem with Lilypond on macOS 13
>> Ventura. When using the Times New Roman font, the capital letter N
>> is mis-printed.
Have a look at the thread starting at
https://lists.gnu.org/archive/html/lilypond-user/2022-12/msg00349.html
whic
Hi.
> On 28 Aug 2023, at 11:36, David F. wrote:
>
> I am experiencing a very weird problem with Lilypond on macOS 13 Ventura.
> When using the Times New Roman font, the capital letter N is mis-printed.
>
I can confirm and replicate this under 13.4.1
> I do not think that
Thank you Jean!
On Sat, May 13, 2023 at 7:19 AM Jean Abou Samra wrote:
>
> Le vendredi 12 mai 2023 à 20:42 -0700, Kenneth Wolcott a écrit :
>
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually implemented a
> fine+dc_al_fine repeat into a 2.24.1 repeat segno and I run into d
Le vendredi 12 mai 2023 à 20:42 -0700, Kenneth Wolcott a écrit :
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually
> implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
> run into difficulties.
>
> Since the fine ends at beat 3 of 4 (well, 2/2 meter), I ru
Forgot to include screenshots of the origin that I'm using as a sample
to engrave from...
On Fri, May 12, 2023 at 8:42 PM Kenneth Wolcott
wrote:
>
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually
> implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
> run
Hi;
I'm converting a 2.22.2 Lilypond engraving where I manually
implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
run into difficulties.
Since the fine ends at beat 3 of 4 (well, 2/2 meter), I run into
issues with partials and bar checks.
I also run into problems with the
ng it again
> and reinstalling with the same result. I tried some other old versions, and
> this is the only version that has this problem. Is it an interaction with
> Windows 11, perhaps (which I upgraded to recently)?
That's possible. I also started to get this problem with an
cript name
Exited with return code -1073741819.
I'm sure this has been OK in the past, and I even tried downloading it again
and reinstalling with the same result. I tried some other old versions, and
this is the only version that has this problem. Is it an interaction with
Windows 11, p
>> [...] after doing a grep over the git repository, which leads me to
>> `property-iterator.cc`, it's not really clear to me what's going
>> on...
>
> Well, you can find it in `define-event-classes.scm`. It's the event
> class for events created by `\override`s.
Ah, yes, I missed that while do
Le jeudi 16 février 2023 à 06:30 +, Werner LEMBERG a écrit :
> ```
>
> >> As can be seen, the acciaccatura neither has a slash nor a slur if
> >> quoted. [...]
> >
> > This looks like a real bug, please file an issue.
>
> [https://gitlab.com/lilypond/lilypond/-/issues/6531](https://gitlab.c
>> As can be seen, the acciaccatura neither has a slash nor a slur if
>> quoted. [...]
>
> This looks like a real bug, please file an issue.
https://gitlab.com/lilypond/lilypond/-/issues/6531
> AFAICS, this works:
>
> ```
> \version "2.25.2"
>
> \layout {
> \context {
> \Score
> qu
Le mercredi 15 février 2023 à 19:34 +, Werner LEMBERG a écrit :
> ```
>
> Consider this example.
>
> ```
> fluteNotes = \relative {
> r2. c''4 |
> d8 \acciaccatura e c d e fis2 |
> g2 d |
> }
>
> oboeNotes = \relative c'' {
> R1 |
> \cueDuring "flute" #UP { R1 } |
> g2 d |
> }
>
Consider this example.
```
fluteNotes = \relative {
r2. c''4 |
d8 \acciaccatura e c d e fis2 |
g2 d |
}
oboeNotes = \relative c'' {
R1 |
\cueDuring "flute" #UP { R1 } |
g2 d |
}
\addQuote "flute" { \fluteNotes }
<<
\new Staff \fluteNotes
\new Staff \oboeNotes
>>
```
As can be
Jean Abou Samra writes:
> Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit :
>> That begs the question whether it would make sense to restrict
>> afterGrace scales to values below 1. But I think that making syntactic
>> decisions based on values rather than types is really icky.
Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit :
> That begs the question whether it would make sense to restrict
> afterGrace scales to values below 1. But I think that making syntactic
> decisions based on values rather than types is really icky. It is
> probably a bad idea
Lukas-Fabian Moser writes:
> Hi Werner,
>
>>> Alternatively you may try to use \afterGrace to insert the \clef
>>> before the bar line, although this would probably require some
>>> manual spacing too.
>> This doesn't work at all: `\afterGrace` doesn't accept a clef, as the
>> image shows.
>
> af
> That is because you are using 1 instead of a note name such as c'1. after-
> grace does not handle this mechanism.
Thanks (and thanks to Lukas, too)!
> Instead of manually extra-offsetting the Clefs you might also do
> something along the lines of [...]
Nice! I will use that.
Werner
1 - 100 of 3888 matches
Mail list logo
