2017-03-26 22:57 GMT+02:00 <caag...@gmail.com>:
> You're setting options on the TabStaff while in the Staff context. Since
> there is no TabStaff context at the moment, one is temporarily created. You
> could fix it by setting the properties in a \with {} block on the TabStaff
> insteadd.
Which is the most common way.
To be complete, sometimes it has advantages to use applyOutput:
solo =
\relative c' {
\applyOutput TabStaff
#(lambda (g c1 c2) (ly:context-set-property! c1 'minimumFret 1))
\applyOutput TabStaff
#(lambda (g c1 c2) (ly:context-set-property! c1 'restrainOpenStrings #t))
c8 f e e d c b a
}
\new Staff \solo
\new TabStaff \solo
Note the settings for _Tab_Staff in 'solo' never affect the standalone Staff.
Cheers,
Harm
> On 03/26/17 22:49, Rob Torop wrote:
>>
>> I'm finding that when I use a TabStaff and also set some properties
>> (either or both of minimumFret and restrainOpenStrings), my first line
>> has an extra TabStaff! What can I do to get rid of it? Thanks!
>>
>> Here's what it looks like:
>>
>> Screen Shot 2017-03-26 at 4.46.59 PM.png
>>
>> And here's the code that generated this:
>>
>> \version "2.19"
>> \language "english"
>>
>> solo = \relative c' {
>>
>> % Either of both of the two settings will cause an extra "TAB" staff
>> to be rendered
>> \set TabStaff.minimumFret=#1
>> \set TabStaff.restrainOpenStrings = ##t
>>
>> c8 f e ef df c bf af
>> }
>>
>> \score {
>> <<
>> \new Staff \solo
>> \new TabStaff \solo
>> >>
>> }
>>
>>
>>
>>
>> _______________________________________________
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
