David Wright writes:
> On Mon 07 Nov 2016 at 03:12:15 (-0700), mclaren
> wrote
>> Musicians must develop a very thick skin and learn to expect this. The
>> crucial issue is to get a score, by whatever means possible, and then move
>> on. Practicing musicians quickly learn to regard programmers a
On Nov 16, 2016, at 11:58 PM, David Wright wrote:
> I guess you have some problems which are far more serious than those
> that arise when playing about with LilyPond or posting here.
BWAHAHAHAHAHAHAH!
That made my night.
Thanks for the chuckle, David.
Best,
Kieren.
On Mon 07 Nov 2016 at 03:12:15 (-0700), mclaren wrote:
> David Wright remarked:
>
> "What I can't understand is why you would want
> to print out a score that is basically impossible to play, and is, in
> any case, written in a notation that is debatably incapable of
> expressing it."
>
> Thi
Am 7. November 2016 13:29:50 MEZ, schrieb David Kastrup :
>Urs Liska writes:
>
>> Am 07.11.2016 um 11:12 schrieb mclaren:
>>
>>> Thus end users must go it alone and find workarounds for themselves.
>>> Programmers will never lift a finger to help you when things go
>>> wrong. Instead, the progr
Urs Liska writes:
> Am 07.11.2016 um 11:12 schrieb mclaren:
>
>> Thus end users must go it alone and find workarounds for themselves.
>> Programmers will never lift a finger to help you when things go
>> wrong. Instead, the programmer will typically blame the victim: "Oh,
>> the program is suppo
Am 07.11.2016 um 11:12 schrieb mclaren:
> David Wright remarked:
>
> "What I can't understand is why you would want
> to print out a score that is basically impossible to play, and is, in
> any case, written in a notation that is debatably incapable of
> expressing it."
>
> This score might be
have devoted many hours to your queries.
Andrew
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On Behalf Of
mclaren
Sent: Monday, 7 November 2016 9:12 PM
To: lilypond-user@gnu.org
Subject: Re: Two different time signatures with
mclaren writes:
> David Wright remarked:
>
> "What I can't understand is why you would want
> to print out a score that is basically impossible to play, and is, in
> any case, written in a notation that is debatably incapable of
> expressing it."
>
> This score might be impossible for _humans_
ck skin and learn to expect this. The
crucial issue is to get a score, by whatever means possible, and then move
on. Practicing musicians quickly learn to regard programmers as a form of
damage and route around them.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Two-dif
On Sat 05 Nov 2016 at 23:35:21 (-0700), mclaren wrote:
> The logical extension of that example I posted with the large time signature,
> 4918233/340340, involves two different simultaneous measures with different
> tuplets and different time signatures, one large, the other not.
Is it a silly ques
Am 6. November 2016 07:51:49 MEZ, schrieb Nathan Ho :
>On 2016-11-05 23:35, mclaren wrote:
>> Urs Liska's and Andrew Ho's page break code works well on most
>examples
>> I've
>> worked through, but it doesn't work here.
>
>Hi mclaren,
>
>I hate to correct you, but the correct names are Hans Lisk
On 2016-11-05 23:35, mclaren wrote:
Urs Liska's and Andrew Ho's page break code works well on most examples
I've
worked through, but it doesn't work here.
Hi mclaren,
I hate to correct you, but the correct names are Hans Liska and Andrew
Ho.
Andrew
___
27;'
\tuplet 16000/14451
{c8[ c c c c c c c c c c c c c c c] }
\bar "|"
\relative c''
\tuplet 16000/14451
{c8[ c c \tuplet 3/2{c c} c c c \tuplet 3/2{c c} c c c \tuplet 3/2{c c} c c
c] }
\bar "|"
\relative c''
\tuplet 16000/14451
{c8[ c c c c c c c c c c c c c
13 matches
Mail list logo
