Re: Issue 4048: Improve crescendo performance with unspecified dynamics (issue 302910043 by nine.fierce.ball...@gmail.com)

2016-07-12 Thread ht . lilypond . development
In short: LGTM. The rest of this comment is just continuing discussion on some of the points in your previous response. On 2016/07/12 05:01:16, Dan Eble wrote: > What are the main user-level justifications for increasing the > complexity of the Dynamic_performer It also improves an example I

Re: Doc: Add a section about handling MIDI dynamics with multiple voices (issue 302930043 by ht.lilypond.developm...@gmail.com)

2016-07-12 Thread Dan Eble
> I suspect all of this behavior is due to the Staff_performer logic, > which tries to distribute notes and dynamics into separate classes by > the names of their associated Voices - maybe this should be done using > some other criterion (such as an internal Voice ID, unique to each Voice > instanc

Re: additional entry in lilypond.org/productions.html?

2016-07-12 Thread Urs Liska
Am 12.07.2016 um 10:00 schrieb Marc Hohl: >> The Productions page has now a long column of concerts on the left and a >> short column of published sheet music on the right. I think that >> "published" in this case means just publicly available? I mean, Mutopia >> is not a publishing company. > >

Re: additional entry in lilypond.org/productions.html?

2016-07-12 Thread Marc Hohl
Am 10.07.2016 um 19:11 schrieb Federico Bruni: Il giorno ven 8 lug 2016 alle 12:36, Marc Hohl ha scritto: I have written some musicals for children and adolescents in the past and have two more musicals in the pipeline, to be released at the end of 2016. The sheets are done with LilyPond and L

Re: Doc: Add a section about handling MIDI dynamics with multiple voices (issue 302930043 by ht.lilypond.developm...@gmail.com)

2016-07-12 Thread ht . lilypond . development
On 2016/07/11 16:39:01, Carl wrote: I think the current behavior of changing dynamics in identically-named but distinct voices is flawed, so I think it should be a known issue, not in the main documentation. I agree that bugs should not be documented as the rules about the behavior. However,