When I feather these beams, the third beam is simply absent. I suppose this is
a bug (or an undocumented "limitation"?), but is there a practical workaround?
I guess I also need to make the beam thickness less so that the structure
becomes more visible, though I suspect that will be less of a
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
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
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
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
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 o
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..
> \fea
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
our example
> does not work unless you ignore bar checks. Why needing to be this way is
> silly to me :)
Well, repeating the same over and over again, although several people
declared not to know exactly what you're, after is not likely
increasing the chance to be understood.
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.
>
Lily scores but never saw a clear answer how to
always get this behavior?
https://www.scoringnotes.com/tutorials/feathered-beams-that-look-and-play-back-correctly-in-sibelius/
Maybe someone can show clearly how Lily handles this correct behavior and
not just default spacing.
--
Sent from: http://lil
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
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
kontrapunktstefan wrote
> Dear Phil,
> thanks for Your explanations.
> I do have now another problem.
> What can I do, when I want to have feathered beams across barlines, like
> e.g.:
>
> \version "2.12.3"
> upper = {
> \override Beam #'grow-direction = #RI
This works great. Thank you.
Mason
On 6 May 2017 at 03:42, Thomas Morley <thomasmorle...@gmail.com> wrote:
> 2017-05-06 4:26 GMT+02:00 Mason Hock <masonh...@gmail.com>:
> > I would like to increase the vertical space between feathered beams. This
> > achieves approxi
2017-05-06 4:26 GMT+02:00 Mason Hock <masonh...@gmail.com>:
> I would like to increase the vertical space between feathered beams. This
> achieves approximately what I want for left-feathered beaming:
>
> % decelerating
> \override Stem.beaming = #(cons (list ) (list 0 3)
I would like to increase the vertical space between feathered beams. This
achieves approximately what I want for left-feathered beaming:
% decelerating
\override Stem.beaming = #(cons (list ) (list 0 3))
\once \override Beam.grow-direction = #LEFT
c16
\override Stem.beaming = #(cons
Hi Federico and Davide,
In English we use the Italian work portamento when singers or players
want to scoop between notes.
Aren't doit and fall forms of portamento without a define
start/end note?
Doit (pron do-it) is a portamento up to the notated pitch, Fall is
a portamento down from the
2013/4/11 Ian Hulin i...@hulin.org.uk:
In English we use the Italian work portamento when singers or players
want to scoop between notes.
We use that word in Italian, too, with the same meaning.
Aren't doit and fall forms of portamento without a define
start/end note?
Yes, they can be seen
Davide Liessi dal...@gmail.com writes:
direct
I can't understand this glossary entry, since there isn't enough context.
I don't think it is specifically a musical term, and I couldn't find
occurrences of direct in NR with a different meaning from the usual,
literal, common one.
Why is
Ciao Federico,
as in my previous email,
Unreferenced statements are my personal opinions.
Sources:
[G] = Enciclopedia della Musica, Garzanti, Milano, 1996
[C] = Sandro Carnelos, Gli organi della diocesi di Vittorio Veneto,
Vittorio Veneto, 2000 (a book that lists characteristics of each of
2013/4/10 Davide Liessi dal...@gmail.com
direct
I can't understand this glossary entry, since there isn't enough context.
I don't think it is specifically a musical term, and I couldn't find
occurrences of direct in NR with a different meaning from the usual,
literal, common one.
Why is
2013/4/8 Davide Liessi dal...@gmail.com
Sources:
[G] = Enciclopedia della Musica, Garzanti, Milano, 1996
[Z] = Daniele Zanettovich, Elementi fondamentali di teoria e di
ortografia musicale, Pizzicato edizioni musicali, Udine, 1988
Unreferenced statements are my personal opinions.
Ciao
2013/4/9 Federico Bruni fedel...@gmail.com
Common Practice Period
well, this one has been translated before:
http://lilypond.org/doc/v2.17/Documentation/notation/writing-pitches#note-names-in-other-languages
as Periodo di pratica comune
does it refer to the western classic music?
better
2013/4/7 Federico Bruni fedel...@gmail.com:
A request for italian users who have a good knowledge of music notation
terminology.
Sources:
[G] = Enciclopedia della Musica, Garzanti, Milano, 1996
[Z] = Daniele Zanettovich, Elementi fondamentali di teoria e di
ortografia musicale, Pizzicato
2013/4/8 Davide Liessi dal...@gmail.com
http://lilypond.org/doc/v2.17/Documentation/music-glossary/feathered-beam
[Z] calls them bandierine convergenti (if tempo is decreasing) or
bandierine divergenti (if tempo is increasing) (in [Z] beams are
called bandierine, uncini or codette).
A request for italian users who have a good knowledge of music notation
terminology.
How would you translate feathered beam?
http://www.lilypond.org/doc/v2.17/Documentation/notation/beams#feathered-beams
I couldn't find any information on Internet nor in an italian book Manuale
di scrittura
.
\version 2.14.2
\include english.ly
% \override Beam #'grow-direction = #LEFT
% % revert to non-feathered beams
% \override Beam #'grow-direction = #'()
\relative c'' {
\key d \major
\numericTimeSignature
r16
\override Beam #'grow-direction = #LEFT
\scaleDurations #'(2 . 1) { e32
to specify the number of beams you want at the end.
\version 2.14.2
\include english.ly
% \override Beam #'grow-direction = #LEFT
% % revert to non-feathered beams
% \override Beam #'grow-direction = #'()
\relative c'' {
\key d \major
\numericTimeSignature
r16
\override
At Sun, 11 Mar 2012 18:03:42 +0100,
Thomas Morley wrote:
Hi,
last year I created a work-around to make feathered beams more variable.
Thanks again to David Nalesnik for his great help.
-
http://old.nabble.com/Making-feathered-beams-more-variable-td32705102.html#a32790344
Now that I've
2012/2/16 Joey Di Nardo username652...@gmail.com:
One more thing is that because they increase in speed, I don't want them
labeled as a tuplet, so I suppose I'll have to figure out how to make that
number invisible in that instance.
\once \override TupletNumber #'transparent = ##t
Cheers,
uncertain as to how to manipulate the make-moment in order to
not return an error. I'd theoretically like to make the feathered beams speed
up, all in the place of a quarter note.
I am currently getting a barcheck error no matter what values I place in
make-moment.
thanks,
Joey
#(ly:make-moment ? ?)
{ wbh16[ wbh wbh r16 wbh] }
r2.
|%27
And I'm a bit uncertain as to how to manipulate the make-moment in order to
not return an error. I'd theoretically like to make the feathered beams
speed up, all in the place of a quarter note.
I am currently getting a barcheck
[ wbh wbh r16 wbh] } }
r2. |
}
\score {
\new DrumStaff {
\percOne
}
}
\version 2.15.27
HTH,
Harm
P.S. Also you might be interested in this thread:
http://old.nabble.com/Making-feathered-beams-more-variable-tt32705102.html#a32790344
with an extended
Hi again,
[ ... ]
P.S. Also you might be interested in this thread:
http://old.nabble.com/Making-feathered-beams-more-variable-tt32705102.html#a32790344
with an extended function to print feathered beams and an improved
feather-duration-function by David Nalesnik.
I just noticed that I
{
\new DrumStaff {
\percOne
}
}
\version 2.15.27
HTH,
Harm
P.S. Also you might be interested in this thread:
http://old.nabble.com/Making-feathered-beams-more-variable-tt32705102.html#a32790344
with an extended function to print feathered beams
to not
return an error. I'd theoretically like to make the feathered beams speed up,
all in the place of a quarter note.
I am currently getting a barcheck error no matter what values I place in
make-moment.
thanks,
Joey
___
lilypond-user mailing list
lilypond
Hi David,
2011/11/4 Thomas Morley thomasmorle...@googlemail.com
(...)
Also, I deleted my attempt to automatize stem-shortning (for now stems are
to be shortened manually. This works! :)). Perhaps I start a new try with
2.15.13 and the 'length-property next weekend.
(...)
I think the
Hi Harm,
On Tue, Nov 1, 2011 at 2:40 PM, harm6 thomasmorle...@googlemail.com wrote:
I tried to make an automated definition (first attachment) and to integrate
it in the grow-beam-var-definition (second attachment). This feature will
only work with kneed beams and if the directions of the
(lambda (n)
(markup #:beam (- beam-length-x x-L)
(slope-part-beam-R n)
beam-thickness)))
(markup-R (lambda (n) (markup (part-beam-R n
;; parts of feathered beams
(beam-pieces
(map
.
Thanks,
Harm
http://old.nabble.com/file/p32761182/change-stem-beam01.ly
change-stem-beam01.ly
http://old.nabble.com/file/p32761182/kneed-beam-stem-test.ly
kneed-beam-stem-test.ly
--
View this message in context:
http://old.nabble.com/Making-feathered-beams-more-variable-tp32705102p32761182.html
Hi Harm,
On Sun, Oct 30, 2011 at 7:08 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
\once \override Stem #'stem-end-position = #-8
Works fine with 2.14.2 and \change Staff.
But there is no effect in the following example.
\version 2.14.2
{ a'8 [
\once \override Score.Stem
Hi David,
2011/10/28 Thomas Morley thomasmorle...@googlemail.com
Hi David,
2011/10/28 David Nalesnik david.nales...@gmail.com
Hi Harm,
(...)
I tried various overrides to adjust the length of the final stem only,
and the solution I got to work is this:
xy = \once\override Stem
Hi Harm,
I added (if (ly:stencil? (ly:stem::print grob)) ... to the function (and
some construction-helpers, maybe deleted). Now it works with \change Staff,
too. 2.15.13 or higher is still needed.
All you need here is a call to ly:stem::print first; there's no need to
integrate it into the
Hi David,
2011/10/30 David Nalesnik david.nales...@gmail.com
Hi Harm,
I added (if (ly:stencil? (ly:stem::print grob)) ... to the function (and
some construction-helpers, maybe deleted). Now it works with \change Staff,
too. 2.15.13 or higher is still needed.
All you need here is a call
use a high turnaround-value with the first,
the next settings are changed. I can't explain or fix this behaviour.
Many thanks,
Harm
P.S.: In harm-feathered-beams-align-to-stems-rev_04.ly I forgot to apply
dir-peak to mark-a. I integrated the correction into the attached file.
\version 2.14.2
this would be
useful with feathered values. (Years ago, I created a proportional
notation piece with Score this way--too long ago to remember if there were
any drawbacks to this method other than the manual calculation involved!)
P.S.: In harm-feathered-beams-align-to-stems-rev_04.ly I forgot to apply
Hi Harm,
On Fri, Oct 28, 2011 at 8:18 AM, Thomas Morley
thomasmorle...@googlemail.com wrote:
Hi David,
2011/10/28 David Nalesnik david.nales...@gmail.com
[ . . . ]
Maybe you could think of some artful way to modify the function in
music-functions-init.ly to incorporate the
Hi again,
On Fri, Oct 28, 2011 at 4:31 PM, David Nalesnik david.nales...@gmail.comwrote:
I worked on this a bit, and I came up with something which will handle the
accel./rit. pattern which you've been using with your feathered beam
function. It works just like \featherDurations, except you
!
-David
harm-feathered-beams-align-to-stems.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
)
{a a a
a a a a
a a a a
a a a a
a a a a
a a a} a]
a2
}
Any idea?
Many thanks,
Harm
--
View this message in context:
http://old.nabble.com/Making-feathered-beams-more-variable-tp32705102p32718725.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com
to use
128th notes.)
Many thanks, I knew it could be done.
The examples that Gould shows (pg. 158) have the peak of the feathered
beams aligned with a stem. I think this would be a useful variation of the
function. It shouldn't be hard to automate: (ly:grob-object grob 'stems)
will get
Hi,
the attached file is a first attempt to make feathered beams more variable.
p.e.:
http://old.nabble.com/file/p32705102/beam15.png
Thanks to David Nalesnik, who answered several questions about the details
of beams.
Some problems persist:
The function is limited up to 64th notes. (I'm
Hi Harm,
On Sun, Oct 23, 2011 at 8:21 AM, harm6 thomasmorle...@googlemail.comwrote:
the attached file is a first attempt to make feathered beams more variable.
p.e.:
http://old.nabble.com/file/p32705102/beam15.png
This is really cool! What a great function!!
Some problems persist
Dear Phil,
thanks for Your explanations.
I do have now another problem.
What can I do, when I want to have feathered beams across barlines, like
e.g.:
\version 2.12.3
upper = {
\override Beam #'grow-direction = #RIGHT
\featherDurations #(ly:make-moment 1 2)
{ \time 7/16 des''16 -. [\p\ es''16
}
--
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
Qian Li qian...@gmail.com writes:
Why does lilypond choke on feathered 8:10 notes but handles 4:6 no problem?
The first example works (even the slur works), but the second doesn't.
Neither example works since it does not have lilypond syntax. Apart
from that, you set the featherDurations to
Why does lilypond choke on feathered 8:10 notes but handles 4:6 no problem?
The first example works (even the slur works), but the second doesn't.
Thanks.
Qian
\times 4/6{
\featherDurations #(ly:make-moment 6 8 ) {
\once \override Beam #'grow-direction = #RIGHT
bf16 ( ef g bf' g ef
}
}
cs,2)
There is one importatnt caveat with the feathering functions: the
numbers in the ratio (here: 2/1) have to be small otherwise our
Rational type overflows.
2007/10/23, Graham Percival [EMAIL PROTECTED]:
I can't speak to the specifics of feathered beams, but there's two
general warnings
I'm attempting to improve the very brief description
of feathered beams in the GDP Notation Reference.
Could those of you more knowledgeable than I am please
check the following draft and either correct or confirm
it. Thanks.
Trevor D
Feathered beams are used to indicate that a small group
I can't speak to the specifics of feathered beams, but there's two
general warnings:
- explanations about what the notation means should go in the glossary.
I might keep the first sentence in your explanation, but move other
parts to the glossary.
- avoid talking through the lilypond code
Michael Sperone wrote:
Thank you for your help, I thought I might need to change the settings
back.
I did get a chance to look through the chapters you mentioned, but
couldn't really find anything that would change the settings back for
the feathered beams. I'm not sure exactly what
Hi,
I have started using lilypond successfully and like it a lot, but I have run into one problem which I cannot figure out for the life of me. I entered feathered beams for one beat, and now all the music I enter on that staff from that point on is feathered.
I am using version 2.10.25 on Mac
Michael Sperone wrote:
I can't tell what I am doing wrong, as I understood it, once I enter
that last } then everything should good back to normal, correct? or
is there something else I need to do?
No, there's no scoping rule like that. :) You need to revert the
setting; see chapters 3-5 or
Can anybody make a definitive implementation of that or should I add this to
my list of items to sponsor (which seems to grove alarmingly..)?
Best Regards,
Mehmet Okonsar, pianist-composer
www.okonsar.com
___
lilypond-user mailing list
On Thursday 15 September 2005 18.37, Mehmet Okonsar wrote:
Can anybody make a definitive implementation of that or should I add this
to my list of items to sponsor (which seems to grove alarmingly..)?
that feature is listed at
http://lilypond-design.com/sponsor/open-features.html
--
Erik
On Mon, 2004-06-14 at 17:40, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
On Mon, 2004-06-14 at 11:16, Bryan, Chris wrote:
Is it possible to do feathered beams in LY? If so, how?
there is no native mechanism for this. i hacked it a while ago by making
two simultaneous beamed
Is it possible to do feathered beams in LY? If so, how?
Thanks,
-Chris
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
On Mon, 2004-06-14 at 11:16, Bryan, Chris wrote:
Is it possible to do feathered beams in LY? If so, how?
there is no native mechanism for this. i hacked it a while ago by making
two simultaneous beamed note-groups, with the beams tilted opposite
directions in each, and tweaked so the beam
.
By the way, in my opinion, the coolest LY feature is the automatic midi
pitch bends when using microtonal accidentals. It rocks!!!
a happy composer,
-Chris Bryan
On Jun 14, 2004, at 12:13 PM, Peter Lutek wrote:
On Mon, 2004-06-14 at 11:16, Bryan, Chris wrote:
Is it possible to do feathered beams
[EMAIL PROTECTED] writes:
I don't know how hard it would be to implement that, but I do know a
bit of c++. If the developers need any grunt-work accomplished, let me
know.
If you're into serious grunting: the code is in lily/beam.cc,
Beam::print(), and it should not be so difficult to add
[EMAIL PROTECTED] writes:
On Mon, 2004-06-14 at 11:16, Bryan, Chris wrote:
Is it possible to do feathered beams in LY? If so, how?
there is no native mechanism for this. i hacked it a while ago by making
two simultaneous beamed note-groups, with the beams tilted opposite
directions
84 matches
Mail list logo
