[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: feature request - lilypond completion of note octave and string
From: |
Pierre Perol-Schneider |
Subject: |
Re: feature request - lilypond completion of note octave and string |
Date: |
Fri, 2 Aug 2013 20:39:33 +0200 |
2013/8/2 BB <address@hidden>
> I come up with one of my ideas again in a feature request.
>
> If one simply transfers music to TabStaff as a rule some notes in a Tab
> make
> trouble because they are not bound to a string. Often notes are interpreted
> out of range of the instrument. So the user dediously has to correct the
> notes of the tab. Sometimes notes are omitted and kill triples, pull offs,
> hammer ons and the bar structure. One gets just a crippled and useless tab.
>
>
Hi BB,
I won't answer your question, I'm no developer, question but here's how I
would right your tab :
\version "2.17.23"
MyTuning = \stringTuning <g, d g b d'>
\new TabStaff {
\key g \major
\set TabStaff.stringTunings = #MyTuning
\tabFullNotation
\stemDown
{
%1
\times 2/3 { <d\5>4^"P" (c)^"H" (<d\5>) }
<d\5>4^"P" (c)
%2
\times 2/3 { gis'4^"H" (f')^"P" (g') }
g8^"H" (a) <d b g>8 g
}
}
As you can see, I find predefind open strings useless and so is the
\relative function for fretted strings instument.
Cheers,
Pierre