Re: guitar position indication

bart deruyter schrieb: >Hey, > >thanks :-), it did the trick indeed, I renamed to firstpos, secondpos, >etc... > >with all those libraries, creating namingconventions becomes critical, >certainly when the editor adds more functionality. > >I didn't even know frescobaldi adds this functionality w

Re: guitar position indication

Hey, thanks :-), it did the trick indeed, I renamed to firstpos, secondpos, etc... with all those libraries, creating namingconventions becomes critical, certainly when the editor adds more functionality. I didn't even know frescobaldi adds this functionality with built-in lilypond code. I'm not

Re: guitar position indication

Hi Bart, 2013/12/23 bart deruyter : > Urs, > > no problem, I have what I've got in attachment here, and the second file > added is a file as reusable library of stuff, including things I've learned > in this conversation. The cause of the error could be in there too. it is. control-points are cod

Re: guitar position indication

Urs, no problem, I have what I've got in attachment here, and the second file added is a file as reusable library of stuff, including things I've learned in this conversation. The cause of the error could be in there too. I've now tried to render the sample code of Simon with control points, and

Re: guitar position indication

Am 23.12.2013 15:18, schrieb Federico Bruni: 2013/12/23 bart deruyter Federico, thanks for the info. I just tried it, compiled the file but I get the same error. can you compile the lilypond file "normally", without any layout control option? anyway, you'd better write to the frescobaldi m

Re: guitar position indication

2013/12/23 bart deruyter > Federico, thanks for the info. > > I just tried it, compiled the file but I get the same error. > can you compile the lilypond file "normally", without any layout control option? anyway, you'd better write to the frescobaldi mailing list (unless Urs jumps in this threa

Re: guitar position indication

Federico, thanks for the info. I just tried it, compiled the file but I get the same error. grtz, Bart http://www.bartart3d.be/ On facebook On Twitter On Identi.ca On G

Re: guitar position indication

2013/12/23 bart deruyter > according to the lilypond output the error occurs in: > > > /usr/local/lib/python2.7/dist-packages/frescobaldi_app/preview_mode/display-control-points.ily:108:37: > Wrong type to apply: (# > (# (# (layout props arg)> (# "II" > > > a bug? > this is a frescobaldi err

Re: guitar position indication

Hi Bart, On Mon, Dec 23, 2013 at 4:43 AM, bart deruyter wrote: > hi, > > I've tried the solution from Simon, works very well, with one minor point. > In frescobaldi, when rendering with the option to have controlepoints > enabled, I get errors and rendering stops. > > rendering without control p

Re: guitar position indication

hi, I've tried the solution from Simon, works very well, with one minor point. In frescobaldi, when rendering with the option to have controlepoints enabled, I get errors and rendering stops. rendering without control points works fine. according to the lilypond output the error occurs in: /usr

Re: guitar position indication

Hello I prefer this : %%caseSpanner #"case" note\startTextSpan note note\stopTextSpan %%CUTE===CUTE caseSpanner = #(define-music-function (parser location str)(string?) #{ \once \override TextSpanner.style = #'line %or dashed-line \once \override TextSpanner.s

Re: guitar position indication

You could define a function that formats its argument the way you want it to look. On Dec 18, 2013, at 9:21 AM, bart deruyter wrote: > Hi all, > > I'm working on a piece for guitar here where in some parts I want to show the > position it is played in (e.g. IV, forth position) . > > I know

Re: guitar position indication

bart deruyter writes: > Thanks for the tips, Simon's solution seems to be the best. Thank you very > much :-D . > > @David Kastrup: > I didn't know \endSpanners. It's an interesting solution, but it adds a > spanner line up to the next note in my case. At least here it does with > lilypond 2.17.9

Re: guitar position indication

On Wed, Dec 18, 2013 at 5:12 PM, bart deruyter wrote: > Thanks for the tips, Simon's solution seems to be the best. Thank you very > much :-D . > you're welcome. i'll be needing this function in the next month or so, so it didn't hurt that you asked... :D > @David Kastrup: > I didn't know \endS

Re: guitar position indication

Thanks for the tips, Simon's solution seems to be the best. Thank you very much :-D . @David Kastrup: I didn't know \endSpanners. It's an interesting solution, but it adds a spanner line up to the next note in my case. At least here it does with lilypond 2.17.97. I read in the manual it should not

Re: guitar position indication

On Wed, Dec 18, 2013 at 3:59 PM, David Kastrup wrote: > bart deruyter writes: > > <...SNIPPETY SNIP...> > > consistent way of indicating a position, without having to rely on > spanners? > > What's wrong with spanners? > > You know about \endSpanners ? > THAT is a cool trick. 10 years of lilypo

Re: guitar position indication

bart deruyter writes: > Hi all, > > I'm working on a piece for guitar here where in some parts I want to show > the position it is played in (e.g. IV, forth position) . > > I know I have to use textspanners for this, but this is intended for > 'spanning over a melody'. What should be used if ther

guitar position indication

Hi all, I'm working on a piece for guitar here where in some parts I want to show the position it is played in (e.g. IV, forth position) . I know I have to use textspanners for this, but this is intended for 'spanning over a melody'. What should be used if there is only one note? Instinctivly I