2015-05-31 23:22 GMT+02:00 Frank D. Engel, Jr. <[email protected]>: > > > On 5/31/2015 16:22, Thomas Morley wrote: >> >> 2015-05-29 1:43 GMT+02:00 Frank D. Engel, Jr. <[email protected]>: >>> >>> >>> On 5/26/2015 18:27, Thomas Morley wrote: >>>> >>>> 2015-05-26 23:37 GMT+02:00 Frank D. Engel, Jr. <[email protected]>: >>>>> >>>>> I have not been able to identify any syntax from which to build such an >>>>> example. >>>>> >>>>> I can only see barre syntax which even comes close. >>>>> >>>>> What I am looking for is a barre that looks like a capo but only on >>>>> some >>>>> strings. >>>>> >>>>> It should also stay inside the diagram and not wind up floating above >>>>> it. >>>>> >>>>> >>>>> On 5/26/2015 09:54, Thomas Morley wrote: >>>>>> >>>>>> 2015-05-26 0:44 GMT+02:00 Frank Engel <[email protected]>: >>>>>>> >>>>>>> Fretboard diagrams cannot currently be limited to a range of strings. >>>>>>> >>>>>>> Ideally there should be the ability to show multiple such capos (this >>>>>>> is >>>>>>> done). >>>>>>> >>>>>>> >>>>>>> My suggested syntax for this would be something like "barre": >>>>>>> >>>>>>> (partial-capo 5 3 2) >>>>>>> >>>>>>> >>>>>>> Examples of existing diagrams: >>>>>>> >>>>>>> http://members.myactv.net/~s.wriston/media/CUT_CAPO_CHORD_CHART.pdf >>>>>>> http://www.thirdhandcapo.com/basics.html >>>>>> >>>>>> >>>>>> >>>>>> Hi Frank, >>>>>> >>>>>> as far as I can see LilyPond can do already all what your links >>>>>> demonstrate. >>>>>> Maybe I'm missing something. >>>>>> Please provide a code-example where LilyPond fails. >>>>>> >>>>>> Cheers, >>>>>> Harm >>>>>> >>>> Please look at the output from (maybe uncommentthe commented lines): >>>> >>>> \markup >>>> \override #'(fret-diagram-details . ((barre-type . straight))) >>>> \fret-diagram-verbose >>>> #'((barre 6 5 5) >>>> ;(place-fret 6 5 2) >>>> ;(place-fret 5 5 2) >>>> (place-fret 4 4 1) >>>> ;(place-fret 3 5 3) >>>> ;(place-fret 2 5 3) >>>> ;(place-fret 1 5 3) >>>> (barre 3 1 5)) >>>> >>>> Isn't it what you want? >>>> >>>> Cheers, >>>> Harm >>>> >>> ok, the straight barre line gets me fairly close... >>> >>> Is there a way to make it thicker? >>> >>> Is there a way to combine this with the other barre type (without making >>> that one thicker) so that I can show barre chords in combination with the >>> capo image? >> >> Look at the example below (yes, it's quite silly, though, we can watch >> what happens) >> >> \markup >> \override #'(fret-diagram-details . >> ( >> (barre-type . straight) >> (dot-radius . 0.4) >> (capo-thickness . 0.5) >> )) >> \fret-diagram-verbose >> #'((barre 5 3 2) >> (mute 6) >> (capo 1) >> (barre 4 3 4) >> (place-fret 5 6) >> (place-fret 4 4) >> (place-fret 3 4) >> ) >> >> capo-thickness can be set independently >> dot-radius is used for dots _and_ for the thickness of barre. >> We could implement an additional property to control the thickness of >> barre. >> Though, have a look at >> >> http://www.lilypond.org/doc/v2.19/Documentation/internals/fret_002ddiagram_002dinterface >> We already have 24(!) properties controlling in fret-diagram-details >> >> Do we really need another one? >> What does others think? >> >>> >>> Regardless, one place this seems to break down is that the dots make it >>> look >>> like a finger should be there (where there is a capo), and without the >>> dots, >>> this gives me some rather strange results: >>> >>> \markup >>> \override #'(fret-diagram-details . ((barre-type . straight))) >>> \fret-diagram-verbose >>> #'((barre 5 3 2) >>> (mute 6) >>> (place-fret 5 6) >>> (place-fret 4 4) >>> (place-fret 3 4) >>> ) >> >> Clearly a bug. >> I fixed it already locally, will create a tracker-issue and provide a >> patch, asap >> >> >> Cheers, >> Harm >> > > Fixing that bug would be the biggest thing for me. Being able to make the > barre the thickness of the capo instead of the thickness of the dots would > be a huge plus if possible, but I think I can live with it being smaller if > I need to. > > Being able to mix barre types (and thicknesses) would be nice, but I can > much more easily live without that one - a "nice to have" but not really a > major need. > > > Thank you! > >
https://code.google.com/p/lilypond/issues/detail?id=4428 _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
