Trouble with EPS backend output use

[Joshua Nichols]

Hello List,

I'm having issues embedding EPS files produced in the back end feature in
2.18.x.

Whenever I create it, I cannot adequately open it in, lets say,
illustrator, or another vector editor, nor can I embed it in a pages or
lyx/latex file without getting errors about the file type.

I once could get it to inkscape, but it it couldn't produce the note heads
and various other vector fonts which I assumed were embedded in the file.

I work mainly with Frescobaldi on the front end.

Help?

​Sincerely,

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

RE: header

[Mark Stephen Mrotek]

Simon,

Your explanation makes sense, if my score were different numbers in one
opus.
My score is two movements of the same opus.
I shall try your suggestion.
Thank you for your kind attention.

Mark

-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de] 
Sent: Tuesday, July 12, 2016 4:27 PM
To: Mark Stephen Mrotek ; 'lilypond-user'

Subject: Re: header

On 13.07.2016 00:38, Mark Stephen Mrotek wrote:
> Simon,
>
> Thank you for your reply and reference to the manual.
> It does seem to be rather complicated for my simple score.
> \header
> \include
> \include
> Why is the "opus" printed with both "includes"?

Because it seems to be designed for a situation where you print 'op. xxx No.
1' on the first piece and 'op. xxx No. 2' on the second. The simpler
solution would be to set the opus field in the first score and leave it
empty (or unset it: opus = ##f) in the second.

HTH, Simon

>
> Mark
>
> -Original Message-
> From: Simon Albrecht [mailto:simon.albre...@mail.de]
> Sent: Tuesday, July 12, 2016 3:28 PM
> To: Mark Stephen Mrotek ; 'lilypond-user'
> 
> Subject: Re: header
>
> On 12.07.2016 23:15, Mark Stephen Mrotek wrote:
>> Hello,
>>
>> An outline of a two movement work (2.18.2)
>>
>> \header {
>>
>> Title = % title
>>
>> Composer = % composer
>>
>> Opus = % opus
>>
>> }
>>
>> \ include %here first movement
>>
>> \page break
>>
>> \include %here second movement
>>
>> Everything compiles as wanted, except the opus appears at the 
>> beginning of the second movement also.
>>
>> What should I adjust?
>>
> Redefine bookTitleMarkup and scoreTitleMarkup in \paper {}, so that 
> opus is referenced from the former, not the latter.
>  aders-
> and-footers#custom-layout-for-titles>
>
> Best, Simon
>


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

Re: header

[Simon Albrecht]

On 13.07.2016 00:38, Mark Stephen Mrotek wrote:

Simon,

Thank you for your reply and reference to the manual.
It does seem to be rather complicated for my simple score.
\header
\include
\include
Why is the "opus" printed with both "includes"?


Because it seems to be designed for a situation where you print ‘op. xxx 
No. 1’ on the first piece and ‘op. xxx No. 2’ on the second. The simpler 
solution would be to set the opus field in the first score and leave it 
empty (or unset it: opus = ##f) in the second.


HTH, Simon



Mark

-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de]
Sent: Tuesday, July 12, 2016 3:28 PM
To: Mark Stephen Mrotek ; 'lilypond-user'

Subject: Re: header

On 12.07.2016 23:15, Mark Stephen Mrotek wrote:

Hello,

An outline of a two movement work (2.18.2)

\header {

Title = % title

Composer = % composer

Opus = % opus

}

\ include %here first movement

\page break

\include %here second movement

Everything compiles as wanted, except the opus appears at the
beginning of the second movement also.

What should I adjust?


Redefine bookTitleMarkup and scoreTitleMarkup in \paper {}, so that opus is
referenced from the former, not the latter.


Best, Simon




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

RE: header

[Mark Stephen Mrotek]

Simon,

Thank you for your reply and reference to the manual. 
It does seem to be rather complicated for my simple score.
\header
\include
\include
Why is the "opus" printed with both "includes"?

Mark

-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de] 
Sent: Tuesday, July 12, 2016 3:28 PM
To: Mark Stephen Mrotek ; 'lilypond-user'

Subject: Re: header

On 12.07.2016 23:15, Mark Stephen Mrotek wrote:
>
> Hello,
>
> An outline of a two movement work (2.18.2)
>
> \header {
>
> Title = % title
>
> Composer = % composer
>
> Opus = % opus
>
> }
>
> \ include %here first movement
>
> \page break
>
> \include %here second movement
>
> Everything compiles as wanted, except the opus appears at the 
> beginning of the second movement also.
>
> What should I adjust?
>

