Wonderful. Thank you.
On Friday, 17 February 2017 09:58:47 UTC, Wilbert wrote:
>
> Dear friends,
>
> I just released the source packages for Frescobaldi 2.20.0, Frescobaldi
> 3.0.0 and python-ly 0.9.5 today. (I couldn't way until my birthday early
> March :-))
>
> Frescobaldi 2.20.0 provides a
On Sat, Feb 18, 2017 at 8:51 PM, Andrew Bernard
wrote:
> Hi Jeffery,
>
> \override Score.SystemStartBar.collapse-height = #6
>
> Andrew
Wonderful, thank you Andrew!
--
Jeffery Shivers
jefferyshivers.com
soundcloud.com/jefferyshivers
___
lily
Hi Jeffery,
\override Score.SystemStartBar.collapse-height = #6
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Sat, Feb 18, 2017 at 8:38 PM, Jeffery Shivers
wrote:
> Hi,
>
> I am using a staff with (many) more than five lines, but when I
> increase the line-count a vertical line appears to the left of the
> staff. How do I prevent that from happening, or at least make that
> line transparent?
I see no
Hi,
I am using a staff with (many) more than five lines, but when I
increase the line-count a vertical line appears to the left of the
staff. How do I prevent that from happening, or at least make that
line transparent?
\version "2.19.54"
\score {
\new Staff {
\override Staff.StaffSymbol.l
Hi Knute,
LSR 410 shows a way to do this. Would that help?
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I have a chord that has both a grace note and an arpeggio spanner, like so:
\version "2.19.54"
{
\grace e''4 2 \arpeggio
}
When Lilypond engraves this, the grace note is to the left of the spanner.
I want it the other way around. I've tried tweaking them both but I can
never get the grace not
[Bug report summary:]
Extenders are not drawn anymore for melismata that include notes that
are not bar-aligned, starting somewhere between 2.19.50 and 2.19.55.
M(N)WE attached - the first and second score should have extenders until
the last note.
Hi Michael,
On 2017-02-18 18:59, Michael
David,
Thanks again.
Just after I posted my previous message I worked it out by myself! Now got 3
pages of music down to one!
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Saturday, February 18, 2017, 5:37:39 PM, you wrote:
> On Sat, Feb 18, 2017 at 11
> I actually meant using an include file like the attached and not having
> to add the music function locally at all.
Since this include file had been posted I've been using it with great
pleasure and like it very much.
There is one problem I'd like to vanish.
It seems extender lines stop at the
On Sat, Feb 18, 2017 at 11:14 AM, Peter Toye wrote:
> David, Jeffery,
>
> Thanks again. But there's a slight problem: I didn't mention that I'm a
> pianist, so have 2 separate staves with the same repeat pattern. The snippet
> below shows some very interesting results, not least at the bar number
Kieren MacMillan writes:
> Hi Guy,
>
>> Why is this now necessary? Is it a case of assumptions about voices
>> changing in the newer 2.19 LP?
>
> I can’t remember exactly when or why it became necessary… I only
> remember getting bitten by it (which is why I know the fix!).
> Perhaps others (e.g.
David, Jeffery,
Thanks again. But there's a slight problem: I didn't mention that I'm a
pianist, so have 2 separate staves with the same repeat pattern. The snippet
below shows some very interesting results, not least at the bar number check.
\score {
\new PianoStaff {
\set Score.current
Ah!
LOL
Same boat and all that.
Thanks again.
On 02/18/2017 10:51 AM, Kieren MacMillan wrote:
Hi Guy,
Why is this now necessary? Is it a case of assumptions about voices changing in
the newer 2.19 LP?
I can’t remember exactly when or why it became necessary… I only remember
getting bitte
Hi Guy,
> Why is this now necessary? Is it a case of assumptions about voices changing
> in the newer 2.19 LP?
I can’t remember exactly when or why it became necessary… I only remember
getting bitten by it (which is why I know the fix!).
Perhaps others (e.g., David Kastrup) can clarify when and
Kieren,
It does indeed. Why is this now necessary? Is it a case of assumptions
about voices changing in the newer 2.19 LP?
Once I update to 2.19, every existing score I have that uses the
temporary polyphonic context will have to be edited to add this; not a
trivial task.
Thanks for your q
Hi Guy,
> testVoicePart = \new Staff \new Voice { \global \test }
That should fix it.
Hope this helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lil
I've searched both the list archives and LilyIssues and do not see this
reported.
I use temporary polyphonic contexts a lot in my choral compositions. I see
that using any version of 2.19 breaks lyric placement if there are slurred
notes in /voiceOne against which lyrics should be placed. There ar
this works:
#(define-markup-command (instruct layout props text) (markup?)
(interpret-markup layout props
#{
\markup \italic \magnify #0.7 #text
#}))
mkTenor = \markup { \instruct "tenor"}
\relative c' {
d1-\mkTenor
}
=Marc
On Sat, Feb 18, 2017 at 9:52 AM, Rob Torop w
Rob Torop writes:
> I have a bunch of repeated things like this
>
>d f \mark \markup \italic \magnify #0.7 "(tenor & trp.)" r16
>
> where I put a little instruction over the melody
>
> I'd like to have a little function to call instead of \mark \markup \italic
> \magnify #0.7 "blah",
I have a bunch of repeated things like this
d f \mark \markup \italic \magnify #0.7 "(tenor & trp.)" r16
where I put a little instruction over the melody
I'd like to have a little function to call instead of \mark \markup \italic
\magnify #0.7 "blah", with the "blah" as a parameter.
21 matches
Mail list logo