[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings |
Date: |
Fri, 09 Jan 2015 13:32:05 +0000 |
Comment #6 on issue 703 by address@hidden: Enhancement: TabStaff
should handle non-monotonic stringTunings
https://code.google.com/p/lilypond/issues/detail?id=703
Like in this simple example, the second stacked notes, A and D on the
first and third strings could be played D on third and A on the fourth
string second fret. Anybody can show me how it can be done, forcing an A
second fret on the fourth string instead of defaulting to the first string?
Thanks
% Created on Sun Feb 26 14:01:54 PST 2012
\version "2.14.0"
\paper {
oddFooterMarkup = \markup {"Hymn 284"}
}
mynotes = {
<d g>2 <d a'>4 <d g>8 <fis a>
<g b>4 <g b> <e a>8 (g) <c, e>4 \break
}
\score {
<<
\new Staff {
\time 4/4
\key g \major
\clef treble
\relative c' {
% Type notes here
\mynotes
}
}
\new TabStaff {
\set TabStaff.stringTunings = #ukulele-tuning
\relative c'{
\mynotes
}
}
%\midi{}
}
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings,
lilypond <=
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/09
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/11
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/11
- Message not available
- Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, lilypond, 2015/01/11