Prall and trill in "articulate" script

[Gilles]

Hello.

It's the first time I use the "\articulate" command.
Very nice improvement on the plain MIDI rendering!

Two remarks:
1. "prall" is interpreted in a way that (IMO) better corresponds
   to "prallprall" (which itself is not implemented).
   [A comment in the code indicates that the "inverted mordent"
   option was not retained.]
2. A "trill" on a tied note only lasts as long as the first written
   note.  The problem is alleviated by using a trill span, but then
   the trill is stopped at the start of the last written note's
   duration.


Thanks,
Gilles



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

ScholarLy newbie, running annotate.ly, gets error message

[Graham King]

excuse the haiku!

In my first attempt at using ScholarLy, I'm trying to compile the
supplied example, openlilylib/ly/scholarly/usage-examples/annotate.ly

The include path for Frescobaldi 2.18.1 is:

/Users/grahamk/Documents/lilypond/include_gk
/Users/grahamk/Documents/lilypond/music/openlilylib
/Users/grahamk/Documents/lilypond/music/openlilylib/ly
/Users/grahamk/lilypond/include

At compile time, the lilypond log starts:


Starting lilypond 2.19.21 [annotate.ly]...

Processing

`/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/usage-examples/annotate.ly'

Parsing...

openLilyLib: library infrastructure successfully loaded.


/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/usage-examples/annotate.ly:5:1:
 warning: openLilyLib: Library main file 
"/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/__main__.ily" 
not found

\useLibrary ScholarLY


/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/annotate/__main__.ily:50:1:
 warning: openLilyLib: Library main file 
"/Users/grahamk/Documents/lilypond/music/openlilylib/ly/utility/__main__.ily" 
not found

However, both files are there:

$ ls
-l 
/Users/grahamk/Documents/lilypond/music/openlilylib/ly/{scholarly,utility}/__main__.ily
-rw-r--r--  1 grahamk  staff  2140 17 Oct
22:36 
/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/__main__.ily
-rw-r--r--  1 grahamk  staff37 17 Oct
22:36 
/Users/grahamk/Documents/lilypond/music/openlilylib/ly/utility/__main__.ily

Can anyone identify the no-doubt humiliatingly-obvious error that I've
committed?

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

Re: ScholarLy newbie, running annotate.ly, gets error message

[David Kastrup]

Urs Liska  writes:

> Am 19.10.2015 um 16:36 schrieb Urs Liska:
>> You didn't do anything wrong but stumbled over a stupid bug I didn't
>> have the time to look into. It seems that at some point I have
>> reversed the logic of an 'if' statement so it spits out that error
>> when everything is OK.
>>
>> So if the results are what you expect please ignore *this* kind of
>> error message.
>>
>> Urs
>
> Ok, for all those who have read that excuse from me lately: This was
> just one time too much. I *did* look into it and fixed it by moving one
> closing paren by one line. Oh I love that language ...

Emacs' scheme-mode does a reasonably good job at making stuff clear with
indentation (there is even a mode in ELPA that will cycle through
different indentations when typing TAB just like python-mode does, but
also maintaining the matching paren count while doing so).

I would not want to edit Scheme code with an editor different from
Emacs.  That's its home turf, and it shows.

-- 
David Kastrup

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

Re: ScholarLy newbie, running annotate.ly, gets error message

[Urs Liska]

Am 19.10.2015 um 16:53 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Am 19.10.2015 um 16:36 schrieb Urs Liska:
>>> You didn't do anything wrong but stumbled over a stupid bug I didn't
>>> have the time to look into. It seems that at some point I have
>>> reversed the logic of an 'if' statement so it spits out that error
>>> when everything is OK.
>>>
>>> So if the results are what you expect please ignore *this* kind of
>>> error message.
>>>
>>> Urs
>> Ok, for all those who have read that excuse from me lately: This was
>> just one time too much. I *did* look into it and fixed it by moving one
>> closing paren by one line. Oh I love that language ...
> Emacs' scheme-mode does a reasonably good job at making stuff clear with
> indentation (there is even a mode in ELPA that will cycle through
> different indentations when typing TAB just like python-mode does, but
> also maintaining the matching paren count while doing so).
>
> I would not want to edit Scheme code with an editor different from
> Emacs.  That's its home turf, and it shows.

Although different from the standard (as was discussed recently)
Frescobaldi works quite well too here. But it still doesn't prevent
making stupid errors, especially when manipulating things afterwards. In
this case I had to enclose the "error" branch of an if expression in a
(begin), and I managed to close that begin too late, thus including the
"success" branch in the begin. That way the error message printed
regardless of the result of the file-exists? test. Well, pretty original
use of an error message, isn't it? ;-/

>


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

Re: any slur after-line-breaking [automated] hacks?

[Simon Albrecht]

On 19.10.2015 04:47, Kieren MacMillan wrote:

a great number of trial-and-error adjustment+compilation cycles


Well, \shapeII by Janek in openlilylib does offer the facility of giving 
a list of lists for each of the siblings of a broken bezier (that’s not 
documented, IIRC), like:

\shapeII #'(((h) (p 20 0.5)) (()()()(0 . -.5)))
I’ve noticed there are bugs with this function, though. But I couldn’t 
debug myself (for lack of time and ability), and Janek didn’t reply to 
an email :-(.


HTH, Simon

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

Re: ScholarLy newbie, running annotate.ly, gets error message

[Urs Liska]

You didn't do anything wrong but stumbled over a stupid bug I didn't
have the time to look into. It seems that at some point I have reversed
the logic of an 'if' statement so it spits out that error when
everything is OK.

So if the results are what you expect please ignore *this* kind of error
message.

Urs

Am 19.10.2015 um 16:33 schrieb Graham King:
> excuse the haiku!
>
> In my first attempt at using ScholarLy, I'm trying to compile the
> supplied example, openlilylib/ly/scholarly/usage-examples/annotate.ly
>
> The include path for Frescobaldi 2.18.1 is:
>
> /Users/grahamk/Documents/lilypond/include_gk
> /Users/grahamk/Documents/lilypond/music/openlilylib
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly
> /Users/grahamk/lilypond/include
>
> At compile time, the lilypond log starts:
>
> Starting lilypond 2.19.21 [annotate.ly ]...
>
> Processing
> 
> `/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/usage-examples/annotate.ly
> '
>
> Parsing...
>
> openLilyLib: library infrastructure successfully loaded.
>
> 
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/usage-examples/annotate.ly:5:1
> <0>: warning: openLilyLib: Library main file
> 
> "/Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/__main__.ily"
> not found
>
> \useLibrary ScholarLY
>
> 
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/annotate/__main__.ily:50:1
> <1>: warning: openLilyLib: Library main file
> 
> "/Users/grahamk/Documents/lilypond/music/openlilylib/ly/utility/__main__.ily"
> not found
>
> However, both files are there:
>
> $ ls -l
> 
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly/{scholarly,utility}/__main__.ily
> -rw-r--r--  1 grahamk  staff  2140 17 Oct 22:36
> 
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly/scholarly/__main__.ily
> -rw-r--r--  1 grahamk  staff37 17 Oct 22:36
> 
> /Users/grahamk/Documents/lilypond/music/openlilylib/ly/utility/__main__.ily
>
> Can anyone identify the no-doubt humiliatingly-obvious error that I've
> committed?
>
> TIA,
> -- Graham
>
>
> ___
> 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: \applyContext, StaffSymbol, and \stopStaff \startStaff