Redefine bookTitleMarkup and scoreTitleMarkup in \paper {}, so that opus is
referenced from the former, not the latter.


Best, Simon


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

Re: header

[Simon Albrecht]

On 12.07.2016 23:15, Mark Stephen Mrotek wrote:


Hello,

An outline of a two movement work (2.18.2)

\header {

Title = % title

Composer = % composer

Opus = % opus

}

\ include %here first movement

\page break

\include %here second movement

Everything compiles as wanted, except the opus appears at the 
beginning of the second movement also.


What should I adjust?



Redefine bookTitleMarkup and scoreTitleMarkup in \paper {}, so that opus 
is referenced from the former, not the latter.



Best, Simon

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

Re: scrunching

[Noeck]

... and perhaps

3. http://lilypondblog.org/2013/11/engraving-challenges-horizontal-spacing/

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

header

[Mark Stephen Mrotek]

Hello,

 

An outline of a two movement work (2.18.2)

 

\header {

Title = % title

Composer = % composer

Opus = % opus

}

\ include %here first movement

\page break

\include %here second movement

 

Everything compiles as wanted, except the opus appears at the beginning of
the second movement also.

 

What should I adjust?

 

Thank you,

 

Mark

 

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

Re: Cue notes in color?

[Klaus Blum]

Salut Jérôme, 

Jérôme Plût-2 wrote
> I would like to have the cues displayed in a different color from the
> remainder of the score.

somewhere in
http://lilypond.org/doc/v2.18/Documentation/notation-big-page.de.html#formatting-cue-notes
there's a hint that if you start a voice context with \cueDuring, you have
to explicitely create it with \new Voice. 

So I ended up with the following: 

% ---
dux = {
  a4 a a a
}
comes = \new Voice {
  \cueDuring #"dux" #UP {R1}
  e4 e e e
}
\addQuote "dux" { \dux } 

\score {
  << \new Staff { \dux } \new Staff { \comes } >>
  \layout {
\context {
  \CueVoice
  \override NoteHead.color = #blue
}
  }
}
% ---

Cheers, 
Klaus



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Cue-notes-in-color-tp192619p192629.html
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

Re: Scheme conversion inexact->exact question

[tisimst]

On Tue, Jul 12, 2016 at 1:51 PM, David Kastrup [via Lilypond] <
ml-node+s1069038n192627...@n5.nabble.com> wrote:

> Abraham Lee <[hidden email]
> > writes:
>
> > Does anyone have a solution for the occasional HUGE integers that can be
> > created for the numerator/denominator when using inexact->exact?
> >
> > For example,
> >
> > (inexact->exact 0.2)
> >
> > yields
> >
> > 3602879701896400/18014398509482000
> >
> > It is correct, but LP doesn't seem to want to deal with such large
> > integers, at least for me.
>
> That should get fixed at some point of time: LilyPond's rational numbers
> precede Guile's but nowadays maintaining them is a nuisance.
>

Good to know.


> > Can this be reduced to 1/5 somehow? Is there a better way to get a
> > rational from a decimal? I can write a crazy function that
> > procedurally determines the minimum power of 10 that gives me a
> > rational with smaller numbers, but I'd rather not. Any advice is very
> > welcome.
>
> guile> (rationalize (inexact->exact 0.2) 1/1)
> 1/5
> guile> (help rationalize)
> `rationalize' is a primitive procedure in the (guile) module.
>
> -- Scheme Procedure: rationalize x eps
>  Returns the _simplest_ rational number differing from X by no more
>  than EPS.
>
>  As required by R5RS, 'rationalize' only returns an exact result
>  when both its arguments are exact.  Thus, you might need to use
>  'inexact->exact' on the arguments.
>
>   (rationalize (inexact->exact 1.2) 1/100)
>   => 6/5
>

Brilliant! I was trying to figure out how to make that function work,
thinking it would be what I needed, and those two examples were perfect in
helping me understand how to use it effectively. I'm back on the road
again! Thank you, David!

--
Abraham Lee




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Scheme-conversion-inexact-exact-question-tp192624p192628.html
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

Re: Scheme conversion inexact->exact question

[David Kastrup]

Abraham Lee  writes:

> Does anyone have a solution for the occasional HUGE integers that can be
> created for the numerator/denominator when using inexact->exact?
>
> For example,
>
> (inexact->exact 0.2)
>
> yields
>
> 3602879701896400/18014398509482000
>
> It is correct, but LP doesn't seem to want to deal with such large
> integers, at least for me.

That should get fixed at some point of time: LilyPond's rational numbers
precede Guile's but nowadays maintaining them is a nuisance.

> Can this be reduced to 1/5 somehow? Is there a better way to get a
> rational from a decimal? I can write a crazy function that
> procedurally determines the minimum power of 10 that gives me a
> rational with smaller numbers, but I'd rather not. Any advice is very
> welcome.

guile> (rationalize (inexact->exact 0.2) 1/1)
1/5
guile> (help rationalize)
`rationalize' is a primitive procedure in the (guile) module.

