Hi there,
Would it be accurate to assume that custom hex/rgb colors in fret diagrams
are not supported as of now?
Sincerely,
Nikita
On Thu, May 16, 2024 at 2:29 AM Nikita Borisenko wrote:
> Hi Jean,
>
> Thanks for the quick response.
>
> Putting quotes around it doesn
Hi Jean,
Thanks for the quick response.
Putting quotes around it doesn't really help. The expression gets ignored
and the dot comes with the default black color in this case.
Sincerely,
Nikita
On Thu, May 16, 2024 at 2:18 AM Jean Abou Samra wrote:
> > Quick question on coloring d
> Quick question on coloring dots in fret-diagrams. There is an option to use
> predefined colors from normal, CSS or X11 palettes which works perfectly well
> in the fret-diagram-verbose with the snippet below:
>
> > (place-fret 3 6 3 dodgerblue2)
>
> For some reason
Hi Everyone,
Hope you are doing well.
Quick question on coloring dots in fret-diagrams. There is an option to use
predefined colors from normal, CSS or X11 palettes which works perfectly
well in the fret-diagram-verbose with the snippet below:
> (place-fret 3 6 3 dodgerblue2)
For some reaso
> There is something I do not like about the fret diagrams in
> Lilypond:
>
> The diagrams are "open" on the side pointing towards the bridge of
> the instrument, with the strings "sticking out" on that side. How
> could I achieve closed rectangles in Li
.
Cheers,
Valentin
Am Mittwoch, 19. April 2023, 20:15:38 CEST schrieb Werner LEMBERG:
> > There is something I do not like about the fret diagrams in
> > Lilypond:
> >
> > The diagrams are "open" on the side pointing towards the bridge of
> > the instrument, with
> There is something I do not like about the fret diagrams in
> Lilypond:
>
> The diagrams are "open" on the side pointing towards the bridge of
> the instrument, with the strings "sticking out" on that side. How
> could I achieve closed rectangles in Li
There is something I do not like about the fret diagrams in Lilypond:
The diagrams are "open" on the side pointing towards the bridge of the
instrument, with the strings "sticking out" on that side. How could I
achieve closed rectangles in Lilypond like e.g. the "Mu
For future reference. I have no idea if this is the most Lilypondic way of
accomplishing what I want, but it works.
#(set-global-staff-size 14)
\layout
{
indent = 0
}
and using
\noBreak
if necessary
I'm trying to create a rhythm chart for guitarists that have specific voicings
shown in fret diagrams. It's mostly correct, except I have two measures on the
first line and three on the remaining. What I want is four measures per line.
I'll fess up to being a beginner with Lil
[mailto:thomasmorle...@gmail.com]
>Sent: Sunday, January 31, 2016 7:14 PM
>To: Peter Gentry
>Cc: lilypond-user
>Subject: Re: Fret Diagrams
>
>Hi Peter,
>
>2016-01-31 19:29 GMT+01:00 Peter Gentry :
>> This may be trivial but searches of themanuals etc have not
>born
ol
markup to be displayed.
So:
It has nothing to do with Fret Diagrams, but ChordNames.
Everywhere you wrote rests the noChordSymbol appears for each rest.
>
> If r1 is replaced by R1 then no "N.C." markup.
R1 is a MultiMeasureRest not a Rest, so noChordSymbol is not printed.
Some for
Hi Peter,
the N.C. symbol ("no chord") appears for rests r but not for full
measure rests R and obviously not for invisible (spacer) rests s. And it
appears for every single rest, so in case of
r2 r4 g
you get
N.C. N.C. G
for a single measure.
You have several choices to avoid this:
a) W
This may be trivial but searches of themanuals etc have not born fruit.
How do you prevent the markup N.C. appearing where there is a note rest. In
fact N.C. does not always appear sometimes once in a
bar sometimes twice for no immediately apparent reason.
If r1 is replaced by R1 then no "N.C."
Many Thanks! Works well, even with "R" instead of "I". Perfect!
On 26.12.2015 12:57, pls wrote:
BB writes:
\markup
\override #'(fret-diagram-details . (
(number-type . arabic)
(finger-code . in-dot))) {
\fret-diagram #"s:3;f:1;6-3-2;5-2-1;5-5-4;4-4-3;"
% percent sign is for comments
% s:3 tel
BB writes:
> \markup
> \override #'(fret-diagram-details . (
> (number-type . arabic)
> (finger-code . in-dot))) {
> \fret-diagram #"s:3;f:1;6-3-2;5-2-1;5-5-4;4-4-3;"
> % percent sign is for comments
> % s:3 tells lilypond to make diagram 3x normal size
> % f:1 is to show finger #'s in circle on
\markup
\override #'(fret-diagram-details . (
(number-type . arabic)
(finger-code . in-dot))) {
\fret-diagram #"s:3;f:1;6-3-2;5-2-1;5-5-4;4-4-3;"
% percent sign is for comments
% s:3 tells lilypond to make diagram 3x normal size
% f:1 is to show f
2015-11-08 16:15 GMT+01:00 BB :
> I just tried your code but get a different PDF result? See attachement.
> I get a warning in German:
>
> Warnung: staff-affinities sollten nur abnehmen
>
> Might mean something like
> staff-affinities should always decrease
>
Did you use my test-file or other cod
2015-11-08 14:52 GMT+01:00 pls :
> Thomas Morley writes:
>
>> 2015-11-08 12:23 GMT+01:00 pls :
>
>>> Hi Harm,
>>>
>>> I finally managed to test your code and I really, really like it! I
>>> especially like the option to
>>> turn the annotations on and off.
>>
>> Glad you like it.
>>
>> Ofcourse i
I just tried your code but get a different PDF result? See attachement.
I get a warning in German:
Warnung: staff-affinities sollten nur abnehmen
Might mean something like
staff-affinities should always decrease
On 08.11.2015 12:23, pls wrote:
Thomas Morley writes:
Hi Patrick,
I did some e
Thomas Morley writes:
> 2015-11-08 12:23 GMT+01:00 pls :
>> Hi Harm,
>>
>> I finally managed to test your code and I really, really like it! I
>> especially like the option to
>> turn the annotations on and off.
>
> Glad you like it.
>
> Ofcourse it's not in the source atm.
> And there's the (l
2015-11-08 12:23 GMT+01:00 pls :
> Thomas Morley writes:
>
>> Hi Patrick,
>>
>> I did some experiments, result attached.
>>
>> Please test. There is a README in it.
>>
>> Please be aware it's experimental code, not ready yet to put up a
>> patch, although it compiles as far as I tested...
>> (some
Thomas Morley writes:
> Hi Patrick,
>
> I did some experiments, result attached.
>
> Please test. There is a README in it.
>
> Please be aware it's experimental code, not ready yet to put up a
> patch, although it compiles as far as I tested...
> (some debugging code is still present, most of it
Thomas Morley writes:
> 2015-11-01 19:55 GMT+01:00 pls :
>> Hey all,
>>
>> currently it's possible to add fingering indications (any character) inside
>> of dots or "below" the strings. (In my attachment in landscape orientation
>> it's rather to the right of the strings). Now I would like to b
Thomas Morley writes:
> 2015-10-29 23:53 GMT+01:00 pls :
>
>>
>> My use case: I have created a huge library of predefined fret
>> diagrams (https://github.com/Philomelos/lilypond-predefined-fretboards)
>> and I would love to be able to e.g. display those diagrams w
2015-10-29 23:53 GMT+01:00 pls :
>
> My use case: I have created a huge library of predefined fret
> diagrams (https://github.com/Philomelos/lilypond-predefined-fretboards)
> and I would love to be able to e.g. display those diagrams with chord steps,
> note names or even
>
Thomas Morley writes:
> 2015-10-29 19:24 GMT+01:00 pls :
>> Hey all,
>>
>> I would like to override some fingering information of predefined fret
>> diagrams. The relevant information should be in the
>> /dot-placement-list/ of the fret-diagram-interface (see
2015-10-29 19:24 GMT+01:00 pls :
> Hey all,
>
> I would like to override some fingering information of predefined fret
> diagrams. The relevant information should be in the
> /dot-placement-list/ of the fret-diagram-interface (see
> http://lilypond.org/doc/v2.19/Documentation/
Hey all,
I would like to override some fingering information of predefined fret
diagrams. The relevant information should be in the
/dot-placement-list/ of the fret-diagram-interface (see
http://lilypond.org/doc/v2.19/Documentation/internals-big-page#fret_002ddiagram_002dinterface).
But I
find the template folder, click the "Config" button in the OOoLilyPond
window and see "Template Path:"
Cheers,
Klaus
Fret-Diagram.ly
<http://lilypond.1069038.n5.nabble.com/file/n179073/Fret-Diagram.ly>
--
View this message in context:
http://lilyp
> On 25 Jul 2015, at 15:45, Socrates Leptos wrote:
>
> Dear lilypond users,
>
> I am new to lilypond so I half expect my question to be so ridiculous... I
> hope that you believe me when I say I made every effort within my still
> confused mind to solve this issue to no avail. Here goes...
>
Dear lilypond users,
I am new to lilypond so I half expect my question to be so ridiculous... I
hope that you believe me when I say I made every effort within my still
confused mind to solve this issue to no avail. Here goes...
In Frescobaldi, I input:
\version "2.18.2"
\markup \fret-diagram
On 26.05.2015, at 23:58, Carl Sorensen wrote:
>
> Let's try again. I have checked this version; it has the warning code.
Yes, it does. Looks very good to me!
Thanks a lot,
patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lis
On 5/26/15 2:44 AM, "pls" wrote:
>
>I¹m sorry to ask but I checked the translation-function files several
>times: Did you inadvertently send me an unchanged file? diff did not show
>any difference between this file and the last file.
If diff didn't how the difference, then there must not have
On 26.05.2015, at 04:34, Carl Sorensen wrote:
> On 5/25/15 5:25 AM, "pls" wrote:
>>
>> Works great! Thanks a million!
>
> Thanks for your feedback.
>
>>
>> Should/Could LilyPond issue a warning message in the case of open strings
>> whenever "wrong" fingers (not 0) are ignored? Or is it b
On 5/25/15 5:25 AM, "pls" wrote:
>
>Works great! Thanks a million!
Thanks for your feedback.
>
>Should/Could LilyPond issue a warning message in the case of open strings
>whenever "wrong" fingers (not 0) are ignored? Or is it better to
>silently set the fingers to 0?
>Example: (Perhaps the us
On 25.05.2015, at 01:16, Carl Sorensen wrote:
> On 5/23/15 11:59 PM, "pls" wrote:
>>
>> \transpose f g { 1 }
>
> Here's a revised version of translation-functions.scm. It will generate
> barres only if fingers are indicated, and multiple strings use the same
> finger. It does work properly
On 5/23/15 11:59 PM, "pls" wrote:
>
>
>>
>> Maybe I should back the code back to where a barre will be indicated
>>only
>> if the fingers are specified in the chord, and no barre will be
>>generated
>> when an open chord is transposed. That would be a straightforward fix.
>> It would never gene
On 23.05.2015, at 22:06, Carl Sorensen wrote:
>
>
> On 5/23/15 6:34 AM, "pls" wrote:
>
>>
>> Here is another test case for your patch:
>>
>> \version "2.19.20"
>>
>> <<
>> \new FretBoards {
>> 1
>> 1
>> \transpose g a { 1 }
>> }
>>
>> These chords can be played with one finge
On 5/23/15 6:34 AM, "pls" wrote:
>
>Here is another test case for your patch:
>
>\version "2.19.20"
>
><<
> \new FretBoards {
>1
>1
>\transpose g a { 1 }
> }
>>>
>
>These chords can be played with one finger! ;)
So what do you recommend be done?
I can make it so no fingerings ar
On 23.05.2015, at 06:22, Carl Sorensen wrote:
>>
>> + some chords lead to unwanted barre indicators, e.g.:
>> + or
>> + (wrong fingers!)
>
> I will look into those. Thanks.
Here is another test case for your patch:
\version "2.19.20"
<<
\new FretBoards {
1
1
\transpose g a
tion as soon as your patch gets accepted (if you
>> want me to). (So far I have found only 2 automatically-generated diagrams
>> without fingering. ;) )
>
> I don't think we want to have all of the diagrams with fingering. We want
> to show the capability of making the diagram
de pop charts, but I'd be
happy to add them. Suspended chords are also not commonly used in US
consumer-grade pop charts.
>+ inversions are missing (Slash chords)
>+ as discussed: the lack of being able to shift the same chord shape up
>and down the fretboard.
When defining your own predefined
would allow \transpose to do the right thing on both chords and
> single notes, relative to fingerings. So \transpose is almost guaranteed
> *not* to work effectively on automatically-generated fret diagrams.
Understood!
>
> That is *why* there is a predefined fretboard capability defined
sonable system I can imagine
that would allow \transpose to do the right thing on both chords and
single notes, relative to fingerings. So \transpose is almost guaranteed
*not* to work effectively on automatically-generated fret diagrams.
That is *why* there is a predefined fretboard capabilit
On 21.05.2015, at 21:06, Carl Sorensen wrote:
>
>
> On 5/21/15 8:39 AM, "pls" wrote:
>>
>>>
>>> I thought about this issue quite a bit when I was creating predefined
>>> fret
>>> diagrams. There, we introduced the idea of a ch
On 5/21/15 8:39 AM, "pls" wrote:
>
>>
>> I thought about this issue quite a bit when I was creating predefined
>>fret
>> diagrams. There, we introduced the idea of a chord shape. There is a
>> function that shifts a chord shape by N frets (offse
ese five basic shapes.
>
> I thought about this issue quite a bit when I was creating predefined fret
> diagrams. There, we introduced the idea of a chord shape. There is a
> function that shifts a chord shape by N frets (offset-fret). At present,
> it adds N to the fret number for e
6, 2, and 1) is a
different shape from an F chord (with barred 6, 2, and 1) in my opinion.
Yes, the pattern on strings 3, 4, and 5 is the same. But the hand pattern
on the chord is different.
I thought about this issue quite a bit when I was creating predefined fret
diagrams. There, we intro
On 21.05.2015, at 02:44, Thomas Morley wrote:
> 2015-05-20 13:16 GMT+02:00 pls :
>>
>>
>> Begin forwarded message:
>>
>> From: pls
>> Subject: Re: how to add barre indications to automatic fret diagrams?
>> Date: 20. Mai 2015 13:12:30 MESZ
>
On 21.05.2015, at 03:49, Carl Sorensen wrote:
>
>
> On 5/20/15 7:30 PM, "Carl Sorensen" wrote:
>
>>
>>
>> On 5/19/15 12:45 PM, "pls" wrote:
>>
>>> Hi all,
>>>
>>> LilyPond¹s automatic fret diagrams r
On 5/20/15 7:30 PM, "Carl Sorensen" wrote:
>
>
>On 5/19/15 12:45 PM, "pls" wrote:
>
>>Hi all,
>>
>>LilyPond¹s automatic fret diagrams really are a very helpful feature!
>>More often than not it helps to not having to predefine and sto
On 5/19/15 12:45 PM, "pls" wrote:
>Hi all,
>
>LilyPond¹s automatic fret diagrams really are a very helpful feature!
>More often than not it helps to not having to predefine and store a
>diagram in a lookup table. But it has one little drawback: it doesn¹t
>a
2015-05-20 13:16 GMT+02:00 pls :
>
>
> Begin forwarded message:
>
> From: pls
> Subject: Re: how to add barre indications to automatic fret diagrams?
> Date: 20. Mai 2015 13:12:30 MESZ
> To: Stephen MacNeil
>
> Hi Stephen,
> On 20.05.2015, at 13:02, Stephen Mac
Begin forwarded message:
> From: pls
> Subject: Re: how to add barre indications to automatic fret diagrams?
> Date: 20. Mai 2015 13:12:30 MESZ
> To: Stephen MacNeil
>
> Hi Stephen,
> On 20.05.2015, at 13:02, Stephen MacNeil wrote:
>
>> sorry forgot one
>
sorry forgot one
\version "2.18.2"
barre = #(define-music-function (barre location str ) (number?)
#{
\once \override FretBoard.before-line-breaking =
#(lambda (grob)
;(display (ly:grob-property grob 'dot-placement-list))
(ly:grob-set-property! grob 'dot-placement-list
(cons `(barre 6 1 ,s
ion! It certainly does get me started. I think this should
> be added to the snippet repository. I could prepare a snippet illustrating
> your code and some other overrides of details of automatically generated
> fret diagrams. Something like that:
>
> \version "2.19.15&quo
the snippet repository. I could prepare a snippet illustrating your
code and some other overrides of details of automatically generated fret
diagrams. Something like that:
\version "2.19.15"
barre = {
\once \override FretBoard.before-line-breaking =
#(lambda (grob)
;(display (ly
2015-05-19 21:59 GMT+02:00 pls :
>
> On 19.05.2015, at 21:47, Stephen MacNeil wrote:
>
> you can check here see if that's what you want.
>
> http://lsr.di.unimi.it/LSR/Search?q=fret-diagram
>
>
> Thanks, but unfortunately these snippets are all about customizing
&g
On 19.05.2015, at 21:47, Stephen MacNeil wrote:
> you can check here see if that's what you want.
>
> http://lsr.di.unimi.it/LSR/Search?q=fret-diagram
Thanks, but unfortunately these snippets are all about customizing predefined
fret diagrams and not about adding barre
Hi all,
LilyPond’s automatic fret diagrams really are a very helpful feature! More
often than not it helps to not having to predefine and store a diagram in a
lookup table. But it has one little drawback: it doesn’t automatically include
a barre indication when several strings are to be
27;t have any modifications to the vertical spacing code. So
it's not going to change the vertical spacing.
>>On 11/12/13 8:46 AM, "Patrick Thomas" wrote:
>>
>>> How can I increase the vertical spacing between lines of chord names
>>>and
>>> f
On 11/12/13 8:46 AM, "Patrick Thomas" wrote:
>How can I increase the vertical spacing between lines of chord names and
>fret diagrams?
>
Change the nonstaff-nonstaff-spacing. See
http://lilypond.org/doc/v2.16/Documentation/notation/flexible-vertical-spac
ing-within-s
Patrick Thomas wrote
> How can I increase the vertical spacing between lines of chord names and
> fret diagrams?
have a look here:
http://www.lilypond.org/doc/v2.17/Documentation/notation/flexible-vertical-spacing-within-systems#spacing-of-non_002dstaff-lines
and in its environment
hth
How can I increase the vertical spacing between lines of chord names and
fret diagrams?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Nov 2013 03:15:34 +
Carl Sorensen wrote:
> Have you read through the Learning Manual? If you're trying to work
> your way through the Notation Reference without having read through
> the Learning Manual, it will be *very* difficult.
S
On 11/1/13 4:35 PM, "Renato" wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Fri, 1 Nov 2013 02:56:17 +
>Carl Sorensen wrote:
>
>>
>>
>> On 10/31/13 8:47 AM, "Renato" wrote:
>>
>>For \markup fret diagram
th "chord diagrams over a
> >staff" scenario):
> >1) use fret-diagram-details to set the various parameters it offers.
> >It would be best to set this once and for all instead of for every
> >single chord
>
> For \markup fret diagrams, you override the fret-diagra
;would be best to set this once and for all instead of for every single
>chord
For \markup fret diagrams, you override the fret-diagram-details property
of a TextScript object (see
http://lilypond.org/doc/v2.16/Documentation/snippets/fretted-strings
Customizing markup fret diagrams):
\overri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, I'd like to produce a sheet with guitar chord diagrams. For now I
have this, which is a good start
\version "2.16.2"
\markup{first set of chords}
\markup{
\fret-diagram #"s:3;f:1;6-x;5-3-1;4-2;3-o;2-1;1-1;"
\fret-diagram #"s:3;f:2;6-x;5-3-1;
On 2/13/12 9:27 PM, "Nick Payne" wrote:
>On 14/02/12 11:50, Carl Sorensen wrote:
>>
>> On 2/13/12 3:13 PM, "Nick Payne" wrote:
>>
>>> If I have a succession of fret diagrams above the chords on a stave,
>>>how
>>> do I al
On 14/02/12 11:50, Carl Sorensen wrote:
On 2/13/12 3:13 PM, "Nick Payne" wrote:
If I have a succession of fret diagrams above the chords on a stave, how
do I align the fret diagrams vertically. In the example below, the chord
names at the top of all three fret diagrams are aligned
On 2/13/12 3:13 PM, "Nick Payne" wrote:
>If I have a succession of fret diagrams above the chords on a stave, how
>do I align the fret diagrams vertically. In the example below, the chord
>names at the top of all three fret diagrams are aligned vertically, but
>the fre
Hi Nick,
On Mon, Feb 13, 2012 at 4:13 PM, Nick Payne wrote:
> If I have a succession of fret diagrams above the chords on a stave, how
> do I align the fret diagrams vertically.
Why not:
\override TextScript #'padding = #1.5
HTH,
David
_
If I have a succession of fret diagrams above the chords on a stave, how
do I align the fret diagrams vertically. In the example below, the chord
names at the top of all three fret diagrams are aligned vertically, but
the fret diagrams for A and C have more space below the chord name and
sit
-table \chordmode{ c'' }
#guitar-tuning
#(chord-shape 'NoTriad guitar-tuning)
<<
\new FretBoards {
\override FretBoard #'fret-diagram-details #'open-string = #" "
\override FretBoard #'fret-diagram-d
Jay Lee mac.com> writes:
> #'(
> (place-fret 4 1 5)
> (place-fret 3 4 ,flatThree)
> (place-fret 2 4 5)
> (place-fret 1 4 "R")
>
On 7/7/11 10:21 PM, "Jay Lee" wrote:
> Neil Puttock gmail.com> writes:
>
>
>> The easiest method is to define the markup first, then insert it into
>> the verbose list:
>>
>> flatSeven = \markup { \concat { \flat 7 } }
>>
>> \markup {
>> \override #'(fret-diagram-details . ((finger-code
Neil Puttock gmail.com> writes:
> The easiest method is to define the markup first, then insert it into
> the verbose list:
>
> flatSeven = \markup { \concat { \flat 7 } }
>
> \markup {
> \override #'(fret-diagram-details . ((finger-code . in-dot)))
> \fret-diagram-verbose #`((place-fret 4
On 7 July 2011 04:36, Jay Lee wrote:
> Anybody? Or is it really not possible?
The easiest method is to define the markup first, then insert it into
the verbose list:
flatSeven = \markup { \concat { \flat 7 } }
\markup {
\override #'(fret-diagram-details . ((finger-code . in-dot)))
\fret-di
Jay Lee mac.com> writes:
>
> Carl Sorensen byu.edu> writes:
>
>
> > And if you want to used a lilypond flat symbol, you can do that as
> well.
> > You'll need to make the fingering a lilypond markup.
>
Anybody? Or is it really not possible?
__
Carl Sorensen byu.edu> writes:
> And if you want to used a lilypond flat symbol, you can do that as
well.
> You'll need to make the fingering a lilypond markup.
I haven't been able to work out the syntax for using the lilypond \flat
symbol in the finger-dot (see elsewhere on this thread wher
Carl Sorensen byu.edu> writes:
>
>
> On 6/29/11 10:13 PM, "Jason Lee" mac.com> wrote:
>
> > Thank you so much!
> >
> > Another question, what about open strings? Can they be marked up
> > individually too with "R", "b3", "b7", etc?
> What did you have in mind?
>
> Carl
>
Ideally, I would
On 6/29/11 10:13 PM, "Jason Lee" wrote:
> Thank you so much!
>
> Another question, what about open strings? Can they be marked up
> individually too with "R", "b3", "b7", etc?
>
Jay,
Please keep these discussions on-list, so all can be kept informed.
The only string labels we have are at
mike apollinemike.com apollinemike.com> writes:
>
> Have you tried
>
> (markup #:flat)
> > (place-fret 4 4 "b7")
Yes. But it doesn't work. I've tried:
(place-fret 4 4 {\flat}7)
(place-fret 4 4 {\flat}"7")
(place-fret 4 4 "{\flat}7")
(place-fret 4 4 \markup{\flat}7)
(place-fret
Have you tried
(markup #:flat)
?
I'm not sure if it'll work, but it's worth a shot!
Cheers,
MS
On Jun 30, 2011, at 3:52 PM, Jay Lee wrote:
> I've tried various kinds of syntax, but can't seem to include the \flat
> symbol.
>
> \addChordShape#'DominantSeventh
> #ukulele
I've tried various kinds of syntax, but can't seem to include the \flat symbol.
\addChordShape #'DominantSeventh
#ukulele-tuning
#'(
(place-fret 4 1 5)
(place-fret 4 4 "b7")
(place-fret 4 6 "R")
(place
Carl
James.
On 30 Jun 2011, at 05:24, "Jay Lee" wrote:
>> I guess we need to add something to the documentation indicating that the
>> fingering in the verbose syntax can be a number, a string, or a lilypond
>> markup.
>>
Let me know what/where as I have a tidy-up patch that I've been noodlin
Carl Sorensen byu.edu> writes:
>
>
> On 6/29/11 5:36 PM, "Jay Lee" mac.com> wrote:
>
> > LilyPonders,
>
> > I would like to be able to re-label the in-dot numbers to use 'b3' and 'b7'
> > instead of '3' and '7' for the flat-third and flat-seventh intervals
> > respectively, and to be able t
On 6/29/11 5:36 PM, "Jay Lee" wrote:
> LilyPonders,
> I would like to be able to re-label the in-dot numbers to use 'b3' and 'b7'
> instead of '3' and '7' for the flat-third and flat-seventh intervals
> respectively, and to be able to use 'R' instead of '1' for the root.
>
> I don't think i
Jay Lee mac.com> writes:
> What I want to do is to change the in-dot finger-code to reflect not
fingerings,
> but scale intervals in scale and arpeggio diagrams of the entire
fretboard or
> part of a fretboard.
Here is the complete example:
\version "2.14.0"
#(define-public ukulele-tuning '
LilyPonders,
I think I'm trying to push LilyPond's fretboard diagrams beyond it's limit in
trying to use fretboards to display scale patterns and intervals rather than
chords and fingerings. So this post is either a request to be able to do
something LilyPond cannot do, or a request to add such fu
Am 12.03.2011 21:39, schrieb Carl Sorensen:
On 3/12/11 1:19 AM, "Marc Hohl" wrote:
Am 11.03.2011 18:52, schrieb Carl Sorensen:
Why not just use a FretBoards context?
Good question; it looked way too complicated for my purposes.
I need some chords played on a mandolin, and there are no
prede
Am 12.03.2011 21:39, schrieb Carl Sorensen:
[...]
[1] Searching the internet, there seems to be the general opinion
that mandolins aren't supposed to play chords at all, but it sounds
cool ;-)
A quick search for "mandolin chords" on google showed lots of places with
chord diagrams for mandolin.
On 3/12/11 1:19 AM, "Marc Hohl" wrote:
> Am 11.03.2011 18:52, schrieb Carl Sorensen:
>> Why not just use a FretBoards context?
>>
> Good question; it looked way too complicated for my purposes.
> I need some chords played on a mandolin, and there are no
> predefined fretboard diagrams for mando
Am 11.03.2011 18:52, schrieb Carl Sorensen:
On 3/11/11 2:34 AM, "Marc Hohl" wrote:
Am 10.03.2011 19:52, schrieb Keith OHara:
Marc Hohl hohlart.de> writes:
I try to put fret diagrams at the beginning of a piece.
My input file looks like this:
<<
\new Ch
On 3/11/11 2:34 AM, "Marc Hohl" wrote:
> Am 10.03.2011 19:52, schrieb Keith OHara:
>> Marc Hohl hohlart.de> writes:
>>> I try to put fret diagrams at the beginning of a piece.
>>> My input file looks like this:
>>>
>>>
Am 10.03.2011 19:52, schrieb Keith OHara:
Marc Hohl hohlart.de> writes:
I try to put fret diagrams at the beginning of a piece.
My input file looks like this:
<<
\new ChordNames \chordmode {
g:m
}
\new Lyrics \lyricmode {
\markup { \fret-diagram #&
Marc Hohl hohlart.de> writes:
>
> I try to put fret diagrams at the beginning of a piece.
> My input file looks like this:
>
> <<
> \new ChordNames \chordmode {
>g:m
> }
> \new Lyrics \lyricmode {
>\marku
- Original Message -
From: "Marc Hohl"
To: "Lilypond-User"
Sent: Wednesday, March 09, 2011 9:26 AM
Subject: Putting fret diagrams in a separate score
Hello list,
I try to put fret diagrams at the beginning of a piece.
My input file looks like this:
\versi
1 - 100 of 157 matches
Mail list logo
