Custon MMR engraver - another issue

[Craig Dabelstein]

Hi again,

When using lilypond on the command line, and trying to engrave multiple
files, the multi measure rest engraver is giving this error when it moves
to the second file on the list:

/Applications/LilyPond\ 2.19.83.app/Contents/Resources/bin/lilypond
-dpoint-and-click -ddelete-intermediate-files --pdf *.ly

fatal error: symbol printMmrRange redefined


I've been using trial and error to try to find the problem but I really
don't know where to look. Anh ideas?


Many thanks,


Craig






-- 
Craig Dabelstein
Owner
Maxime's Music
M: 0404884173
A: 19 Twelfth Ave,  Kedron QLD 4031, Australia
W: concertbandmusicstore.com E:
cr...@concertbandmusicstore.com 

Re: Custom MMR Range engraver problem under 2.19.83

[Craig Dabelstein]

Thank you everyone.

Craig


On Mon, 6 Jan 2020 at 11:23, David Kastrup  wrote:

> David Kastrup  writes:
>
> > Thomas Morley  writes:
> >
> >> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn <
> lilyp...@maltemeyn.de>:
> >>>
> >>>
> >>>
> >>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> >>> > Hi all,
> >>> >
> >>> > I've been using the custom mmr-range-engraver (from this thread:
> >>> >
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> >>> > It was working perfectly under 2.19.82 but won't work under 2.19.83.
> No
> >>> > error messages at all. Just mmr bar numbers not displaying. Has
> anyone
> >>> > else experienced this?
> >>> >
> >>> > Craig
> >>>
> >>> Could you please give a minimal working example (or at least link to
> the
> >>> message containing a compilable code, not to the start of the thread)?
> >>>
> >>
> >> It's
> >> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
> >>
> >> A minimal for the problem:
> >>
> >> \markup
> >> \center-column {
> >>foo
> >>\translate #'(0 . 3)
> >>\with-dimensions #empty-interval #empty-interval
> >>bar
> >> }
> >>
> >> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> >> No clue what happens and why.
> >> Probably a bug, to tired to do further research, thoug.
> >
> > Bisecting.
>
> 06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
> commit 06be909202d2ced6e651e4420bc8068eafae023e
> Author: Thomas Morley 
> Date:   Sat May 26 23:45:55 2018 +0200
>
> Issue 5331 Let general-column deal reliable with empty args
>
> Previously an args-list of empty-stencils issued a programming error:
>   Improbable offset for stencil: -inf staff space
> This patch removes empty stencils from the args-list.
> If args-list is empty, an empty stencil is returned.
>
> :04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998
> 2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm
>
>
> --
> David Kastrup
>
>

-- 
Craig Dabelstein
Owner
Maxime's Music
M: 0404884173
A: 19 Twelfth Ave,  Kedron QLD 4031, Australia
W: concertbandmusicstore.com E:
cr...@concertbandmusicstore.com 

Re: Custom MMR Range engraver problem under 2.19.83

[David Kastrup]

David Kastrup  writes:

> Thomas Morley  writes:
>
>> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>>>
>>>
>>>
>>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
>>> > Hi all,
>>> >
>>> > I've been using the custom mmr-range-engraver (from this thread:
>>> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
>>> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
>>> > error messages at all. Just mmr bar numbers not displaying. Has anyone
>>> > else experienced this?
>>> >
>>> > Craig
>>>
>>> Could you please give a minimal working example (or at least link to the
>>> message containing a compilable code, not to the start of the thread)?
>>>
>>
>> It's
>> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>>
>> A minimal for the problem:
>>
>> \markup
>> \center-column {
>>foo
>>\translate #'(0 . 3)
>>\with-dimensions #empty-interval #empty-interval
>>bar
>> }
>>
>> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
>> No clue what happens and why.
>> Probably a bug, to tired to do further research, thoug.
>
> Bisecting.

