Am 20.04.2015 um 08:45 schrieb Andrew Bernard:
So Ponders,
What size paper do you print scores on?
A4 exclusively, sometimes folded A3 (but only when letting print through
external service providers).
But I always suffer from that being somewhat too small for really usable
scores. If I ha
Hi Andrew,
I use A4 for most "small" or "normal" scores (SATB choir). Sometimes A5
But full scores for the director with an orchestral score I use B4 -
sometimes A3.
Cheers,
Jan-Peter
Am 20.04.2015 um 08:45 schrieb Andrew Bernard:
So Ponders,
What size paper do you print scores on?
Andrew
So Ponders,
What size paper do you print scores on?
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Brian,
We could go halves in a shipping container.
Andrew
On 20 April 2015 at 05:29:07, Brian Barker (b.m.bar...@btinternet.com) wrote
I've got this down to 19 tonnes, but I doubt that's any more useful!
___
lilypond-user mailing list
lilypond-u
On Sun, 19 Apr 2015 21:39:29 -0400
Kieren MacMillan wrote:
> Do you not remember the tipping point when OpenOffice was
> embraced over Microsoft Office as the official office application suite
> by certain governments?
That's a totally different case: OO and MSO are two similar tools, that
have
If you want to put an arbitrary page number in the header, not the proper
consecutive one, how can this be done?
Useful when setting a score where you do not necessary;y do the pages in
monotonically increasing order.
Andrew
___
lilypond-user maili
Hi Urs,
Can you tell me why we should be interested in helping music publishers exactly?
If they are such corporate dinosaurs that do not recognise the benefits of
advanced lilypond technology, open source and open systems, of what concern is
it to the community of lilypond engravers?
I would
On Sun, Apr 19, 2015 at 03:12:20PM +0200, Orm Finnendahl wrote:
[...]
> Another thing: For me, also the implementation of transposing
> instruments is less than ideal (I prefer to write the pitches in
> concert pitch and have them transposed for the parts, rather than the
> other way around, as it
Hi Gilles (et al.),
> To whom LilyPond should strive to "offer the future”?
To everyone it possibly can. ;)
> IMHO, certainly not to the "[...] big house[s] with traditions,
> regulations and limitations”.
Why not? What’s to say that Lilypond can’t initially fit within those
traditions, regul
Am 17.04.2015 um 16:05 schrieb Kieren MacMillan:
Hi Urs,
First off, thank you so much for your continuing efforts on behalf of Lilypond.
They are really important, and no doubt time- and energy-consuming for you,
with little promise of immediate benefit to you personally. The ‘Pond
apprecia
Paul,
It is terrific. Now only one input of notes is generating Voice Staff for
jianpu notation and new Staff for music score. Thank you.
I try to put r8 r16 r32 and I got the following error:Starting
lilypond-windows.exe 2.19.17 [sample_jianpu2.ly]...Processing
`K:/sample_lily-code/sample_j
Hi,Paul!
I am impressed by your code! You have really made things automated! To note
about improvement, accidentals in jianpu look identical to those in standard
notation, but the baseline is about 0.75 height position of numeric note head
height button up. Lines indicating duration (aka. beam
Hi David,
> On Apr 18, 2015, at 1:14 AM, Paul Morris wrote:
>
> In the attached file is a start on a more automated way to do it. It uses a
> custom note head engraver and custom rest engraver (written in Scheme) to
> automatically alter the note head and rest stencils. By going further in th
Urs,
Yours is the approach I used. It did exactly what I needed. Thank you!
In this case I had some parts which started on the left page. I needed
something on the "cover" so as not to leave it blank.
-David
- Original Message -
> From: "Urs Liska"
> To: rich...@rshann.plus.com, bo
On Sat, 18 Apr 2015 23:33:25 + (GMT)
"bobr...@centrum.is" wrote:
> Create separate title/cover page in LaTeX and assemble the PDFs; seems a
> bit kludgy, though should work just fine. Failing any more integrated
> approach I would probably do this.
This is the approach I've been using for y
On 18/04/15 22:57, Wols Lists wrote:
> I must admit this is an example of "monkey see, monkey do" coding, but
> I'm pretty certain I was given it on this list originally, this is the
> second time I've tried to do something like this, and it's most
> definitely not right ...
>
> I'm trying to repl
Trevor Daniels treda.co.uk> writes:
> Martin Tarenskeen wrote Saturday, April 18, 2015 6:29 PM
>
> > Just a wild guess: did anyone on Windows try the same speed comparison
using
> > the --ps option instead of pdf output?
>
> Just done that. The conversion from ps to pdf takes only a couple o
Andrew Bernard wrote:
Yes, it is quite muddy!
I just took a look at the Guile 2.0 reference manual. Generally they use
procedure but the book also uses the term function interchangeably further on
inside, so I suppose it does not matter so much! No doubt the book is written
by a large team of
Hello.
On Sun, 19 Apr 2015 10:00:46 -0400, Kieren MacMillan wrote:
Hi Gilles,
[...]
Another thing: For me, also the implementation of transposing
instruments is less than ideal (I prefer to write the pitches in
concert pitch and have them transposed for the parts, rather than
the
other way
Wols Lists wrote:
On 18/04/15 22:11, PMA wrote:
Aha. So the improper-er their code got, the tougher time
compilers had trying to -- as Martin says -- "throw it out".
All told, is there now any real need _not_ to use the terms
"function" and "procedure" interchangeably? That is, any
real need
Hi Andrew, Hi Nick,
Maybe try small local printers: they can usually cut you custom sizes in
the colour/weight/sort you need.
They'll probably quote for few thousand pieces though...
Cheers,
Pierre
2015-04-19 11:11 GMT+02:00 Nick Payne :
> On 19/04/2015 18:46, Andrew Bernard wrote:
>
> Dear Pond
Hi Gilles,
>> [...]
>>
>> Another thing: For me, also the implementation of transposing
>> instruments is less than ideal (I prefer to write the pitches in
>> concert pitch and have them transposed for the parts, rather than the
>> other way around, as it is implemented at the moment).
>> [...]
>
Hi David,
I feel really stupid having said such a silly question just after a first
lecture...
Here's some old open source code just in case it'll help you find some
inspiration ;) : http://www.a1soft.com/smusic/
Sorry for the noise,
Cheers,
Pierre
2015-04-18 15:16 GMT+02:00 Super-User :
> Hi Pi
Hi Paul
2015-04-18 21:22 GMT+02:00 Paul Morris :
> Hi Pierre,
>
> Looking at this some more I see how it would really be handy for working
> with paths in LilyPond. Thanks for creating it and sharing it! I made
> some revisions to the code in the graph-paper file, simplifying things.
> See atta
Added to the LSR: http://lsr.di.unimi.it/LSR/Item?id=995
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi.
[Sorry for the thread hijacking.]
[...]
Another thing: For me, also the implementation of transposing
instruments is less than ideal (I prefer to write the pitches in
concert pitch and have them transposed for the parts, rather than the
other way around, as it is implemented at the moment)
Hi Kieren,
Am Samstag, den 18. April 2015 um 17:54:44 Uhr (-0400) schrieb Kieren
MacMillan:
>
> Would love to see it, but the link didn’t work for me… =\
that's strange. I just tried again and it works for me. Could it be
that your browser complained because of a missing certificate as the
syste
Peter Heisen wrote Wednesday, March 25, 2015 3:42 AM
> In the following modified example, the first beat of each ending has been
> changed to a rest, and a syllable removed from the lyrics to match. Now when
> compiled, it shows two first endings and two second endings. Moreover the
> log co
Yes, it is quite muddy!
I just took a look at the Guile 2.0 reference manual. Generally they use
procedure but the book also uses the term function interchangeably further on
inside, so I suppose it does not matter so much! No doubt the book is written
by a large team of authors.
An argument f
Hi Peter,
I don't know if it's possible to specify the output format in the
Lilypond file, but you can choose the paper size from the command line:
http://www.lilypond.org/doc/v2.18/Documentation/usage/command_002dline-usage
Then you have two commands to run, but you don't have to update your
On 19/04/2015 18:46, Andrew Bernard wrote:
Dear Ponderers,
Down under here in Australia we use A4 and A3. A4 is just too small
for piano music, and A3 is generally too big to fit on the music desk
comfortably.
The ideal size for me is Klavierformat (235x310mm) which is the
standard size of
Am 19. April 2015 10:35:08 MESZ, schrieb Andrew Bernard
:
>Well if you consult the bible Structure and Interpretation of Computer
>Programs by Abelson, Sussman, and Sussman, the term function is
>strictly reserved for mathematical objects, and procedure is uniformly
>used for what people loosely
Dear Ponderers,
Down under here in Australia we use A4 and A3. A4 is just too small for piano
music, and A3 is generally too big to fit on the music desk comfortably.
The ideal size for me is Klavierformat (235x310mm) which is the standard size
of editions such as Henle and so on. This paper si
Thank you!
I have been using
\override TupletBracket.avoid-slur = #’outside
to no effect.
Why do you have to adjust the number but not the bracket? Not entirely obvious.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu
Well if you consult the bible Structure and Interpretation of Computer Programs
by Abelson, Sussman, and Sussman, the term function is strictly reserved for
mathematical objects, and procedure is uniformly used for what people loosely
call functions.
As to the discussion about the distinction b
Am 19. April 2015 10:09:53 MESZ, schrieb Richard Shann
:
>On Sat, 2015-04-18 at 23:33 +, bobr...@centrum.is wrote:
>> I'm trying to make a title/cover page within LilyPond. I'm aware of
>the possibility of workarounds:
>>
>> lilypond-book/LaTeX; Strikes me as a bit ham-fisted, not sure if
On Sat, 2015-04-18 at 23:33 +, bobr...@centrum.is wrote:
> I'm trying to make a title/cover page within LilyPond. I'm aware of the
> possibility of workarounds:
>
> lilypond-book/LaTeX; Strikes me as a bit ham-fisted, not sure if I would run
> into trouble as I've seen the warning about \pa
37 matches
Mail list logo