[Paul Morris]

> On Oct 19, 2015, at 1:56 AM, David Kastrup  wrote:
> 
> I think your main problem is that you are using \applyContext here at
> Voice level where it does not really do anything worthwhile.

Ah, I see.

> Try \context Staff \applyContext …

That did the trick and now it works, thanks!

\version “2.19.22” 

myfunc =
#(define-music-function () ()
   #{
 \context Staff
 \applyContext
 #(lambda (context)
;; access context properties and pick a property setting based on 
them...
(ly:context-pushpop-property context 'StaffSymbol 'color green))
 \stopStaff
 \startStaff
   #})

{
  c'
  % now it works!
  \context Staff
  \applyContext
  #(lambda (context)
 ;; access context properties and pick a property setting based on them...
 (ly:context-pushpop-property context 'StaffSymbol 'color red))  
  \stopStaff \startStaff
  c'
  % and you can put it in a music function
  \myfunc
  c'
}


> Though frankly I have no idea what \myFunc is trying to do.  You are
> keeping state in a global variable which is not going to work when using
> \myFunc in several contexts in parallel.

Um, never mind that, it was just my clumsy attempt to try to use \override 
Staff.StaffSymbol... to set the grob property when I couldn’t get 
ly:context-pushpop-property to work.  

Thanks again, I really appreciate your help.  No telling how long or if I would 
have ever figured that out on my own.

