p.s. Notice how telling Lilypond to consider the feathered measure separately
from the rest, it does something different spacing-wise (which may or may not
be what you want):
\version "2.19.82"
\layout {
system-count = 4
}
\new Staff
\relative c' {
\newSpacingSection
\override Beam.grow-di
Hi Reggie,
> Show me how as the work continues "naturally"" it would
> space out. It doesn't it's always clumpy.
[…]
> It looks terrible even worse with testing breaks.
Lilypond is satisfying the requirements you have provided, either via explicit
breaks (see your examples) or system-count (see
Kieren MacMillan wrote
> Hi Reggie,
>
>> WHy does measure now have no spacing out duration even though I use { }
>> around the whole feather area? See it works then it doesn't work.
>
> No… it works and then it still works. ;)
>
> \new Staff
> \relative c' {
> \override Beam.grow-direction = #
Kieren MacMillan wrote
> Hi Reggie,
>
>> WHy does measure now have no spacing out duration even though I use { }
>> around the whole feather area? See it works then it doesn't work.
>
> No… it works and then it still works. ;)
>
> \new Staff
> \relative c' {
> \override Beam.grow-direction = #
Hi Reggie,
> WHy does measure now have no spacing out duration even though I use { }
> around the whole feather area? See it works then it doesn't work.
No… it works and then it still works. ;)
\new Staff
\relative c' {
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 23:18 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>>
>> Is there a way in LilyPond to simply add a beam line without changing the
>> time or anything else behind the elements? I mean, visually say I had a
>> c16
>> feather beam measure that had all
Am Fr., 21. Dez. 2018 um 23:18 Uhr schrieb Reggie :
>
> Is there a way in LilyPond to simply add a beam line without changing the
> time or anything else behind the elements? I mean, visually say I had a c16
> feather beam measure that had all the math and checks OK. But I wanted 3
> lines for my
Thomas Morley-2 wrote
>> Do you think it's even possible to write a function to automatically
>> space
>> according to the feather beam length and duration?
>
> As said, likely it's possible.
> Speaking only for myself, I doubt I've the time to try.
>
> Cheers,
> Harm
>
> _
Am Fr., 21. Dez. 2018 um 19:26 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > \featherDurations changes durations, nothing more!! It does not change
> > spacing on it's own.
> > The changed spacing is more a side-effect. Doing note-spacing is a
> > very involved process, durations are only one
On 12/21/18, 11:25 AM, "Reggie" wrote:
I would hope beg love for someone to write a function that simply put spaced
out notes according to the speed of the feathers. Finale Sibelius do this
for years now. Hack yes but doable every time it works. What's LilyPond work
around
Thomas Morley-2 wrote
> \featherDurations changes durations, nothing more!! It does not change
> spacing on it's own.
> The changed spacing is more a side-effect. Doing note-spacing is a
> very involved process, durations are only one element of the
> calculation.
>
> So I ensure you \featherDuara
Am Fr., 21. Dez. 2018 um 17:51 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Meanwhile I think you didn't understand that feathered beams, done with
> > \override Beam.grow-direction = #RIGHT
> > and
> > \featherDurations
> > are _independant_ from each other. See:
> >
> > \version "2.19.82"
>
Thomas Morley-2 wrote
> Meanwhile I think you didn't understand that feathered beams, done with
> \override Beam.grow-direction = #RIGHT
> and
> \featherDurations
> are _independant_ from each other. See:
>
> \version "2.19.82"
>
> {
> r2..
> \featherDurations #(ly:make-moment 1 2)
> { c''3
Hi Reggie,
It's impossible to have feather
beams cross barlines and look correect why is this?
I’m confused… How, exactly, does this not output the kind of thing you want?
%%% SNIPPET BEGINS
\version "2.19.80"
{
r2..
\override Beam.grow-direction = #RIGHT
\featherDurations #(ly:mak
Am Fr., 21. Dez. 2018 um 17:18 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
>
> > reegistoop@
>
> > >:
> >
> >> It's impossible to have feather
> >> beams cross barlines and look correect why is this?
> >
> > ??
> >
> > What's wrong with:
>
Kieren MacMillan wrote
> Hi Reggie,
>
>> the notes are not spaced out according to the feathered tempo. […]
>> They should be spaced out to show slow fast change
>
> Why is that necessary? I mean, you obviously *want* that… but I’m not sure
> they "should" be spaced out like that, necessarily.
>
Kieren MacMillan wrote
> Hi Reggie,
>
>> the notes are not spaced out according to the feathered tempo. […]
>> They should be spaced out to show slow fast change
>
> Why is that necessary? I mean, you obviously *want* that… but I’m not sure
> they "should" be spaced out like that, necessarily.
>
Hi Reggie,
> the notes are not spaced out according to the feathered tempo. […]
> They should be spaced out to show slow fast change
Why is that necessary? I mean, you obviously *want* that… but I’m not sure they
"should" be spaced out like that, necessarily.
> How do you do that?
There are do
Hi Reggie,
> Thomas Morley wrote
>> What's wrong with:
> as I earlier mentioned over and over, the bar lines fail.
> Your example does not work unless you ignore bar checks.
Harm’s example works fine for me; no bar line "failure".
What’s the log output when you try it?
Cheers,
Kieren.
_
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Thomas Morley-2 wrote
> Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> It's impossible to have feather
>> beams cross barlines and look correect why is this?
>
> ??
>
> What's wrong with:
>
> \version "2.19.82"
>
> {
> r2..
> \override Beam.grow-direction = #
Am Fr., 21. Dez. 2018 um 15:21 Uhr schrieb Reggie :
> It's impossible to have feather
> beams cross barlines and look correect why is this?
??
What's wrong with:
\version "2.19.82"
{
r2..
\override Beam.grow-direction = #RIGHT
c'32[ \repeat unfold 6 c'' c'] r2..
}
Cheers,
Harm
__
t;> \featherDurations #(ly:make-moment 1 2)
>> { des''16 -. [\p\< es''16 -. e''16 -. f''16 -. ges''16 -. as''16 -.
>> c'''16
>> -> -. \f] }
>> }
>> lower = { \global
>>\override
l
>\override Beam #'grow-direction = #RIGHT
>
> \featherDurations #(ly:make-moment 1 2)
> { r16 r r r r r16 -> -. \sfz }
>
> }
> \score {
> << \new Staff \upper
> \new Staff \lower >>
> }
>
> --
> Phil Holmes
>
>
>
ke-moment 1 2)
{ r16 r r r r r16 -> -. \sfz }
}
\score {
<< \new Staff \upper
\new Staff \lower >>
}
--
Phil Holmes
- Original Message -----
From: Stefan Thomas
To: lilypond-user
Sent: Thursday, September 30, 2010 9:42 AM
Subject: synchronization of feathered beams
Dear community,
I have a problem with the synchronisation in the below quoted snippet.
I expect to have the notes on the end of the bar on the same vertical
height.
How can I achieve it?
Thanks for help,
Stefan
\version "2.12.3"
global = { \time 7/8 }
upper = { \global
\featherDurations #(ly:ma
27 matches
Mail list logo
