Any interest in participating in GSoC for SugarLabs project that utilizes lilypond?

[Devin Ulibarri]

Hi,

I have been working together with the SugarLabs team to create a visual
programming language for music called Music Blocks (MB). Users code with
blocks (like Scratch), and they can also export to lilypond code.
SugarLabs is participating again in Google Summer of Code (GSoC) and we
would love to have another person on board as a mentor (or a candidate,
if any are reading this message).

It would be great to have another person involved as a mentor to help
inform the kind of lilypond code we are generating with our program. No
one here is particularly knowledgeable with Lilypond. We just read the
docs and create something that works well enough. We think that having
another, more knowledgeable, person would be very helpful for the summer.

Links: The development version is at walterbender.github.io/musicblocks,
but a version that can generate PDF using lilypond software on the
server is available at https://homegrownapps.tk/musicblocks/

Short instructions on Lilypond generation with MB is located at
https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS

This is the Google Summer of Code description:
(Originally Published at
https://wiki.sugarlabs.org/go/Summer_of_Code/2018#Project_Ideas)
Brief explanation
Music Blocks is capable of exporting Lilypond code of which general
instructions can be found here in the Music Blocks guide and its source
code can be found here. We would like to 1) document how the Music
Blocks source code works for current and future developers to learn and
benefit from, 2) project manage this portion of Music Blocks development
(e.g. "what works" and "what needs to be done". An example of a draft of
a simple type of this analysis exists for you to start from.), and 3)
improve existing code where needed and implement needed features.
Expected results
Detailed documentation created for developer audience that details
how Music Blocks exports to Lilypond; documentation to help manage what
needs to be completed; and implement and improve lilypond export features.
Knowledge prerequisites
Literacy in reading music; functional knowledge of Lilypond code
(some of your own scores would be nice); Organizational and Project
Management Skills; JavaScript

If you are interested, please let me know.

Thanks!

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

GhostScript Fail (regression 2.19.17 to 2.19.18)

[Andrew Smith]

I'm getting a failure all-around on a new Arch VM I'm running in my windows
machine. I'm using lyp here to make a/b version testing easier. Basically,
the gs command is failing when liilypond runs it but it works just fine
when I copy/paste it and run it manually.

2.19.17 works, but 2.19.18 fails. Shell info + file is below.
GhostScript system version is 9.22.

https://gist.github.com/andrewcsmith/eb17a859e62921f3ad50a4c5298628e9

This is urgent for me, as I don't have access to the old machine where this
worked, and I have some libraries that use the recent font changes --
thanks a lot.


```
[vagrant@bazinga ly_test]$ lyp use 2.19.18
Using Lilypond version 2.19.18
[vagrant@bazinga ly_test]$ lyp compile test.ly
Lyp 1.3.5
GNU LilyPond 2.19.18
Processing `/tmp/lyp/wrappers/test.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
-dDEVICEHEIGHTPOINTS=841.89
-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
-sOutputFile=./test.pdf -c.setpdfwrite -ftest.ps)' failed (256)

fatal error: failed files: "/tmp/lyp/wrappers/test.ly"

[vagrant@bazinga ly_test]$ lyp use 2.19.17
Using Lilypond version 2.19.17
[vagrant@bazinga ly_test]$ lyp compile test.ly
Lyp 1.3.5
GNU LilyPond 2.19.17
Processing `/tmp/lyp/wrappers/test.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
```

File:

