I agree with this, but I can imagine the following distinct engraving
styles:
1. Beam over rests only when the beam both begins and ends with a note.
2. Also beam over initial rests.
3. Also beam over final rests.
Further, I can imagine wanting e.g. c16[ r c r], rather than c16[ r c] r,
but in
Hello everyone,
My problem comes from the incompatibility of proportionally spacing the
notes within feathered beams and the completion heads engraver. I'm trying
to achieve this result (in the manual):
But the completion heads engraver completely messes it up, forcing me to
choose a regular
I've got this score:
\version "2.19.82"
\new TabStaff { q }
It results in the following tab, which is not what I want:
q4.pdf
Description: weird tab
:---
:To-
:A--4---
:B--4-4-
:---2-2-
:---
Is there any way to retain the fingering from the full chord when using
the `q` chord
> -- Forwarded message --
> From: David Kastrup
> To: Kieren MacMillan
> Cc: foxfanfare , Lilypond-User Mailing List <
> lilypond-user@gnu.org>
> Bcc:
> Date: Tue, 02 Apr 2019 17:33:07 +0200
> Subject: Re: Automatic beaming with rest
> Kieren MacMillan writes:
>
> > p.s.
> >
> >
Hi Carl,
> I think that if we can get smarter autobeaming (like we need to do to get
> subdivision and tuplets done right) we can do beaming over rests. Probably
> we need to do a two-pass beam check to get the autobeaming right for
> subdivision, and if we do two-pass, we can beam over
On 4/2/19, Werner LEMBERG wrote:
> Can you suggest a (possibly read-only) property or properties that
> could be easily added to either the `Clef' or `NoteColumn' grob on the
> C++ side, and which would considerably simplify the code?
Hi Werner,
upcoming new features notwithstanding, could you
On 4/2/19, 9:41 AM, "Kieren MacMillan" wrote:
>Hi David,
>> What is the "beat" as defined for the beam?
> Perhaps I should use the word "moment"… Example: In 3/4, one can set the
autobeamer to beam sub-quarter notes as 3, or 2+1, or 1+2, or 1+1+1 (or even
other
Hi David,
> What is the "beat" as defined for the beam?
Perhaps I should use the word "moment"… Example: In 3/4, one can set the
autobeamer to beam sub-quarter notes as 3, or 2+1, or 1+2, or 1+1+1 (or even
other options, I suppose). The moment an auto-beam encompasses (as a result of
the
Hi David,
> So if we have
> { \time 4/4 c'8 r4 c'8 8 8 8 8 }
> will there be a beam across r4?
Would there be a beam across
c'8 c'4 c'8
? If yes, then yes; if no, then no.
> What if we have r8 r8 instead?
Would there be a beam across
c'8 c'8 c'8 c'8
? If yes, then yes; if no, then no.
Kieren MacMillan writes:
> p.s.
>
> Before you ask: Yes, it would be great to include the option/parameter
> to extend across *all* rests that fall within the "beat" as defined
> for the beam,
What is the "beat" as defined for the beam?
> even if they fall outside the compass of the two
Kieren MacMillan writes:
> Hi David,
>
>> So if you have a bar containing only rests, the autobeamer places
> beams over them?
>
> LOL
> Sure, we can play this game…
It's not a game to work out specs. It's not optional. Computers don't
do handwaving.
> An automatic beam must start from a
Hi there,
> I don't think it's quite that simple as rests that begin or end beam groups
> wouldn't have beams over them, only ones in the middle.
Not strictly true: in modern scores, the beam could easily extend over those
rests (especially if stemlets are used). We just need to give the user
p.s.
Before you ask: Yes, it would be great to include the option/parameter to
extend across *all* rests that fall within the "beat" as defined for the beam,
even if they fall outside the compass of the two "boundary notes" for the auto
beam.
Kieren.
Kieren
On 2019-04-02 11:05 AM, Kieren MacMillan wrote:
The auto-beamer should beam according to the settings that it would apply if
there were no rests.
I don't think it's quite that simple as rests that begin or end beam
groups wouldn't have beams over them, only ones in the middle.
It might be
Hi David,
> So if you have a bar containing only rests, the autobeamer places beams over
> them?
LOL
Sure, we can play this game…
An automatic beam must start from a note and end at a second note.
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website:
Kieren MacMillan writes:
> Hi David,
>
>> It is not clear what that option would be supposed to do when.
>
> The auto-beamer should beam according to the settings that it would
> apply if there were no rests.
>
> Seems perfectly clear to me… but maybe that’s because I want the feature. =)
So
Hi David,
> It is not clear what that option would be supposed to do when.
The auto-beamer should beam according to the settings that it would apply if
there were no rests.
Seems perfectly clear to me… but maybe that’s because I want the feature. =)
Cheers,
Kieren.
Kieren MacMillan writes:
> Hey there,
>
>> But in my case, it is a typical engraving rule and I was wondering if I
>> wasn't missing a little option like
>> \set BeamOverRest = ##t
>
> I would love that option. Maybe submit it as a formal request?
Too much handwaving. It is not clear what
Hey there,
> But in my case, it is a typical engraving rule and I was wondering if I
> wasn't missing a little option like
> \set BeamOverRest = ##t
I would love that option. Maybe submit it as a formal request?
Cheers,
Kieren.
Kieren MacMillan, composer
‣
Brett,
Much thanks, that does indeed fix the issue.
Regards.
Guy Stalnaker
jimmyg...@gmail.com
On Mon, Apr 1, 2019 at 8:15 PM Brett Duncan wrote:
> I think you want
>
> \override MultiMeasureRest #'expand-limit = #7 (or whatever value you
> decide - the default is 10).
>
> Brett
>
> On
On Tue, Apr 2, 2019 at 3:06 AM Malte Meyn wrote:
>
>
> Am 01.04.19 um 21:12 schrieb Urs Liska:
> > I fully agree with all of that, but I think what Johan wanted to say is
> that we should *first* work towards DMuFL compliance before spending
> manpower on Emmentaler extensions.
> > Which I think
Aaron Hill writes:
> On 2019-04-02 4:26 am, David Kastrup wrote:
>> Aaron Hill writes:
>>> Where have I gone wrong in my thinking?
>>
>> _Either_ the Event_chord_iterator _or_ the Rhythmic_music_iterator are
>> doing the broadcasting of note events, depending on whether the notes
>> are within
On 2019-04-02 4:26 am, David Kastrup wrote:
Aaron Hill writes:
Where have I gone wrong in my thinking?
_Either_ the Event_chord_iterator _or_ the Rhythmic_music_iterator are
doing the broadcasting of note events, depending on whether the notes
are within a chord or not. _Only_ the
Aaron Hill writes:
> NOTE: I know that \bendAfter currently does not support all of the
> usages below; this all is coming from my investigation into how to
> enable such support. My plan is to create a patched version of the
> engraver in Scheme as a proof-of-concept; and if it works, I can
NOTE: I know that \bendAfter currently does not support all of the
usages below; this all is coming from my investigation into how to
enable such support. My plan is to create a patched version of the
engraver in Scheme as a proof-of-concept; and if it works, I can port
the results back to
Am 02.04.19 um 09:48 schrieb Malte Meyn:
Am 02.04.19 um 09:34 schrieb Urs Liska:
But that probably should wait until the release of 2.20.0 and
2.21.0, shouldn’t it?
I don't think so. Of course such a fundamental change doesn't belong
in 2.20, but adding stuff to the development branch
Am 02.04.19 um 09:34 schrieb Urs Liska:
But that probably should wait until the release of 2.20.0 and 2.21.0,
shouldn’t it?
I don't think so. Of course such a fundamental change doesn't belong in
2.20, but adding stuff to the development branch doesn't seem
problematic to me. If it should
Am 02.04.19 um 09:05 schrieb Malte Meyn:
Am 01.04.19 um 21:12 schrieb Urs Liska:
I fully agree with all of that, but I think what Johan wanted to say
is that we should *first* work towards DMuFL compliance before
spending manpower on Emmentaler extensions.
Which I think is true and not. If
thedoctor818 wrote
> \paper {
> left-margin = 15
> top-system-spacing #'basic-distance = #10
> score-system-spacing #'basic-distance = #10
> system-system-spacing #'basic-distance = #10
> last-bottom-spacing #'basic-distance = #10
> }
>
> [...]
>
> \score {
> [...]
> \new
Am 01.04.19 um 21:12 schrieb Urs Liska:
I fully agree with all of that, but I think what Johan wanted to say is that we
should *first* work towards DMuFL compliance before spending manpower on
Emmentaler extensions.
Which I think is true and not. If there is someone willing to spend efforts
Thank you Aaron for you reply!
In the meantime I'm trying the other approch you proposed: %% Glissando in
second voice.
Ciao, g.
On Tue, 2 Apr 2019 at 08:44, Aaron Hill wrote:
> On 2019-04-01 11:32 pm, Gianmaria Lari wrote:
> > ... and it is possible to apply bendafter to a chord instead of
On 2019-04-01 11:32 pm, Gianmaria Lari wrote:
... and it is possible to apply bendafter to a chord instead of a
single
note? I tried
\bendAfter #-6 ..
but it doesn't work.
Oh, dear. Seems to be an unsupported feature to apply falls/doits to
notes within a chord or to the chord
On 2019-04-01 11:19 pm, Gianmaria Lari wrote:
AAron, is there any way to move the bend code outside the score part?
That's almost always possible. Here it is wrapped up in a custom event
function:
\version "2.19.82"
zigzagBendAfter = #(define-event-function (steps) (number?)
... and it is possible to apply bendafter to a chord instead of a single
note? I tried
\bendAfter #-6 ..
but it doesn't work.
g.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
AAron, is there any way to move the bend code outside the score part?
Thank you, g.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Tue, 2 Apr 2019 at 03:21, Aaron Hill wrote:
> On 2019-04-01 5:15 pm, Colin Campbell wrote:
> > On 2019-04-01 5:28 p.m., Gianmaria Lari wrote:
> >> Attached to this email a screenshot of the result of this code
> >>
> >> \version "2.21.0"
> >> \fixed c'' {
> >> \override
36 matches
Mail list logo
