Re: No string for pitch #Pitch (SOLVED)
On 11/20/09 8:58 PM, Jesús Guillermo Andrade gandr...@usermail.com wrote: Got the prick little b... It was as Carl initially suggested. I made a minimal example and found that there was a problem with the model for the string tuning function. Thanks a lot... There was also a bug in the code that you found for me. It's been fixed in git. You don't need to get the latest, as the warning is harmless. But your code would not generate the warning even with the wrong octave in the latest version of LilyPond. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: No string for pitch #Pitch (SOLVED)
Got the prick little b... It was as Carl initially suggested. I made a minimal example and found that there was a problem with the model for the string tuning function. Thanks a lot... El 20/11/2009, a las 10:31 p.m., Jesús Guillermo Andrade escribió: Yes... definitely except for the little fact that if I change the chords from their original positions, then the fretboard is incorrect... the finger positions change one fret up. So... what is the logic behind it? If the chord is in the correct pitch the frets are ok, but I get what you called the octavation error. Something is wrong here ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
