lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Solution to 7 over sqr(71) time against integer polyrhythms


From: Urs Liska
Subject: Re: Solution to 7 over sqr(71) time against integer polyrhythms
Date: Tue, 22 Nov 2016 09:16:36 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0


Am 22.11.2016 um 08:26 schrieb mclaren:
>  If that's really the philosophy behind
> Lilypond, this forum should shut down right now and post the following
> message:
>
> IF YOU ENCOUNTER ANY PROBLEM OR CRASH OR PROGRAM HANG WITH LILYPOND, FIX IT
> YOURSELF. DON'T BEAT YOUR CHEST COMPLAINING, JUST DO IT YOURSELF.
>
> Somehow I don't see that message being sent.  

Well said.

> Instead, there's a recognition
> that Lilypond is a piece of code that may have limitations. And those
> limitations may affect real musicians in the real world. So you've got a
> community of people who will try to help out when someone encounters a
> problem.
well, that's true - if you extend the last sentence with "..., reports
it in an appropriate manner and helps with what is necessary to pin down
the issue."
Which is exactly *not* what you've done.

If you'd do a poll you'd realize that an overwhelming majority of users
pointing out (assumed) issues have been welcomed and helped out, either
by fixing their input errors or by having the found issue added to the
tracker (if they have then be solved is a matter of the complexity of
the problem and the available resources).
The problem with *your* issues is that you a) didn't report them in a
manner that is even close to appropriate and b) that you didn't help
tracking them down. For example, I've pointed out that many of the files
you sent were simply faulty. When the input has metric errors you can't
judge LilyPond's behaviour with regard to meter and breaks. Instead of
fixing the error and coming back you went on with other files.

If you look closely you should notice that behind your back - and
*despite* your outrageous behaviour - our developers have discussed the
underlying matters.
That said, I can imagine that if you'd step back, push the "reset"
button and come back presenting your problems in a decent way and
properly collaborate you would be heard. No guarantee that the issues
would be solved, though.

Urs



reply via email to

[Prev in Thread] Current Thread [Next in Thread]