\score {
\new Voice {
c'4 d' e' f'
}

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

Re: PDF woes

[Vaughan McAlley]

On 19 January 2018 at 10:13, Travis Weller  wrote:

> Hi Tim,
>
> The feature has worked wonderfully for me for many years. It uses PDF
> links that point to lilypond as a "helper app." I would guess I'm probably
> not the only one using it despite frescobaldi being popular. The change
> happened when I got a new computer.
>
> The links work with Acrobat... and I'd happily use Acrobat, but as I
> mentioned before it is a "known issue" that it won't update the PDF file
> when you typeset repeatedly. The lilypond website says to use Preview.app.
>
> Thanks,
> Travis
>
>
Apple seemed to break all my custom software every system update. The fix
was somewhere in the security settings, and never easy to find. Sometimes I
had to relearn XCode to recompile.

I did prefer Preview to look at my scores. Attached is the same score (on
Linux - I gave up on Apple) in Frescobaldi (Poppler) and the default Debian
PDF viewer. It needs to be viewed at 100% to compare them properly. The
main issue is the fuzzy staff line. But I overlook that for the convenience
of Frescobaldi.

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

Re: Left-handed fretboard?

[Thomas Morley]

2018-01-18 23:32 GMT+01:00 Torsten Hämmerle :
> Thomas Morley-2 wrote
>> Meanwhile I think supporting negative string-distance is a bad idea,
>> because too many detail-problems need adjustments. And using negative
>> string-distance was not intended as I introduced it. I should have
>> always gone for (abs ...). But this could be corrected...

https://sourceforge.net/p/testlilyissues/issues/5265/

> When driving through "Friederieke" today, I was thinking of (abs ...), too,
> but on the other hand - please don't beat me - give it a try and see what
> happens if you *set StaffSymbol.staff-space to #-1*.


It gives bad output and warnings, etc
Anything specific you want me to observe?

Best,
  Harm

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

Re: Phrasing slurs on two-voice stave

[Simon Albrecht]

On 22.01.2018 13:09, N. Andrew Walsh wrote:
What I'm trying to do is ensure that the phrasing slur extends to the 
last note of the bar. Problem is, the client wants the 16th notes on 
the lower voice, but the slur above. I've been using \stemDown and 
\stemUp to flip the stem directions, but this causes problems, as 
here, where the slur collides with the other voice's stems. Is there a 
more elegant/effective way of doing this? It also has to work for 
phrasing slurs across several measures.


Never use \stemDown and \stemUp for overriding the stem direction of an 
entire voice. You get exactly the same output as for the code you posted 
from this:


%%%
\version "2.19.80"
\relative c {
  \clef bass
  \time 4/8
  <<
    { d8. f16 d4 }
    \\
    { d16^\( f a f d a' f d\) }
  >>
}
%%

I would consider the following a semantically appropriate solution, 
though unfortunately the PhrasingSlur shape needs to be tweaked:


%%
\score {
  \relative c {
    \clef bass
    \time 4/8
    <<
  { d8.\=1 \( f16 d4 }
  \\
  { d16 f a f d a' f d\=1 \) }
    >>
  }
  \layout {
    \context {
  \Staff
  \consists "Phrasing_slur_engraver"
  \override PhrasingSlur.avoid-slur = #'outside
  \mergeDifferentlyDottedOn
    }
    \context {
  \Voice
  \remove "Phrasing_slur_engraver"
    }
  }
}
%%%

Best, Simon

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

Re: Phrasing slurs on two-voice stave

[Andrew Bernard]

Hi Andrew,

That's right, slurs are quadratic beziers and you can adjust the control
points. If you have used Adobe Illustrator it should be clear, for the
bezier curves there are the same.

Possibly more than you need to know, but some nice illustrations:

https://en.wikipedia.org/wiki/B%C3%A9zier_curve#Quadratic_B%C3%A9zier_curves

There's a much better slur shaping function called /shapeII available in
openlilylib. It has some small shortcomings or limitations but it is easier
to use and tweak. It has some good ways to specify the control points that
are not absolute coordinates. I think sometimes my scores consist entirely
of calls to /shapeII, so heavily do I use it. It works reliably for me.

Andrew


On 23 January 2018 at 02:12, N. Andrew Walsh 
wrote:

>
>
> Ah, thank you. And I also see that it's in the NR at 5.5.4. Very helpful!
> Am I correct in assuming that (phrasing)slurs are bezier curves, and thus
> the four control points listed for \shape behave the way bezier-curve
> control points do?
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Phrasing slurs on two-voice stave

[N. Andrew Walsh]

Hi Ben,

On Mon, Jan 22, 2018 at 1:59 PM, Ben  wrote:
>
> Hi,
>
> Personally, I would probably want the slur on the bottom as it's cleaner
> and easier to implement,
>

yes, and also notationally superior. But the client is, alas! a
hobbyist-composer who does things for "expressive" reasons and insists they
should be that way (I once got nearly into a shouting match because he had
directly translated the German "Attacke" [which means something like
"strike hard"] to the Italian "attacca" [which, as we know, means "continue
without break to the next movement"] and wouldn't believe he couldn't use
the latter as an expressive marking until I made him look it up in his
music dictionary). I would also point out that he puts a phrasing slur on
*every* phrase, throughout the piece, so this is a recurring issue. Sigh.


> but I guess you could play around and offset the slur to taste...
> [see attached]
>
>
Ah, thank you. And I also see that it's in the NR at 5.5.4. Very helpful!
Am I correct in assuming that (phrasing)slurs are bezier curves, and thus
the four control points listed for \shape behave the way bezier-curve
control points do?

Thanks again,

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

Re: Phrasing slurs on two-voice stave

[Ben]

On 1/22/2018 7:09 AM, N. Andrew Walsh wrote:

Hi List,

I have the following:

-
\version "2.19.80"

\relative c {
  \clef bass
  \time 4/8
 <<
   { \stemDown d16\( f a f d a' f d\) }
   \\
   { \stemUp d8. f16 d4 }
 >>
}
-

What I'm trying to do is ensure that the phrasing slur extends to the 
last note of the bar. Problem is, the client wants the 16th notes on 
the lower voice, but the slur above. I've been using \stemDown and 
\stemUp to flip the stem directions, but this causes problems, as 
here, where the slur collides with the other voice's stems. Is there a 
more elegant/effective way of doing this? It also has to work for 
phrasing slurs across several measures.


Cheers,

A



Hi,

Personally, I would probably want the slur on the bottom as it's cleaner 
and easier to implement, but I guess you could play around and offset 
the slur to taste...

[see attached]

You may have to compromise on what the finished slur looks like if it 
*must* be on top but, I hope this helps! :)


\version "2.19.80"

\relative c {
  \clef bass
  \time 4/8


 <<
   \shape #'((0 . 0) (0 . 3.5) (0 . 1.5) (0 . 0)) PhrasingSlur
   { \stemDown d16\( f a f d a' f d\) }
   \\
   { \stemUp d8. f16 d4 }
 >>

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

Phrasing slurs on two-voice stave

[N. Andrew Walsh]

Hi List,

I have the following:

-
\version "2.19.80"

\relative c {
  \clef bass
  \time 4/8
 <<
   { \stemDown d16\( f a f d a' f d\) }
   \\
   { \stemUp d8. f16 d4 }
 >>

}
-

What I'm trying to do is ensure that the phrasing slur extends to the last
note of the bar. Problem is, the client wants the 16th notes on the lower
voice, but the slur above. I've been using \stemDown and \stemUp to flip
the stem directions, but this causes problems, as here, where the slur
collides with the other voice's stems. Is there a more elegant/effective
way of doing this? It also has to work for phrasing slurs across several
measures.

Cheers,

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

Re: Transcriber title

[Torsten Hämmerle]

Hi Álvaro,

In the very likely case that you're using custom title markup anyway, I'd
like to mention the possibility of simply adding any desired non-standard
header variable to the \header section:

\header {
  transcriber = "Álvaro Cáceres Muñoz"
}

...and retrieving it later in your custom
bookTitleMarkup/scoreTitleMarkup/evenHeaderMarkup etc. exactly like any
other standard \header variable:

\fromproperty #'header:transcriber

On custom title markup, please refer to:
3.2.2 Custom titles headers and footers

  

HTH,
Torsten




--
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: Left-handed fretboard?

[Blöchl Bernhard]

I just jumped into that thread and will give my 2 cent:
I know violine- and guitar- and bass-teachers that have a large mirror 
in the teaching room for the leftys.


I have nothing against special coding if developers find it worth the 
time. But a mirror is a cheap, fast and easy solution.


regards


Am 18.01.2018 18:06, schrieb Karlin High:

On 1/18/2018 10:11 AM, Carl Sorensen wrote:
I believe that we should have some sort of display on the left-hand 
diagram indicating it's a left-hand diagram.  But I don't know what 
that should be.


Perhaps a left-pointing arrow at the top or the side of the fretboard?

If it's not text, it wouldn't need translation.


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