|
From: | Peter Olin |
Subject: | Re:Disappearing hyphens (endashes) in lyrics |
Date: | Fri, 21 Oct 2011 01:11:36 +0200 |
Send lilypond-user mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."
Today's Topics:
1. Re:Disappearing hyphens (endashes) in lyrics (Christ van Willegen)
2. Re:Disappearing hyphens (endashes) in lyrics (Mats Bengtsson)
3. clashing note columns (David Bobroff)
4. Re:clashing note columns (David Bobroff)
5. Re:clashing note columns (Nick Payne)
6. Change in convert-ly with 2.15.14? (Nick Payne)
7. Re:A problem with lilypond (Francisco Vila)
----------------------------------------------------------------------
Message: 1
Date: Thu, 20 Oct 2011 08:04:53 +0200
From: Christ van Willegen <address@hidden>
To: David Rogers <address@hidden>
Cc: address@hidden, Peter Olin <address@hidden>
Subject: Re: Disappearing hyphens (endashes) in lyrics
Message-ID:
<CA+Ot1OycvD7rH3EtYczXzmcheBVQ+rF4=address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Oct 20, 2011 at 03:26, David Rogers <address@hidden> wrote:
> This will alert the singer, at the time they need to know, "this is only
> half of the word". In your proposal, if another voice (or the accompaniment)
> has a lot of notes, the dash could end up "in the middle of nowhere", even
> potentially on the next line.
It does not indicate 'this is half a word' in his case, but 'this is a
parenthesis', so i would lessen the confusion (I think!).
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
------------------------------
Message: 2
Date: Thu, 20 Oct 2011 07:38:44 +0000 (UTC)
From: Mats Bengtsson <address@hidden>
To: address@hidden
Subject: Re: Disappearing hyphens (endashes) in lyrics
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Christ van Willegen <cvwillegen <at> gmail.com> writes:
>
> On Thu, Oct 20, 2011 at 03:26, David Rogers <davidandrewrogers <at> gmail.com>
wrote:
> > This will alert the singer, at the time they need to know, "this is only
> > half of the word". In your proposal, if another voice (or the accompaniment)
> > has a lot of notes, the dash could end up "in the middle of nowhere", even
> > potentially on the next line.
>
> It does not indicate 'this is half a word' in his case, but 'this is a
> parenthesis', so i would lessen the confusion (I think!).
>
> Christ van Willegen
For completeness, I hope you know about http://lsr.dsi.unimi.it/LSR/Item?id=680,
even though it does not answer this specific question.
/Mats
------------------------------
Message: 3
Date: Thu, 20 Oct 2011 08:46:40 +0000
From: David Bobroff <address@hidden>
To: lilypond-user <address@hidden>
Subject: clashing note columns
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
In a piece I'm doing in LilyPond I have a lot more single-staff
polyphony than I've dealt with before. I'm getting loads of:
warning: ignoring too many clashing note columns
The *output* looks fine.
Example: http://notendur.centrum.is/~bobroff/lily/measure.png
The 'd' in the half-note chord is tied over from the eighth note and is
in the upper voice. If I don't flip the stem direction the stem is up
and the note head offset. If I flip the stem it lines up as in the
original (shown in the link) but I get the warning. Should I just
ignore this and put up with the warnings? It is, of course, more
important that the output look good, but I'd also like a 'clean'
LilyPond run, too.
-David
------------------------------
Message: 4
Date: Thu, 20 Oct 2011 09:12:23 +0000
From: David Bobroff <address@hidden>
To: lilypond-user <address@hidden>
Subject: Re: clashing note columns
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 10/20/2011 8:46 AM, David Bobroff wrote:
> In a piece I'm doing in LilyPond I have a lot more single-staff
> polyphony than I've dealt with before. I'm getting loads of:
>
> warning: ignoring too many clashing note columns
>
> The *output* looks fine.
>
> Example: http://notendur.centrum.is/~bobroff/lily/measure.png
>
> The 'd' in the half-note chord is tied over from the eighth note and
> is in the upper voice. If I don't flip the stem direction the stem is
> up and the note head offset. If I flip the stem it lines up as in the
> original (shown in the link) but I get the warning. Should I just
> ignore this and put up with the warnings? It is, of course, more
> important that the output look good, but I'd also like a 'clean'
> LilyPond run, too.
>
> -David
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
Ah, it seems I found my answer here:
http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-notes#suppressing-warnings-for-clashing-note-columns
-David
------------------------------
Message: 5
Date: Thu, 20 Oct 2011 20:31:36 +1100
From: Nick Payne <address@hidden>
To: address@hidden
Subject: Re: clashing note columns
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
)On 20/10/11 20:12, David Bobroff wrote:
> On 10/20/2011 8:46 AM, David Bobroff wrote:
>> In a piece I'm doing in LilyPond I have a lot more single-staff
>> polyphony than I've dealt with before. I'm getting loads of:
>>
>> warning: ignoring too many clashing note columns
>>
>> The *output* looks fine.
>>
> Ah, it seems I found my answer here:
>
> http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-notes#suppressing-warnings-for-clashing-note-columns
Just be aware that if you turn on this override (\override NoteColumn
#'ignore-collision = ##t), and are also merging differently headed notes
in different voices, then the heads of merged half notes get filled in.
Without the override they don't:
\version "2.15.14"
\relative c' {
\mergeDifferentlyHeadedOn
<< { c16 a' b a } \\ { c,2 } >>
\override NoteColumn #'ignore-collision = ##t
<< { c16 a' b a } \\ { c,2 } >>
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/lilypond-user/attachments/20111020/aa8c4e8b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.preview.png
Type: image/png
Size: 3141 bytes
Desc: not available
URL: <http://lists.gnu.org/archive/html/lilypond-user/attachments/20111020/aa8c4e8b/attachment.png>
------------------------------
Message: 6
Date: Thu, 20 Oct 2011 20:43:44 +1100
From: Nick Payne <address@hidden>
To: "address@hidden" <address@hidden>
Subject: Change in convert-ly with 2.15.14?
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I use jEdit with Lilypondtool to edit ly source files. I recently
installed LP 2.15.14, and now, when I open an ly file in jEdit and run
convert-ly from the Lilypondtool menu or toolbar, I get two error
dialogs from jEdit. The first is titled "I/O Error" and says "Each
buffer can only execute one I/O operation at a time. Please wait until
the current operation finishes before starting another one". Behind that
is another dialog titled "Files changed on disk", and says
"Automatically reloaded: ", followed by the name of the file.
I haven't seen these messages before when running previous versions of
convert-ly with the same editing setup, and I have been using jEdit and
Lilypondtool for a considerable time without any version upgrade to
either. jEdit 4.4.1 and Lilypondtool 2.12.932 on Ubuntu amd64. In the
jEdit global options I have it set to automatically reload open files if
they are changed on disk, but this is how I have always had it set, and
these error messages have only been appearing since installing LP 2.15.14.
Nick
------------------------------
Message: 7
Date: Thu, 20 Oct 2011 12:11:30 +0200
From: Francisco Vila <address@hidden>
To: Martin Tarenskeen <address@hidden>, LilyPond-User list
<address@hidden>
Subject: Re: A problem with lilypond
Message-ID:
<CACAEdyCrijNF-i-DxC1KM=msHu9A=address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
2011/10/20 Martin Tarenskeen <address@hidden>:
> On Thu, 20 Oct 2011, Francisco Vila wrote:
>> 2011/10/19 ?<address@hidden>:
>>> I?were wondering if there is someway to fill the code and at same time
>>> generating the score for me to see what I am writting?
>> When I am typing music with Frescobaldi, I usually type a measure at a
>> time and press CTLR-M immediately, then I continue typing without
>> waiting for LilyPond to finish.
>> Sure, that puts the CPU in heavy load, but only for the period I am
>> transcribing intensively.
> I have tried different text-to-score music typesetting systems (mup,
> abcm2ps, pmw, and lilypond). Lilypond has become my first choice because of
> flexibility and quality of output. But compared to the other ones, speed is
> not it's strongest point. It is I think the flexibility (=complexity) in
> combination with the Scheme interpreted language that makes it slow. The
> competitors I mention are all 100% hardcoded compiled C programs. Lilypond
> is "easier" to tweak by the end-user thanks to the Scheme language.
>
> The trick address@hidden is asking for is possible with for example
> EasyABC, using abcm2ps, and it works pretty good for small to medium sized
> scores.
>
> But to end positively: today's fast computers make it already much easier to
> live with Lilypond's slowness.
I think that LilyPond is not especially slow considering what it does:
it does not limit itself to stroke your commands on a paper. It
performs a beauty contest in search of optimal layouts given a bunch
of typesetting rules and restraints. That way you can firstly
concentrate on music until you decide that you want this or that
forced layout.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
------------------------------
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user
End of lilypond-user Digest, Vol 107, Issue 51
**********************************************
screen-capture.png
Description: PNG image
[Prev in Thread] | Current Thread | [Next in Thread] |