TAB problem

2020-04-08 Thread bb
I like to avoid open strings, except for the lowest possible string, as there is no alternative. Is it possible to raise an exception in lilypond? How? Thanks. Example: check =\relative c {c8 e f gis a b } \score {   <<     \new Staff { \check }     \new TabStaff {       \set

Re: TAB-problem

2017-12-28 Thread bb
Thank you! My problem is solved! Regards Am 28.12.2017 um 16:02 schrieb bb: > OK. You sent two versions. I will check it. Thank you! > > Am 28.12.2017 um 16:00 schrieb bb: >> As there got lost my original mail, I have to add that I only want >> "cleftext" or "test" or whatever text defined in

Re: TAB-problem

2017-12-28 Thread bb
OK. You sent two versions. I will check it. Thank you! Am 28.12.2017 um 16:00 schrieb bb: > As there got lost my original mail, I have to add that I only want > "cleftext" or "test" or whatever text defined in the code only once at > the beginning of every TAB line. NOT every time the clef

Re: TAB-problem

2017-12-28 Thread bb
As there got lost my original mail, I have to add that I only want "cleftext" or "test" or whatever text defined in the code only once at the beginning of every TAB line. NOT every time the clef changes! Am 28.12.2017 um 15:54 schrieb bb: > Thank you for answering. Your code has exactly the

Re: TAB-problem

2017-12-28 Thread Malte Meyn
Am 28.12.2017 um 15:54 schrieb bb: Thank you for answering. Your code has exactly the problem I wanted to overcome. There is a "cleftext"  every time the clef changes! No it has not. Have a close look: I do \omit Clef \once \override Clef.stencil You do \override Clef.stencil That’s

Re: TAB-problem

2017-12-28 Thread bb
Thank you for answering. Your code has exactly the problem I wanted to overcome. There is a "cleftext"  every time the clef changes! I minimized my example code due to your expectations. Regards begin ## \version "2.19.65"    D-Dorian =  \relative c {   \clef "bass_8"

Re: TAB-problem

2017-12-28 Thread Malte Meyn
Am 28.12.2017 um 15:22 schrieb Malte Meyn: Set the clef stencil to ##f (\omit is a shorthand for that) and only set the stencil for the first occurence. As I realised some seconds after sending the message, this isn’t enough if you want to have the clef at the beginning of each line. Then

Re: TAB-problem

2017-12-28 Thread Malte Meyn
Am 28.12.2017 um 14:21 schrieb bb: I attach an example code. (Sorry, my skills are just not developed enough to shorten the code essential.) Here is a much smaller example. It’s not minimal but near. How to build such an example? Well, just leave everything out that has nothing to do with

TAB-problem

2017-12-28 Thread bb
A six string bass has a tonal range that overlaps in part with the guitar. Therefore it is convenient to write parts of a score in treble clef. While writing sheet music with tabs I get a problem with the notes for the strings of the TAB. I get it for every change of the clef again and I get  it

Banjo tab problem

2012-06-17 Thread banjo hero
Hi gang. I'm a new lilypond user, so I might just be overlooking something stupid here. If so, sorry. I'm working on a piece that I'm using the default banjo C tuning for, but the tab is coming out wrong - the fifth string's fret numbers are incorrect. There are notes being indicated as

Banjo tab problem

2012-06-17 Thread banjo hero
Hi gang. I'm a new lilypond user, so I might just be overlooking something stupid here. If so, sorry. I'm working on a piece that I'm using the default banjo C tuning for, but the tab is coming out wrong - the fifth string's fret numbers are incorrect. There are notes being indicated as

Re: Banjo tab problem

2012-06-17 Thread banjo hero
Apologies for the double-post. I sent the second one about two hours after the first, I think, not realizing the turnaround would be more like 24 hours for it to post. Weird. Anyway, I was able to puzzle this one out on my own; the .ly file I was working with was generated by tuxguitar, and was

Re: Banjo tab problem

2012-06-17 Thread Janek Warchoł
On Sun, Jun 17, 2012 at 7:02 PM, banjo hero banjoh...@gmail.com wrote: Apologies for the double-post.  I sent the second one about two hours after the first, I think, not realizing the turnaround would be more like 24 hours for it to post.  Weird. Anyway, I was able to puzzle this one out on