Re: TABS string

2017-02-22 Thread Gilles Peltzer
An easy fix was to force the string mark to be under the staff using underscore. { a,2.-2 | d,2.-1_\5 | g2._\4 | c,2.| }>> -G On Wed, Feb 22, 2017 at 9:55 PM, Gilles Peltzer wrote: > Hi Thomas, > Thanks for the help. I understand

Re: TABS string

2017-02-22 Thread Gilles Peltzer
Hi Thomas, Thanks for the help. I understand the logic and giving the priority to open strings is a good default. This is why I wanted to use the string number in the base line: { a,2.-2 | d,2.-1\5 | g2.\4 | c,2. | }>> Doing so made the TABS look ok but the \5 on the d appears shifted to the

Re: TABS string

2017-02-22 Thread Thomas Morley
2017-02-22 19:32 GMT+01:00 Gilles Peltzer : > Hello, > LiliPond version "2.18.2" > In the following example, the TABS indicate a free string for the first > notes of bar 2 and bar 3, which is not what I want. > If I indicate the string number for the d and g notes on the lower

TABS string

2017-02-22 Thread Gilles Peltzer
Hello, LiliPond version "2.18.2" In the following example, the TABS indicate a free string for the first notes of bar 2 and bar 3, which is not what I want. If I indicate the string number for the d and g notes on the lower voice, the TABS is correct but the indcations shifts to the upper voice on