-- Scheme Procedure: rationalize x eps
 Returns the _simplest_ rational number differing from X by no more
 than EPS.

 As required by R5RS, 'rationalize' only returns an exact result
 when both its arguments are exact.  Thus, you might need to use
 'inexact->exact' on the arguments.

  (rationalize (inexact->exact 1.2) 1/100)
  => 6/5

-- 
David Kastrup

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

Re: lilypond - Tex

[Marc Hohl]

Am 12.07.2016 um 18:24 schrieb David Wright:

On Tue 12 Jul 2016 at 17:25:35 (+0200), Marc Hohl wrote:

IIUC, the original question was about to integrate LaTeX code within
LilyPond, not the other way round ;-)


? Of course it is when you snip the rest of the OP,


Ok, sorry.



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

Re: Spiridione, Nova Instructio pro pulsandis organis

[Ali Cuota]

Thanks, this helps much I think.
Francois

2016-07-12 12:52 GMT-05:00, Mark Stephen Mrotek :
> Francois,
>
> Here is a reference. The actual article is in California.
> http://www.worldcat.org/search?q=su%3ASpiridion%2C+1615-1685.+Nova+instructi
> o.=hot_subject
>
> Mark
>
> -Original Message-
> From: lilypond-user
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
> Ali
> Cuota
> Sent: Tuesday, July 12, 2016 10:24 AM
> To: lilypond-user 
> Subject: OT: Spiridione, Nova Instructio pro pulsandis organis
>
> Hello,
>
> I know this is quite OT actually, but who knows where there is an extended
> review of this work?
> Thanks in advance,
> Francois
>
> ___
> 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

Scheme conversion inexact->exact question

[Abraham Lee]

Does anyone have a solution for the occasional HUGE integers that can be
created for the numerator/denominator when using inexact->exact?

For example,

(inexact->exact 0.2)

yields

3602879701896400/18014398509482000

It is correct, but LP doesn't seem to want to deal with such large
integers, at least for me. Can this be reduced to 1/5 somehow? Is there a
better way to get a rational from a decimal? I can write a crazy function
that procedurally determines the minimum power of 10 that gives me a
rational with smaller numbers, but I'd rather not. Any advice is very
welcome.

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

Re: scrunching

[Urs Liska]

Am 12. Juli 2016 20:31:08 MESZ, schrieb "Br. Gabriel-Marie | SSPX" 
:
>If my music is taking up too much space, how can I scrunch 
>it horizontally?
>
>In other words, I want to get more notes and lyrics onto a 
>staff.
>
>I've set this all the way to 0, but am not yet getting the 
>effect I want.
>\override Lyrics.LyricSpace #'minimum-distance = #0.7
>

1. Find a lyrics font that is narrow. LilyPond's default text font takes a lot 
of horizontal space. 

2. Look here: 
https://github.com/openlilylib/snippets/tree/master/notation-snippets/adjust-horizontal-spacing

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

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

scrunching

[Br. Gabriel-Marie | SSPX]

If my music is taking up too much space, how can I scrunch 
it horizontally?


In other words, I want to get more notes and lyrics onto a 
staff.


I've set this all the way to 0, but am not yet getting the 
effect I want.

\override Lyrics.LyricSpace #'minimum-distance = #0.7
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Spiridione, Nova Instructio pro pulsandis organis

[Mark Stephen Mrotek]

Francois,

Here is a reference. The actual article is in California.
http://www.worldcat.org/search?q=su%3ASpiridion%2C+1615-1685.+Nova+instructi
o.=hot_subject

Mark

-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Ali
Cuota
Sent: Tuesday, July 12, 2016 10:24 AM
To: lilypond-user 
Subject: OT: Spiridione, Nova Instructio pro pulsandis organis

Hello,

I know this is quite OT actually, but who knows where there is an extended
review of this work?
Thanks in advance,
Francois

___
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

OT: Spiridione, Nova Instructio pro pulsandis organis

[Ali Cuota]

Hello,

I know this is quite OT actually, but who knows where there is an
extended review of this work?
Thanks in advance,
Francois

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

