Re: [ANN] LilyQuick 0.92beta

2017-03-29 Thread Vaughan McAlley 
On 29 Mar 2017 11:46 a.m., "tisimst"  wrote:

Hi, Vaughan!

On Tue, Mar 28, 2017 at 6:36 PM, Vaughan McAlley [via Lilypond] <[hidden
email] > wrote:

> Greetings,
>
> I’m happy to announce LilyQuick 0.92beta. The main feature is
> (hopefully) simpler installation with (hopefully) clearer
> documentation. As well, LilyQuick can now automatically quit Qsynth
> when it quits. Enjoy!
>

Congrats! This is exciting! I would love to see a short video of this in
use to have a better grasp for the time savings over manual entry. Any
chance you can be convinced to put something together and post it on
YouTube?

Best,
Abraham

--
View this message in context: Re: [ANN] LilyQuick 0.92beta

Sent from the User mailing list archive
 at Nabble.com.

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


Hi Abraham,

That's a good idea. I'll look into it. I'll have to find a time when the
kids aren't in to avoid a repeat of the BBC Korea interview :-)

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

Re: Rootless slash chords, 2017 edition

2017-03-29 Thread Thomas Morley 
2017-03-28 19:49 GMT+02:00 Thomas Morley :
> 2017-03-28 0:39 GMT+02:00 Dmitry :

>> - in Chord_name_engraver::process_music, track repeating root parts of
>> slash chords and pass NIL pitches to a chordNameFunction in case of
>> repetition. Everything should be similar to handling chordChanges,
>> however this time we should remember and compare whole chord
>> structures, not markup.

>
> %% Tries to compare the relevant parts of the markups for current and previous
> %% chord.
> %%
> %% Probably it would be far easier to compare actual pitches

Below some code actually tracking and comparing pitches.
The bass-only feature can be switched on/off.
One limitation persists, inversions are not recognized, see third example.

\version "2.19.57"

