Re: No string for pitch #<Pitch

[Carl Sorensen]

On 11/19/09 5:59 AM, "Jesús Guillermo Andrade" <address@hidden>
wrote:

> David:
> El 18/11/2009, a las 02:51 a.m., David Kastrup escribió:
> 
>> Sounds like Lilypond is running out of strings for the given chords.
>> Just a wild guess.
> 
> Yes.. it is kind of shocking right?. But fact is that the notes listed
> by lilypond, I have surmised, are part of the chords I have already
> specified using this method:
> 
> %(define-public cuatro-tuning '(4 -1 -5 -10 -15 -20))
> cuatrotuning = #'(11 18 14 9)
> %%  C chords
> 
> \storePredefinedDiagram \chordmode {c}
>                          #cuatrotuning
>                          #"3-3;2-2;1-1-(;1-1-);"
> \storePredefinedDiagram \chordmode {c:7}
>                          #cuatrotuning
>                          #"1-1-(;2-2;;1-1-);"

Have you tested this terse-mode string to make sure it works properly?  I'm
not positive what the behavior of the fret-diagram code is given a missing
fret number for a string.  I suppose it should default to 0, but I'm not
positive it does.  And right now my time is limited so I can't test it for a
few days.

> 
> Then, after storing several chords of the same id as before (i.e. c, c:
> 7 etc) in the harmonies variable, I used this form to make the
> conversion into good frets:
> 
>   \new FretBoards {
>        \set stringTunings = #cuatrotuning
>        \override FretBoard
>          #'(fret-diagram-details string-count) = #'4
>        \override FretBoard
>          #'(fret-diagram-details finger-code) = #'in-dot
>        \harmonies
>         }
> 
> So... the only thing that comes to my mind is that lilypond, somehow,
> constructs these chords as it sees fit (in terms of octave placement)
> then checks if all notes CAN or COULD be played by the strings. if the
> pitch is out of range, then it prints the warning. All that said,
> though, it should be possible to force lilypond into not going up, but
> down the neck of the instrument.
> Now: any ideas?

Somehow the chord you are calling is not one of the predefined diagrams,
perhaps because the octave is wrong.  The predefined diagrams are octave
specific; if the music is more than an octave away from the predefined
diagrams, the predefined diagram will not be used.

If the chord is one of the predefined diagrams, the code that creates the
error message you have seen is never used.

The error message you have seen is caused when LilyPond is trying to
calculate its own fret diagram based on the pitches.

If you will get a minimal example (e.g. one chord) that shows the problem,
then I will be able to figure out what's going on.

HTH,

Carl