Cue notes in color?

[Jérôme Plût]

I would like to have the cues displayed in a different color from the
remainder of the score.

I tried the following (note my strong canon-writing skills) :

dux = {
  a4 a a a
}
comes = {
  \override NoteHead.color = #blue
  \cueDuring #"dux" #UP R1
  \revert NoteHead.color
  e4 e e e
}
\addQuote "dux" { \dux }

\score {
  << \new Staff { \dux } \new Staff { \comes } >>
  \layout { } }

However, all notes are still black.
I also tried some variants:
 - enclosing the whole block in a \new CueVoice: no effect;
 - with \override only: I get black A notes and blue E notes, which is
   quite the converse of what I want...
 - with CueVoice.NoteHead.color: both A and E are black, and now E are
   small.
 - without any \override and \revert: same as above;

How should I do this?

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

Re: Generating cropped PDFs

[David Wright]

On Tue 12 Jul 2016 at 14:29:41 (+0200), Mojca Miklavec wrote:
> On 12 July 2016 at 13:32, David Kastrup wrote:
> > Mojca Miklavec writes:
> >> I would occasionally like to create cropped PDFs (either entirely
> >> cropped or with some reasonable/configurable margin) without having to
> >> guess the size of the paper for each snippet.
> >>
> >> I found a page which seems to contain reasonable answers:
> >>
> >> 
> >>
> >> but:
> >>
> >> 1.) Even if both -dpreview and \include "lilypond-book-preamble.ly"
> >> from the first answer create cropped PDFs, the fonts are screwed up (I
> >> get some very weird ugly font). I'm not sure if this is a bug or not.
> >
> > 2.19.45 got a really bad font bug when creating multiple output files.
> > A fix is in the queue.  Revert back to 2.19.44 for now.
> 
> Thank you, that solved the problem.

That may solve the font problem but, having tried these two methods
out, I didn't find them particularly satisfactory.

-dpreview seemed to crop the output but with different amounts of
whitespace on each edge. I use a margin of one bp in pdfcrop (zero
makes previewing difficult because I don't like the print touching
the window's frame) and that's what I get.

lilypond-book-preamble.ly decomposes the page into fragments and then
puts them back together, but not correctly. For example, it'll rip the
opus off the music and then put it back together with more whitespace
in between.

The great advantage of pdfcrop as I see it is that, having got LP to
lay out the page exactly as you want it (which can be no mean feat),
it can't disturb it. And you don't have to inject anything into the
LP source or functionality. This last point is an argument against
my using the newer one-line/page settings, though you might have
success there.

Cheers,
David.

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

Re: lilypond - Tex

[David Wright]

On Tue 12 Jul 2016 at 17:25:35 (+0200), Marc Hohl wrote:
> IIUC, the original question was about to integrate LaTeX code within
> LilyPond, not the other way round ;-)

? Of course it is when you snip the rest of the OP, as you did in
http://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00326.html
The OP discussed the difficulties being had with integrating LP
nsiooets in LaTeX. There's mileage left in those methods.

> Am 12.07.2016 um 16:35 schrieb Henning Hraban Ramm:
> >Hi,
> >maybe have a look at my LilyPond/ConTeXt setup at 
> >http://wiki.contextgarden.net/LilyPond (Sample Include File).
> >
> >If you dont like lilypond-book, you might try LyLuaTeX 
> >(https://github.com/jperon/lyluatex).

Cheers,
David.

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

Re: lilypond - Tex

[Marc Hohl]

IIUC, the original question was about to integrate LaTeX code within 
LilyPond, not the other way round ;-)


Am 12.07.2016 um 16:35 schrieb Henning Hraban Ramm:

Hi,
maybe have a look at my LilyPond/ConTeXt setup at 
http://wiki.contextgarden.net/LilyPond (Sample Include File).

If you dont like lilypond-book, you might try LyLuaTeX 
(https://github.com/jperon/lyluatex).

Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)





___
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: lilypond - Tex

[Henning Hraban Ramm]

Hi,
maybe have a look at my LilyPond/ConTeXt setup at 
http://wiki.contextgarden.net/LilyPond (Sample Include File).

If you dont like lilypond-book, you might try LyLuaTeX 
(https://github.com/jperon/lyluatex).

Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)





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

Re: Exploring an idea for interactive display of annotations

[Urs Liska]

Hi Paul,

thanks for your pointers.


