Hi Joram,
2014-11-02 1:46 GMT+01:00 Noeck noeck.marb...@gmx.de:
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
Try :
\version 2.19.15
\new PianoStaff
\new Staff { g-_ }
\new Dynamics {
s
Hi All,
I've slightly changed this snippet. Syntax has been simplyfied : \myBox
#width #heigth
http://lsr.di.unimi.it/LSR/Item?id=953
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
Hello folks,
In the following sample, how can I have the second mark displayed at the
beginning of the second line?
Adding the hidden measure and bar line trick prevents the new time indication
to be printed at the end of the first line, unfortunately.
Thanks for your help!
JM
—
Yes, you are right. The unicode fonts failed on 2.19.5. I even tried the
new windows 10 and it failed.
Now that I know it works on linux (thanks to Bric), I will try to get
access to linux using virtual box and try it out.
On Sat, Nov 1, 2014 at 2:08 PM, Werner LEMBERG w...@gnu.org wrote:
If
Very interesting developements here. I love Lilypond!
I am fine with the default font at the moment, just wondering if any of
these fonts has specific improvements for ancient notation engraving.
Thank you,
A
--
View this message in context:
On 2 Nov 2014, at 11:31, Jayaratna jayara...@gmail.com wrote:
Very interesting developements here. I love Lilypond!
I am fine with the default font at the moment, just wondering if any of
these fonts has specific improvements for ancient notation engraving.
Check here:
No, I haven't attempted anything related to ancient notation. What kind of
improvements are you thinking of?
-Abraham
Sent from my iPhone
On Nov 2, 2014, at 4:31 AM, Jayaratna [via Lilypond]
ml-node+s1069038n168293...@n5.nabble.com wrote:
Very interesting developements here. I love
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I try to move the tenor text above the staff I fail. I have read the
manual pages, but it does not work. What to change?
I have tested the following piece and it compiles, however, not with the result
I want.
Thank you
Bernhard
version
Noeck wrote Sunday, November 02, 2014 12:46 AM
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
You're right, Joram, \offset is not a solution. In fact, it seems to point to
another problem with
Bernhard Kleine wrote Sunday, November 02, 2014 12:02 PM
When I try to move the tenor text above the staff I fail. I have read the
manual pages, but it does not work. What to change?
I have tested the following piece and it compiles, however, not with the
result I want.
Almost right, but
Hi,
On Sun, Nov 2, 2014 at 6:23 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Noeck wrote Sunday, November 02, 2014 12:46 AM
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
You're right, Joram,
Let alone the music spacing, I think the diamond note heads are fare too
small, in general.
This is taken on a 12pt score magnified at 180%, default lilypond engraving:
http://lilypond.1069038.n5.nabble.com/file/n168304/2014-11-02-180946_1024x600_scrot.png
Look at the quavers flags, and
Interesting stuff, I should try it. I guess I'll wait for the 2.19 version to
become stable
and try some different fonts.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168305.html
Sent from the User mailing list archive
David, you wrote Sunday, November 02, 2014 12:44 PM
No, it's not a problem with \offset.
Substitute this for the call to \offset, and you'll see that it's actually an
issue with X-offset here:
\once \override DynamicText.X-offset = #-3
Ah, sorry to cast invalid aspersions on \offset,
On Sun, Nov 2, 2014 at 6:55 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
David, you wrote Sunday, November 02, 2014 12:44 PM
No, it's not a problem with \offset.
Substitute this for the call to \offset, and you'll see that it's
actually an issue with X-offset here:
\once
This may help you, although it is fairly complex:
http://lsr.di.unimi.it/LSR/Item?id=892
Knute Snortum
(via Gmail)
On Sun, Nov 2, 2014 at 2:12 AM, Jacques Menu imj-...@bluewin.ch wrote:
Hello folks,
In the following sample, how can I have the second mark displayed at the
beginning of the
Hi again,
On Sun, Nov 2, 2014 at 7:08 AM, David Nalesnik david.nales...@gmail.com
wrote:
Offsetting arpeggio.positions is nice, I think. (Though not precise;
there is quantization which unavoidably kicks in, I think. It's still nice
for arpeggios across tiny intervals, where you don't want
Hello,
As far as I know, which is certainly minimal, ties cannot be input across
voices as in
\new Voice \relative c' { \voiceOne }
\new Voice \relative c' { \voiceTwo }
.
How could I achieve ties as in the attached example?
Thank you for your kind attention.
On Nov 2, 2014, at 4:24 PM, Mark Stephen Mrotek carsonm...@ca.rr.com wrote:
Hello,
As far as I know, which is certainly minimal, ties cannot be input across
voices as in
\new Voice \relative c' { \voiceOne }
\new Voice \relative c' { \voiceTwo }
.
How
Mike,
Thank you for your reply and the suggestion. I shall try it.
“Never let the perfect be the enemy of the good!”
Mark
From: Mike Solomon [mailto:m...@mikesolomon.org]
Sent: Sunday, November 02, 2014 6:43 AM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re: Ties
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
\new Staff = down {
\clef bass
s2
}
\new PianoStaff
\new Staff =
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
Hi Mike,
Thanks for your reply.
Mike Solomon wrote
This is a persistent issue in LilyPond development - there was some work
on it in course a couple years ago that has since been put on hold but I
hope to pick it back up one day.
I totally understand it.
Mike Solomon wrote
I know that
Gilberto Agostinho gilbertohasnofb at gmail.com writes:
[in the context of music generated by an algorithm]
I am having trouble dealing with ottava changes while using autochange.
The example showed \ottava changing the ottavation of staves by hand,
but the music moving between staves
Gilberto Agostinho gilbertohasnofb at gmail.com writes:
but when changing staff the ottava position
gets lower (!) and collides with the beam.
LilyPond allows you to beam to any other staff, so in general that
beam might have to go up and cross the ottava bracket, while the
bracket must stay
Hi Keith,
Keith OHara wrote
The general solution seems to be to apply whatever algorithm you use
to choose ottavation after applying the \autochange routine
\autoOctave \autoChange {...}
or maybe easier to merge them into one.
Oh, I see! So now I will probably aim to produce something
Hi Keith,
Thanks for the detailed explanation, I think I understand the situation well
now.
Keith OHara wrote
I have no better suggestion. The manual tweak is simple, though,
\once\override Staff.OttavaBracket.staff-padding = #6
Thanks anyway. Unfortunately my case of avoiding manual
29 matches
Mail list logo
