Here you go: https://gitlab.com/lilypond/lilypond/-/issues/6736
Thanks again Werner
L
On Tue, Aug 6, 2024 at 10:01 PM Luca Fascione wrote:
> Ok cool, thanks Werner.
> I'll make a ticket
>
> L
>
> On Tue, Aug 6, 2024 at 6:38 PM Werner LEMBERG wrote:
>
>>
>>
I can code myself in Scheme?
>
> I don't know (Harm can certainly make a better educated guess than
> me), but my gut feeling says that it is a hard problem, especially to
> get the horizontal spacing right.
>
>
> Werner
>
--
Luca Fascione
On Tue, Aug 6, 2024 at 5:47 PM Werner LEMBERG wrote:
>
> > I'm looking for a way to make a "fingering bracket": [...]
>
> Please file an issue,
>
Sure!
Is this not something I can code myself in Scheme?
L
--
Luca Fascione
scheme
(implemented in scheme, ha.) would fall flat on its face when dealing with
whole-notes.
But instead it doesn't. I can see that both rests and whole notes have
associated Stem grobs.
What kind of sorcery is that?
Thanks again guys
L
--
Luca Fascione
g_engraver, which attaches
fingering in the way we want
\remove Fingering_engraver
\consists #Guitar_fingering_engraver
}
}
guitar = {
\key c \major
\time 2/4
\clef "violin_8"
4
4
}
\score {
\new Staff = "guitar" {
\key c \major
\time 2/4
\clef "violin_8"
4
4
}
\layout { }
}
--
Luca Fascione
ing (list grob)) but that also didn't seem to do much useful
Cheers
L
--
Luca Fascione
Aha. I _also_ removed the use of m-chordify and now it all works as you
said.
Great, slur problem solved.
And thanks again
--
Luca Fascione
(as a test I also added \remove New_fingering_engraver and all the
fingering went away, do it is doing something)
On Sat, Jul 27, 2024 at 4:06 PM Luca Fascione wrote:
>
>
> On Sat, Jul 27, 2024 at 1:31 PM David Kastrup wrote:
>
>> Have you tried my other suggestion of just r
fingering" for
music that has gone through
the (make-music 'EventChord 'elements (list m)) part
Am I doing it wrong, maybe?
L
--
Luca Fascione
Kastrup wrote:
> Luca Fascione writes:
>
> > Hi David, I just tried out your suggestion, and it works quite well.
> > One issue I found is that it moves slurs from "above the beam" to "at
> > the notehead" (in fact, it seems to me the slur is actually "a
report.
Cheers,
Luca
On Thu, Jul 25, 2024 at 10:02 PM David Kastrup wrote:
> Luca Fascione writes:
>
> > Ok, so. I tested this eventChords idea, and it seems to behave as if this
> > a-4
> > was entered as this
> > -4
> > but unfortunately I actually nee
Ok, so. I tested this eventChords idea, and it seems to behave as if this
a-4
was entered as this
-4
but unfortunately I actually need this
how can I achieve that?
Thanks a lot David,
Luca
On Wed, Jul 24, 2024 at 10:19 PM Luca Fascione wrote:
> Thus might do it yes.
> Does even
Thus might do it yes.
Does even chords transform single notes into chords, does nothing to chords
and leaves untouched everything else? (Key changes, time markings changes,
all that stuff)
Thanks David!
L
On Wed, 24 Jul 2024, 21:01 David Kastrup, wrote:
> Luca Fascione writes:
>
chords?
I think the `\parallelMusic` macro works more or less this way, maybe.
Any pointers to code/snippets to use for inspiration would be greatly
appreciated.
Many thanks
Luca
--
Luca Fascione
Lovely, thank you Knute
L
On Mon, 20 Nov 2023, 16:11 Knute Snortum, wrote:
> On Mon, Nov 20, 2023 at 6:34 AM Luca Fascione
> wrote:
>
>> Did this change between 22 and 24?
>> Is there somewhere I can go to see the implementation for the LSR that
>> used 2.22?
>&g
a way to override that. I used it
> once to put a bracket around a cord. You just have to override one of the
> properties to move the endpoints in the negative direction as well as an x
> offset for the closing side.
>
> On Mon, Nov 20, 2023, 7:35 AM Luca Fascione wrote:
>
>&
Did this change between 22 and 24?
Is there somewhere I can go to see the implementation for the LSR that used
2.22?
L
On Mon, 20 Nov 2023, 15:07 Knute Snortum, wrote:
> On Mon, Nov 20, 2023 at 4:35 AM Luca Fascione
> wrote:
>
>> Also,
>> it doesn't seem to actual
n_tests.ly:4:19: error: bad grob property path
\once \override
Parentheses.stencils = #(lambda (grob)
paren_tests.ly:10:19: error: bad grob property path
\once \override
Parentheses.stencils = #(lambda (grob)
On Fri, Nov 17, 2023 at 12:29 PM Luca Fascione wrote:
> Yes, I was thinking more ab
On Fri, Nov 17, 2023 at 11:58 AM Jean Abou Samra wrote:
> Le vendredi 17 novembre 2023 à 11:44 +0100, Luca Fascione a écrit :
>
> Nice. Thanks Jean. This solves it for my current score
>
> In general, what's the background for this not working though?
> You seem to imply
\left \right system to
gauge delimiter sizes?
Cheers
L
On Fri, Nov 17, 2023 at 11:18 AM Jean Abou Samra wrote:
> Le vendredi 17 novembre 2023 à 10:58 +0100, Luca Fascione a écrit :
>
> Hi all,
>
>
>
> Try
>
> https://lsr.di.unimi.it/LSR/Item?id=902
>
>
--
Luca Fascione
ly, I believe it's just the
> standard General MIDI percussion keymap.
>
> At 10:52 on 17 Nov 2023, Luca Fascione wrote:
> > Hi,
> > I'm converting a MIDI file to lilypond with a drumset track.
>
> > My process goes through MusicXML, but the `musicxml2ly` scri
parentheses (chords are there but parens are not)
Also,
\new ChordNames { \chordmode { \parenthesize { a:m7 } } }
produces the chord symbol and no parentheses
\parenthesisOpenSymbol also is rejected inside \chordmode
Cheers
L
--
Luca Fascione
mind, the mapping lilypond uses to go from the percussion notes to
its MIDI output is all I need (and then I can reverse that). If someone
could get me a breadcrumb to that, that'd be grand.
Thanks
Luca
--
Luca Fascione
even without
> barlines in the beginning.
>
'msorry what's that? Could you show me?
What version of lilypond are you using?
Thanks again,
L
--
Luca Fascione
epeat unfold 2 { c c c c } \break
\repeat unfold 4 { c c c c }
}
\score {
\m
}
On Tue, Nov 22, 2022 at 3:17 PM Luca Fascione wrote:
> Noice, thanks Leo, this is enough of a workaround for my current state,
> thanks for figuring that out
>
> Cheers,
> Luca
>
> On
wn you can work
> around it by printing the barlines at the beginning of staves too, by adding
> \defineBarLine "|" #'("|" "|" "|”)
> to the layout block.
>
> HTH
> /Leo
>
> 22 nov. 2022 kl. 13:30 skrev Luca Fascione :
>
> Ok, so,
st clef visible
}
m = \relative c'' {
c4 c c c | \break
4 cis cis cis |
4 cis cis cis |
\repeat unfold 2 { c c c c } \break
4 c c c |
4 cis cis cis |
\repeat unfold 2 { c c c c } \break
\repeat unfold 4 { c c c c }
}
\score {
\m
}
On Tue, Nov 22,
It seems to have something to do with this:
\override Clef.break-visibility = #'#(#f #f #f)
I'm working on shortening the source
L
On Tue, Nov 22, 2022 at 12:25 PM Luca Fascione wrote:
> Ha. Ok, I'll whittle it down to something small that repros it then.
> Thanks Leo!
&
rror is probably needed to solve this. Try to make a minimal example.
> That said, one could guess that it could have something to do with
> break-alignments.
>
> Best
> /Leo
>
> 22 nov. 2022 kl. 11:27 skrev Luca Fascione :
>
> Hi all,
> In a sheet I'm working on
ny thanks,
Luca
[image: image.png]
--
Luca Fascione
Awesome, thanks Jean!
L
On Sun, 20 Nov 2022, 00:30 Jean Abou Samra, wrote:
> Le 20/11/2022 à 00:02, Luca Fascione a écrit :
> > Hi all,
> > I have some 2 voice music coming from musicxml like this
> >
> > 4 8. 16 ~ ~ 2.
> >
> > and I'd like to split i
rescobaldi, but I couldn't find a transformation for this purpose)
Cheers,
Luca
--
Luca Fascione
Yes! Thanks Jean, I don't know why I didn't see this myself.
Cheers!
L
On Thu, 17 Nov 2022, 00:27 Jean Abou Samra, wrote:
> Le 16/11/2022 à 23:44, Luca Fascione a écrit :
> > Hi all,
> > is there a way to run the chord naming logic from two voices (in my
> > ca
that source
Cheers
Luca
--
Luca Fascione
What if instead of `\upbeat` (which is weirdly named when used in the
end-of-music/phrase/hymn/passage scenario) this new thing is just called
`\partialMusic`?
It's backward compatible, does something easy to use in some simple
scenarios, leaves everything else in place for more refined use cases,
What if you rotate them instead?
Rename the current \partial \partialDuration,
convert.ly now is just s/partial/partialDuration/
and \partial always takes music from now on
It's the same as Werner said, but keeps the good name
L
On Sun, 20 Mar 2022, 08:24 Werner LEMBERG, wrote:
>
> > A con
Hi Valentin,
thanks for the super prompt reply!
On Sun, Mar 6, 2022 at 5:34 PM Valentin Petzel wrote:
> So instead of doing the assoc-set! you might want to do something like
>
> (ly:grob-set-property! grob 'details `((beamed-lengths . ,stem-bmlgths)
> . ,detls))
>
For my edification, I'l
you want
> to
> know what exact properties a grob has, you can look in define-grobs.scm.
> And
> similar stuff.
>
> And if you encounter something you really do not understand, ask the list.
> We’ve got some really marvellous people here who appear to know about
> everything yo
"grep and in the source", it's all in "scm/". Vague pointers like that are hopefully all I'll need.
Many thanks,
Luca
On Mon, Feb 21, 2022 at 6:49 PM Luca Fascione wrote:
> Yes exactly, because of how our finger to note relation works, the
> enhancement in
t; rather confusing, as there is no monotonic relating between finger and
> pitch.
> As such I suppose guitar people would want to use fingerings with left or
> right
> orientations in chords anyway.
>
> Cheers,
> Valentin
>
> Am Montag, 21. Februar 2022, 17:47:58 CET schrieb L
b 21, 2022 at 5:42 PM Valentin Petzel wrote:
> No, not nescessarily. If we want all Fingerings on top or below there is
> no real benefit of doing the chord thing. In fact doing that leads to the
> exact same issue of the fingering for d being next to the other ones.
>
> Cheers,
>
the Beam (this does still get messed up by
> very
> slanted Beams, it might be useful to also get a reference to the Beam grob
> to
> factor in the angle of the Beam). With this we can estimate the free space
> between NoteHead and Beam, and depending on this space, shift the
> F
e chord some note heads are
> on
> the other side of the Stem the alignment of something like -1-2-3
> would
> change (disregarding that it wouldn’t even be clear what note head to use).
>
> Cheers,
> Valentin
>
> Am Montag, 21. Februar 2022, 09:19:30 CET schrieb Luca Fa
gt; Am So., 20. Feb. 2022 um 22:41 Uhr schrieb Luca Fascione <
> l.fasci...@gmail.com>:
>
> > a) I'm looking for a way to get the fingerings where I want them without
> > using one-note-chord tricks
>
> Well, for Fingerings not in chord, like b-1 or -2-1 X-parent
&
e results. Somewhat like here.
>
> Valentin
>
> Am Sonntag, 20. Februar 2022, 21:17:31 CET schrieb Luca Fascione:
> > So... would anybody be able to lend a hand here please?
> >
> > Many thanks
> > Luca
> >
> > On Sat, Feb 12, 2022 at 7:49 PM Luca Fascione
t necessarily looking
for a "simple" solution.
If the answer is: "it's a big change involving steps a to f", I'm happy to
have at it, under somebody's guidance.
Given that solving this problem is a need of mine, I feel it's completely
fine that it ends up b
So... would anybody be able to lend a hand here please?
Many thanks
Luca
On Sat, Feb 12, 2022 at 7:49 PM Luca Fascione wrote:
> Hello,
> sorry for the double-post, I'm unsure whether this should go to -user or
> -devel.
>
> I'm looking for some guidance to set up fing
Hi Thomas,
maybe this can be handy: the `moreutils` package has a utility called `ts`,
that will prepend a timestamp to each line of output.
If you pipe the output of your compilation into it, you can get timing
information quite easily, here's an example:
% ls | ts -s "%H:%M:%.S"
00:00:00.13
Hi Simon,
so this actually works rather well, I ended up taking the rotation out, as
with the actual font you get a better sense of the nib direction with the
original orientation of the solidus, nonetheless I do really like your
suggestion of using a slightly larger size, I find it does help a fai
with the actual font, of
> course, only with LilyPond’s default Sans font. So you’ll likely have to
> adjust the numerical values in lines 6 and 27–29 to taste. See <
> http://lilypond.org/doc/v2.18/Documentation/notation/text-markup-commands>
> for documentation on the markup
have forwarded it there but I strongly suggest you subscribe at
>> https://lists.gnu.org/mailman/listinfo/lilypond-user to automatically
>> receive any replies.
>>
>> Best
>> Urs
>>
>> Am 20.11.2015 um 10:46 schrieb LilyPond blog contact form:
>>
>>
4 bes'2 }
>>
\layout {}
}
%%
You can see I have hardcoded the form of Cmaj7 to render as Cmaj7/B, but
the spacing feels like a step in the right direction (admittedly the
kerning could use work, but it feels like a reasonable compromise)
I have attached the co
52 matches
Mail list logo
