Trevor Daniels wrote
> "Reggie" <
> reegistoop@
> > wrote 21/12/2018 19:10:12
>>\relative c'
>>{
>> \override Beam.grow-direction = #LEFT
>> \featherDurations #(ly:make-moment 2/1)
>> c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
>>}
>>
>>My CODE has no errors. And yet the 2/1 does NOT sp
Reggie wrote
> Aaron Hill wrote
>> Given the current implementation, it would be necessary to use an
>> approximate rational like 50/63 as the moment in order to get 'f' to be
>> half of 'c'. Why that number? Well, it's a close approximation to the
>> irrational cube root of one half. We dete
On 12/21/18, 12:10 PM, "Reggie" wrote:
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out
"Reggie" wrote 21/12/2018 19:10:12
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out any notes at ALL
it's just normal beamed notes wit
On 2018-12-21 11:10 am, Reggie wrote:
\relative c'
{
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
c32[ d e f g f e f d f g f d e d f] c4~c | c1 |
}
My CODE has no errors. And yet the 2/1 does NOT space out any notes at
ALL
it's just normal beamed notes wi
Am Fr., 21. Dez. 2018 um 20:10 Uhr schrieb Reggie :
>
> Aaron Hill wrote
> > Given the current implementation, it would be necessary to use an
> > approximate rational like 50/63 as the moment in order to get 'f' to be
> > half of 'c'. Why that number? Well, it's a close approximation to the
> >
Aaron Hill wrote
> Given the current implementation, it would be necessary to use an
> approximate rational like 50/63 as the moment in order to get 'f' to be
> half of 'c'. Why that number? Well, it's a close approximation to the
> irrational cube root of one half. We determine this exact va
Reggie,
On 12/21/18, 11:30 AM, "Reggie" wrote:
The fractions do NOT always accelerando, while fractions greater than one
generate a
ritardando as intended. That is why I began this mess in the first place :))
Please show us a specific example that does not work the way you wa
On 12/21/2018 11:54 AM, Aaron Hill wrote:
On 2018-12-21 5:14 am, Reggie wrote:
Hello. I see what you are saying thank you. I just feel that feather
beaming
is so confusing it all depends on so much, it's not simple like "select
these notes and change beam style to feather left or right". It's f
Aaron Hill wrote
> This means your score really should be bar check clean *before* you ever
> use \featherDurations.
>
> At the end of the day, there is no real need to use any math for the
> \featherDurations moment. Any positive rational less than one will
> produce an accelerando, while fr
Aaron Hill wrote
> At the end of the day, there is no real need to use any math for the
> \featherDurations moment. Any positive rational less than one will
> produce an accelerando, while fractions greater than one generate a
> ritardando. The best thing to do is to listen to the MIDI output
On 2018-12-21 5:14 am, Reggie wrote:
Hello. I see what you are saying thank you. I just feel that feather
beaming
is so confusing it all depends on so much, it's not simple like "select
these notes and change beam style to feather left or right". It's
first,
math. Then, trial error. Then, settl
Michael Gerdau wrote
> First thing you have to answer for yourself is:
> What do I need feathered beams for?
> The answer should be something along the line "to visually notate an
> accellerando or rallentando".
> Assuming that's your answer then you should have a rough idea as to how
> strongly yo
> How does one calculate the extra numbers needing to be for the spacing OUT
> of notes as the feather speed up slow down. They always look spaced tight
> together as real notes just beamed differently. When you engrave a feather
> beam measure should youy first figure out how many notes you want
Michael Gerdau wrote
>> I understand your math now but I do not understand how you began to know
>> how
>> to use math from the beginning. How did you determine which note NEEDED
>> the
>> math to it? Is there a sort of study sheet where we can look to find out
>> which notes need math for each tim
> I understand your math now but I do not understand how you began to know how
> to use math from the beginning. How did you determine which note NEEDED the
> math to it? Is there a sort of study sheet where we can look to find out
> which notes need math for each time we use?
I'm not sure what yo
Thomas Morley-2 wrote
> {
> \time 1/4
> b16*4 | % i.e. 1/16 lasts 1/4
> b16*4/3 b b | % b16*4 is 1/4, so b16*4/3 is a third of 1/4
> %% similar for 1/32,
> b32*2 %{is 1/16%} *4 |
> b32*2*4/3 b b |
> %% etc
> }
>
> HTH,
> Harm
>
> ___
> l
Am Mo., 17. Dez. 2018 um 22:13 Uhr schrieb Reggie :
>
> Thomas Morley-2 wrote
> > Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie <
> > Scale durations:
> >
> > \relative d {
> > \clef bass
> > \override Beam.grow-direction = #RIGHT
> > \featherDurations #(ly:make-moment 3/4)
> > c16*4
Thomas Morley-2 wrote
> Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie <
> reegistoop@
> >:
>
>> How do you change the amount of "beams" you feather when
>> the amount of notes is example 3. You need to just forget it? 3 beams
>> are
>> not possible?
>>
>> \relative d {
>> \clef bass
>>
Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie :
> How do you change the amount of "beams" you feather when
> the amount of notes is example 3. You need to just forget it? 3 beams are
> not possible?
>
> \relative d {
> \clef bass
> \time 4/4
> d2 e4
> \override Beam.grow-direction = #
Vaughan McAlley wrote
> On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh <
> n.andrew.walsh@
> >
> wrote:
>
>> Hi List,
>>
>> I'm trying to use the \featherDurations command on a brief passage:
>>
>> \relative c' {
>> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
>> \override Beam
Vaughan McAlley wrote
> On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh <
> n.andrew.walsh@
> >
> wrote:
>
>> Hi List,
>>
>> I'm trying to use the \featherDurations command on a brief passage:
>>
>> \relative c' {
>> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
>> \override Beam
Hi Reggie,
well, my "solution" was that the client changed his mind and didn't want a
ritardando there, so I did away with them.
But no, I've never found a good way to calculate feathered beams (nor how
to space them properly to match their changing duration values). This seems
like something Lil
On Mon, 17 Dec 2018 at 16:07, Vaughan McAlley
wrote:
> On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh
> wrote:
>
>> Hi List,
>>
>> I'm trying to use the \featherDurations command on a brief passage:
>>
>> \relative c' {
>> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
>> \overri
On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh
wrote:
> Hi List,
>
> I'm trying to use the \featherDurations command on a brief passage:
>
> \relative c' {
> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
> \override Beam.grow-direction = #LEFT
> \featherDurations #(ly:make-mome
N. Andrew Walsh wrote
> Hi List,
>
> I'm trying to use the \featherDurations command on a brief passage:
>
> \relative c' {
> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
> \override Beam.grow-direction = #LEFT
> \featherDurations #(ly:make-moment 2/1)
> { a,32[\( b cis dis
Hi List,
I'm trying to use the \featherDurations command on a brief passage:
\relative c' {
a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
\override Beam.grow-direction = #LEFT
\featherDurations #(ly:make-moment 2/1)
{ a,32[\( b cis dis eis]\)\fermata }
\override Beam.grow-di
27 matches
Mail list logo