#(define (define-translator-property symbol type? description)
  (if (not (and (symbol? symbol)
(procedure? type?)
(string? description)))
  (ly:error "error in call of define-translator-property"))
  (if (not (equal? (object-property symbol 'translation-doc) #f))
  (ly:error (_ "symbol ~S redefined") symbol))

  (set-object-property! symbol 'translation-type? type?)
  (set-object-property! symbol 'translation-doc description)
  symbol)

#(for-each
  (lambda (x)
(apply define-translator-property x))
`(
  (dropEqualRoot
   ,boolean?
   "To be used in @code{ChordName}-context.  If set @code{#t}, successive
chords, which differ only in their bass, will have only this bass printed.")
   ))

#(define (test-engraver ctx)
  (let ((prev '())
(notes '())
(chord-name-grobs '()))
(make-engraver
  (listeners
 ((note-event engraver ev)
   (set! notes (cons (ly:prob-property ev 'music-cause) notes
  (acknowledgers
 ((chord-name-interface engraver grob source-engraver)
(set! chord-name-grobs (cons grob chord-name-grobs
  ((stop-translation-timestep translator)
 (let* (;; not sure yet, whether 'sorted-notes' is needed and should
;; replace 'notes' in 'current-bass+elts'
;(sorted-notes
;  (sort
;notes
;  (lambda (n1 n2)
;(ly:pitchmarkup (caar current-bass+elts) #f)
 (set! prev current-bass+elts)
 (set! chord-name-grobs '())
 (set! notes '(
  ((finalize translator)
 (set! prev '())

%
%%
%% EXAMPLES
%%
%

\paper {
  indent = 0
  ragged-right = ##f
}

\layout {
  \context {
  \Score
  \override RehearsalMark.self-alignment-X = #LEFT
  }
  \context {
\Staff
\accidentalStyle forget
  }
  \context {
\ChordNames
dropEqualRoot = ##t
\consists \test-engraver
  }
}

%%%
%% I
%%%

\markup
\rounded-box \fill-line { "Various tests" }

tstI =
\chordmode {
c4:m/e c:m c:m/+g c:m/fes c/fes c/d c:7/d c:7/+g d e e:m f:m f:m f
}
<<
  \new ChordNames \tstI
  \new Staff \tstI
>>

%%%
%% II
%%%

\markup
\rounded-box \fill-line { "Test switching on/off via \"dropEqualRoot\"" }

tstII =
\chordmode {
\mark "dropEqualRoot = ##t in \\layout"
c4
c/f
c:m7
c:m7/+bes
c:m7
c:m7/cis
r2
\break
\set dropEqualRoot = ##f
\mark "\\set dropEqualRoot = ##f"
c4
c/f
c:m7
c:m7/+bes
c:m7
c:m7/cis
r2
\break
\unset dropEqualRoot
\mark "\\set dropEqualRoot = ##t"
c4
c/f
c:m7
c:m7/+bes
c:m7
c:m7/cis
r2
}
<<
  \new ChordNames  \tstII
  \new Staff \tstII
>>

%%%
%% III
%%%

\markup
\rounded-box \fill-line {
  \column {
"Limitation:"
 \wordwrap-string
 %% jEdit highlighting is not smart enough, thus the strange line-break ...
 #"Here the \"root
\"-part is never dropped, because the main-chords are always different, which
can't be observed in ChordNames, though.
All chords but the last are inversions!"
  }
}

tstIII =
\chordmode {
c:m7
c:m7/bes
c:m7/g
c:m7/ees
c:m7/+bes
}
<<
  \new ChordNames  \tstIII
  \new Staff \tstIII
>>

HTH,
  Harm

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

Re: Discussion - LilyPond engraving manifest

2017-03-29 Thread Noeck 
… sorry, I should have read the issue before. You already discussed a
lot of ideas (output variable, log output parsing, your suggestion of a
manifest file).

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

Re: LSR down?

2017-03-29 Thread Juan Cristóbal Cerrillo 
Hello,

Also down in Mexico.

best,
jc

> On Mar 29, 2017, at 11:10 AM, Xavier Scheuer  wrote:
> 
> Hello everybody,
> 
> It is down here (ERR_CONNECTION_TIMED_OUT).
> Is it just me (Belgium here), or it is down again?
> 
> This raises (again) the question of LSR mirroring, that I asked
> some years ago. Do we have some nice people from lilypond-user
> who have a server and could set up a LSR mirror, so users still
> have access to the nice snippets available on the LSR?
> 
> For people interested here is a link to Reinhold's tutorial
> to set up a local LSR mirror.
> http://wiki.kainhofer.com/lilypond/lsr_setup 
> 
> https://lists.gnu.org/archive/html/lilypond-user/2011-05/msg00371.html 
> 
> 
> Cheers,
> Xavier
> 
> 
> 
> On 27 March 2017 at 21:25, Thomas Morley  > wrote:
> >
> > 2017-03-27 9:24 GMT+02:00 Malte Meyn  > >:
> > >
> > >
> > > Am 27.03.2017 um 02:30 schrieb Andrew Bernard:
> > >> LSR still down as at 0030 UTC here in Australia.
> > >>
> > >> Andrew
> > >
> > > No time zone problems here so http://lsr.di.unimi.it/LSR/Snippet?id=1007 
> > > 
> > > shows up correctly but the search gives no results:
> > > http://lsr.di.unimi.it/LSR/Search?q=notehead 
> > > 
> >
> >
> >
> > Hi all,
> >
> > I had reported the problem.
> >
> > Seba thinks it's fixed now (for now).
> > My own testings were successful.
> >
> > May I ask for feedback whether it works out there as well?
> >
> > Cheers,
> >  Harm
> >
> 
> -- 
> Xavier Scheuer >
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: Discussion - LilyPond engraving manifest

2017-03-29 Thread Noeck 
Hi Pierre-Luc,

do you know the document variables in Frescobaldi:
http://frescobaldi.org/uguide.html#help_docvar_output

I don't know how complex the naming of your output files gets, but as
only the beginning of the output file name has to match, you probably
can get quite far with this output variable.

I guess this mechanism could be extended to some regex matching if you
need more fine grained control which files are output files and which not.

Does that help or is it not clever enough for your use case?

Joram


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

Re: LSR down?

2017-03-29 Thread Xavier Scheuer 
Hello everybody,

It is down here (ERR_CONNECTION_TIMED_OUT).
Is it just me (Belgium here), or it is down again?

This raises (again) the question of LSR mirroring, that I asked
some years ago. Do we have some nice people from lilypond-user
who have a server and could set up a LSR mirror, so users still
have access to the nice snippets available on the LSR?

For people interested here is a link to Reinhold's tutorial
to set up a local LSR mirror.
http://wiki.kainhofer.com/lilypond/lsr_setup
https://lists.gnu.org/archive/html/lilypond-user/2011-05/msg00371.html

Cheers,
Xavier



On 27 March 2017 at 21:25, Thomas Morley  wrote:
>
> 2017-03-27 9:24 GMT+02:00 Malte Meyn :
> >
> >
> > Am 27.03.2017 um 02:30 schrieb Andrew Bernard:
> >> LSR still down as at 0030 UTC here in Australia.
> >>
> >> Andrew
> >
> > No time zone problems here so http://lsr.di.unimi.it/LSR/Snippet?id=1007
> > shows up correctly but the search gives no results:
> > http://lsr.di.unimi.it/LSR/Search?q=notehead
>
>
>
> Hi all,
>
> I had reported the problem.
>
> Seba thinks it's fixed now (for now).
> My own testings were successful.
>
> May I ask for feedback whether it works out there as well?
>
> Cheers,
>  Harm
>

-- 
Xavier Scheuer 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Style questions

2017-03-29 Thread David Wright 
On Wed 29 Mar 2017 at 15:28:56 (+0300), Dmytro O. Redchuk wrote:
> 2017-03-29 8:46 GMT+03:00 Dmytro O. Redchuk :
> >> I have come across this reference, which claims to handle them,
> >> but I have yet to try it out:
> >>
> >> https://github.com/wbsoft/lilymusic/blob/master/include/merge-rests.ily
> > Oh, thank you, I have to try it too :)
> 
> There should be 1 in line 110
> (https://github.com/wbsoft/lilymusic/blob/master/include/merge-rests.ily#L110)
> for lilypond 2.18 (2.4 and up?)

Yes, that fixes the only snag I have seen so far which was putting
whole-measure rests under the centre line instead of the one above.

Thanks for the explanation of what you were referring to.
The toy example in the snippet could be better constructed
to test it more thoroughly; for example dotted rests.

Cheers,
David.

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

Re: StaffSymbol.thickness relative to staff space

2017-03-29 Thread Kieren MacMillan 
Hi Urs,

Perhaps this thread can offer some help?


Cheers,
Kieren.

> On Mar 29, 2017, at 9:48 AM, Urs Liska  wrote:
> 
> Hi,
> 
> nearly all lengths are calculated either in relation to a staff space or
> to the staffsymbol's line-thickness. But I don't find the relation/ratio
> between these fundamental values.
> 
> I need to set StaffSymbol.thickness to a specific value relative to
> staff spaces (i.e. 0.1 staff spaces).
> 
> ly:staff-symbol-line-thickness grob
> 
> basically gives exactly what I'd need, but I need it as a global
> override, not only in relation to a specific grob.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

StaffSymbol.thickness relative to staff space

2017-03-29 Thread Urs Liska 
Hi,

nearly all lengths are calculated either in relation to a staff space or
to the staffsymbol's line-thickness. But I don't find the relation/ratio
between these fundamental values.

I need to set StaffSymbol.thickness to a specific value relative to
staff spaces (i.e. 0.1 staff spaces).

ly:staff-symbol-line-thickness grob

basically gives exactly what I'd need, but I need it as a global
override, not only in relation to a specific grob.

Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: Color of lyric hyphen

2017-03-29 Thread Urs Liska 


Am 29.03.2017 um 14:45 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Am 29.03.2017 um 12:53 schrieb David Kastrup:
>>> Urs Liska  writes:
 But as you can see in the attached image it remains black, while the
 extender and the text itself are correctly colored.

 Did I misinterpret what LyricHyphen is or is this a bug?
>>> This is a regression due to
>>>
>>> commit 2dc76513c4edb8e18e6170069677eb0dd9b54209
>>> Author: Knut Petersen 
>>> Date:   Sat Mar 4 18:10:19 2017 +
>>>
>>> LyricHyphen whiteout
>>> 
>>> Issue 5033
>> Thanks for the info. Can I expect this to be fixed in 2.19.58 or do I
>> have to go back to 2.19.54 for this project?
> 2.19.58 is already out and the regression is present in current master.
> At the current point, no issue is recorded for the problem, no work is
> in progress for fixing it, and I don't see that the "whiteout" issue has
> a color model other than black and white considered yet.

OK, thanks.

>
> The above commit appears first in 2.19.57.
>

Sorry, that was a typo, I meant going back to 2.19.56.

Could the bug squad please open an issue for this?

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: Color of lyric hyphen

2017-03-29 Thread David Kastrup 
Urs Liska  writes:

> Am 29.03.2017 um 12:53 schrieb David Kastrup:
>> Urs Liska  writes:
>>>
>>> But as you can see in the attached image it remains black, while the
>>> extender and the text itself are correctly colored.
>>>
>>> Did I misinterpret what LyricHyphen is or is this a bug?
>> This is a regression due to
>>
>> commit 2dc76513c4edb8e18e6170069677eb0dd9b54209
>> Author: Knut Petersen 
>> Date:   Sat Mar 4 18:10:19 2017 +
>>
>> LyricHyphen whiteout
>> 
>> Issue 5033
>
> Thanks for the info. Can I expect this to be fixed in 2.19.58 or do I
> have to go back to 2.19.54 for this project?

2.19.58 is already out and the regression is present in current master.
At the current point, no issue is recorded for the problem, no work is
in progress for fixing it, and I don't see that the "whiteout" issue has
a color model other than black and white considered yet.

The above commit appears first in 2.19.57.

-- 
David Kastrup

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

Re: Style questions

2017-03-29 Thread Dmytro O. Redchuk 
2017-03-29 8:46 GMT+03:00 Dmytro O. Redchuk :
>> I have come across this reference, which claims to handle them,
>> but I have yet to try it out:
>>
>> https://github.com/wbsoft/lilymusic/blob/master/include/merge-rests.ily
> Oh, thank you, I have to try it too :)

There should be 1 in line 110
(https://github.com/wbsoft/lilymusic/blob/master/include/merge-rests.ily#L110)
for lilypond 2.18 (2.4 and up?)

-- 
  Dmytro O. Redchuk

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

Re: Color of lyric hyphen

2017-03-29 Thread Urs Liska 


Am 29.03.2017 um 12:53 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Hi,
>>
>> I would expect that with the following code the hyphen separating the
>> lyrics syllables would be printed red:
>>
>> \version "2.19.57"
>>
>> \layout {
>>   \context {
>> \Lyrics
>> \override LyricHyphen.color = #red
>> \override LyricText.color = #blue
>> \override LyricExtender.color = #magenta
>>   }
>> }
>>
>> music = {
>>   c'2 c'2 ~ c'1
>> }
>>
>> text = \lyricmode {
>>   Hel -- lo __
>> }
>>
>> <<
>>   \new Staff \new Voice = "mel" \music
>>   \new Lyrics \lyricsto "mel" \text
>>
>> But as you can see in the attached image it remains black, while the
>> extender and the text itself are correctly colored.
>>
>> Did I misinterpret what LyricHyphen is or is this a bug?
> This is a regression due to
>
> commit 2dc76513c4edb8e18e6170069677eb0dd9b54209
> Author: Knut Petersen 
> Date:   Sat Mar 4 18:10:19 2017 +
>
> LyricHyphen whiteout
> 
> Issue 5033

Thanks for the info. Can I expect this to be fixed in 2.19.58 or do I
have to go back to 2.19.54 for this project?

Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Discussion - LilyPond engraving manifest

2017-03-29 Thread Pierre-Luc Gauthier 
Hello there,

I know some LilyPond code editors (like Frescobaldi) have to reverse
engineer the LilyPond music files to figure out what it /should/ be
looking for as far as what files where actually generated by LilyPond.

I happen to rely a lot on code based on something like :

\version "2.19.58"

#(ly:book-process
  (ly:make-book
   $defaultpaper
   $defaultheader
   #{ \score {c'} #})
  $defaultpaper
  $defaultlayout
  "ThisIsThePDFFileName")

…recursively generating lots of book from a list of different
instruments with each different editions to engrave. Well Frescobaldi
for one has no clue of what is going on and for obvious reasons. I
suppose one could generate PDF filenames based on the time and date
for all I know.

So, as mentioned in this thread :
https://github.com/wbsoft/frescobaldi/issues/546

Could a possible solution be for LilyPond to produce a manifest file
at compilation?

The manifest file could be set as an option at compilation so that
editors could reliably find said manifest. It would then be trivial to
read that manifest of produced files at the end of compilation.

I suppose this compiler manifest could be plain text and in a easily
digestible format (e.g. one file per line).

./music.pdf
./music.svg
./music.midi

As a workaround, I am currently using 2 systems one being a set of
scheme functions to publish final work and my old system of explicitly
commenting %{%} \book blocks in some file as I need work on them.

What are your thoughts on this?
Should it not be LilyPond responsibility to report what it has done?

-- 
Pierre-Luc Gauthier

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

Re: Color of lyric hyphen

2017-03-29 Thread David Kastrup 
Urs Liska  writes:

> Hi,
>
> I would expect that with the following code the hyphen separating the
> lyrics syllables would be printed red:
>
> \version "2.19.57"
>
> \layout {
>   \context {
> \Lyrics
> \override LyricHyphen.color = #red
> \override LyricText.color = #blue
> \override LyricExtender.color = #magenta
>   }
> }
>
> music = {
>   c'2 c'2 ~ c'1
> }
>
> text = \lyricmode {
>   Hel -- lo __
> }
>
> <<
>   \new Staff \new Voice = "mel" \music
>   \new Lyrics \lyricsto "mel" \text
>>>
>
>
> But as you can see in the attached image it remains black, while the
> extender and the text itself are correctly colored.
>
> Did I misinterpret what LyricHyphen is or is this a bug?

This is a regression due to

commit 2dc76513c4edb8e18e6170069677eb0dd9b54209
Author: Knut Petersen 
Date:   Sat Mar 4 18:10:19 2017 +

LyricHyphen whiteout

Issue 5033

-- 
David Kastrup

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

Color of lyric hyphen

2017-03-29 Thread Urs Liska 
Hi,

I would expect that with the following code the hyphen separating the
lyrics syllables would be printed red:

\version "2.19.57"

\layout {
  \context {
\Lyrics
\override LyricHyphen.color = #red
\override LyricText.color = #blue
\override LyricExtender.color = #magenta
  }
}

music = {
  c'2 c'2 ~ c'1
}

text = \lyricmode {
  Hel -- lo __
}

<<
  \new Staff \new Voice = "mel" \music
  \new Lyrics \lyricsto "mel" \text
>>


But as you can see in the attached image it remains black, while the
extender and the text itself are correctly colored.

Did I misinterpret what LyricHyphen is or is this a bug?

Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org

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

Re: Unclear doc?

2017-03-29 Thread Malte Meyn 


Am 29.03.2017 um 08:41 schrieb Menu Jacques:
> Hello folks,
> 
> In appendix A.17 of the LPNR v2.19.57, what doest the « No setting… »
> sentence mean?
> 
> alternativeNumberingStyle (symbol)
> The style of an alternative’s bar numbers. Can be numbers for going back
> to the same number or numbers-with-letters for going back to the same
> number with letter suffixes. *No setting will not go back in
> measure-number time*.

No setting means either “there is no setting” or “it’s set to #'()”.

\version "2.19.56"

music = {
  \repeat volta 3 R1*2
  \alternative {
R
R
R
  }
  R
}

\layout {
  \context {
\Score
\override BarNumber.break-visibility = #end-of-line-invisible
  }
}

\new Score \music

\new Score \with {
  alternativeNumberingStyle = #'numbers
} \music

\new Score \with {
  alternativeNumberingStyle = #'numbers-with-letters
} \music

\new Score \with {
  alternativeNumberingStyle = #'numbers-with-letters
} {
  \music
  \set Score.alternativeNumberingStyle = #'()
  \music
}

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

Unclear doc?

2017-03-29 Thread Menu Jacques 
Hello folks,

In appendix A.17 of the LPNR v2.19.57, what doest the « No setting… » sentence 
mean?

alternativeNumberingStyle (symbol)
The style of an alternative’s bar numbers. Can be numbers for going 
back to the same number or numbers-with-letters for going back to the same 
number with letter suffixes. No setting will not go back in measure-number time.

JM

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