Fwd: \bar "" as discretionary break point without affecting spacing

2020-12-21 Thread Daniel Tobias Johansen Langhoff
Thank you!

I ended up doing this because I want the breath marks to be a bit off
the right edge.


\version "2.20.0"

lineEnd = {
  \once \override BreathingSign.space-alist.staff-bar = #'(minimum-space . 0)
  \once \override BreathingSign.space-alist.right-edge = #'(extra-space . 1.0)
  \breathe \bar ""
}

\score {
  \relative a' {
\override Score.BarLine.break-visibility = #end-of-line-invisible
\omit Score.TimeSignature
\cadenzaOn
\repeat unfold 5 {
  \repeat unfold 8 { a4 } \lineEnd
}
\repeat unfold 8 { a4 }
\revert Score.BarLine.break-visibility
\bar "|."
  }
}


On Mon, Dec 21, 2020 at 5:50 PM Aaron Hill  wrote:
>
> On 2020-12-21 4:25 am, Daniel Tobias Johansen Langhoff wrote:
> > Hi!
> >
> > I have some unmetered music in which I want to put discretionary line
> > breaks at the end of verse lines. Currently I am using \bar "". This
> > however, affects the spacing, most notably the position of the breath
> > marks. Is there any way to achieve this without spacing issues?
> >
> > lineEnd = { \breathe \bar "" }
> >
> > \score {
> >   \relative f' {
> > \key f \major
> > \omit Score.TimeSignature
> > \cadenzaOn
> > f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
> > a4 a2 g4 bes4( a) g4 f2( e4) f2 \lineEnd
> > f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
> >   }
> > }
>
> Does this help?
>
> 
> \version "2.20.0"
>
> lineEnd = {
>\once \override BreathingSign.space-alist =
>#(grob-transformer 'space-alist
>  (lambda (grob orig)
>   (assoc-set! orig 'staff-bar '(minimum-space . 0
>\breathe
>\bar ""
> }
>
> \score {
>\relative f' {
>  \key f \major
>  \omit Score.TimeSignature
>  \cadenzaOn
>  f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
>  a4 a2 g4 bes4( a) g4 f2( e4) f2 \lineEnd
>  f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
>}
> }
> 
>
>
> -- Aaron Hill



Re: I hope this is on topic, pdf indications

2020-12-21 Thread Robin Bannister

  jh wrote:

Hello-
I'm still using 2.18.2
And my PDF 'reader' is Sumatra.  Until I did an upgrade of Sumatra when
my cursor was hovering over a note there was information about where in
the .ly file this note was.
After the upgrade this no longer happens.  What could be the disconnect
between the two?



Your problem seems to be that LilyPond has stopped generating the 
point-and-clicks entries in the pdf. Check out

http://lilypond.org/doc/v2.21/Documentation/usage/configuring-the-system-for-point-and-click#enabling-point-and-click


The upgrade might have overwritten your sumatrapdfrestrict.ini file.
Its white list for link protocols may no longer have a 'textedit' entry.
But that wouldn't stop you being able to read the indications.


Caveat:  I am not running the latest Sumatra version.


Cheers,
Robin



Re: Cowell clusters

2020-12-21 Thread Klaus Blum

Hi Gilberto,

Am 21.12.2020 um 17:51 schrieb lilypond-user-requ...@gnu.org:


Ideally, I think applying it to a chord (something like \cowellCluster
4) would be the ideal solution. It also does not handle whole
notes, as those do not have stems to be hacked. If I come up with
something interesting I will make sure to post it here.


please have a look at the link to the German forum (the thread there
continues in English):
https://lilypondforum.de/index.php/topic,820.msg4546.html?PHPSESSID=6djk9rm3a7m81mmuqu25mjiehb#msg4546

I've posted an improved version there, and Harm has an even more
interesting solution.

Cheers,
Klaus



I hope this is on topic, pdf indications

2020-12-21 Thread jh

Hello-
I'm still using 2.18.2
And my PDF 'reader' is Sumatra.  Until I did an upgrade of Sumatra when 
my cursor was hovering over a note there was information about where in 
the .ly file this note was.
After the upgrade this no longer happens.  What could be the disconnect 
between the two?
I understand that if I used Fresco this would not be an issue (well it 
might be I'm not fond of the appearance of Fresco but use it 
infrequently to find an issue I can't find on my own) but between PSPad 
that I use to write .ly's and this pdf reader it worked fine and doesn't 
now.  If you think it's the PSPad and that I should fall back to 
notepad+ or something tell me that or?

this is a win7pro machine and very old (2007) if that's relevant.

If this is a mystery to just live with telling me that would be helpful 
too.

Jay

--
Thank you Sound & Silence POB 4833 Seattle, Wa 98194 206-328-7694
www.soundand.com

I am looking for 2-3 dancers various abilities/disciplines for a piece
Called The Box it was scheduled for November  but we know how that has
gone. However I am interested in making videos of the moves and having
dancers work on them and the music before we can get into the same
room... Paid rehearsals and the door divided evenly by participants.
Spread the word please.



Re: Articulation mark & slur placement

2020-12-21 Thread Thomas Morley
Am Mo., 21. Dez. 2020 um 17:58 Uhr schrieb Xavier Scheuer :
>
> On Sun, 20 Dec 2020 at 16:31, Michael Seifert  wrote:
> >
> > Well, if we’re doing everything the way Elaine Gould wants us to, 
> > then:
> >
> > - articulation should go generally go next to the notehead, not 
> > next to the stem; but
> > - the marcato mark usually goes above the staff, regardless of stem 
> > direction.  (Note: not directly above the stemm, but above the staff).
> >
> > So one could fix the problem for up-stemmed notes simply by putting the 
> > marcato accent above the staff (and tweaking its vertical placement.)  But 
> > the problem would remain for the same snippet an octave higher, with 
> > down-stemmed notes.
> >
> > Interestingly, the accent mark > *does* behave the way I want it to 
> > in the code below.  Effectively, I want the marcato mark (and the “staccato 
> > wedge”) to behave like the accent mark in the code below, rather than 
> > behaving like the staccato or tenuto marks.
> >
> > \relative c' {
> > d'4-^( e4 f4-.) r4
> > d4->( e4 f4-.) r4
> > d4-.( e4 f4-.) r4
> > d4--( e4 f4-.) r4
> > d4-!( e4 f4-.) r4
> > }
> >
>
> Hello Mike,
>
> I thought changing the avoid-slur property of marcato and staccatissimo 
> scripts from inside (default) to around (value for accent) would give the 
> behavior you want.
> But this does not work, the output is totally different and I have many 
> programmation errors: script direction not yet known.
> The problem also exhibits with accent, whereas I just copied the default 
> (unmodified) settings!
> A bug?
>
> #(define my-script-alist

Hi Xavier,

I didn't follow this thread, thus I don't know whether the output is
as intended.
Nevertheless,  you need to quasiquote your additions, i.e.

(append `(

Cheers,
  Harm

>(append '(
>   ("accent"
> (avoid-slur . around)
> (padding . 0.20)
> (script-stencil . (feta . ("sforzato" . "sforzato")))
> (side-relative-direction . ,DOWN))
>   ("marcato"
> (script-stencil . (feta . ("dmarcato" . "umarcato")))
> (padding . 0.20)
> (avoid-slur . around)
> ;;(staff-padding . ())
> (quantize-position . #t)
> (side-relative-direction . ,DOWN))
>   ("staccatissimo"
> (avoid-slur . around)
> (quantize-position . #t)
> (script-stencil . (feta . ("dstaccatissimo" . 
> "ustaccatissimo")))
> (padding . 0.20)
> (skyline-horizontal-padding . 0.10)
> (side-relative-direction . ,DOWN)
> (toward-stem-shift . 1.0)
> (toward-stem-shift-in-column . 0.0))
>   ) default-script-alist)
>)
>
> \layout {
>   \context {
> \Score
> scriptDefinitions = #my-script-alist
>   }
> }
>
> \relative c' {
>   d'4-^( e4 f4-.) r4
>   d4->( e4 f4-.) r4
>   d4-.( e4 f4-.) r4
>   d4--( e4 f4-.) r4
>   d4-!( e4 f4-.) r4
> }
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer 
>



Re: Articulation mark & slur placement

2020-12-21 Thread Xavier Scheuer
On Sun, 20 Dec 2020 at 16:31, Michael Seifert  wrote:
>
> Well, if we’re doing everything the way Elaine Gould wants us to,
then:
>
> - articulation should go generally go next to the notehead, not
next to the stem; but
> - the marcato mark usually goes above the staff, regardless of
stem direction.  (Note: not directly above the stemm, but above the staff).
>
> So one could fix the problem for up-stemmed notes simply by putting the
marcato accent above the staff (and tweaking its vertical placement.)  But
the problem would remain for the same snippet an octave higher, with
down-stemmed notes.
>
> Interestingly, the accent mark > *does* behave the way I want it
to in the code below.  Effectively, I want the marcato mark (and the
“staccato wedge”) to behave like the accent mark in the code below, rather
than behaving like the staccato or tenuto marks.
>
> \relative c' {
> d'4-^( e4 f4-.) r4
> d4->( e4 f4-.) r4
> d4-.( e4 f4-.) r4
> d4--( e4 f4-.) r4
> d4-!( e4 f4-.) r4
> }
>

Hello Mike,

I thought changing the avoid-slur property of marcato and staccatissimo
scripts from inside (default) to around (value for accent) would give the
behavior you want.
But this does not work, the output is totally different and I have many
programmation errors: script direction not yet known.
The problem also exhibits with accent, whereas I just copied the default
(unmodified) settings!
A bug?

#(define my-script-alist
   (append '(
  ("accent"
(avoid-slur . around)
(padding . 0.20)
(script-stencil . (feta . ("sforzato" . "sforzato")))
(side-relative-direction . ,DOWN))
  ("marcato"
(script-stencil . (feta . ("dmarcato" . "umarcato")))
(padding . 0.20)
(avoid-slur . around)
;;(staff-padding . ())
(quantize-position . #t)
(side-relative-direction . ,DOWN))
  ("staccatissimo"
(avoid-slur . around)
(quantize-position . #t)
(script-stencil . (feta . ("dstaccatissimo" .
"ustaccatissimo")))
(padding . 0.20)
(skyline-horizontal-padding . 0.10)
(side-relative-direction . ,DOWN)
(toward-stem-shift . 1.0)
(toward-stem-shift-in-column . 0.0))
  ) default-script-alist)
   )

\layout {
  \context {
\Score
scriptDefinitions = #my-script-alist
  }
}

\relative c' {
  d'4-^( e4 f4-.) r4
  d4->( e4 f4-.) r4
  d4-.( e4 f4-.) r4
  d4--( e4 f4-.) r4
  d4-!( e4 f4-.) r4
}

Cheers,
Xavier

-- 
Xavier Scheuer 


Re: \bar "" as discretionary break point without affecting spacing

2020-12-21 Thread Aaron Hill

On 2020-12-21 4:25 am, Daniel Tobias Johansen Langhoff wrote:

Hi!

I have some unmetered music in which I want to put discretionary line
breaks at the end of verse lines. Currently I am using \bar "". This
however, affects the spacing, most notably the position of the breath
marks. Is there any way to achieve this without spacing issues?

lineEnd = { \breathe \bar "" }

\score {
  \relative f' {
\key f \major
\omit Score.TimeSignature
\cadenzaOn
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
a4 a2 g4 bes4( a) g4 f2( e4) f2 \lineEnd
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
  }
}


Does this help?


\version "2.20.0"

lineEnd = {
  \once \override BreathingSign.space-alist =
  #(grob-transformer 'space-alist
(lambda (grob orig)
 (assoc-set! orig 'staff-bar '(minimum-space . 0
  \breathe
  \bar ""
}

\score {
  \relative f' {
\key f \major
\omit Score.TimeSignature
\cadenzaOn
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
a4 a2 g4 bes4( a) g4 f2( e4) f2 \lineEnd
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
  }
}



-- Aaron Hill



\bar "" as discretionary break point without affecting spacing

2020-12-21 Thread Daniel Tobias Johansen Langhoff
Hi!

I have some unmetered music in which I want to put discretionary line
breaks at the end of verse lines. Currently I am using \bar "". This
however, affects the spacing, most notably the position of the breath
marks. Is there any way to achieve this without spacing issues?

lineEnd = { \breathe \bar "" }

\score {
  \relative f' {
\key f \major
\omit Score.TimeSignature
\cadenzaOn
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
a4 a2 g4 bes4( a) g4 f2( e4) f2 \lineEnd
f4 a2 bes4 c2 bes4 a2 g4 a2 \lineEnd
  }
}

Kind regards,
Daniel Tobias



Re: Dynamic text vertical positioning issue

2020-12-21 Thread Aaron Hill

On 2020-12-20 9:35 pm, Ahanu Banerjee wrote:
In the following example, dynamic text does not vertically reposition 
when
"+" marking (i.e., left-hand pizzicato) is given vertical offset. 
Please

advise if I have missed an obvious solution. Thanks!

\version "2.20.0"
{
  % dynamic text has wrong vertical position:
  \stemDown e'-\tweak extra-offset #'(0.3 . 1.5) _+ \p
  % expected behaviour:
  e'_1\p
}


extra-offset is what it says: "extra".  Its effect happens *after* all 
other layout logic is performed.


You instead need to adjust the X-offset and Y-offset properties:


\version "2.20.0"
{
  \stemDown
  e' -\offset X-offset #0.3
 -\offset Y-offset #1.5
 _+ \p
  e' _1 \p
}



-- Aaron Hill