![]() And as the TuxGuitar lilypond export is perfectly prepared (one bar in one line), it is a perfect base for "manual tweaks". Writing the chords section in lilypond in chordmode is not too big a job - usually takes some ten minutes. Lilypond can analyze a voice or a staff for harmonies an add the symbols, but often the guitar-specific chord tweaks (other bass = slash cord, inversions) yield ultrajazzy modified chord symbols, though they are gutarist's bread and butter style. ) )įor my use, I created a Lilypond Template (with the voices, the staffs and of course also the paper size) and add just the voices from the TuxGuitar exported Lilypond file, as I have to tweak for my co-cacophonians to read (and play -) ) something not so guitar-centric. if you're not already doing that.Īnother one throws in for Chord Symbols (never done that in Lilypond, err, successfully. Perhaps you can collaborate with some of the folks doing the LilyPond tab stuff. There seems to be no page setup feature in TuxGuitar (i.e., margins, paper size, etc.) but if you add such a feature in the future, could you also export that information to the LilyPond output. I know that LilyPond still lacks all the fine details we'd might like in its tab output but it would be nice, as you get to it, to generate LilyPond code for as many of the little details (slides, bends, grace notes, pick direction, etc.) as possible.Īlso it would be great if chord names at least, if not diagrams, came across into LilyPond too. ![]() ![]() Doing LilyPond tabs directly in Emacs was a big hurdle. Generating LilyPond output is a great idea.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |