[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Auto-beaming infrastructure redo
From: |
Carl Sorensen |
Subject: |
Re: Auto-beaming infrastructure redo |
Date: |
Sat, 3 Jul 2010 04:37:59 -0600 |
On 7/3/10 2:14 AM, "Hans Aberg" <address@hidden> wrote:
> On 3 Jul 2010, at 01:04, Carl Sorensen wrote:
>>> If I throw in tuplets in this AST, setting them to 1:1, I get:
>>> +
>>> |
>>> (1:1, [(2, 1/8), (3, 1/8), +, (3, 1/8)])
>>> |
>>> (1:1, [(2, 1/8), ((3, 1/8), (2, 1/8)])
>>>
>>> That is, the tuplet p:q just appears as a pair (p, q) attached to the
>>> list.
>>
>> But we don't need to introduce the tuplets in the LilyPond structure,
>> because the p:q for tuplets is already handled by LilyPond, as far
>> as I can
>> tell. At least for right now, I think we can use a single
>> fundamental unit.
>
> I think you may need to have the tuplets as a part of this structure
> in order to compute the correct beaming. Then the current flexible
> approach of LilyPond where they can be broken up in pieces might be a
> complication.
Can you give me a specific example of beaming where the tuplets would be
necessary?
Thanks,
Carl
- Auto-beaming infrastructure redo, Carl Sorensen, 2010/07/02
- Re: Auto-beaming infrastructure redo, Graham Percival, 2010/07/02
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/02
- Re: Auto-beaming infrastructure redo, Carl Sorensen, 2010/07/02
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/02
- Re: Auto-beaming infrastructure redo, Carl Sorensen, 2010/07/02
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/03
- Re: Auto-beaming infrastructure redo,
Carl Sorensen <=
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/03
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/03
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/03
- Re: Auto-beaming infrastructure redo, Hans Aberg, 2010/07/03
Re: Auto-beaming infrastructure redo, Trevor Daniels, 2010/07/02