Am 10.07.2016 um 18:39 schrieb Paul:
> Hi Urs,
>
> On 07/08/2016 08:34 PM, Urs Liska wrote:
>>
>> I would like to do the following:
>>
>>   * Let ScholarLY add an 'id to the affected grob
>>   * Let ScholarLY export annotations to a JSON file (including the
>> same ID).
>>   * Let LilyPond compile to SVG (where the elements get the ID)
>>   * Display the SVG score in a web page
>>   * Use the ID to create popovers displaying the annotation
>>   * Use it also to display a list of annotations with links to the
>> score elements
>>
>> I think all this should be principally quite straightforward - and
>> provide us with the basics for stuff that can go pretty far into what
>> digital editions do today.
>>
>> I would implement the website part with Angular, as that's what I
>> have some experience with. But if someone chimes in and insists on
>> taking a different approach I wouldn't object.
>>
>
> Two quick thoughts:
>
> Sounds complementary to LilyPond HTML Live Score.  Might be some
> useful overlap to work with / leverage there?
>
> https://gitlab.com/sigmate/lilypond-html-live-score

Hm, I'll definitely have a closer look and get in touch with the author.
But I'm not sure if that's really compatible (for example as it exploits
the same property as I have in mind).

>
> As you probably know, I've heard that Angular 2 is quite different
> from Angular 1.x. (big break in backwards compatibility, difficult
> migration from 1 to 2, etc.)  So if you're using Angular, I think
> you'd want to use version 2. 
>
> React.js might be worth considering as well.  I'll be using it for my
> GSOC project.  What you describe seems relatively simple (as web apps
> go), so maybe the more minimal approach of React would make sense and
> do all you need? 

Good, maybe an incentive to give it a try (or at least look). The fact
that Angular is the only framework I know so far isn't really a good
argument ...

Best
Urs

>
> Just some thoughts, I'm no expert, and I don't expect I'll have time
> to contribute to this...
>
> Cheers,
> -Paul
>
>
> ___
> 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: Generating cropped PDFs

[Paul]

On 07/12/2016 07:07 AM, Mojca Miklavec wrote:

I would occasionally like to create cropped PDFs (either entirely
cropped or with some reasonable/configurable margin) without having to
guess the size of the paper for each snippet.


In 2.19.x there's now one-line-auto-height page breaking:

http://lilypond.org/doc/v2.19/Documentation/notation/page-breaking#one_002dline_002dauto_002dheight-page-breaking

Which would do what you want if your snippets fit on one line.

I also created a one-page-auto-height patch for multiple-line snippets 
(where you set the page width and the page height is automatically 
calculated, fitting everything on one page, perhaps a very tall page).  
It worked and made it through the usual code review and testing but then 
when it was committed to the staging branch it did not pass the tests 
there for some mysterious reason. (Maybe it was due to different 
versions of gcc?)  I haven't had time to work on it further (and I'm not 
really sure what to do next even if I did).


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

-Paul

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

Re: Generating cropped PDFs

[Mojca Miklavec]

On 12 July 2016 at 13:32, David Kastrup wrote:
> Mojca Miklavec writes:
>
>> Hello,
>>
>> I would occasionally like to create cropped PDFs (either entirely
>> cropped or with some reasonable/configurable margin) without having to
>> guess the size of the paper for each snippet.
>>
>> I found a page which seems to contain reasonable answers:
>>
>> 
>>
>> but:
>>
>> 1.) Even if both -dpreview and \include "lilypond-book-preamble.ly"
>> from the first answer create cropped PDFs, the fonts are screwed up (I
>> get some very weird ugly font). I'm not sure if this is a bug or not.
>
> 2.19.45 got a really bad font bug when creating multiple output files.
> A fix is in the queue.  Revert back to 2.19.44 for now.

Thank you, that solved the problem.

Mojca

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

Re: Position fingerings for diatonic accordion that include button name (not just finger)

[Mojca Miklavec]

On 11 July 2016 at 22:44, Carl Sorensen wrote:
> On 7/11/16 12:06 PM, "David Kastrup" wrote:
>
>>I think the fundamental question is how to provide the information.
>>
>>We have a similar choice to make with tablature: enter the musical
>>information, or enter the playing instructions.
>>
>>With tablature, the choice ended up being notes, occasionally helped
>>with string numbers.  Where this "occasionally helped" is not present,
>>you have the advantage of being able to _transpose_ and a new tablature
>>falls out.

Except that this doesn't work with diatonic accordions at all. Except
for some rare occasions it's impossible to get a tablature for a
differently tuned accordion (and differently tuned ones cannot play
together at all).

