On Sat, Oct 19, 2019 at 9:00 AM wrote:
>
> Date: Sat, 19 Oct 2019 10:06:10 +0200
> From: Malte Meyn
> To: bug-lilypond
> Subject: polyphony and TabStaff: don’t put two voices on the same
> string
> Message-ID:
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi list,
>
>
Sorry, here comes the buggy example:
\version "2.19.83"
\relative c'{
\time 2/4
% This first line gives the error:
d16 d64-. ( d-. d-. d-. ) e16 e16:64 fis16 fis16:64 g16 g16:64 |
% Explicitly shortening the beam helps:
d16 [ d64-. ( d-. d-. d-. )] e16 e16:64 fis16 fis16:64 g16 g16:64 |
% Very
Hi,
The following example illustrates a bug in 2.19.83 that's a regression
against 2.18. Compiling with 2.19.83 gives
GNU LilyPond 2.19.83
Processing `bug.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...lilypond:
Am 13.10.19 um 20:30 schrieb Trevor Bača:
Hi,
While "c4:32" correctly expresses a quarter note stem tremolo slashes,
typing (badly-formed) "r4:32" probably only happens when a user is editing
a source file and changes a note to a rest without regard for the stem
tremolo suffix.
However,
Hi list,
this was reported at the LilyPond facebook group. When having “real”
polyphony with multiple Voice contexts, the notes are put on the strings
independently which can lead to several voices with different frets on
the same string.
The first three “chords” on the TabStaff should look
