When a key change occurs at a line break, in many (most?) editions the
key is cancelled at the end of the first line, and not at the beginning
of the subsequent line. According to the Fine Manual, this is supposed
to be the default behaviour (I'm looking at
lilypond-internals/KeyCancellation.h
Han-Wen Nienhuys wrote:
it's probably better to use
lilypond.org/doc/{stable,development}/
as more permanent links.
I didn't realize I could do that, thanks. There's probably a bunch of
places where this is true; I'll go look for them.
Cheers,
- Graham
__
Graham Percival escreveu:
> James Kilfiger wrote:
>> There is a broken link on the page
>> http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Changing-defaults
>>
>>
>> the link is :
>>
>> It is written as a HTML document, which is available
>> http://lilypond.org/doc/v2.8/Documentation/user
Graham Percival escreveu:
> I've added this as
> http://code.google.com/p/lilypond/issues/detail?id=232
>
> but I suspect it may be quite tricky to implement. I think that a
> better short-term solution is to define
> \minorKey
>
> which sets up the correct noteheads for minor. You can use this
I've added this as
http://code.google.com/p/lilypond/issues/detail?id=232
but I suspect it may be quite tricky to implement. I think that a
better short-term solution is to define
\minorKey
which sets up the correct noteheads for minor. You can use this same
definition for many pieces; see
Issue 232: shapeNoteStyles should change based on current key
http://code.google.com/p/lilypond/issues/detail?id=232
New issue report by gpermus:
When the current key is a minor key, the shapeNoteStyles are set wrong.
The shape noteheads change depending on the key of the piece.
shapeNoteStyle
Thanks for the report! This bug has already been fixed in the unstable
branch with a new method of checking for vertical collisions. This will
not be backported to the 2.10 series (there are still problems with it),
but you could either look forward to the next big stable release, or try
usin
Daniel Johnson wrote:
In 2.10.10, Dynamic_performer and Span_dynamic_performer have been
replaced by New_dynamic_performer, but convert-ly does not make a change
or issue a warning. I've been using them in my midi block, and now I
will have to remember to manually change them.
Thanks,
http:/
Issue 231: convert-ly and New_dynamic_performer
http://code.google.com/p/lilypond/issues/detail?id=231
New issue report by gpermus:
In 2.10.10, Dynamic_performer and Span_dynamic_performer have been replaced
by New_dynamic_performer, but convert-ly does not make a change or issue a
warning.
Is
James Kilfiger wrote:
There is a broken link on the page
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Changing-defaults
the link is :
It is written as a HTML document, which is available
http://lilypond.org/doc/v2.8/Documentation/user/
lilypond-internals/">on-line,
but is also inc
Issue 230: segfault 2.11.10
http://code.google.com/p/lilypond/issues/detail?id=230
New issue report by hanwenn:
\version "2.11.10"
\score
{
\new Staff \relative c'''
{
\time 2/4
4\fermata
\grace {bes32[( a g fis g a bes c d c bes a g f e d c cis d a] c2)}
4\fer
At this point, anyone who is going to bother to put in the effort and
expense of getting imagesetter output will probably also have the
money for Finale, Sibelius, SCORE, or similar. Lilypond just isn't in
that league yet (although it is getting there).
Actually I do have the money for Sibeli
Han-Wen Nienhuys wrote:
Marnen Laibow-Koser escreveu:
Of course laser printouts are better for this purpose, but not everyone
is lucky enough to have a 1200-dpi laser printer sitting around. My
A 600dpi x 1200dpi printer can be had for less than EUR 100 nowadays,
will produce output that
Han-Wen Nienhuys wrote:
The weight of the barline has to be considered in relation to the visual
weight of the rest of the page. Music is usually played and read
from a page, not from separate symbols.
Agreed. But up to now, we've been focusing on individual symbols. I
would be happy to
Bertalan Fodor wrote:
I think we should definitely go to a print shop and create a film with
some LinoType machine in 4800dpi
[...]
That would be a lovely idea. Unfortunately, there are three problems:
* Money
* Time
* The fact that it would not be representative of the output conditions
of t
Marnen Laibow-Koser escreveu:
> Han-Wen Nienhuys wrote:
>> You cannot judge typography from screen, no matter how much you magnify.
>> It's just not the same thing.
>
> If you're trying to judge the look of a whole page, of course that's
> true. However, for the look of a single character or a s
Marnen Laibow-Koser escreveu:
> Of course laser printouts are better for this purpose, but not everyone
> is lucky enough to have a 1200-dpi laser printer sitting around. My
A 600dpi x 1200dpi printer can be had for less than EUR 100 nowadays,
will produce output that is better than virtually a
Han-Wen Nienhuys wrote:
You cannot judge typography from screen, no matter how much you magnify.
It's just not the same thing.
If you're trying to judge the look of a whole page, of course that's
true. However, for the look of a single character or a small area, I
completely disagree. And
Jan Nieuwenhuizen wrote:
When designing bar
lines, we were looking for a practice that was backed by big houses,
but also something interesting or exceptional(ly beautiful), rather
than something too common and `looking also ok'.
Hmm. I wonder if this was in fact the right way to go: exception
Marnen Laibow-Koser escreveu:
> Han-Wen Nienhuys wrote:
>> Marnen Laibow-Koser escreveu:
> [...]
>>> Nope, wrong again. My original judgement came in fact from viewing the
>>> PDF file.
> [...]
>> The fanciest computer displays are 142 dpi (1600x1200 14" laptop
>> screen). This is not good enough
I think we should definitely go to a print shop and create a film with
some LinoType machine in 4800dpi (it generally costs some EUR per page)
and judge according to :
- the various types of music (I'm quite sure that a choir with piano
piece crowded with lyrics will need other line sizes than a
Han-Wen Nienhuys wrote:
Marnen Laibow-Koser escreveu:
[...]
Nope, wrong again. My original judgement came in fact from viewing the
PDF file.
[...]
The fanciest computer displays are 142 dpi (1600x1200 14" laptop
screen). This is not good enough for judging typography.
Augh! The moment I
Marnen Laibow-Koser <[EMAIL PROTECTED]> writes:
> Then that was the luck of the draw. I basically chose a few books
> more or less at random, and added some editions whose aesthetics I
> like (such as Henle). I will be trying to enlarge my sample and
> seeing if the numbers change.
>
> Or should
Han-Wen Nienhuys wrote:
I think we have a difference of opinion. I would rather
call that fuzzy and uneven.
Well, at 2400 dpi, yes. But while my scanner has that sort of optical
resolution, I do not. At actual size, the output is actually pretty
hard to tell from laser output.
Best,
Marn
Marnen Laibow-Koser escreveu:
> Han-Wen Nienhuys wrote:
> [...]
>
>> Your judgement of "ugly" was based on prints that come from an
>> inferior printer.
>
> Nope, wrong again. My original judgement came in fact from viewing the
> PDF file.
Which why -at the top the examples page
http://lilyp
Marnen Laibow-Koser <[EMAIL PROTECTED]> writes:
> What do you mean by "further investigation"? My conclusion
I was referring to Werner and Han-Wen. By further investigation, I
meant looking at printed output; comparing with the originals that
Lily's bar lines were designed from and trying to di
Marnen Laibow-Koser escreveu:
> Han-Wen Nienhuys wrote:
> [...]
>
>> Your judgement of "ugly" was based on prints that come from an
>> inferior printer.
>
> Nope, wrong again. My original judgement came in fact from viewing the
> PDF file.
>
> And I wouldn't call my printer "inferior". Oh sure
Han-Wen Nienhuys wrote:
[...]
Your judgement of "ugly" was based on prints that come from an inferior
printer.
Nope, wrong again. My original judgement came in fact from viewing the
PDF file.
And I wouldn't call my printer "inferior". Oh sure, it's an inkjet
printer, but the output is fi
Marnen Laibow-Koser escreveu:
> I would have just measured from the PDF file, had it not been for John
> Neeman's point that the document might print slightly differently.
You'll get exact measurements from the PDF, but it's about esthetics first.
Your judgement of "ugly" was based on prints that
29 matches
Mail list logo