06be909202d2ced6e651e4420bc8068eafae023e is the first bad commit
commit 06be909202d2ced6e651e4420bc8068eafae023e
Author: Thomas Morley 
Date:   Sat May 26 23:45:55 2018 +0200

Issue 5331 Let general-column deal reliable with empty args

Previously an args-list of empty-stencils issued a programming error:
  Improbable offset for stencil: -inf staff space
This patch removes empty stencils from the args-list.
If args-list is empty, an empty stencil is returned.

:04 04 1f7b4bbaa3a3fb2614daa9b9a58ac279aded4998 
2a55b8acbf49de4695c9afd37f1d60768084d8e1 M  scm


-- 
David Kastrup

Re: Custom MMR Range engraver problem under 2.19.83

[David Kastrup]

Thomas Morley  writes:

> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>>
>>
>>
>> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
>> > Hi all,
>> >
>> > I've been using the custom mmr-range-engraver (from this thread:
>> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
>> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
>> > error messages at all. Just mmr bar numbers not displaying. Has anyone
>> > else experienced this?
>> >
>> > Craig
>>
>> Could you please give a minimal working example (or at least link to the
>> message containing a compilable code, not to the start of the thread)?
>>
>
> It's
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>
> A minimal for the problem:
>
> \markup
> \center-column {
>foo
>\translate #'(0 . 3)
>\with-dimensions #empty-interval #empty-interval
>bar
> }
>
> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> No clue what happens and why.
> Probably a bug, to tired to do further research, thoug.

Bisecting.

-- 
David Kastrup

Re: Custom MMR Range engraver problem under 2.19.83

[Thomas Morley]

Am Mo., 6. Jan. 2020 um 01:09 Uhr schrieb Thomas Morley
:
>
> Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
> >
> >
> >
> > Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> > > Hi all,
> > >
> > > I've been using the custom mmr-range-engraver (from this thread:
> > > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> > > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
> > > error messages at all. Just mmr bar numbers not displaying. Has anyone
> > > else experienced this?
> > >
> > > Craig
> >
> > Could you please give a minimal working example (or at least link to the
> > message containing a compilable code, not to the start of the thread)?
> >
>
> It's
> https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html
>
> A minimal for the problem:
>
> \markup
> \center-column {
>foo
>\translate #'(0 . 3)
>\with-dimensions #empty-interval #empty-interval
>bar
> }
>
> With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
> No clue what happens and why.
> Probably a bug, to tired to do further research, thoug.
>
> Anyway,
> Craig change formatMMRNumber to:
>
> formatMMRNumber =
> #(define-scheme-function (start stop)(integer? integer?)

Delete the line below, it's forgotten debugging code.

> (pretty-print (number->string (- stop start)))
> #{
>   \markup
> \column {
>\halign #0 #(number->string (- stop start))
> %   %% value found by try and error
>\translate-scaled #'(0 . -6.5)
>\with-dimensions #empty-interval #empty-interval
>\halign #0
>\normal-text
>\fontsize #-2
>\line {
>  #(number->string (1+  start))
>  " - "
>  #(number->string stop)
>}
> }
> #})
>
> and the functionality should be restored.
>
> Cheers,
>   Harm

Re: Custom MMR Range engraver problem under 2.19.83

[Thomas Morley]

Am Mo., 6. Jan. 2020 um 00:53 Uhr schrieb Malte Meyn :
>
>
>
> Am 06.01.20 um 00:02 schrieb Craig Dabelstein:
> > Hi all,
> >
> > I've been using the custom mmr-range-engraver (from this thread:
> > https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html).
> > It was working perfectly under 2.19.82 but won't work under 2.19.83. No
> > error messages at all. Just mmr bar numbers not displaying. Has anyone
> > else experienced this?
> >
> > Craig
>
> Could you please give a minimal working example (or at least link to the
> message containing a compilable code, not to the start of the thread)?
>

It's
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00543.html

A minimal for the problem:

