I just came across a workaround for this LilyPond crash - adding
\once \override MultiMeasureRestNumber #'transparent = ##t
before the multi-measure rests in the second voice results in the
typesetting finishing correctly.
I came across this because I was getting the number printed twice in
On Thu, Feb 27, 2014 at 10:27:53AM +, Richard Shann wrote:
I just came across a workaround for this LilyPond crash - adding
I have been getting very occasional segfaults with Lily since at
least 2.17. I have never been able to create a minimal example
because as soon as I change anything
On Thu, 2013-11-14 at 21:14 +0100, Jan-Peter Voigt wrote:
On 14.11.2013 16:19, Joseph Rushton Wakeling wrote:
there is an update of this snippet in the mail archives and I will post
my version later.
Fantastic, thank you! :-)
so, here is the version I regularly use ... in fact, this is
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo notehead mess.
That looks painful.
The duplicate rests section didn't register with my brain until a few
seconds later. I certainly prefer the 2014 look more with the merging, for
sure,
2013/11/20 Urs Liska u...@openlilylib.org:
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo notehead mess.
That looks painful.
They noticed too ;-)
http://www.finalemusic.com/blog/rolls-tremolos-jari-williamsson-and-finale-2014/
Janek Warchoł janek.lilyp...@gmail.com schrieb:
2013/11/20 Urs Liska u...@openlilylib.org:
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo
notehead mess.
That looks painful.
They noticed too ;-)
2013/11/20 Urs Liska u...@openlilylib.org:
Janek Warchoł janek.lilyp...@gmail.com schrieb:
2013/11/20 Urs Liska u...@openlilylib.org:
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo
notehead mess.
That looks painful.
They noticed
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/11/20 Urs Liska u...@openlilylib.org:
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo notehead mess.
That looks painful.
They noticed too ;-)
2013/11/20 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
2013/11/20 Urs Liska u...@openlilylib.org:
Am 14.11.2013 12:03, schrieb SoundsFromSound:
To be honest, the first thing my eyes went to was the tremolo notehead
mess.
That looks painful.
They noticed too
2013/11/15 Wilbert Berendsen wbs...@xs4all.nl:
Op Thu, 14 Nov 2013 09:52:06 +0100
Urs Liska u...@openlilylib.org schreef:
Hi all,
this has just appeared:
http://www.finalemusic.com/blog/quick-peeks-at-finale-2014-consolidate-rests/
and I think what they describe as inferior behaviour in
Hi all,
this has just appeared:
http://www.finalemusic.com/blog/quick-peeks-at-finale-2014-consolidate-rests/
and I think what they describe as inferior behaviour in Finale 2012 is
(nearly) exactly what we have to do (OK, we don't have to manually drag
rests to an appropriate place but let
It would be a great idea (although I haven't idea about the way to implement
it into LilyPond).
But I noticed how ugly the tremelo-notehead collision is, with Finale 2014
default settings ;-)
Philippe
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learn-from-Finale
Hi Urs,
there is a snippet in LSR:
http://lsr.dsi.unimi.it/LSR/Item?id=336
which did this for a long time. To me it seems, that finale learned from
lilypond ;)
I adapted it and integrated it in my own always-to-load-extensions and
use it in all my choral transcriptions.
Best, Jan-Peter
Am
Am 14.11.2013 11:16, schrieb Jan-Peter Voigt:
Hi Urs,
there is a snippet in LSR:
http://lsr.dsi.unimi.it/LSR/Item?id=336
which did this for a long time. To me it seems, that finale learned from
lilypond ;)
I adapted it and integrated it in my own always-to-load-extensions and
use it in all my
Am 14.11.2013 11:08, schrieb Karl Hammar:
Urs Liska:
Does anybody have an idea how one could improve this situation for LilyPond?
You have to be more specific, what is it you want ?
I'm not wanting anything specific, just raise this issue.
It seems that there already _is_ a solution, so
-
composer | sound designer
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learn-from-Finale-2014-seriously-tp153908p153918.html
Sent from the User mailing list archive at Nabble.com
Urs Liska u...@openlilylib.org writes:
But I often have to do things like
{
\voiceOne d'4 \oneVoice r \voiceOne d'
}
\new Voice {
\voiceTwo d4 s d
}
For this purpose I once wrote a function:
\dual {
g'4 \rr4 g'
} {
d'4 s d'
}
-- Johan
rr =
On 14/11/13 11:16, Jan-Peter Voigt wrote:
there is a snippet in LSR:
http://lsr.dsi.unimi.it/LSR/Item?id=336
which did this for a long time.
Please note that multi-measure rests are not automatically combined.
In addition, it hardly matches the ease of the Sibelius/Finale features if the
Johan Vromans jvrom...@squirrel.nl writes:
For this purpose I once wrote a function:
rr =
#(define-music-function
(parser location dur)
(ly:duration?)
#{ \oneVoice #(make-music 'RestEvent 'duration dur) \voiceOne #}
)
rr =
#(define-music-function
(parser location dur)
Hi Joseph,
Am 14.11.2013 14:45, schrieb Joseph Rushton Wakeling:
Please note that multi-measure rests are not automatically combined.
there is an update of this snippet in the mail archives and I will post
my version later.
In addition, it hardly matches the ease of the Sibelius/Finale
On 14/11/13 15:05, Jan-Peter Voigt wrote:
there is an update of this snippet in the mail archives and I will post
my version later.
Fantastic, thank you! :-)
You're right, but I would take this as a proposal to add this as a
standard command to lily.
Yes, I agree. In fact for optimal
David Kastrup d...@gnu.org writes:
rr =
#(define-music-function
(parser location dur)
(ly:duration?)
#{ \tweak direction #CENTER r$dur #})
would seem saner.
Thanks for the suggestion. I needed
#{ \tweak #'direction #'CENTER r$dur #})
but it sure looks nice(r).
Do you know
Johan Vromans jvrom...@squirrel.nl writes:
David Kastrup d...@gnu.org writes:
rr =
#(define-music-function
(parser location dur)
(ly:duration?)
#{ \tweak direction #CENTER r$dur #})
would seem saner.
Thanks for the suggestion. I needed
#{ \tweak #'direction #'CENTER
I've always used Phil's solution (manually placing one rest and using s for
the other), but, come to think of it, it would be nice for this to be done
automatically.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Learn-from-Finale-2014-seriously-tp153908p153952.html
2013/11/14 Michael Rivers michaeljriv...@gmail.com
I've always used Phil's solution (manually placing one rest and using s for
the other), but, come to think of it, it would be nice for this to be done
automatically.
After typing a full orchestral movement and solving the merge problem with
Am 2013-11-14 um 23:26 schrieb Phil Burfitt phil.burf...@talktalk.net:
I may be stating the obvious...but I've always used b4\rest (or whatever note
position you want the rest) in one voice and s4 in the other voices. Not that
elegant, but simple.
But doesn’t that play the b4 in MIDI?
Henning Hraban Ramm lilypon...@fiee.net writes:
Am 2013-11-14 um 23:26 schrieb Phil Burfitt phil.burf...@talktalk.net:
I may be stating the obvious...but I've always used b4\rest (or
whatever note position you want the rest) in one voice and s4 in the
other voices. Not that elegant, but
Op Thu, 14 Nov 2013 09:52:06 +0100
Urs Liska u...@openlilylib.org schreef:
Hi all,
this has just appeared:
http://www.finalemusic.com/blog/quick-peeks-at-finale-2014-consolidate-rests/
and I think what they describe as inferior behaviour in Finale 2012
is (nearly) exactly what we have to
28 matches
Mail list logo