-Paul


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

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

[Paul Morris]

> On Oct 19, 2015, at 10:59 AM, David Kastrup  wrote:
> 
> Paul Morris  writes:
>> 
>> That did the trick and now it works, thanks!
>> 
>> \version “2.19.22” 
>> 
>> myfunc =
>> #(define-music-function () ()
>>   #{
>> \context Staff
>> \applyContext
>> #(lambda (context)
>>;; access context properties and pick a property setting based on 
>> them...
>>(ly:context-pushpop-property context 'StaffSymbol 'color green))
>> \stopStaff
>> \startStaff
>>   #})
> 
> Frankly, anything wrong with
> 
>\temporary \override Staff.StaffSymbol.color = #green
> 
> here?

That would work except I want to be able to access Staff context properties and 
then, based on their values, decide what to set the StaffSymbol property to.  
In this example, say color it either green or blue.  I just left these details 
out of my tiny example (as I tried to indicate with the comment "access context 
properties and pick a property setting based on them…”, which may not have been 
very clear).

> Assuming you want a temporary override (which is what
> ly:context-pushpop-property does) in order to be able to revert to the
> previous setting afterwards.

I actually don’t think I’ll need to be able to revert.  I was just using 
ly:context-pushpop-property because it was shown in the examples in the 
extending manual.

Thanks again,
-Paul



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

Re: ScholarLy newbie, running annotate.ly, gets error message

[Urs Liska]

Am 19.10.2015 um 16:36 schrieb Urs Liska:
> You didn't do anything wrong but stumbled over a stupid bug I didn't
> have the time to look into. It seems that at some point I have
> reversed the logic of an 'if' statement so it spits out that error
> when everything is OK.
>
> So if the results are what you expect please ignore *this* kind of
> error message.
>
> Urs

Ok, for all those who have read that excuse from me lately: This was
just one time too much. I *did* look into it and fixed it by moving one
closing paren by one line. Oh I love that language ...

So please pull the latest changes from openLilyLib and *this* bug should
be gone.

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

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

[David Kastrup]

Paul Morris  writes:

>> On Oct 19, 2015, at 1:56 AM, David Kastrup  wrote:
>> 
>> I think your main problem is that you are using \applyContext here at
>> Voice level where it does not really do anything worthwhile.
>
> Ah, I see.
>
>> Try \context Staff \applyContext …
>
> That did the trick and now it works, thanks!
>
> \version “2.19.22” 
>
> myfunc =
> #(define-music-function () ()
>#{
>  \context Staff
>  \applyContext
>  #(lambda (context)
> ;; access context properties and pick a property setting based on 
> them...
> (ly:context-pushpop-property context 'StaffSymbol 'color green))
>  \stopStaff
>  \startStaff
>#})

Frankly, anything wrong with

\temporary \override Staff.StaffSymbol.color = #green

here?

Assuming you want a temporary override (which is what
ly:context-pushpop-property does) in order to be able to revert to the
previous setting afterwards.

-- 
David Kastrup

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

Re: ScholarLy newbie, running annotate.ly, gets error message

[Graham King]

On Mon, 2015-10-19 at 16:48 +0200, Urs Liska wrote:

> 
> 
> 
> Am 19.10.2015 um 16:36 schrieb Urs Liska:
> 
> > 
> > You didn't do anything wrong but stumbled over a stupid bug I didn't
> > have the time to look into. It seems that at some point I have
> > reversed the logic of an 'if' statement so it spits out that error
> > when everything is OK.
> > 
> > So if the results are what you expect please ignore *this* kind of
> > error message.
> > 
> > Urs
> 
> 
> Ok, for all those who have read that excuse from me lately: This was
> just one time too much. I *did* look into it and fixed it by moving
> one closing paren by one line. Oh I love that language ...
> 
> So please pull the latest changes from openLilyLib and *this* bug
> should be gone.


Done.  Fixed.  Many thanks Urs.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

[David Kastrup]

Paul Morris  writes:

>> On Oct 19, 2015, at 10:59 AM, David Kastrup  wrote:
>> 
>> Paul Morris  writes:
>>> 
>>> That did the trick and now it works, thanks!
>>> 
>>> \version “2.19.22” 
>>> 
>>> myfunc =
>>> #(define-music-function () ()
>>>   #{
>>> \context Staff
>>> \applyContext
>>> #(lambda (context)
>>>;; access context properties and pick a property setting based on 
>>> them...
>>>(ly:context-pushpop-property context 'StaffSymbol 'color green))
>>> \stopStaff
>>> \startStaff
>>>   #})
>> 
>> Frankly, anything wrong with
>> 
>>\temporary \override Staff.StaffSymbol.color = #green
>> 
>> here?
>
> That would work except I want to be able to access Staff context
> properties and then, based on their values, decide what to set the
> StaffSymbol property to.  In this example, say color it either green
> or blue.  I just left these details out of my tiny example (as I tried
> to indicate with the comment "access context properties and pick a
> property setting based on them…”, which may not have been very clear).

Ok, that makes sense.  One can override grob properties with a callback
but they will be called (with the grob as argument) at the time the
property is actually needed, and at that time the only context
properties from the time of call will be the grob property defaults
stored in the grob, in this case the StaffSymbol settings.  And it does
not sound like that would help you.

So \applyContext indeed seems like the right call here.

-- 
David Kastrup

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

Re: [OT] Printer with or without Postscript

[David Wright]

Quoting Johan Vromans (jvrom...@squirrel.nl):
> On Tue, 13 Oct 2015 21:17:19 +1100
> Andrew Bernard  wrote:
> 
> > I am not convinced evince is very good at anything at all. Would this not
> > be an issue with evince, rather than other parts of the toolchain?
> 
> That could very well be the case. I was just referring to a common workflow
> of 1. create a PDF document, 2. view it for visual inspection, and then
> 3. print it from the viewer.

A very common workflow but IMO a very poor one. If you have problems
printing, where do you start looking for the cause? (for example,
artifacts like those in the right side of your lpev.png).

I only ever print from applications to a file. Then I print the file.

Were I to have a problem, I can now choose assorted appropriate tools
to look at whether the file is correct. I can use those same tools on
files I printed years ago and see if an application's behaviour has
changed (eg evince switched from printing through PS to printing
through PDF around 2009 AIUI).

If the file is correct, I can now examine the printing chain and put
assorted appropriate testfiles through that.

Furthermore, if you print from applications, you have no record of the
options you might have used to get the final output, so you might not
be able to reproduce it if need be.