\markup
\center-column {
   foo
   \translate #'(0 . 3)
   \with-dimensions #empty-interval #empty-interval
   bar
}

With 2.19.82 "bar" is printed, it completely disappears with 2.19.83
No clue what happens and why.
Probably a bug, to tired to do further research, thoug.

Anyway,
Craig change formatMMRNumber to:

formatMMRNumber =
#(define-scheme-function (start stop)(integer? integer?)
(pretty-print (number->string (- stop start)))
#{
  \markup
\column {
   \halign #0 #(number->string (- stop start))
%   %% value found by try and error
   \translate-scaled #'(0 . -6.5)
   \with-dimensions #empty-interval #empty-interval
   \halign #0
   \normal-text
   \fontsize #-2
   \line {
 #(number->string (1+  start))
 " - "
 #(number->string stop)
   }
}
#})

and the functionality should be restored.

Cheers,
  Harm

Custom MMR Range engraver problem under 2.19.83

[Craig Dabelstein]

Hi all,

I've been using the custom mmr-range-engraver (from this thread:
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00505.html). It
was working perfectly under 2.19.82 but won't work under 2.19.83. No error
messages at all. Just mmr bar numbers not displaying. Has anyone else
experienced this?

Craig



-- 
Craig Dabelstein
Owner
Maxime's Music
M: 0404884173
A: 19 Twelfth Ave,  Kedron QLD 4031, Australia
W: concertbandmusicstore.com E:
cr...@concertbandmusicstore.com 

ANN: LilyJSSVG, first pre-release (BIG improvement)

[Paolo Prete]

Hello all,

I am very happy to announce the first version of the LilyJSSVG editor,
after the various tests made in the previous days (I have not yet committed
the release, but everything is ready).

https://github.com/paolo-prete/LilyJSSVG

As you can see, this version brings VERY IMPORTANT differences compared to
the test versions: everything is in fact absolutely automated, and is
achieved through the point-and-click system on the score, from which you
can open drop-down menus for editing objects with The mouse. Instead of
explaining all this in words, I suggest you see the following video, in
which with LilyJSSVG I open a Beethoven sonata taken from the Mutopia
project and modify it.

https://github.com/paolo-prete/LilyJSSVG/blob/master/LilyJSSVG.ogv

Obviously my intent is to create a complete editor. In the next few days I
will insert various other grob to modify (hairpins, accidents, keys,
brackets etc.).

I really invite you to consider the features of this editor.

1) For the first time, objects can be modified with the mouse avoiding the
unnerving trial and error process. Note that the system I used has nothing
different from the tweaks and overrides that are normally done through a
text editor. I kept the same names of the objects (Script, Beam,
DynamicText etc.): the only difference is that here the coordinates are
calculated and written directly with the mouse. So all this is not at all
in opposition to Lilypond's logic, but rather strengthens it.

2) The editor doesn't need ANYTHING to compile. It is in fact generated by
Lilypond himself!

I did all this because I believe in Lilypond a lot and I use it often. I
wanted to invest my time because in this way I speed up the writing of the
scores.
I really needed to speed up many operations, and I am achieving this result.
But it would be really nice if you help me. Again: watch the video.

In the coming weeks, after adding more grobs to modify, I will suspend the
development. At this point, I will be able to actively dedicate myself to
the project only if I am supported. The help I ask from you is 1) test 2)
code cleaning 3) documentation 4) support for writing in Javascript. 5)
Test on Windows / OSx

For point 4) I am willingly available for those who want to learn how to
add new features to the code.

If supported, I will try to continue the work by adding a text editor with
the various features of syntax highlighting etc. If I will not be
supported, unfortunately I will devote myself to the project much more
occasionally (I will however try to continue developing it, because I
believe in it). Of course, I cannot do everything alone, and I would like
to see the Lilypond development team (should I cross-post this to
lilypond-devel ml?)  saying something about the possibility of including
this feature in the Lilypond project.

HTH
Paolo

Re: named strings in TABs