Here's it's actually the reverse. I would say that it would be
desirable to be able to get proper scores (so that for example a piano
can accompany the accordion player) for a differently tuned accordion
playing on the same buttons. And in this case entering the music with
"buttons" rather than pitches helps.

Anyway, if the user would decide to enter pitches, like , then
this could be played with either <"A4" "A5"> or <"C2" "C3">. Since
LilyPond doesn't have the capability to offer interactive help to the
writer, the lilypond could at best write "either A4 or C2" for  or
the user would have to manually enter the button label. And once the
button label is required, asking to do both becomes very error-prone.

I probably wouldn't mind a mode where I would type , then
LilyPond would provide me both alternatives and write the complete
score for me in "button notation" with alternatives (that would
probably help a lot in the beginning when one doesn't know which
button is which and if one gets the usual scores from somewhere), but
eventually one would have to enter the button names to create
unambiguous tablatures. The best I could do would be something like

or
   
to give a hint to LilyPond that the outermost row should be used for
that particular pitch and it would then use "A4" and "A5" instead of
"C2" and "C3".


Also: entering the usual pitches is already supported. Maybe the only
thing that's missing is the ability to effortlessly add nicely aligned
tablatures at some places only. But entering button names is not yet
supported and it would be great if there was a way to do it.

>>  You can change the string tuning, and a new tablature falls
>>out.  This would be the same with diatonic accordions: you could change
>>your instrument to one with a different tuning or transpose the melody,
>>and you'd get a new score.  And/or you could change your choice of when
>>to push or pull (assuming notes are available) and you'd get a new score
>>appropriately changed.

I'm a total beginner, but I'm afraid that you think too much from a
perspective of a player of a chromatic accordion :) :) :).

What you are proposing is impossible (or at least very hard) to do
most of the time. Or at least the one doing this must know very well
what he or she is doing. And even then: what prevents LilyPond from
checking whether the song is "transposable" to a differently tuned
accordion even if the input stays in "button names"?

(But yes, I agree, being able to spit the button name suggestions
automatically would be a nice feature in any case.)

> I know nothing about diatonic accordions, but given your comment on this
> it seems that the best approach would be to define an diatonic accordion
> engraver that could take a note together with an accordion description
> (the equivalent of a StringTuning) and automatically spit out the symbol.
> It could be consisted in a new context that is an alias for ChordNames,
> but with the chord-namer function changed to an accordion namer function.
> And if you need the push/pull information to help decide the button you
> could use \downbow and \upbow (at least in the beginning).

I looked at
http://lilypond.org/doc/v2.19/Documentation/notation/displaying-chords
and I like the syntax
\chordmode { c d e }
that automatically generates the whole chord and this seems nice. (I
don't like the fact that one cannot easily do things like {c
\chordmode {c} c d}, but that's ok.)

I made some short "summary" of my type of accordion at
https://github.com/mojca/frajtonarca/tree/master/uglasitve
https://github.com/mojca/frajtonarca/blob/master/uglasitve/basi-crop.pdf
and the same song that I already posted yesterday at

https://github.com/mojca/frajtonarca/blob/master/tablature/ljudske/na-planincah.pdf

(The question mark means that I'm not sure whether this is how the
chord is properly written / how it actually sounds. I was just
blind-guessing.)

It might be easiest to start with the basses than with the melody basses though.

If this feature gets properly supported, it would make sense to
provide some defaults, but it should be straightforward to provide a
definition for the tuning somewhere 

Re: Generating cropped PDFs

[Simon Albrecht]

On 12.07.2016 13:07, Mojca Miklavec wrote:

1.) Even if both -dpreview and \include "lilypond-book-preamble.ly"
from the first answer create cropped PDFs, the fonts are screwed up (I
get some very weird ugly font). I'm not sure if this is a bug or not.


That’s astounding. Please give a small example.

Best, Simon

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

Re: Generating cropped PDFs

[David Kastrup]

Mojca Miklavec  writes:

> Hello,
>
> I would occasionally like to create cropped PDFs (either entirely
> cropped or with some reasonable/configurable margin) without having to
> guess the size of the paper for each snippet.
>
> I found a page which seems to contain reasonable answers:
>
> 
>
> but:
>
> 1.) Even if both -dpreview and \include "lilypond-book-preamble.ly"
> from the first answer create cropped PDFs, the fonts are screwed up (I
> get some very weird ugly font). I'm not sure if this is a bug or not.

2.19.45 got a really bad font bug when creating multiple output files.
A fix is in the queue.  Revert back to 2.19.44 for now.  I think the fix
is not yet committed to the repository, so even using a current checkout
will not help here.

