Re: replace-stencil and overlay-stencil (was: Re: time signature 4 / \breve ?)

2019-10-16 Thread Pierre Perol-Schneider
Thank you for this Aaron!
Cheers,
Pierre

Le jeu. 17 oct. 2019 à 06:42, Aaron Hill  a
écrit :

> On 2019-10-16 7:00 pm, Graham King wrote:
> > \version "2.19.82"
> > {
> >   \once \override Staff.TimeSignature #'stencil =
> > #(lambda (grob)
> >   (grob-interpret-markup
> >grob
> >#{ \markup
> >   \override #'(baseline-skip . 1)
> >   \center-column {
> > \musicglyph "four"
> > \musicglyph "noteheads.sM1" } #}))
> >   \time 8/1
> >   c'\breve c' c' c'
> > }
>
> If you find yourself doing this type of stencil \override on a regular
> basis, you could wrap it up in a more general-purpose helper similar to
> the following:
>
> 
> \version "2.19.83"
>
> replace-stencil = #(define-music-function (grob text) (grob-list?
> markup?)
>(define (stencil grob) (grob-interpret-markup grob text))
>#{ \override $grob . stencil = $stencil #})
>
> {
>\once \replace-stencil Staff.TimeSignature
>  \markup \override #'(baseline-skip . 1)
>\center-column { \musicglyph "four" \musicglyph "noteheads.sM1" }
>\time 8/1 c'\breve c' c' c'
> }
> 
>
> Putting together the function above got me thinking about and working on
> a version that overlays \markup on an existing stencil instead of
> replacing it:
>
> 
> \version "2.19.83"
>
> overlay-stencil = #(define-music-function (grob align text)
>(grob-list? (number-pair? '(0 . 0)) markup?)
>(define stencil (grob-transformer 'stencil (lambda (grob orig)
>  (let ((x (interval-index (ly:stencil-extent orig X) (car align)))
>(y (interval-index (ly:stencil-extent orig Y) (cdr align)))
>(new (grob-interpret-markup grob text)))
>(ly:stencil-add orig (ly:stencil-translate new (cons x y)))
>#{ \override $grob . stencil = $stencil #})
>
> red-x = \markup \with-dimensions-from \null
>\vcenter \center-align \with-color #red "X"
>
> {
>\overlay-stencil Staff.Clef #'(-1 . 1) "Clef"
>b'8 c''
>\temporary \overlay-stencil NoteHead \red-x
>g' a'
>\revert NoteHead.stencil
>b'2
> }
> 
>
> Not sure how useful these would be in practice, but the resulting syntax
> might be preferable for some folks.
>
>
> -- Aaron Hill___
> 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: time signature 4 / \breve ?

2019-10-16 Thread Paul Scott
Graham,

Thank you very much for both your solutions!

Paul

On Oct 16, 2019, at 7:00 PM, Graham King  wrote:

> Another way (slightly different result):
> 
> \version "2.19.82"
> 
> { 
>  \once \override Staff.TimeSignature #'stencil =
>#(lambda (grob)
>  (grob-interpret-markup
>   grob
>   #{ \markup
>  \override #'(baseline-skip . 1) 
>  \center-column {
>\musicglyph "four"
>\musicglyph "noteheads.sM1" } #}))
>  \time 8/1
>  c'\breve c' c' c'
> }
> 
> ___
> 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: time signature 4 / \breve ?

2019-10-16 Thread Paul Scott

On Oct 16, 2019, at 6:14 PM, Ben  wrote:

Ben,

Thank you very much!

Paul

> On 10/16/2019 8:59 PM, Paul Scott wrote:
>> Is it possible to write a time signature 4 / \breve ?
>> 
>> This occurs in Carmina Burana.
>> 
>> Thank you for any ideas,
>> 
>> Paul
>> 
> Hi Paul,
> 
> Does this help get you close to what you're looking for?
> 

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


replace-stencil and overlay-stencil (was: Re: time signature 4 / \breve ?)

2019-10-16 Thread Aaron Hill

On 2019-10-16 7:00 pm, Graham King wrote:

\version "2.19.82"
{
  \once \override Staff.TimeSignature #'stencil =
#(lambda (grob)
  (grob-interpret-markup
   grob
   #{ \markup
  \override #'(baseline-skip . 1)
  \center-column {
\musicglyph "four"
\musicglyph "noteheads.sM1" } #}))
  \time 8/1
  c'\breve c' c' c'
}


If you find yourself doing this type of stencil \override on a regular 
basis, you could wrap it up in a more general-purpose helper similar to 
the following:



\version "2.19.83"

replace-stencil = #(define-music-function (grob text) (grob-list? 
markup?)

  (define (stencil grob) (grob-interpret-markup grob text))
  #{ \override $grob . stencil = $stencil #})

{
  \once \replace-stencil Staff.TimeSignature
\markup \override #'(baseline-skip . 1)
  \center-column { \musicglyph "four" \musicglyph "noteheads.sM1" }
  \time 8/1 c'\breve c' c' c'
}


Putting together the function above got me thinking about and working on 
a version that overlays \markup on an existing stencil instead of 
replacing it:



\version "2.19.83"

overlay-stencil = #(define-music-function (grob align text)
  (grob-list? (number-pair? '(0 . 0)) markup?)
  (define stencil (grob-transformer 'stencil (lambda (grob orig)
(let ((x (interval-index (ly:stencil-extent orig X) (car align)))
  (y (interval-index (ly:stencil-extent orig Y) (cdr align)))
  (new (grob-interpret-markup grob text)))
  (ly:stencil-add orig (ly:stencil-translate new (cons x y)))
  #{ \override $grob . stencil = $stencil #})

red-x = \markup \with-dimensions-from \null
  \vcenter \center-align \with-color #red "X"

{
  \overlay-stencil Staff.Clef #'(-1 . 1) "Clef"
  b'8 c''
  \temporary \overlay-stencil NoteHead \red-x
  g' a'
  \revert NoteHead.stencil
  b'2
}


Not sure how useful these would be in practice, but the resulting syntax 
might be preferable for some folks.



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


Re: time signature 4 / \breve ?

2019-10-16 Thread Graham King
Another way (slightly different result):

\version "2.19.82"

{ 
  \once \override Staff.TimeSignature #'stencil =
#(lambda (grob)
  (grob-interpret-markup
   grob
   #{ \markup
  \override #'(baseline-skip . 1) 
  \center-column {
\musicglyph "four"
\musicglyph "noteheads.sM1" } #}))
  \time 8/1
  c'\breve c' c' c'
}

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


Re: time signature 4 / \breve ?

2019-10-16 Thread Graham King
\version "2.19.82"

tsMarkup = \markup {
  \override #'(baseline-skip . 0.5)
  \column { \number 4 \note #"breve" #0 }
}

{
  \override Staff.TimeSignature.style = #'default
  \override Staff.TimeSignature.stencil = #(lambda (grob)
(grob-interpret-markup grob tsMarkup))

  \time 8/1
  c'\breve c' c' c'
}

HTH
-- Graham


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


Re: time signature 4 / \breve ?

2019-10-16 Thread Ben

On 10/16/2019 8:59 PM, Paul Scott wrote:

Is it possible to write a time signature 4 / \breve ?

This occurs in Carmina Burana.

Thank you for any ideas,

Paul


Hi Paul,

Does this help get you close to what you're looking for?

(see attached)

%%%

\version "2.19.83"

#(use-modules (ice-9 regex))

my-format-procedure =
#(define-scheme-function (parser location args)(pair?)
   #{
 \markup
 \concat {
   \number $(car args)
   \raise #-0.9 \huge "/"
   \small
   \override #'(style . default)
   \note $(cdr args) #DOWN
 }
   #})

%% alternative:
%{
my-format-procedure =
#(define-scheme-function (parser location args)(pair?)
#{
\markup
\override #'(baseline-skip . 0.5)
\column {
\number $(car args)
\override #'(style . default)
\note $(cdr args) #DOWN
}
#})
%}
#(define ((format-time-sig-with-note frac trim?) grob)
   (let* ((num (if (pair? frac) (car frac) 4))
  (den (if (pair? frac) (cdr frac) 4))
  (args
   (cond ((string? den)
  (cons (number->string num)
    den))
 ((and (integer? (/ num 3))
   (integer? (/ den 2)))
  (cons (number->string (if trim? (/ num 3) num))
    (if trim?
    (string-append (number->string (/ den 2)) ".")
    (number->string den
 ((and (integer? (/ num 2))
   (integer? (/ den 2)))
  (cons (number->string (if trim? (/ num 2) num))
    (number->string (if trim? (/ den 2) den
 (else
  (cons (number->string num)
    (number->string den))
 (grob-interpret-markup grob #{ \my-format-procedure $args #})))

time =
#(define-music-function (parser location trm vals)((boolean? #t) pair?)

   ;; c/p from define-makups.scm
   (define log2
 (let ((divisor (log 2)))
   (lambda (z) (inexact->exact (/ (log z) divisor)

   ;; c/p from define-makups.scm
   (define (parse-simple-duration duration-string)
 "Parse the `duration-string', eg ''4..'' or ''breve.'',
and return a (log dots) list."
 (let ((match (regexp-exec (make-regexp 
"(breve|longa|maxima|[0-9]+)(\\.*)")

    duration-string)))
   (if (and match (string=? duration-string (match:substring match 0)))
   (let ((len (match:substring match 1))
 (dots (match:substring match 2)))
 (list (cond ((string=? len "breve") -1)
 ((string=? len "longa") -2)
 ((string=? len "maxima") -3)
 (else (log2 (string->number len
   (if dots (string-length dots) 0)))
   (ly:error (_ "not a valid duration string: ~a") 
duration-string


   (let* ((den (cdr vals))
  (num (car vals)))
 (if (string? den)
 (let* ((parsed (parse-simple-duration den)))
   ;; TODO lazy bump ...
   (cond ((and (= -1 (car parsed)) (zero? (cadr parsed)))
  (set! den 1)
  (set! num (* 2 num)))
 ((and (= -1 (car parsed)) (= 1 (cadr parsed)))
  (set! den 1)
  (set! num (* 3 num)))
 ((and (= -2 (car parsed)) (zero? (cadr parsed)))
  (set! den 1)
  (set! num (* 4 num)))
 ((and (= -2 (car parsed)) (= 1 (cadr parsed)))
  (set! den 1)
  (set! num (* 6 num)))
 (else (ly:error "not smart enough to handle ~a" den)

 #{
   \temporary \override Staff.TimeSignature.stencil =
   #(format-time-sig-with-note vals trm)
   $(make-music
 'TimeSignatureMusic
 'beat-structure '()
 'denominator den
 'numerator num)
 #}))

\relative c' {

  \override Staff.TimeSignature.Y-offset = 5

  \time 9/4
  \repeat unfold 9 c4

  \time 3/4
  \repeat unfold 3 c4

  \time ##f 3/4
  \repeat unfold 3 c4

  \time 7/4
  \repeat unfold 7 c4

  \time 12/2
  \repeat unfold 4 c1.

  \time #'(3 . "breve.")
  \repeat unfold 3 c\breve.


  \time #'(3 . "longa")
  \repeat unfold 3 c\longa

  \time #'(4 . "longa.")
  \repeat unfold 4 c\longa.

  \time #(cons 4 "breve")
  \clef bass
  f\breve-> c-> d-> c->

  \bar"|."
}

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


Re: lost in trying to fine oll-core and or package.ily

2019-10-16 Thread David Wright
On Tue 15 Oct 2019 at 14:34:25 (+), Urs Liska wrote:
> 
> For example call LilyPond with (something like (adjust to the Windows 
> environment)
>   lilypond-windows.exe -I C:\openLilyLib path\to\document.loy
  ↑
Does this mean the trailing slash bug¹ been fixed?

https://lists.gnu.org/archive/html/lilypond-user/2018-08/msg00235.html
(The thread covers several other related aspects of -I and other switches.)

¹ as documented in "Usage" 2.19.83, p3, boxed note.



Cheers,
David.

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


time signature 4 / \breve ?

2019-10-16 Thread Paul Scott
Is it possible to write a time signature 4 / \breve ?

This occurs in Carmina Burana.

Thank you for any ideas,

Paul



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


Re: Tuplets up and down at the same musical moment

2019-10-16 Thread Kieren MacMillan
Hi Andrew,

> Any clues what greater context could be affecting this?

Could it be the same problem as in this thread 
?

Just a thought.
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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


Re: lost in trying to fine oll-core and or package.ily

2019-10-16 Thread David Wright
On Wed 16 Oct 2019 at 00:17:06 (-0400), Freeman Gilmore wrote:
> On Tue, Oct 15, 2019 at 7:16 PM Urs Liska  wrote:
> 
> > Simon has already given a very clear answer, but I want to add some more
> > examples that may help you understanding the context and a part of your
> > question that may not be fully covered yet.
> >
> The following is making it clear, i have 5 questions below.
> >
> > Say you have a document
> >   C:\myscores\alleluja.ly
> > which contains a line
> >   \include "my-config.ily"
> > (note that the file extensions are not significant but only *conventions*,
> > .ly typically indication LilyPond documents and .ily *i*nclude ly files)
> >
> > If you navigate to C:\myscores and compile this file using
> >   lilypond-windows.exe alleluja.ly
> > LilyPond will look for the file my-config.ily first in the directory of
> > the main file (C:\myscores) and then in some directories in the LilyPond
> > installation itself.
> >
> > However, if you compile using
> >   lilypond-windows.exe -I C:\my-lilypond-library alleluja.ly
> > then LilyPond will *additionally* look for the include file in the
> > directory C:\my-lilypond-library.
> >
> > If the \include statement references not simply a file but a relative path
> > then the include file will be looked for in all item of the search path:
> >   \include "lyriclib/hymns.ily"
> > would then find files like
> >   C:\myscores\lyriclib\hymns.ily
> >   C.\my-lilypons-library\lyriclib\hymns.ily
   ↑ is a colon

> 1, Why would you do this?

Were C:\my-lilypond-library to contain a dozen subdirectories
(lyriclib, noteslib, tablib, chordlib, say), it would be impractical
to specify them all in the command line. In my posted example, I had
three: the parent, margins and part-midis.

The penalty is having to specify the subdirectory with the filename,
as in \include lyriclib/hymns.ily above. For each include directive,
the -I directories are searched from left to right until a filename
matches.

> 2, What stops you from searching the whole file system?

In theory, nothing. In practice, the command line would probably be
too long as you'd have to specify every "upper-level" directory with
an -I switch. (By upper-level, I mean any directory above the path
in the \include directive itself.)

Note that -I C:\ does not imply that all the top-level directories in
C:\ are searched: there's no recursion here. Each filename that is
included consists entirely of one (optional) -I value concatentated
with one \include value; nothing in between.

> >   This is how openLilyLib is loaded. If you have oll-core stored so that
> >   C:\openLilyLib\oll-core\package.ily
> >   is a file and call LilyPond with
> >   lilypond-windows.exe -I C:\openLilyLib alleluja.ly
> >   then
> >   \include "oll-core/package.ily"
> >   will find the file because the search path C:\openLilyLib plus the
> > relative path given in the \include statement "oll-
> >   core/package.ily" will be joined to C:\openLilyLib\oll-core\package.ily

> 1, Using the include: \include “C:\openLilyLib\oll-core\package.ily” in
> alleluja.ly .   Would lilypond-windows.exe  alleluja.ly work?
> 
> 2, If not, why?

You need to distinguish directory names being handed to -I in the
command line from paths being handed to \include directives.

. For -I, use the conventions of your operating system (though I don't
  know how Windows deals with the "drive" names thenselves, as linux
  doesn't work that way; they *should* work).

. For \include, use the forward slash (/), and make sure too that you
  don't use 66/99 double quotation marks instead of ASCII ones. So
\include “C:\openLilyLib\oll-core\package.ily”
  becomes
\include "C:/openLilyLib/oll-core/package.ily"

> 3,Before you stated “Then you need to add C:\openLilyLib to LilyPond’s
> search path”; is this what you mean:   lilypond-windows.exe -I
> C:\openLilyLib alleluja.ly

Assuming this line is being split by your email client's attempt to
generate a text representation of your HTML postings, then it should
be correct.

lilypond-windows.exe -I C:\openLilyLib alleluja.ly

So C:\openLilyLib should be where you installed whatever you downloaded.
You might have seen this already:

https://github.com/openlilylib/oll-core/wiki

> > On Tue 15 Oct 2019 at 11:16:43 (-0400), Freeman Gilmore wrote:
> > > Now if I use the include with the path  C:\openLilyLib , dose Lilypond
> > > search all the directories and subdirectories of openLilyLib or do i need
> > > an include  ...\directory\file for each file I use?

The latter: only the directory given with -I is searched, as noted above.

Cheers,
David.

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


Re: Tuplets up and down at the same musical moment

2019-10-16 Thread Andrew Bernard
Any clues what greater context could be affecting this?

Andrew


On Wed, 16 Oct 2019 at 22:18, Andrew Bernard 
wrote:

> Pardon this somewhat strange question. The following MWE showing how to
> tweak tuplet brackets up and down at the same musical moment works
> perfectly fine (!). But in the context of my larger score the inner bracket
> refuses to move with the tweak. I can't provide a minimal example for the
> error because it only occurs in the full score.
>
> What would cause something like this to fail? [A bug? My stupidity? I
> don't know.]
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Tweaking glissando timing stems

2019-10-16 Thread Thomas Morley
Am Mo., 14. Okt. 2019 um 12:22 Uhr schrieb Leo Correia de Verdier
:

> When you write that "inner beams positions can’t be affected from 
> Glissando.after-line-breaking", do you mean it’s impossible, that they would 
> need to be recreated rather than repositioned or just that the actual code 
> can’t handle them yet?

The code recreates Stems (and moves Script), but it can't _move_ Beams.
It would likely be possible to completely recreate Beam.stencil,
though this is inconveniant and would add a lot code...

Currently, this means my code sometimes returns ugly output for Beams,
which will need to be corrected with an additional override for
Beam.positions.


Cheer,
  Harm

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


Re: Makefile help!

2019-10-16 Thread karl
foxfanfare:
> piano-solo.01.pdf: piano-solo.01.ly \
>   $(general) \
>   dialogs.01.ily \
>   global.01.ily \
>   notes.piano-solo.01.ily \
>   pedals.01.ily
...
> ... and so on! Is there a better way to write this only one time?

Try something like:

piano-solo.%.pdf: piano-solo.%.ly \
$(general) \
dialogs.%.ily \
global.%.ily \
notes.piano-solo.%.ily \
pedals.%.ily
...

Have a look at "Syntax of Static Pattern Rules" in make documentation
$ info make

Also, you could use a dependancy finder like:
 http://aspodata.se/git/musik/bin/depend_ly

Regards,
/Karl Hammar



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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6 and Catalina 10.15

2019-10-16 Thread Hans Åberg

> On 16 Oct 2019, at 23:08, Thomas Scharkowski  
> wrote:
> 
>  Original-Nachricht 
>>> On 16 Oct 2019, at 21:54, Thomas Scharkowski  
>>> wrote:
>>> 
>>>  Original-Nachricht 
> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
> wrote:
> 
> I am cautious and did not upgrade to 10.15 Catalina yet.
> 
> On my current (10.14.6) system lilypond-devel does not build:
> 
>> error: expected initializer before '__OSX_AVAILABLE_STARTING'
>> https://trac.macports.org/ticket/59130
> 
> Would this be different on Catalina?
 The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it 
 yet, though.
> I'd rather try to build lilypond-devel on my working system before 
> upgrading.
 It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 
 10 (which you might try).
 Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying 
 because stuff is updated rather fast right now.
>>> 
>>> Ok, I'll try to downgrade to Xcode 10.
>> I believe one can have them side-by-side and use xcode-select to choose, 
>> though I haven’t tried it.
> lilypond-devel built with Xcode 10.3 on MacOS 10.14.6!
> :-)

Good, meanwhile, the port lilypond-devel seems to work on MacOS 10.15, or at 
least a small snippet compiled.

> Thank you,

You are welcome.



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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Thomas Scharkowski

 Original-Nachricht 



On 16 Oct 2019, at 21:54, Thomas Scharkowski  wrote:

 Original-Nachricht 

On 16 Oct 2019, at 18:35, Thomas Scharkowski  wrote:

I am cautious and did not upgrade to 10.15 Catalina yet.

On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Would this be different on Catalina?

The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.

I'd rather try to build lilypond-devel on my working system before upgrading.

It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).
Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.


Ok, I'll try to downgrade to Xcode 10.


I believe one can have them side-by-side and use xcode-select to choose, though 
I haven’t tried it.




lilypond-devel built with Xcode 10.3 on MacOS 10.14.6!
:-)
Thank you,
Thomas

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


Makefile help!

2019-10-16 Thread foxfanfare
Hi all,

I'm currently working on a big project and learning how to use a makefile
for convenience. I'd like to know if some guys here knows how to write a
proper loop? I have the following example which can generate the PDF for
every single movement of a large set of pieces (there is 35 pieces in
total):

piano-solo.01.pdf: piano-solo.01.ly \
$(general) \
dialogs.01.ily \
global.01.ily \
notes.piano-solo.01.ily \
pedals.01.ily

piano-solo.02.pdf: piano-solo.02.ly \
$(general) \
dialogs.02.ily \
global.02.ily \
notes.piano-solo.02.ily \
pedals.02.ily

... and so on! Is there a better way to write this only one time?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Hans Åberg

> On 16 Oct 2019, at 21:54, Thomas Scharkowski  
> wrote:
> 
>  Original-Nachricht 
>>> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
>>> wrote:
>>> 
>>> I am cautious and did not upgrade to 10.15 Catalina yet.
>>> 
>>> On my current (10.14.6) system lilypond-devel does not build:
>>> 
 error: expected initializer before '__OSX_AVAILABLE_STARTING'
 https://trac.macports.org/ticket/59130
>>> 
>>> Would this be different on Catalina?
>> The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it 
>> yet, though.
>>> I'd rather try to build lilypond-devel on my working system before 
>>> upgrading.
>> It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 
>> 10 (which you might try).
>> Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying 
>> because stuff is updated rather fast right now.
> 
> Ok, I'll try to downgrade to Xcode 10.

I believe one can have them side-by-side and use xcode-select to choose, though 
I haven’t tried it.



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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Thomas Scharkowski

 Original-Nachricht 



On 16 Oct 2019, at 18:35, Thomas Scharkowski  wrote:

I am cautious and did not upgrade to 10.15 Catalina yet.

On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Would this be different on Catalina?


The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.


I'd rather try to build lilypond-devel on my working system before upgrading.


It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).

Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.



Ok, I'll try to downgrade to Xcode 10.

Thomas

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


Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

2019-10-16 Thread Kieren MacMillan
Hi Robert,

> 16 bars in normal 2-staff PianoStaff on 4 systems. Then follow 4 bars in 
> 3-staff PianoStaff on one system, followed by 12 bars in in normal 2-staff 
> PianoStaff on three systems.

How about this?

%%%  SNIPPET BEGINS
\version "2.19.83"

showMMRs = {
  \set Staff.keepAliveInterfaces =
#'( rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}

letStaffVanish = \set Staff.keepAliveInterfaces = #'()

breaks = {
  \repeat unfold 4 { \repeat unfold 4 { s1 \noBreak } \break }
  \repeat unfold 4 { s1 \noBreak } \break
  \repeat unfold 3 { \repeat unfold 4 { s1 \noBreak } \break }
}

thirdStaffMusic = {
  \clef bass
  R1*16
  \showMMRs c1 1 1 1
  \letStaffVanish
  R1*12
}

\layout {
  \context {
\PianoStaff
\remove "Keep_alive_together_engraver"
\RemoveAllEmptyStaves
  }
}

\score {
  \new PianoStaff <<
\new Staff << \repeat unfold 32 { c'4 4 4 4 } \breaks >>
\new Staff << \repeat unfold 32 { c'4 4 4 4 } >>
\new Staff \thirdStaffMusic
  >>
}
%%%  SNIPPET ENDS

Hope that helps!
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Werner LEMBERG
 error: expected initializer before '__OSX_AVAILABLE_STARTING'
 https://trac.macports.org/ticket/59130
>>
>> Try to install gcc9, then retry installation of lilypond-devel
>> (with `port clean lilypond-devel' before doing that).
>
> I have already done this - no success.

OK.  Unfortunately, I can't help more.


Werner



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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Hans Åberg

> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
> wrote:
> 
> I am cautious and did not upgrade to 10.15 Catalina yet.
> 
> On my current (10.14.6) system lilypond-devel does not build:
> 
> > error: expected initializer before '__OSX_AVAILABLE_STARTING'
> > https://trac.macports.org/ticket/59130
> 
> Would this be different on Catalina?

The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.

> I'd rather try to build lilypond-devel on my working system before upgrading.

It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).

Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.



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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Thomas Scharkowski

 Original-Nachricht 



On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Try to install gcc9, then retry installation of lilypond-devel (with
`port clean lilypond-devel' before doing that).


 Werner


Thank you,

I have already done this - no success.

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


Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Werner LEMBERG

> On my current (10.14.6) system lilypond-devel does not build:
> 
>> error: expected initializer before '__OSX_AVAILABLE_STARTING'
>> https://trac.macports.org/ticket/59130

Try to install gcc9, then retry installation of lilypond-devel (with
`port clean lilypond-devel' before doing that).


Werner

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


Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

2019-10-16 Thread Robert Blackstone
Hi Kieren,

Thanks for your reaction. 

I could not imagine a MWE for this problem. But I can tell you what my “trick'’ 
is and I can also send you the whole file.

It is Federico Mompou's Prelude No. 9. It begins with 16 bars in normal 2-staff 
PianoStaff on 4 systems. Then follow 4 bars in 3-staff PianoStaff on one 
system, followed by 12 bars in in normal 2-staff PianoStaff on three systems.  
My “trick” is to split the whole into tree separate scores and “concatenate" 
them in one _ly.tex - file. (I’m using TeXShop as editor).
 
It works but for the too short system with the  3-staff PianoStaff. If I could 
stretch that a bit it would be OK.

If it is OK with you to send you the complete file I will do that after having 
added a few lacking dynamic signs.

Best regards,
Robert

> On 16 Oct 2019, at 12:30, Kieren MacMillan  
> wrote:
> 
> Hi Robert,
> 
>> Is there a “valid” possibility to insert into a normal 2-staff PianoStaff a 
>> few bars with a 3-staff PianoStaff?
> 
> Absolutely. [Note: In most traditional engraving, such a 3-staff section 
> would usually fill the entire system, even if that meant having full-measure 
> rests in measures at the beginning or end of the system.]
> 
>> I used some trick but the result is unsatisfactory since that  
>> 3-staff-segment does not fill the space available in that system and I have 
>> not been able to stretch it a bit to reach the right-side margin. The result 
>> is a  sort of indentation in the wrong place.
> 
> It is essentially impossible to diagnose the issue with your example because 
> you did not provide code (preferably a MWE) to consider.
> 
> Best,
> Kieren.
> 
> 
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
> 


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


64 bit - MacPorts lilypond-devel on Mojave 10.14.6

2019-10-16 Thread Thomas Scharkowski

I am cautious and did not upgrade to 10.15 Catalina yet.

On my current (10.14.6) system lilypond-devel does not build:

> error: expected initializer before '__OSX_AVAILABLE_STARTING'
> https://trac.macports.org/ticket/59130

Would this be different on Catalina?
I'd rather try to build lilypond-devel on my working system before 
upgrading.


Thomas

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


Re: 64 bit

2019-10-16 Thread Werner LEMBERG

>>> Maybe if a compiler is not listed as a dependency, it will just
>>> take what is currently installed.
>> 
>> Yes.
> 
> So perhaps it suffices to remove it from the lilypond-devel
> dependency list to get it to install.

What dependency?


Werner

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


Re: 64 bit

2019-10-16 Thread Hans Åberg


> On 16 Oct 2019, at 15:53, Mario Bolognani  wrote:
> 
> is there any simple way to run Frescobaldi+LilyPond on Catalina? Maybe in a 
> not so delayed future?

It is also in MacPorts:
% port info frescobaldi
frescobaldi @2.20.0_1 (editors, python)

% port info frescobaldi-devel
frescobaldi-devel @20180806 (editors, python)

> Your suggestions are for experienced users not for musicians with an amateur 
> approach to the platform?

It is not difficult to install and run MacPorts. The problem discussed is that 
not everything has been updated yet.

To install MacPorts, download the installer here and run it:
  https://www.macports.org/install.php



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


64 bit

2019-10-16 Thread Mario Bolognani
Dear developers,

is there any simple way to run Frescobaldi+LilyPond on Catalina? Maybe in a not 
so delayed future? Your suggestions are for experienced users not for musicians 
with an amateur approach to the platform?


Mario Bolognani



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


Re: 64 bit

2019-10-16 Thread Hans Åberg

> On 16 Oct 2019, at 15:37, Werner LEMBERG  wrote:
> 
>> Maybe if a compiler is not listed as a dependency, it will just take
>> what is currently installed.
> 
> Yes.

So perhaps it suffices to remove it from the lilypond-devel dependency list to 
get it to install.



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


Re: 64 bit

2019-10-16 Thread Werner LEMBERG

> It may be the case that only lilypond-devel is actively maintained,

Probably true.  I only take care of `lilypond-devel' and know nothing
of `lilypond'.

> but it was reported on the devel list that the dependency gcc8
> didn’t build.

The patch to fall back to gcc9 has been applied to the git repository
already.

> Curiously, it is not listed as a dependency for port lilypond.

MacPorts tries to avoid explicit dependencies on compilers.  Instead,
possibly working compilers are added to the fallback list, and not
working compilers are added to the blacklist.

> Maybe if a compiler is not listed as a dependency, it will just take
> what is currently installed.

Yes.


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


Re: Slurring into another voice without breaking a beam

2019-10-16 Thread Ben

On 10/16/2019 9:32 AM, Simon Albrecht wrote:

Hi Ben,

could you maybe submit an issue to 
? If not, I’ll do it 
myself, but I’m currently short on time…


Best, Simon


Oh, good idea!

I'll submit it shortly :) Have a great day!





On 16.10.19 13:15, Ben wrote:

On 10/15/2019 6:16 PM, Simon Albrecht wrote:

On 15.10.19 23:35, Ben wrote:

On 10/15/2019 4:43 PM, Simon Albrecht wrote:

On 15.10.19 14:33, Ben wrote:

What version(s) are you using Simon?



The same, basically…

Are you loading modules using the ‘new’ syntax? i.e.

\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

Best, Simon


Yes, copied your code and pasted it as is.



Then I’m afraid I’m out of ideas… can you send a minimal example?

Best, Simon


Sure, no problem. The code should look familiar. :)

Here's an attachment showing how the shapeII *appears* to be working, 
however there are always warnings - even from a fresh git clone. The 
version warnings keep coming up...sorry I don't know why it's happening.


For testing, I simulated a new user to LilyPond: installed a fresh 
virtual machine, installed unstable LilyPond, cloned openlilylib, and 
added it to the path in Frescobaldi as I have done in my production 
machine.


Everything is configured correctly as far as I can tell. Maybe 
something in oll-core needs an update, just guessing from the log 
messages. I highlighted some of the log for you.


Thanks for your help Simon!

%%
\version "2.19.83"
\language "english"
\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

\relative {
   \time 12/8
   \stemDown
   8  ^(  ) (
  ) ^(  )  |
 \stemDown
   8  ^(  ) (
  ) ^(  ) 
}
%%%

Log output:

Processing `C:/Users/Ben/Desktop/file.ly'

Parsing...

/openlilylib/snippets/notation-snippets/shaping-bezier-curves/shapeII/module.ily:2:10:*error: 
cannot find file: 
`ly/_internal/utilities/lilypond-version-predicates.ily'*


*\include "ly/_internal/utilities/lilypond-version-predicates.ily"*


C:/Users/Ben/Desktop/file.ly:13:5: warning:


openLilyLib. DEPRECATION:

*Using 'lilypond-less-than?' from oll-core is deprecated.*

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, *and all uses of 'lilypond-less-than?'*

**

*should properly be replaced with that.*


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions 



-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(20.6 . -3.7)) _( bf>(


C:/Users/Ben/Desktop/file.ly:17:5: warning:


openLilyLib. DEPRECATION:

Using 'lilypond-less-than?' from oll-core is deprecated.

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, and all uses of 'lilypond-less-than?'

should properly be replaced with that.


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions 



-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(.2 . -.7)) _( bf>(


Completed successfully in 0.8".


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


Re: Slurring into another voice without breaking a beam

2019-10-16 Thread Simon Albrecht

Hi Ben,

could you maybe submit an issue to 
? If not, I’ll do it 
myself, but I’m currently short on time…


Best, Simon

On 16.10.19 13:15, Ben wrote:

On 10/15/2019 6:16 PM, Simon Albrecht wrote:

On 15.10.19 23:35, Ben wrote:

On 10/15/2019 4:43 PM, Simon Albrecht wrote:

On 15.10.19 14:33, Ben wrote:

What version(s) are you using Simon?



The same, basically…

Are you loading modules using the ‘new’ syntax? i.e.

\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

Best, Simon


Yes, copied your code and pasted it as is.



Then I’m afraid I’m out of ideas… can you send a minimal example?

Best, Simon


Sure, no problem. The code should look familiar. :)

Here's an attachment showing how the shapeII *appears* to be working, 
however there are always warnings - even from a fresh git clone. The 
version warnings keep coming up...sorry I don't know why it's happening.


For testing, I simulated a new user to LilyPond: installed a fresh 
virtual machine, installed unstable LilyPond, cloned openlilylib, and 
added it to the path in Frescobaldi as I have done in my production 
machine.


Everything is configured correctly as far as I can tell. Maybe 
something in oll-core needs an update, just guessing from the log 
messages. I highlighted some of the log for you.


Thanks for your help Simon!

%%
\version "2.19.83"
\language "english"
\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

\relative {
   \time 12/8
   \stemDown
   8  ^(  ) (
  ) ^(  )  |
 \stemDown
   8  ^(  ) (
  ) ^(  ) 
}
%%%

Log output:

Processing `C:/Users/Ben/Desktop/file.ly'

Parsing...

/openlilylib/snippets/notation-snippets/shaping-bezier-curves/shapeII/module.ily:2:10:*error: 
cannot find file: 
`ly/_internal/utilities/lilypond-version-predicates.ily'*


*\include "ly/_internal/utilities/lilypond-version-predicates.ily"*


C:/Users/Ben/Desktop/file.ly:13:5: warning:


openLilyLib. DEPRECATION:

*Using 'lilypond-less-than?' from oll-core is deprecated.*

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, *and all uses of 'lilypond-less-than?'*

**

*should properly be replaced with that.*


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions

-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(20.6 . -3.7)) _( bf>(


C:/Users/Ben/Desktop/file.ly:17:5: warning:


openLilyLib. DEPRECATION:

Using 'lilypond-less-than?' from oll-core is deprecated.

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, and all uses of 'lilypond-less-than?'

should properly be replaced with that.


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions

-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(.2 . -.7)) _( bf>(


Completed successfully in 0.8".




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


Re: 64 bit

2019-10-16 Thread Hans Åberg

> On 16 Oct 2019, at 09:09, Alan Shaw  wrote:
> 
> PS By doing this I got 2.18.2.

This is 'sudo port install lilypond’. It may be the case that only 
lilypond-devel is actively maintained, but it was reported on the devel list 
that the dependency gcc8 didn’t build. Curiously, it is not listed as a 
dependency for port lilypond. Maybe if a compiler is not listed as a 
dependency, it will just take what is currently installed.



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


Re: 64 bit

2019-10-16 Thread Alan Shaw
PS By doing this I got 2.18.2.

On Wed, Oct 16, 2019 at 12:06 AM Alan Shaw  wrote:

> Here's what I did:
> 1.
> https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/
> (step 17, sudo make install, failed, but I ran it again and it succeeded.)
> 2. https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00040.html
>
> Both of these took a very long time because many dependencies had to be
> installed. Take a long lunch.
>
> On Tue, Oct 15, 2019 at 10:12 PM marco.massobrio <
> marco.massob...@gmail.com> wrote:
>
>>
>> I Havel installed catalina 10.15 on my Mac andiamo lilypond 2.19.83 don't
>> run
>> HELP!
>>
>> Inviato da smartphone Samsung Galaxy.
>> ___
>> 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: 64 bit

2019-10-16 Thread Alan Shaw
Here's what I did:
1.
https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/
(step 17, sudo make install, failed, but I ran it again and it succeeded.)
2. https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00040.html

Both of these took a very long time because many dependencies had to be
installed. Take a long lunch.

On Tue, Oct 15, 2019 at 10:12 PM marco.massobrio 
wrote:

>
> I Havel installed catalina 10.15 on my Mac andiamo lilypond 2.19.83 don't
> run
> HELP!
>
> Inviato da smartphone Samsung Galaxy.
> ___
> 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


Tuplets up and down at the same musical moment

2019-10-16 Thread Andrew Bernard
Pardon this somewhat strange question. The following MWE showing how to
tweak tuplet brackets up and down at the same musical moment works
perfectly fine (!). But in the context of my larger score the inner bracket
refuses to move with the tweak. I can't provide a minimal example for the
error because it only occurs in the full score.

What would cause something like this to fail? [A bug? My stupidity? I don't
know.]

Using 2.19.83.

%
\version "2.19.83"

% tuplets up and down at same musical moment

treble = {
  \time 1/4
  \override TupletBracket.bracket-visibility = ##t
  \tupletUp
  \tuplet 5/4 {
c''16
\tupletDown
\tuplet 3/2 { c'' c'' c'' } c'' c''
  } |
  \tupletDown
  \tuplet 5/4 {
\tweak TupletBracket.direction #UP
\tuplet 3/2 { c''16  c'' c'' } c'' c'' c''
  } |

}

bass = {
  \clef bass
  \override TupletBracket.bracket-visibility = ##t

  \tweak TupletBracket.direction #UP
  \tuplet 5/4 {
\tweak direction #DOWN
\tuplet 5/4 { f,,32 g,, bes,, b,, c, } ees,8.^> ^~
  } |
  ees,1 |

}

\score {
  <<
\new Staff { \treble }
\new Staff { \bass }
  >>
  \layout {}
}

%

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


Re: Slurring into another voice without breaking a beam

2019-10-16 Thread Ben

On 10/15/2019 6:16 PM, Simon Albrecht wrote:

On 15.10.19 23:35, Ben wrote:

On 10/15/2019 4:43 PM, Simon Albrecht wrote:

On 15.10.19 14:33, Ben wrote:

What version(s) are you using Simon?



The same, basically…

Are you loading modules using the ‘new’ syntax? i.e.

\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

Best, Simon


Yes, copied your code and pasted it as is.



Then I’m afraid I’m out of ideas… can you send a minimal example?

Best, Simon


Sure, no problem. The code should look familiar. :)

Here's an attachment showing how the shapeII *appears* to be working, 
however there are always warnings - even from a fresh git clone. The 
version warnings keep coming up...sorry I don't know why it's happening.


For testing, I simulated a new user to LilyPond: installed a fresh 
virtual machine, installed unstable LilyPond, cloned openlilylib, and 
added it to the path in Frescobaldi as I have done in my production machine.


Everything is configured correctly as far as I can tell. Maybe something 
in oll-core needs an update, just guessing from the log messages. I 
highlighted some of the log for you.


Thanks for your help Simon!

%%
\version "2.19.83"
\language "english"
\include "oll-core/package.ily"
\loadModule snippets.notation-snippets.shaping-bezier-curves.shapeII

\relative {
   \time 12/8
   \stemDown
   8  ^(  ) (
  ) ^(  )  |
 \stemDown
   8  ^(  ) (
  ) ^(  ) 
}
%%%

Log output:

Processing `C:/Users/Ben/Desktop/file.ly'

Parsing...

/openlilylib/snippets/notation-snippets/shaping-bezier-curves/shapeII/module.ily:2:10:*error: 
cannot find file: `ly/_internal/utilities/lilypond-version-predicates.ily'*


*\include "ly/_internal/utilities/lilypond-version-predicates.ily"*


C:/Users/Ben/Desktop/file.ly:13:5: warning:


openLilyLib. DEPRECATION:

*Using 'lilypond-less-than?' from oll-core is deprecated.*

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, *and all uses of 'lilypond-less-than?'*

**

*should properly be replaced with that.*


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions

-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(20.6 . -3.7)) _( bf>(


C:/Users/Ben/Desktop/file.ly:17:5: warning:


openLilyLib. DEPRECATION:

Using 'lilypond-less-than?' from oll-core is deprecated.

openLilyLib explicitly does not suppport LilyPond 2.18 anymore,

so users are expected to use the development version 2.19 or a

later stable release.

Since LilyPond 2.19.57 the version predicate 'ly:version?' is

included in LilyPond, and all uses of 'lilypond-less-than?'

should properly be replaced with that.


Reference:

http://lilypond.org/doc/v2.19/Documentation/usage/writing-code-to-support-multiple-versions

-

\shapeII #'((0 . -.7)(p 30 .4)(p 30 .4)(.2 . -.7)) _( bf>(


Completed successfully in 0.8".


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


Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

2019-10-16 Thread Kieren MacMillan
Hi Robert,

> Is there a “valid” possibility to insert into a normal 2-staff PianoStaff a 
> few bars with a 3-staff PianoStaff?

Absolutely. [Note: In most traditional engraving, such a 3-staff section would 
usually fill the entire system, even if that meant having full-measure rests in 
measures at the beginning or end of the system.]

> I used some trick but the result is unsatisfactory since that  
> 3-staff-segment does not fill the space available in that system and I have 
> not been able to stretch it a bit to reach the right-side margin. The result 
> is a  sort of indentation in the wrong place.

It is essentially impossible to diagnose the issue with your example because 
you did not provide code (preferably a MWE) to consider.

Best,
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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


Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

2019-10-16 Thread Robert Blackstone
Dear all,

Is there a “valid” possibility to insert into a normal 2-staff PianoStaff a few 
bars with a 3-staff PianoStaff?

I used some trick but the result is unsatisfactory since that  3-staff-segment 
does not fill the space available in that system and I have not been able to 
stretch it a bit to reach the right-side margin. The result is a  sort of 
indentation in the wrong place.

Probably the player would not care but from an aesthetic point of view it is 
unacceptable. 
 
Thanks in advance for any advice or suggestion.

Best regards,

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