[Thomas Morley]

Am So., 5. Jan. 2020 um 12:23 Uhr schrieb Malte Meyn :
>
>
>
> Am 05.01.20 um 10:55 schrieb bb:
> > I named the strings in my TABs successfully as long as I use natural
> > note names. If I use flats and sharps I get an error. How do I gat flats
> > and sharps?
>
> How did you input the sharps? #, ♯, or \sharp? The character # is
> special in LilyPond, you’d have to enclose the note name in quotes "f#".
> But I’d recommend true sharp symbols using \sharp:
>
> \markup \center-column {
>\concat { f \hspace #0.5 \raise #0.6 \sharp  }
>\concat { c \hspace #0.2 \raise #0.6 \sharp  }
> }
>
>

Below a generic suggestion:

#(define-markup-command (note-name layout props p)(ly:pitch?)
#:properties ((lowercase #f)
  (proc note-name->markup))
"Prints the given pitch as markup.  The pitch should usually entered like, p.e.
@code{##{ fis #}}.
Default procedure to print the markup is @code{note-name->markup}. Other
possibilities are:
@code{(chord-name->german-markup #f)}
@code{(chord-name->german-markup #t)}
@code{note-name->german-markup}
@code{(chord-name->italian-markup #f)}
@code{(chord-name->italian-markup #t)}"
  (interpret-markup layout props
(make-override-markup '(word-space . 0) (proc p lowercase

%% Example

\markup \note-name ##{ cis #}

%% Table of possible examples

names =
\markup
  \column {
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
\override #`(proc . ,(chord-name->german-markup #f))
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
\override #`(proc . ,(chord-name->german-markup #t))
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
\override #`(proc . ,note-name->german-markup)
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
\override #`(proc . ,(chord-name->italian-markup #f))
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
\override #`(proc . ,(chord-name->italian-markup #t))
\line { \note-name ##{ b #} \note-name ##{ bes #} \note-name
##{ dis #} }
  }

\markup
 \column {
   \pad-around #2
   "Current defaults, note: using note-name->german-markup is always lowercase"
   \names
   \pad-around #2
   "Applying \\override #'(lowercase . #t)"
   \override #'(lowercase . #t)
   \names
 }

Cheers,
  Harm

Re: named strings in TABs

[bb]

Solved: use "f#" "c#"

Am 05.01.20 um 10:55 schrieb bb:
> I named the strings in my TABs successfully as long as I use natural
> note names. If I use flats and sharps I get an error. How do I gat flats
> and sharps?
>
> \version "2.19.80"
> \score  {  <<
> \new TabStaff{ 
>   \override Staff.Clef #'stencil = #ly:text-interface::print
>   \override Staff.Clef #'text =
>   \markup
>   \center-column {{ fis cis  }     % how to get f# c# ???}
> }  >>  }
>
> kind regards
>
>
>

Re: named strings in TABs

[Malte Meyn]

Am 05.01.20 um 10:55 schrieb bb:

I named the strings in my TABs successfully as long as I use natural
note names. If I use flats and sharps I get an error. How do I gat flats
and sharps?


How did you input the sharps? #, ♯, or \sharp? The character # is 
special in LilyPond, you’d have to enclose the note name in quotes "f#". 
But I’d recommend true sharp symbols using \sharp:


\markup \center-column {
  \concat { f \hspace #0.5 \raise #0.6 \sharp  }
  \concat { c \hspace #0.2 \raise #0.6 \sharp  }
}

named strings in TABs

[bb]

I named the strings in my TABs successfully as long as I use natural
note names. If I use flats and sharps I get an error. How do I gat flats
and sharps?

\version "2.19.80"
\score  {  <<
\new TabStaff{ 
  \override Staff.Clef #'stencil = #ly:text-interface::print
  \override Staff.Clef #'text =
  \markup
  \center-column {{ fis cis  }     % how to get f# c# ???}
}  >>  }

kind regards