Am Samstag, 12. Dezember 2009 08:35:24 schrieb David Kastrup:
Jay Anderson horndud...@gmail.com writes:
Also for the other responses, sorry if I didn't explain it very well.
This is the only way I've seen triple (and quadruple) stops notated so
I thought it would be self-explanatory.
Jay Anderson wrote:
I've attached a picture of the particular chord I was working on
(for viola, alto clef, in 3/4). In this case
I want to keep it explicitly notated and all in the same voice.
I suppose that this is notionally c g e'2.
Something which sounds like that but looks like
c4*3 g e'2.
Mmm, that was where you started.
Sorry for the noise.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Reinhold Kainhofer reinh...@kainhofer.com writes:
Am Samstag, 12. Dezember 2009 08:35:24 schrieb David Kastrup:
Jay Anderson horndud...@gmail.com writes:
Also for the other responses, sorry if I didn't explain it very well.
This is the only way I've seen triple (and quadruple) stops notated
Am Samstag, 12. Dezember 2009 08:35:24 schrieb David Kastrup:
Again: could you explain why you want to write 2. as a duration and then
remove the dot manually?
This does not really make sense at all.
Thanks for the other examples. I hadn't seen it notated like that
before (I'm not a
Robin Bannister r...@dataway.ch writes:
c4*3 g e'2.
Mmm, that was where you started. Sorry for the noise.
You can get a better-looking result at the cost of quadrupling the
number of warnings.
{
\clef G \relative c' {
\once \override NoteColumn #'ignore-collision =
2009/12/12 David Kastrup d...@gnu.org:
Robin Bannister r...@dataway.ch writes:
c4*3 g e'2.
Mmm, that was where you started. Sorry for the noise.
You can get a better-looking result at the cost of quadrupling the
number of warnings.
{
\clef G \relative c' {
\once
I'm confused by the docs for collision resolution:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Multiple-voices#Multiple-voices
In the example, the c2 and c8 are not merged because they have
different note-heads. But in the second bar, the e2 and e8 *are*
merged, despite having
Le 8 déc. 2009 à 18:40, Alexander Kobel a écrit :
It was written by someone (Nicolas?) who needed it
I've written it be never needed it nor used it. It was a very old
feature request.
___
lilypond-user mailing list
lilypond-user@gnu.org
Am Samstag, 12. Dezember 2009 11:33:33 schrieb Philip Potter:
I'm confused by the docs for collision resolution:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Multiple-voices#M
ultiple-voices
In the example, the c2 and c8 are not merged because they have
different note-heads.
Philip Potter wrote Saturday, December 12, 2009 10:33 AM
I'm confused by the docs for collision resolution:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Multiple-voices#Multiple-voices
In the example, the c2 and c8 are not merged because they have
different note-heads. But in
On Sat, Dec 12, 2009 at 12:03 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Coping to the bug list for confirmation.
I'm not sure the \oneVoice keyword is needed. Actually I'm not sure at
all *what* the example is aiming to demonstrate... Besides, doesn't
the doc explicitely mentions that this
Hm... I tried this a bit... Isn't a good solution either as it seems,
since I often have pedal where there are no notes.
(Already tried this polyphony thing: { } \\ { } \\ ; but this
doesn't actually work fine)
Do you have any idea how I could change the pedal behaviour at certain
points in my
Hi Stefan,
Hm... I tried this a bit... Isn't a good solution either as it seems,
since I often have pedal where there are no notes.
(Already tried this polyphony thing: { } \\ { } \\ ; but this
doesn't actually work fine)
It probably does if you use
{} \new Voice {}
instead.
Do you
Hi all,
I was playing around with canvas (html 5- most modern browsers are
compatible except IE) when I thought of quickly creating a frontend to make
note inputs for lilypond easier (in the style of a music notation software,
but not quite really).
Here's the link: http://jabtunes.com/notation/
Does Lilypond run under Windows 7?
Roberto Altschul
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
It worked fine on the Win7 release candidate I had installed as a virtual
machine a while back. I would assume it works under the actual release as
well. Give it a try. :)
Jon
On Fri, Dec 11, 2009 at 8:37 PM, Roberto Altschul
roberto.altsc...@comcast.net wrote:
Does Lilypond run under
On 12.12.2009, at 00:29, Neil Puttock wrote:
2009/12/11 stefankaegi ska...@hispeed.ch:
uhm... I have some doubts you understand me properly... The pedalling
actually should be like in my example (pedal on e and f), but
it's a
bit bad positioned.
This is a nasty bug of the Dynamics
In the future, a better formed question would be, Hi, I installed
lilypond on Windows 7 and am having these problems…
On 12.12.2009, at 03:37, Roberto Altschul wrote:
Does Lilypond run under Windows 7?
Roberto Altschul
___
lilypond-user
Sorry, Since the bad frustrating Midi tie problem persists, I have to roll back
to 2.13.7, and wait for a version with fixed tie playback.
Haipeng
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
As mentioned in the release message, users are strongly recommended to
use 2.12.2, not 2.13. We will let you know when we think that 2.13.x
is ready for users to test.
Cheers,
- Graham
2009/12/12 胡海鹏 - Hu Haipeng hhpmu...@163.com:
Sorry, Since the bad frustrating Midi tie problem persists, I
Just to sum up:
stop =
#(define-music-function (parser location music) (ly:music?)
(set! (ly:music-property music 'tweaks)
(acons 'before-line-breaking
(lambda (grob)
(let ((dots (ly:grob-object grob 'dot)))
(ly:grob-set-property! grob
Am Samstag, 12. Dezember 2009 15:43:37 schrieb 胡海鹏 - Hu Haipeng:
Sorry, Since the bad frustrating Midi tie problem persists, I have to roll
back to 2.13.7, and wait for a version with fixed tie playback.
I've tried to fix the bug, but I'm always running into memory corruption
issues, and I
Sorry, Since the bad frustrating Midi tie problem persists, I have
to roll back to 2.13.7, and wait for a version with fixed tie
playback.
I second this: This belongs to the non-existent bug category
`annoying' :-)
Seriously: It should be fixed ASAP, or please revert to the old
behaviour.
Am Samstag, 12. Dezember 2009 17:34:36 schrieb Werner LEMBERG:
Sorry, Since the bad frustrating Midi tie problem persists, I have
to roll back to 2.13.7, and wait for a version with fixed tie
playback.
I second this: This belongs to the non-existent bug category
`annoying' :-)
Valentin Villenave wrote Saturday, December 12, 2009 12:36 PM
On Sat, Dec 12, 2009 at 12:03 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Coping to the bug list for confirmation.
I'm not sure the \oneVoice keyword is needed. Actually I'm not
sure at
all *what* the example is aiming to
It works fine. Indeed I will be patching the MS Windows Learning Tutorial with
screenshots that came from Windows 7 soon.
Once I get my head around git ;)
James
-Original Message-
From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of
Jonathan Kulp
Sent: Sat
On Sat, Dec 12, 2009 at 5:58 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
The half note and eighth note at the start of the second measure are
incorrectly merged because \mergeDifferentlyHeadedOn cannot
successfully complete the merge when three or more notes line up in
the same column,
Hi,
I am running 2.13.8 and I am just finishing a large concerto with three
movements with a full score of 90 pages. I have four percussion parts.
I use the RhythmicStaff for my percussion parts without tonality. The
RhythmicStaff(s) layout fine in the full score, but the layout isn't
fine on
Craig,
Just to say that 2.13.8 is an unstable release and this is obviously a big
project for you, rather than 'trying it out for fun' so to that end, have to
tried to compile the file using the stable 2.12.x release. At least that way we
know if it is something new in this work-in-progress
Hey everybody, I'm having a problem with noteheads in different voices
colliding, and I can't seem to fix it. I tried the standard fix from the
notation: \once \override NoteColumn #'force-hshift = # , which worked fine
in a test case I did, but for some reason has zero effect in the document.
I downloaded the 2.13.9 documentation and extracted the PDFs. I notice
that in web.pdf, most of the graphics are rendered too large and run off
the edge of the page...
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
Hi,
I just did a compile with 2.12 and the layout is good.
Craig Bakalian
On Sat, 2009-12-12 at 16:45 -0500, James Lowe wrote:
Craig,
Just to say that 2.13.8 is an unstable release and this is obviously a big
project for you, rather than 'trying it out for fun' so to that end, have to
33 matches
Mail list logo