-- 
David Kastrup

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

Generating cropped PDFs

[Mojca Miklavec]

Hello,

I would occasionally like to create cropped PDFs (either entirely
cropped or with some reasonable/configurable margin) without having to
guess the size of the paper for each snippet.

I found a page which seems to contain reasonable answers:



but:

1.) Even if both -dpreview and \include "lilypond-book-preamble.ly"
from the first answer create cropped PDFs, the fonts are screwed up (I
get some very weird ugly font). I'm not sure if this is a bug or not.

2.) The "convert" command from ImageMagick rasterizes the PDF.

3.) I don't want PNGs.

Using "pdfcrop" from TeX Live does the trick, but I wonder if there is
any obvious way to do it from within lilypond that I overlooked (then
I could also configure the margin).

Thank you,
Mojca

(Please CC me.)

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

Re: Gould question

[David Kastrup]

Simon Albrecht  writes:

> On 11.07.2016 22:33, Carl Sorensen wrote:
>> On 7/11/16 7:54 AM, "Simon Albrecht"  wrote:
>>> Hello,
>>>
>>> what do the authorities say on beaming something like this:
>>>
>>> %%
>>> \version "2.19.45"
>>> {
>>>\time 2/2
>>>\repeat unfold 4 { \tuplet 6/4 { c16 e g c' g e } }
>>> }
>>> %%
>>>
>>> Currently, it¹s beamed by half-measure, which I think impairs
>>> legibility, so I introduced a patch changing this to beaming by quarter
>>> note value (issue 4919).
>> The authorities say to beam by the beat, which is the half measure.  I
>> think that's why the default is what it is.
>
> However, somewhere one has to draw the line – it’s certainly not an
> option to have 16 32nd notes beamed together (unless subdivided).

In 2/2 splitting up the beams sub-beat is just wrong.  Now we have the
"unless subdivided" moniker here and LilyPond should likely do more in
_that_ respect.  In particular when beaming over several tuplet groups,
a subdivision corresponding to the number-carrying groups seems pretty
much mandatory to me irrespective of whether one uses binary subdivision
schemes (which I often find overdoing it) elsewhere.

> And I’d draw it just below 16th notes.

For subdivision, yes.  But splitting beams completely inside of a beat
does not make sense automatically since we are then talking about a
judicious breach of rules, and that really should be done manually.

-- 
David Kastrup

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

Re: Gould question

[Urs Liska]

Am 12.07.2016 um 09:27 schrieb Simon Albrecht:
> On 11.07.2016 22:33, Carl Sorensen wrote:
>> On 7/11/16 7:54 AM, "Simon Albrecht"  wrote:
>>> Hello,
>>>
>>> what do the authorities say on beaming something like this:
>>>
>>> %%
>>> \version "2.19.45"
>>> {
>>>\time 2/2
>>>\repeat unfold 4 { \tuplet 6/4 { c16 e g c' g e } }
>>> }
>>> %%
>>>
>>> Currently, it¹s beamed by half-measure, which I think impairs
>>> legibility, so I introduced a patch changing this to beaming by quarter
>>> note value (issue 4919).
>> The authorities say to beam by the beat, which is the half measure.  I
>> think that's why the default is what it is.
>
> However, somewhere one has to draw the line – it’s certainly not an
> option to have 16 32nd notes beamed together (unless subdivided). And
> I’d draw it just below 16th notes.

Gould writes (p. 153): "Divisions of a beat are beamed together in all
metres, in order to simplify reading beats". In the following examples
she beams half notes in 2/2 and 3/2 - but the examples only use quavers
and nothing shorter. So I *think* she would actually suggest not to beam
semiquavers or even shorter notes over more than a crotchet or at least
consider that a valid approach.

Actually using beam subdivision is somewhat problematic (although
conceivable). With beam subdivision the number of beams should
correspond to the metric value of the position - and at the crotchet
this is *zero* beams.

Urs


>
> Best, Simon
>
> ___
> 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: lilypond - Tex

[Marc Hohl]

Am 11.07.2016 um 21:26 schrieb bart deruyter:

Hi all,
[...]

I don't think it is possible now, but maybe it would be interesting to
work the other way round: inserting latex code in a lilypond file. Or
would it be possible? :-)


Is

https://github.com/openlilylib/snippets/tree/master/specific-solutions/xelatex-markup-list

what you're searching for?

HTH,

Marc


grtz,
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 


___
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: state-of-the-art for algorithmic hooks and Lilypond+(La)TeX

[Urs Liska]

Am 12.07.2016 um 09:39 schrieb Orm Finnendahl:
> Am Dienstag, den 12. Juli 2016 um 09:26:38 Uhr (+0200) schrieb Urs Liska:
>> You know that in Karlsruhe every student of music informatics and
>> musicology has to take a class in common lisp (in their 3rd
>> semester)?
> In Essen its part of the curriculum as well, but I'm not aware of many
> younger composers actually using it in earnest.
>

Sure.
Having it in the curriculum (especially with only one class) doesn't
mean much. I'm currently teaching a group of students "Scheme in
LilyPond", and my worries about selling coals to Newcastle have proved
unfounded ;-)

However, that doesn't mean making code fragments available is completely
in vain.
There *are* people who know that Lisp can be used for making music,
there is OpenMusic, and it *can* be possible to raise interest by
increasing the amount of stuff that is around.
Some of my most interesting projects have been made possible because I
had some code online and someone chimed in by either using and
questioning it or actually developing it further.

Urs

> --
> Orm


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

Re: state-of-the-art for algorithmic hooks and Lilypond+(La)TeX

[Orm Finnendahl]

Am Dienstag, den 12. Juli 2016 um 09:26:38 Uhr (+0200) schrieb Urs Liska:
> 
> You know that in Karlsruhe every student of music informatics and
> musicology has to take a class in common lisp (in their 3rd
> semester)?

In Essen its part of the curriculum as well, but I'm not aware of many
younger composers actually using it in earnest.

--
Orm

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

Re: Gould question

[Simon Albrecht]

On 11.07.2016 22:33, Carl Sorensen wrote:

On 7/11/16 7:54 AM, "Simon Albrecht"  wrote:

Hello,

what do the authorities say on beaming something like this:

%%
\version "2.19.45"
{
   \time 2/2
   \repeat unfold 4 { \tuplet 6/4 { c16 e g c' g e } }
}
%%

Currently, it¹s beamed by half-measure, which I think impairs
legibility, so I introduced a patch changing this to beaming by quarter
note value (issue 4919).

The authorities say to beam by the beat, which is the half measure.  I
think that's why the default is what it is.


However, somewhere one has to draw the line – it’s certainly not an 
option to have 16 32nd notes beamed together (unless subdivided). And 
I’d draw it just below 16th notes.


Best, Simon

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

Re: state-of-the-art for algorithmic hooks and Lilypond+(La)TeX

[Urs Liska]

Am 12. Juli 2016 09:20:32 MESZ, schrieb Orm Finnendahl 
:
>Hi Kieren,
>
>Am Montag, den 11. Juli 2016 um 13:55:48 Uhr (-0400) schrieb Kieren
>MacMillan:
>> 
>> 1. On the topic of algorithmic stuff, I sent him the link to
>> Abjad. If there’s a better starting place, or other links I should
>> forward to him, please let me know!
>
>Dated and by no means par to Trevor's approach, but probably worth
>mentioning (as of its lisp heritage):
>
>http://fomus.sourceforge.net/
>
>and
>
>https://common-lisp.net/project/fomus/
>
>He can also contact me. There is a lot of stuff written in common lisp
>for my own work on my hard drives. As it is very specific for my needs
>and in a language hardly anybody uses, I never bothered to make it
>available.

You know that in Karlsruhe every student of music informatics and musicology 
has to take a class in common lisp (in their 3rd semester)?

>
>--
>Orm
>--
>Prof. Orm Finnendahl
>Komposition
>Hochschule für Musik und Darstellende Kunst
>Eschersheimer Landstr. 29-39
>60322 Frankfurt am Main
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: state-of-the-art for algorithmic hooks and Lilypond+(La)TeX

[Orm Finnendahl]

Hi Kieren,

Am Montag, den 11. Juli 2016 um 13:55:48 Uhr (-0400) schrieb Kieren
MacMillan:
> 
> 1. On the topic of algorithmic stuff, I sent him the link to
> Abjad. If there’s a better starting place, or other links I should
> forward to him, please let me know!

Dated and by no means par to Trevor's approach, but probably worth
mentioning (as of its lisp heritage):

http://fomus.sourceforge.net/

and

https://common-lisp.net/project/fomus/

He can also contact me. There is a lot of stuff written in common lisp
for my own work on my hard drives. As it is very specific for my needs
and in a language hardly anybody uses, I never bothered to make it
available.

--
Orm
--
Prof. Orm Finnendahl
Komposition
Hochschule für Musik und Darstellende Kunst
Eschersheimer Landstr. 29-39
60322 Frankfurt am Main

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