Having eventually downloaded that PNG (squirrel.nl disappeared from
google's nameservers for a while) I wondered whether the images are
rescans of printouts through glass, or generated through computation.

Cheers,
David.

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

Re: Emacs lilypond-mode

[Laura Conrad]

> "David" == David Kastrup  writes:

David> What it does do is trying to track the current "tonality".
David> That's an interesting idea but requires an editing mode that
David> will _propagate_ corrections in order to work nicely.  Of
David> course, the same will be needed in order to have automatic
David> note length recognition cooperate nicely with manual
David> corrections, fixing later durations based on corrections on
David> earlier ones.

I'm not that interested in note length.  I'm not a good enough keyboard
player to be able to enter notes with very accurate lengths.  I use the
left hand to play the  MIDI keyboard and the right hand on the keypad to
do the lengths.  I'm pretty fast this way, and pretty accurate, except
for the silly accidentals midi-input-mode makes up.   The problem is
when entering long note values, which are common in early 16th century
music, I have to leave the keypad to type \breve and \longa.

>>> It works but has the major disadvantage that it doesn't play the MIDI
>>> notes as well as reading them.
>> 
>> The current version of lily-midi.el which I still need to fold into
>> the LilyPond repository does not do so either.

David> You probably mean not as much playing while entering (your
David> MIDI keyboard should do that) as you mean playing while
David> editing.

No, I mean playing while entering.  My USB MIDI keyboard doesn't have
any sounds -- it needs the computer to do the playing.  If I work hard
with Linux audio, I can get Jack and a synthesizer to play sounds when I
play, but midi-input-mode won't talk to Jack.

David> midi-kbd.el retains the full timing information.  So it is
David> prepared for more complex editing modes that make use of
David> them, the simplest of course being just replay of the current
David> region exactly as entered (what to do with manual
David> insertions/corrections?  No idea).  Again, this is not yet
David> done.  And I'm not quite sure how to best do it: one would
David> likely need to open a (raw?) MIDI output device for it as
David> well.

I'm not sure how useful emacs deciding what you want to hear would
be. Something like midi-play-region would be nice.


-- 
Laura   (mailto:lcon...@laymusic.org)

(617) 661-8097  233 Broadway, Cambridge, MA 02139   
 

Mr. Barenboim recalled observing Mr. Boulez lead Schoenberg's "Pelleas
und Melisande" with the BBC Symphony in the early 1960s.

"I sat with the score during the rehearsal," he said. "At the
beginning there is quite a lot of chromaticism, and at a certain point
there was a chord out of tune and Pierre said, 'No, no, this is sharp,
this is flat.' I was amazed.

"As a pianist I had no idea how he heard all that. I mean, when I
thought my piano was out of tune, I just called the tuner. So I asked
Pierre how he did it. I was starting to conduct, and I wanted to know
if this was something I could learn.

"Pierre said: 'You have to have the courage to say what you hear and
think when you conduct. Either the player will correct you and say
it's not me out of tune, it's the second oboe, or you will be
right. But in any case you will learn. Don't put your ego above the
music. Do what you have to do for the sake of the music, and only in
that way will you make progress.' "

Quoted by Michael Kimmelman in the New York Times, January 10, 2010

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

Re: [OT] Printer with or without Postscript

[Johan Vromans]

On Mon, 19 Oct 2015 10:59:42 -0500
David Wright  wrote:

> A very common workflow but IMO a very poor one. If you have problems
> printing, where do you start looking for the cause? (for example,
> artifacts like those in the right side of your lpev.png).
> 
> I only ever print from applications to a file. Then I print the file.

How do you print? cat > /dev/printer? lpr? A viewer? Except for the first,
they all involve 'hidden' software between the physical PostScript file and
the physical printout.

> Having eventually downloaded that PNG (squirrel.nl disappeared from
> google's nameservers for a while) I wondered whether the images are
> rescans of printouts through glass, or generated through computation.

Two rescans at high density, glued together in GIMP.

-- Johan

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

Re: Emacs lilypond-mode

[Simon Albrecht]

On 19.10.2015 18:01, Laura Conrad wrote:

The problem is
when entering long note values, which are common in early 16th century
music, I have to leave the keypad to type \breve and \longa


Except you’d enter it with shortened note values (say to 1/4) and use 
e.g. the Frescobaldi Rhythm Tools to convert them afterwards.


Yours, Simon


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

Re: Emacs lilypond-mode

[Laura Conrad]

> "Simon" == Simon Albrecht  writes:

Simon> On 19.10.2015 18:01, Laura Conrad wrote:
>> The problem is
>> when entering long note values, which are common in early 16th century
>> music, I have to leave the keypad to type \breve and \longa

Simon> Except you’d enter it with shortened note values (say to 1/4)
Simon> and use e.g. the Frescobaldi Rhythm Tools to convert them
Simon> afterwards.

If I'm reading from a modern edition that has everything shortened,
yes.  

If I'm reading from facsimile or a modern edition with original note
values, I prefer to enter what's in front of me.


-- 
Laura   (mailto:lcon...@laymusic.org)

(617) 661-8097  233 Broadway, Cambridge, MA 02139   
 

Solitary Observation Brought Back From A Sojourn In Hell

At midnight tears
Run into your ears.

Louise Bogan


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

Re: Emacs lilypond-mode

[David Kastrup]

Laura Conrad  writes:

>> "Simon" == Simon Albrecht  writes:
>
> Simon> On 19.10.2015 18:01, Laura Conrad wrote:
> >> The problem is
> >> when entering long note values, which are common in early 16th century
> >> music, I have to leave the keypad to type \breve and \longa
>
> Simon> Except you’d enter it with shortened note values (say to 1/4)
> Simon> and use e.g. the Frescobaldi Rhythm Tools to convert them
> Simon> afterwards.
>
> If I'm reading from a modern edition that has everything shortened,
> yes.  
>
> If I'm reading from facsimile or a modern edition with original note
> values, I prefer to enter what's in front of me.

Well, enter 7 and 9 and do a global search and replace on the region
when you are finished.  Or teach Emacs to do that S right when
entering.

-- 
David Kastrup

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

Re: [OT] Printer with or without Postscript

[David Wright]

Quoting Johan Vromans (jvrom...@squirrel.nl):
> On Mon, 19 Oct 2015 10:59:42 -0500
> David Wright  wrote:
> 
> > A very common workflow but IMO a very poor one. If you have problems
> > printing, where do you start looking for the cause? (for example,
> > artifacts like those in the right side of your lpev.png).
> > 
> > I only ever print from applications to a file. Then I print the file.
> 
> How do you print? cat > /dev/printer? lpr? A viewer? Except for the first,
> they all involve 'hidden' software between the physical PostScript file and
> the physical printout.

Sticking to the order here (rather than the order at Tue, 13 Oct 2015
12:09:27 +0200), method 2; ie through GS and HP's hpcups filter to
convert the PDF to pcl3. I'm not sure what you mean by hidden.
Method 1 is expensive and, as you pointed out, still involves GS to go
from PDF to PS. Method 3 is what I am avoiding, in the sense of being
*in* the printing chain. Obviously I view PDFs in viewer, usually xpdf.

> > Having eventually downloaded that PNG

> Two rescans at high density, glued together in GIMP.

Does the PDF file you're viewing in evince look ok when you magnify it
on the screen? If so, what does method 2 produce when you print that
file? This should help isolate your problem.

Cheers,
David.

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

Serpent Publications

[Simon Albrecht]

Hello Laura,

I just had a look at your  collection. 
Very nice project you have there! I like the concept of using parts and 
retaining the original ‘measure notation’. (Personally, I also think we 
might gain a lot by just turning to use the traditional c clefs again – 
it really helps polyphonic thinking in my eyes, and perhaps it wouldn’t 
pose much of a difficulty if one were used to them.)

Two small hints:
– You should really use proper lyric hyphens and extenders, like:
\lyricmode { ly -- ric __ }.
– Unfortunately, LilyPond’s default text font is quite wide, so perhaps 
you might want to look for a narrower one. Personally, I very much like 
the Alegreya font (which has a Sans version as well) from 
.


But thanks for your work on this!
Yours, Simon

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

Re: Emacs lilypond-mode

[David Kastrup]

Laura Conrad  writes:

>> "David" == David Kastrup  writes:
>
> David> What it does do is trying to track the current "tonality".
> David> That's an interesting idea but requires an editing mode that
> David> will _propagate_ corrections in order to work nicely.  Of
> David> course, the same will be needed in order to have automatic
> David> note length recognition cooperate nicely with manual
> David> corrections, fixing later durations based on corrections on
> David> earlier ones.
>
> I'm not that interested in note length.  I'm not a good enough keyboard
> player to be able to enter notes with very accurate lengths.  I use the
> left hand to play the  MIDI keyboard and the right hand on the keypad to
> do the lengths.  I'm pretty fast this way, and pretty accurate, except
> for the silly accidentals midi-input-mode makes up.   The problem is
> when entering long note values, which are common in early 16th century
> music, I have to leave the keypad to type \breve and \longa.
>
> >>> It works but has the major disadvantage that it doesn't play the MIDI
> >>> notes as well as reading them.
> >> 
> >> The current version of lily-midi.el which I still need to fold into
> >> the LilyPond repository does not do so either.
>
> David> You probably mean not as much playing while entering (your
> David> MIDI keyboard should do that) as you mean playing while
> David> editing.
>
> No, I mean playing while entering.  My USB MIDI keyboard doesn't have
> any sounds -- it needs the computer to do the playing.  If I work hard
> with Linux audio, I can get Jack and a synthesizer to play sounds when I
> play, but midi-input-mode won't talk to Jack.

Uh, use aconnect -l ?

And then use aconnect to connect your USB MIDI port to some Timidity
port?  Emacs does not have to do anything here.  You can connect one
Midi input to more than one output.

If you have time lag problems, ask back.  I think Ubuntu's default
Timidity settings are somewhat less than real-time friendly.  Probably
nothing fazing an organ player, but for an accordionist something like a
half-second delay can be quite the nuisance.

> David> midi-kbd.el retains the full timing information.  So it is
> David> prepared for more complex editing modes that make use of
> David> them, the simplest of course being just replay of the current
> David> region exactly as entered (what to do with manual
> David> insertions/corrections?  No idea).  Again, this is not yet
> David> done.  And I'm not quite sure how to best do it: one would
> David> likely need to open a (raw?) MIDI output device for it as
> David> well.
>
> I'm not sure how useful emacs deciding what you want to hear would
> be. Something like midi-play-region would be nice.

Without running it through LilyPond first I assume.

-- 
David Kastrup

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