This is a known problem that has not made it into the bug tracker, as
far as I can see.
See http://lists.gnu.org/archive/html/lilypond-devel/2007-04/msg00136.html
Also, as you can see later in the same thread, it doesn't help to add
the bar engraver
to the context. Here comes a somewhat modified
2008/6/4 Mats Bengtsson <[EMAIL PROTECTED]>:
> This is a known problem that has not made it into the bug tracker, as far as
> I can see.
Now it has:
http://code.google.com/p/lilypond/issues/detail?id=631
Cheers,
Valentin
___
bug-lilypond mailing list
Hi,
Piano centered dynamics are not centered between the two staves.
Am I missing something?
Thanks!
Zoltan
%%%
%%%
%% The Learning Manual (A
have come across a tricky case (although I have to admit that I don't
see what should be tricky about your example).
HTH
Urs
Am 12.10.2010 22:41, schrieb Zoltan Selyem:
Hi,
Piano centered dynamics are not centered between the two staves.
Am I missing something?
Thanks!
Z
Przemyslaw,
On Thu, Jan 28, 2016 at 6:02 PM, Przemyslaw Pawelczyk [via Lilypond] <
ml-node+s1069038n186599...@n5.nabble.com> wrote:
> Hi!
>
> There is a piano centered dynamics template that was present in
> Lilypond Learning Manual for v2.14, but is not available in recent
Hi, Abraham!
On Fri, Jan 29, 2016 at 6:49 PM, Abraham Lee wrote:
> On Thu, Jan 28, 2016 at 6:02 PM, Przemyslaw Pawelczyk [via Lilypond] <
> ml-node+s1069038n186599...@n5.nabble.com> wrote:
>> There is a piano centered dynamics template that was present in
>> Lilypond L
is the PDF with both overrides:
> http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics-workaround.pdf
Here is the PDF w/o overrides:
http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics.pdf
I've noticed another thing just now, after
On Sat 30 Jan 2016 at 00:00:43 (+0100), Przemyslaw Pawelczyk wrote:
> I've noticed another thing just now, after zooming in.
> Regardless of the overrides, first half note in the lower staff
> actually does not line up with quater note in the upper staff.
Isn't that because a minim is wider then
Updates:
Status: Fixed
Labels: fixed_2_13_4
Comment #1 on issue 581 by n.puttock: add engraver for dynamics; simplifies
piano-centered-dynamics
http://code.google.com/p/lilypond/issues/detail?id=581
(No comment was entered for this change.)
--
You received this message
Updates:
Status: Verified
Comment #2 on issue 581 by v.villenave: add engraver for dynamics;
simplifies piano-centered-dynamics
http://code.google.com/p/lilypond/issues/detail?id=581
Nice :-)
--
You received this message because you are listed in the owner
or CC fields of this issue
Issue 581: add engraver for dynamics; simplifies piano-centered-dynamics
http://code.google.com/p/lilypond/issues/detail?id=581
New issue report by gpermus:
The attached patch adds an engraver_group Dynamics and makes PianoStaff
accept it.
Han-Wen asked:
Just a simple tangential question: do
Issue 631: Collision piano centered dynamics and cross-staff barlines
http://code.google.com/p/lilypond/issues/detail?id=631
New issue report by v.villenave:
% When the dynamics have their own Voice, they tend to collide
% with barlines. Adding the Bar_engraver doesn't help.
\version &qu
> Nice :-)
I think this deserves a NEWS entry.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
> I'm not top posting.
Example:
\version "2.11.23"
upper = \relative c'' {
\clef treble
\key c \major
\time 4/4
a b c d
}
lower = \relative c {
\clef bass
\key c \major
\time 4/4
a2 c
}
dynamic
The same holds true for a ChoirStaff with Lyrics under every contained staff.
It would be nice if the instrumentName for more than one staff were vertically
centered before the staff-like contexts, and not counting not-stafflike
contexts like lyrics/dynamics etc outside the staffs.
I did not tr
Thanks for the report -- but is this a report about the docs, or a
bug in the program?
If it's something about the docs, please note that the templates
are generated from LSR; they should be fixed in there.
If it's a bug in the program, please create a minimal example.
Cheers,
- Graham
On Thu,
I think Wilbert has already provided a very accurate description of the
problem
and its solution (to just move the Dynamics context outside the
PianoStaff).
I can add a sentence in the section on Instrument names.
However, I also agree with Wilbert's "It would be nice ...", so an ambitious
bug
Graham Percival wrote:
You hear that, Valentin? Be ambitious. :)
This is probably related to Trevor's recent email to -devel about
adding Dynamics to performer-init.ly.
No! You will see exactly the same problem if you include a Lyrics or a
FiguredBass or a ChordNames or whatever context in
You hear that, Valentin? Be ambitious. :)
This is probably related to Trevor's recent email to -devel about
adding Dynamics to performer-init.ly. But since it involves piano
and I'm strictly strings-only, (and since I'm not Bug Meister any
more) I happily haven't looked at any of these emails.
On 04/02/2008, Graham Percival <[EMAIL PROTECTED]> wrote:
> You hear that, Valentin? Be ambitious. :)
Well, I am, but generally you're the one who prevents me from being so :)
Honestly, I think this is all about LilyPond dumb-but-logical way of
doing things, so the current behavior doesn't seem
20 matches
Mail list logo
