Carl D. Sorensen schrieb:
On 4/18/09 9:22 AM, "Marc Hohl" wrote:
Carl D. Sorensen schrieb:
People who care strongly about tablature (of which I am *not* one) should be
the people who make the decision about what the default should be. In fact,
I don't think there's anybody on the
On 4/18/09 9:22 AM, "Marc Hohl" wrote:
> Carl D. Sorensen schrieb:
>> People who care strongly about tablature (of which I am *not* one) should be
>> the people who make the decision about what the default should be. In fact,
>> I don't think there's anybody on the core development team who
Ok, as Carl proposed, I put some modifications in ly/engraver-init.ly,
namely I created a \TabNumVoice , which is a copy of \TabVoice without
stems, dots, markups etc. The problem with the numbers in brackets
which are used at line breaks to indicate tied notes isn't solved yet, but
I have now at
On 4/2/09 1:14 AM, "Marc Hohl" wrote:
>>
>> Oh, absolutely. But it's not necessary to add everything all at once.
>> While we're in a development cycle (2.13), we can add features a little bit
>> at a time, and hopefully be close to done by the time we release 2.14.
>>
> Just curious: is t
Carl D. Sorensen schrieb:
On 4/1/09 1:09 AM, "Marc Hohl" wrote:
Carl D. Sorensen schrieb:
Would it be easier to define two separate staff commands? In my files, I
define
noten = \relative c { c d e f }
and feed this into a Staff AND a TabStaff. So, why not create a compoun
David Stocker schrieb:
Marc Hohl wrote:
I think you should also add:
\override TabVoice.Tie #'transparent = ##t
Yes, of course. But then another problem occurs: if the tie isn't
visible, it looks as if there are two distinct
notes. Therefore, I think strongly about a scheme function (wh
David Stocker wrote:
Marc Hohl wrote:
I think you should also add:
\override TabVoice.Tie #'transparent = ##t
Yes, of course. But then another problem occurs: if the tie isn't
visible, it looks as if there are two distinct
notes. Therefore, I think strongly about a scheme function (whic
On 4/1/09 1:09 AM, "Marc Hohl" wrote:
> Carl D. Sorensen schrieb:
>>
>>
> Would it be easier to define two separate staff commands? In my files, I
> define
>
> noten = \relative c { c d e f }
>
> and feed this into a Staff AND a TabStaff. So, why not create a compound
> Staff (called \Mus
Marc Hohl wrote:
I think you should also add:
\override TabVoice.Tie #'transparent = ##t
Yes, of course. But then another problem occurs: if the tie isn't
visible, it looks as if there are two distinct
notes. Therefore, I think strongly about a scheme function (which at
the end should b
Marc Hohl wrote:
I think you should also add:
\override TabVoice.Tie #'transparent = ##t
Yes, of course. But then another problem occurs: if the tie isn't
visible, it looks as if there are two distinct
notes. Therefore, I think strongly about a scheme function (which at
the end should be
I think you should also add:
\override TabVoice.Tie #'transparent = ##t
Yes, of course. But then another problem occurs: if the tie isn't
visible, it looks as if there are two distinct
notes. Therefore, I think strongly about a scheme function (which at the
end should be hidden in the
Tab
Carl D. Sorensen schrieb:
If I understand correctly, you have a group of interested users who are
working on defining how Tablature should behave.
You also have a couple of tablature users who are interested in becoming
Frogs and thus joining the development team (Marc is one of them, IIRC).
W
On 3/31/09 2:46 PM, "Grammostola Rosea" wrote:
> Grammostola Rosea wrote:
>> Marc Hohl wrote:
>>> Grammostola Rosea schrieb:
>>>
>>>
>>> Btw it's time to make tablature with invisible Ties, Slurs, Dots,
>>> Stems etc. default imo.
>>>
>> I don't know whether th
Grammostola Rosea wrote:
Grammostola Rosea wrote:
Marc Hohl wrote:
Grammostola Rosea schrieb:
Btw it's time to make tablature with invisible Ties, Slurs,
Dots, Stems etc. default imo.
I don't know whether this should be the default, but it should be
archieved with a simple
command, li
Grammostola Rosea wrote:
Marc Hohl wrote:
Grammostola Rosea schrieb:
Btw it's time to make tablature with invisible Ties, Slurs, Dots,
Stems etc. default imo.
I don't know whether this should be the default, but it should be
archieved with a simple
command, like \tabNumbersOnly (which
Marc Hohl wrote:
Grammostola Rosea schrieb:
Btw it's time to make tablature with invisible Ties, Slurs, Dots,
Stems etc. default imo.
I don't know whether this should be the default, but it should be
archieved with a simple
command, like \tabNumbersOnly (which isn't defined yet).
Marc
Grammostola Rosea schrieb:
Btw it's time to make tablature with invisible Ties, Slurs, Dots,
Stems etc. default imo.
I don't know whether this should be the default, but it should be
archieved with a simple
command, like \tabNumbersOnly (which isn't defined yet).
Marc
I agree, all thou
Grammostola Rosea wrote:
Marc Hohl wrote:
Grammostola Rosea schrieb:
Neil Puttock wrote:
2009/3/28 Grammostola Rosea :
Hi,
I want to get invisible slurs in tablature... how?
Simply \override Slur #'transparent in the same way as you've done for
the other objects in your TabStaff con
Marc Hohl wrote:
Grammostola Rosea schrieb:
Neil Puttock wrote:
2009/3/28 Grammostola Rosea :
Hi,
I want to get invisible slurs in tablature... how?
Simply \override Slur #'transparent in the same way as you've done for
the other objects in your TabStaff context.
Why aren't you usin
Neil Puttock wrote:
2009/3/28 Grammostola Rosea :
Hi,
I want to get invisible slurs in tablature... how?
Simply \override Slur #'transparent in the same way as you've done for
the other objects in your TabStaff context.
Why aren't you using ties though
(http://lilypond.org/doc/v2.12/
2009/3/28 Grammostola Rosea :
>
> Hi,
>
> I want to get invisible slurs in tablature... how?
Simply \override Slur #'transparent in the same way as you've done for
the other objects in your TabStaff context.
Why aren't you using ties though
(http://lilypond.org/doc/v2.12/Documentation/user/lilypo
21 matches
Mail list logo
