On 2016/07/12 13:38:16, dan_faithful.be wrote:
> 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
> 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
>
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.
https://codereview.appspot.com/302930043/diff/20001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/302930043/diff/20001/Documentation/notation/input.itely#newcode3028
Documentation/notation/input.itely:3028: value 0.71 in the
Heikki, this is so much better than your first patch. Thanks for
working on it!
As I mention in the comments, 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. But I like
https://codereview.appspot.com/302930043/diff/20001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/302930043/diff/20001/Documentation/notation/input.itely#newcode3028
Documentation/notation/input.itely:3028: value 0.71 in the
Much improved over the first attempt, thanks. LGTM.
Trevor
https://codereview.appspot.com/302930043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
This is too wordy for the notation reference. We need to have a minimum
number of words in the NR, and instead show things by examples.
It should just have examples that show the problem and the solution.
Since we can't see the MIDI output in the manual, there should be a
statement of what
Reviewers: ,
Description:
Doc: Add a section about handling MIDI dynamics with multiple voices
As MIDI dynamics of every Voice are by default independent of
dynamic changes occurring in all other Voices, writing LilyPond
input using multiple voices may require some additional
considerations to
