Another question -- is there any way to make the narrow end of a feathered beam
show more than one beam? That is, as far as I can see, the beams taper down to
one point (as in this code snip) but the documentation doesn't show any way to
specify the number of beams you want at the end.
\version
On 03/10/2012 09:55 PM, Patrick Karl wrote:
On Mar 10, 2012, at 1:35 PM, James wrote:
Message: 6
Date: Sat, 10 Mar 2012 19:34:40 +
From: James
To: "Peter O'Doherty"
Cc: lilypond-user@gnu.org
Subject: Re: tupletFullLength clashes with barline
Message-ID:
Content-Type: text/plain; c
On Sun, Mar 11, 2012 at 09:25:55AM +0100, Peter O'Doherty wrote:
> On 03/10/2012 09:55 PM, Patrick Karl wrote:
> >On Mar 10, 2012, at 1:35 PM, James wrote:
> >
> >>Message: 6
> >>Date: Sat, 10 Mar 2012 19:34:40 +
> >>From: James
> >>To: "Peter O'Doherty"
> >>Cc: lilypond-user@gnu.org
> >>Subje
> I'm not top posting
Nick Payne internode.on.net> writes:
>
> I would expect that all four beams should be subdivided, but only the
> second beam in the bar is being subdivided:
>
> \version "2.15.33"
>
> \relative c' {
> \set tupletSpannerDuration = #(ly:make-moment 1 4)
> \set b
2012/3/11 Janek Warchoł :
> Thanks and happy birthday to you! Frescobaldi is great!
Yeah, I'm still not entirely convinced by the KDE-less version (in a
couple months we should discuss it in the Report :-).
But: happy birthday!
Cheers,
Valentin.
___
On Sun, Mar 11, 2012 at 12:49 AM, wrote:
> By and large, the project is already providing what FreeBSD
> LilyPond users want and need: a good product, built from clean,
> open source code which is highly portable to run on a variety of
> platforms. Well done, all of you.
Hi Jim,
would you by a
Hi,
Another question concerning tuplets:
\remove "Forbid_line_break_engraver"
\override Beam #'breakable = ##t
only seem to work with a single stave.
The code below causes a warning:
warning: forced break was overridden by some other event, should you be
using bar checks?
Is there an alterna
"Nick Payne" wrote in message
news:4f5acab6.8090...@internode.on.net...
I would expect that all four beams should be subdivided, but only the
second beam in the bar is being subdivided:
\version "2.15.33"
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\set baseMoment
On 03/11/2012 11:42 AM, m...@apollinemike.com wrote:
On Mar 11, 2012, at 11:40 AM, Peter O'Doherty wrote:
Hi,
Another question concerning tuplets:
\remove "Forbid_line_break_engraver"
\override Beam #'breakable = ##t
Try adding:
\override TupletBracket #'breakable = ##t
Cheers,
MS
Sorry
Peter O'Doherty-2 wrote:
>
> Hi,
> Another question concerning tuplets:
>
> \remove "Forbid_line_break_engraver"
> \override Beam #'breakable = ##t
>
> only seem to work with a single stave.
>
no, they are alive in the \Voice environment!
hth
Eluze
--
View this message in context:
http://
On 3/11/12 12:53 AM, "James Harkins" wrote:
>At Sun, 11 Mar 2012 08:12:35 +0100,
>m...@apollinemike.com wrote:
>> The best way to achieve that with current LilyPond is Scheme engravers.
>>
>> There have been a few examples of Scheme engravers posted on this list
>>(if you search Scheme engraver
David Nalesnik gmail.com> writes:
>
>
> Hi Zsolt,
> On Sat, Mar 10, 2012 at 4:43 PM, -Eluze gmail.com> wrote:
>
>
> Zsolt Cselényi wrote:
>
>
> >
>
> > For the above the first line is broken after three "bla"-s and the hyphen
> > of the
> > last "bla" sticks out completely on the right.
>
On Sat, Mar 10, 2012 at 12:32 PM, Mark Mathias wrote:
> Why do Bar Lines disappear when reducing the Staff Line count? I've tried
> several alterations to the layout context for score, but don't get the right
> results.
>
> \version "2.15.33"
>
> \relative c'' {
>
> \override Staff . StaffSymbol #
Valentin Villenave writes:
> 2012/3/11 Janek Warchoł :
>> Thanks and happy birthday to you! Frescobaldi is great!
>
> Yeah, I'm still not entirely convinced by the KDE-less version (in a
> couple months we should discuss it in the Report :-).
Should improve portability. For me, KDE is a non-st
On Mar 11, 2012, at 9:04 AM, James Harkins wrote:
> Another question -- is there any way to make the narrow end of a feathered
> beam show more than one beam? That is, as far as I can see, the beams taper
> down to one point (as in this code snip) but the documentation doesn't show
> any way to
On Mar 11, 2012, at 5:33 AM, James Harkins wrote:
> Possibly a common question, sorry if asked and answered before, but Google
> failed me...
>
> I'm considering some aleatoric notation (so-called "box notation") for a
> piece but couldn't find info in the manuals (the "contemporary notation"
On Mar 11, 2012, at 8:53 AM, James Harkins wrote:
> At Sun, 11 Mar 2012 08:12:35 +0100,
> m...@apollinemike.com wrote:
>> The best way to achieve that with current LilyPond is Scheme engravers.
>>
>> There have been a few examples of Scheme engravers posted on this list (if
>> you search Scheme
Hello,
Von: Graham Percival
>Technical reasons? not many. Cultural reasons? they don't like
>binaries.
Actually, there are two significant technical reasons: the official FreeBSD
packages are usually
a bit behind on updates, and if you're running an older version of FreeBSD,
packages may
On Mar 11, 2012, at 11:40 AM, Peter O'Doherty wrote:
> Hi,
> Another question concerning tuplets:
>
> \remove "Forbid_line_break_engraver"
> \override Beam #'breakable = ##t
>
Try adding:
\override TupletBracket #'breakable = ##t
Cheers,
MS
___
li
At Sun, 11 Mar 2012 13:40:19 +,
Carl Sorensen wrote:
> You might offer a bounty to Mike or to David Kastrup, in which case they
> would write the custom engraver for you.
Thinking about that... either monetary or a delivery from a microbrewery? :-p
This might be viable in the meantime. I alre
Zsolt Cselényi wrote:
>
>
> Hi, of course in the _tiny_ example I used narrow paper (yes, 2.8 cm) to
> bring
> out the error. However, it also happens in case of normal paper size:
> every now
> and then when working with longer chants where syllables have to be broken
> at
> the end of line, t
Hi Eluze,
2012/3/10 -Eluze :
>
>
>
>>
The first image is a scanned example of what I've been trying to
reproduce, and the second where I've gotten so far—which is pretty
close. The only thing missing is the systemStartBracket, and I'm stuck
with no idea how to insert one in the
Hi Nick,
2012/3/9 Nick Payne :
> Thanks. I gave it a try. The one shortcoming I've found is that the ends of
> LV ties on a chord containing a second no longer align.
That's because "factor" is used in a multiplication. An easy fix would
be to change that to an addition. But now a new problem ar
On Sun, Mar 11, 2012 at 11:15:57AM +0100, Valentin Villenave wrote:
> On Sun, Mar 11, 2012 at 12:49 AM, wrote:
> > By and large, the project is already providing what FreeBSD
> > LilyPond users want and need: a good product, built from clean,
> > open source code which is highly portable to run o
Hi Zsolt,
2012/3/11 -Eluze :
>
>
> Zsolt Cselényi wrote:
>>
>>
>> Hi, of course in the _tiny_ example I used narrow paper (yes, 2.8 cm) to
>> bring
>> out the error. However, it also happens in case of normal paper size:
>> every now
>> and then when working with longer chants where syllables have
2012/3/11 John Link :
> Hi Thomas,
>
> I just joined the LilyPond list and have sent three messages but not
> received copies of them despite having specified in my settings that I am to
> receive copies of messages I send. I have received messages from you. Have
> you received any of my previous m
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'
On Sat, Mar 10, 2012 at 04:01, Thomas Morley
wrote:
>>> I'm hoping to Lilypond something not at all uncommon in pop sheet
>>> music but missing from the snippet repository and eluding my search
>>> phrases. It's basically an inline block of coda set apart from the
>>> bars preceding it, like so:
28 matches
Mail list logo
