Le 14/11/2021 à 13:49, Thomas Morley a écrit :
Am Fr., 12. Nov. 2021 um 13:44 Uhr schrieb Leo Correia de Verdier
:
Dear Harm and list!
The chords were not that hard to implement. What I did was:
1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset from
glissandoStemsOn
Am Fr., 12. Nov. 2021 um 13:44 Uhr schrieb Leo Correia de Verdier
:
>
> Dear Harm and list!
>
> The chords were not that hard to implement. What I did was:
>
> 1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset
> from glissandoStemsOn and glissandoStemsOff. Transparency is s
Dear Harm and list!
The chords were not that hard to implement. What I did was:
1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset from
glissandoStemsOn and glissandoStemsOff. Transparency is set for individual
noteheads and used to determine wether a notehead should be p
Am Mo., 25. Okt. 2021 um 12:00 Uhr schrieb Leo Correia de Verdier
:
>
> Don’t worry, you’re doing far more on this than anyone could reasonably
> expect.
>
> The final result should be something along these lines, but what I was asking
> about is just the chord possibility. I have looked a little
Don’t worry, you’re doing far more on this than anyone could reasonably expect.
The final result should be something along these lines, but what I was asking
about is just the chord possibility. I have looked a little more into the code
and it’s far far above my level, but I’ve found som places
Am Mo., 25. Okt. 2021 um 00:02 Uhr schrieb Leo Correia de Verdier
:
> One feature I would find useful would be the ability to make chords with one
> ”gliss-note” and one regular notehead. I implemented this (not entirely
> successfully) on top of an earlier version of your code by making it work
Dear Harm!
I am very thankful for and moved by the effort you’re putting into this!
One feature I would find useful would be the ability to make chords with one
”gliss-note” and one regular notehead. I implemented this (not entirely
successfully) on top of an earlier version of your code by mak
Am Fr., 22. Okt. 2021 um 15:45 Uhr schrieb Thomas Morley
:
>
> Am Fr., 22. Okt. 2021 um 14:48 Uhr schrieb Thomas Morley
> :
> >
> > Am Fr., 22. Okt. 2021 um 14:33 Uhr schrieb Dimitris Marinakis
> > :
> > >
> > > I'd really like to test this version but I'm getting an error :
> > > In procedure ly:g
Am Fr., 22. Okt. 2021 um 14:48 Uhr schrieb Thomas Morley
:
>
> Am Fr., 22. Okt. 2021 um 14:33 Uhr schrieb Dimitris Marinakis
> :
> >
> > I'd really like to test this version but I'm getting an error :
> > In procedure ly:grob-object in expression (ly:grob-object stem (quote
> > glissandi) ...):
>
Am Fr., 22. Okt. 2021 um 14:33 Uhr schrieb Dimitris Marinakis
:
>
> I'd really like to test this version but I'm getting an error :
> In procedure ly:grob-object in expression (ly:grob-object stem (quote
> glissandi) ...):
> Wrong number of arguments to #
You need a more recent version, 2.23.3 wo
I'd really like to test this version but I'm getting an error :
In procedure ly:grob-object in expression (ly:grob-object stem (quote
glissandi) ...):
Wrong number of arguments to #
On Fri, Oct 22, 2021 at 11:57 AM Thomas Morley
wrote:
> Am Di., 5. Okt. 2021 um 13:39 Uhr schrieb Leo Correia de
Am Di., 5. Okt. 2021 um 13:39 Uhr schrieb Leo Correia de Verdier
:
>
> Dear Harm and list!
>
> After almost two years I’m back using this code and found some things I would
> need help with.
> (I have done some additions to it, so it can hackishly handle additional
> noteheads on the stems/noteco
Now with the attached example:
When editing the example for the last time before sending it I noticed the
second problem was only in the code I had written myself, and that the
reproduction of it with your code had to do with another issue. In my case it
probably have to do with some flaw in th
Dear Harm and list!
After almost two years I’m back using this code and found some things I would
need help with.
(I have done some additions to it, so it can hackishly handle additional
noteheads on the stems/notecolumns and also tweaks rests passed by the
glissando line, byt as I’m not very
Am Fr., 25. Okt. 2019 um 22:41 Uhr schrieb Leo Correia de Verdier
:
> I realized that defining the glissando gradient taking the stencil as point
> of departure, rather than the grob properties, makes it work for broken
> glissandi too. It was a quite minimal change.
>
> (gliss-gradient (/ (+ (-
Brilliant!
I realized that defining the glissando gradient taking the stencil as point of
departure, rather than the grob properties, makes it work for broken glissandi
too. It was a quite minimal change.
(gliss-gradient (/ (+ (- (car stil-y-ext) (cdr stil-y-ext)) (* half-line-thick
2))
Am Sa., 19. Okt. 2019 um 12:36 Uhr schrieb Thomas Morley
:
> Meanwhile I've probably found a method to affect Beams from inside a
> Glissando.after-line-breaking, but currently it's not mature to say
> more.
> Anyway, my goal will be to make Beams parallel to the glissando-line,
> I don't think do
> 19 okt. 2019 kl. 12:36 skrev Thomas Morley :
>
> Am Sa., 19. Okt. 2019 um 00:01 Uhr schrieb Leo Correia de Verdier
> :
>>
>> Thanks a lot for your help!
>>
>> Quite to my surprise I found the following snippet does work.
>>
>>
>>
>> \version "2.19.82"
>>
>> #(define changebeam (la
Am Sa., 19. Okt. 2019 um 00:01 Uhr schrieb Leo Correia de Verdier
:
>
> Thanks a lot for your help!
>
> Quite to my surprise I found the following snippet does work.
>
>
>
> \version "2.19.82"
>
> #(define changebeam (lambda (grob)
> (let* ((stem (ly:grob-object grob '
Thanks a lot for your help!
Quite to my surprise I found the following snippet does work.
\version "2.19.82"
#(define changebeam (lambda (grob)
(let* ((stem (ly:grob-object grob 'stem))
(beam (ly:grob-object stem 'beam)))
Am Mo., 14. Okt. 2019 um 12:22 Uhr schrieb Leo Correia de Verdier
:
> When you write that "inner beams positions can’t be affected from
> Glissando.after-line-breaking", do you mean it’s impossible, that they would
> need to be recreated rather than repositioned or just that the actual code
> c
Thank you very much!
Since I’m not very experienced with either lilypond or programming in general
this will be a lot for me to break up, understand and work with, but it
contains most of what I need. Now I’ll go and do my homework for some days (or
even longer). In some time I’ll be back with
Am Do., 10. Okt. 2019 um 14:51 Uhr schrieb Leo Correia de Verdier
:
>
> Dear list!
>
> I'm soon going to start engraving a piece that contains very many glissandi
> with timing marks (or actually, glissandi with broken bowing and
> articulations during the way). The snippet in
> http://lilypond.
Dear list!
I'm soon going to start engraving a piece that contains very many glissandi
with timing marks (or actually, glissandi with broken bowing and articulations
during the way). The snippet in
http://lilypond.org/doc/v2.19/Documentation/notation/expressive-marks-as-lines#glissando
mention
24 matches
Mail list logo
