Re: no line for textspanner

2010-08-01 Thread Neil Puttock
On 31 July 2010 18:44, Xavier Scheuer  wrote:

> Maybe you could also modify the doc NR 1.3.1 Dynamics, the snippet
> "Hiding the extender line for text dynamics", to replace
>
>  \override DynamicTextSpanner #'dash-period = #-1.0
>
> by
>
>  \override DynamicTextSpanner #'style = #'none

Thanks, I'd forgotten about that snippet.  I'll add a convert rule
deprecating the use of 'dash-period, so it'll be converted
automatically during the next LSR update.

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


strange midi problem

2010-08-01 Thread Federico Bruni
Hi,

I have a strange issue (see attached minimal example).

I'm using a guitar tuning where 6th and 5th string are tuned 1 fret down
(DGDGBE).

The harmonic over 7th fret of 4th string (an a) is displayed correctly
(on 7th fret) only if I use a(n incorrect) lower pitch. Otherwise it's 1
pitch up... and I get a <19> on TabStaff.

The curious thing is that, if I use the lower pitch, it displays the
note as being on 4th string, while it would be actually on 6th string.

I hope the example will make it more clear (look at second voice).

Am I missing something?

Thanks,
Federico
\version "2.13"


global = {
  \key g \major
  \time 4/4
  \set Staff.midiInstrument = #"acoustic guitar (steel)"
  %% tuning: DGDGBE
  \set TabStaff.stringTunings = #'(4 -1 -5 -10 -17 -22)
}

first =  \relative c'' {
  \global

  %% 1
  \repeat volta 2 {
  s16~
  \once \override HarmonicParenthesesItem #'stencil = ##f 
 
  
  ~
  \once \override HarmonicParenthesesItem #'stencil = ##f 
  |
  }
  
  
}

second =  \relative c' {
  \global

  %% 1
  4 % right pitch in midi but wrong fret in TabStaff
  
   % right fret in TabStaff but wrong pitch in midi
   % here I should have put a g,
}



\score {
  \new StaffGroup <<
\new Staff = "guitar" <<
  \context Voice = "first voice" { \clef "G_8" \voiceOne  \first }
  \context Voice = "second voice" { \clef "G_8" \voiceTwo  \second }
>>
\new TabStaff = "tab" <<
  \context TabVoice = "tab first voice" { \clef "moderntab" \voiceOne \first }
  \context TabVoice = "tab second voice" { \clef "moderntab" \voiceTwo \second }
>>
  >>

  \layout {
indent = #0
\context {
  \Staff
  \override StringNumber #'transparent = ##t
}
  }
  \midi {
\context {
  \Score tempoWholesPerMinute = #(ly:make-moment 80 4)
}
  }
}___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


TextSpanner and line thickness

2010-08-01 Thread Mike Solomon
Hey all,
I'm working on a piece where the thickness of a text spanner represents
playing intensity, and in writing it, I'm realizing that the thickness of
text spanners has an effect on their X extents (see the minimal example
below).  This is due (I think) to the round-cap line ending.  I would gladly
use non-rounded lines so that they stop consistently at the same horizontal
spot independent of their thickness.  Before I dive into my git repository
to cobble together a solution, if any of you know a way to get around this
problem by standardizing the horizontal lengths of text spanners, I'd
appreciate it!

~Mike

***
\version "2.13.29"

\relative c' {
\override TextSpanner #'style = #'solid-line
\override TextSpanner #'thickness = #10
a b c d\startTextSpan
a b c d
a b c d\stopTextSpan
a b\startTextSpan
a b c d
a b c d\stopTextSpan
}

\relative c' {
\override TextSpanner #'style = #'solid-line
\override TextSpanner #'thickness = #20
a b c d\startTextSpan
a b c d
a b c d\stopTextSpan
a b\startTextSpan
a b c d
a b c d\stopTextSpan
}

\relative c' {
\override TextSpanner #'style = #'solid-line
\override TextSpanner #'thickness = #50
a b c d\startTextSpan
a b c d
a b c d\stopTextSpan
a b\startTextSpan
a b c d
a b c d\stopTextSpan
}

\relative c' {
\override TextSpanner #'style = #'solid-line
\override TextSpanner #'thickness = #100
a b c d\startTextSpan
a b c d
a b c d\stopTextSpan
a b\startTextSpan
a b c d
a b c d\stopTextSpan
}



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Slurs at line breaks

2010-08-01 Thread Jonas Müthing

Hi Jethro,

thanks for that idea. However, I would have to do that everytime I do  
a new version of the file. Is there maybe another way to shorten Slurs  
and Ties before/after linebreaks?


Greetings,

Jonas


Am 27.07.2010 um 22:08 schrieb Jethro Van Thuyne:


On Tue, 27 Jul 2010 21:59:52 +0200, Jonas Müthing wrote:

When a slur goes over more than one line, the lilypond prints the  
slur
into the last bar line and starts the slur on the next line very  
close

to the key signature. I would like to change this an achieve a result
similair to the tie-behaviour. Is there any way to do so?


Hi Jonas,

Although it might not be very relevant for the Lilypond list code- 
wise, I

generally solve these kind of (minor) flaws in Inkscape, using the SVG
output. Simply because it's the fastest way.

lilypond -dbackend=svg score.ly

Best regards,

Jethro.




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: TextSpanner and line thickness

2010-08-01 Thread Neil Puttock
On 1 August 2010 09:40, Mike Solomon  wrote:

>    I'm working on a piece where the thickness of a text spanner represents
> playing intensity, and in writing it, I'm realizing that the thickness of
> text spanners has an effect on their X extents (see the minimal example
> below).  This is due (I think) to the round-cap line ending.  I would gladly
> use non-rounded lines so that they stop consistently at the same horizontal
> spot independent of their thickness.  Before I dive into my git repository
> to cobble together a solution, if any of you know a way to get around this
> problem by standardizing the horizontal lengths of text spanners, I'd
> appreciate it!

I think the simplest way around this is to emend the drawing routine
to remove the round-cap ending.

Unfortunately, the extent box assumes the line's rounded, so there's a
hard-coded widening in line-interface.cc.  Your best bet is to change
the default X-extent callback to remove it:

\override TextSpanner #'X-extent =
#(lambda (grob)
   (let ((thick (* (ly:grob-property grob 'thickness)
   (ly:staff-symbol-line-thickness grob)))
 (ext (ly:grob::stencil-width grob)))
 (interval-widen ext (/ thick -2

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user