Hi,
The lilypond output that is produced from musicxml2ly uses another
indentation style than I see in my own scores when using for example Vim
or Frescobaldi, or in all examples in the Lilypond documentation.
for example:
%commonly used style
music = \relative c' {
a b c d
}
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:
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
Am 14.11.2013 09:50, schrieb David Kastrup:
Marc Hohl m...@hohlart.de writes:
Here is what I coded:
Not really. You are mixing note languages in here; this would never
have worked. Please test your examples before posting.
Now the last f,, should be marked with a broken bracket to be
Am 14.11.2013 09:50, schrieb David Kastrup:
Marc Hohl m...@hohlart.de writes:
Here is what I coded:
Not really. You are mixing note languages in here; this would never
have worked. Please test your examples before posting.
Uh, sorry, I overlooked that.
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, but my eyes didn't process that as standout
Marc Hohl m...@hohlart.de writes:
Am 14.11.2013 09:50, schrieb David Kastrup:
Marc Hohl m...@hohlart.de writes:
Here is what I coded:
Not really. You are mixing note languages in here; this would never
have worked. Please test your examples before posting.
Now the last f,, should be
Ah yes, of course. It works now :) Thanks a lot!
On 14 November 2013 00:32, Eluze elu...@gmail.com wrote:
Gagi Petrovic wrote
I tried your method (see below), but it still doesn't work correctly. Now
the text is nicely placed under all the fermata, but i don't understand
why
the slur
David Kastrup wrote
Helge Kruse lt;
Helge.Kruse@
gt; writes:
This interface improvement also effectively enforces top-posting: it
takes
extra effort to post replies in the middle of quotes (like a
conversation)
and most people don't care.
I am in the e-mail world for some decades. It
[...]
Thanks, that works better, but there is no way to code broken
ligatures out-of-the-box, as shown in the picture.
Ah, I misunderstood your problem: you want a ligature broken al
niente: one that basically comes from nowhere, and one that breaks into
nowhere.
Yes, exactly.
That would
SoundsFromSound soundsfromso...@gmail.com writes:
[fullquote deleted]
I had no idea this was the norm. I've always been writing on top - including
the previous messages below my reply for years now, which I now assume was a
byproduct of working as an IT consultant as a secondary job. It feels
2013/11/14 David Kastrup d...@gnu.org:
I am in the e-mail world for some decades. It was always a good
style to write the answer on top of all other text and to not delete
anything that has written before.
In a mailing list? No.
Sorry, you missed one point. I wrote about mails in general.
Hi,
What we actually want here on lilypond mailing lists is not literally
bottom-posting, but inline-replying:
http://en.wikipedia.org/wiki/Posting_style#Interleaved_style (yes,
some people indeed use bottom posting to refer to inline replying,
but this is ambiguous and therefore not helpful. I'm
Janek Warchoł janek.lilyp...@gmail.com writes:
What we actually want here on lilypond mailing lists is not literally
bottom-posting, but inline-replying:
http://en.wikipedia.org/wiki/Posting_style#Interleaved_style (yes,
some people indeed use bottom posting to refer to inline replying,
but
Helge Kruse helge.kr...@gmx.net writes:
2013/11/14 David Kastrup d...@gnu.org:
An improvement that _does_ _not_ _scale_ is no improvement.
Don't see _scale_ here, since it's not designed for mailing list,
sorry.
It's not designed for _any_ significantly extended exchange.
I think
Janek Warchoł wrote
Hi,
What we actually want here on lilypond mailing lists is not literally
bottom-posting, but inline-replying:
http://en.wikipedia.org/wiki/Posting_style#Interleaved_style (yes,
some people indeed use bottom posting to refer to inline replying,
but this is ambiguous and
2013/11/14 David Kastrup d...@gnu.org:
Janek Warchoł janek.lilyp...@gmail.com writes:
What we actually want here on lilypond mailing lists is not literally
bottom-posting, but inline-replying:
http://en.wikipedia.org/wiki/Posting_style#Interleaved_style (yes,
some people indeed use bottom
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
Hi LilyPonders,
There are two broken links in the main page http://lilypond.org/
In the very beginning, under LilyPond 2.17.95 released! November 3, 2013,
there are links to Updating files with convert-ly and Bug reports. When
clicking on either of them, my browser tells me 404 Not Found.
Take
Hi Gilberto,
2013/11/14 Gilberto Agostinho gilbertohasn...@gmail.com:
Hi LilyPonders,
There are two broken links in the main page http://lilypond.org/
In the very beginning, under LilyPond 2.17.95 released! November 3, 2013,
there are links to Updating files with convert-ly and Bug reports.
Replies directed to bug-lilypond.
Gilberto Agostinho gilbertohasn...@gmail.com writes:
Hi LilyPonders,
There are two broken links in the main page http://lilypond.org/
In the very beginning, under LilyPond 2.17.95 released! November 3,
2013, there are links to Updating files with
2013/11/14 David Kastrup d...@gnu.org:
In the very beginning, under LilyPond 2.17.95 released! November 3,
2013, there are links to Updating files with convert-ly and Bug
reports. When clicking on either of them, my browser tells me 404
Not Found.
Ugh. That one's tricky as it apparently
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
Thank you Janek for explaining this..
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
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
Oh, and i forgot: thanks for the report, Gilberto!
Janek
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
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
Janek Warchoł wrote
Oh, and i forgot: thanks for the report, Gilberto!
No problems at all. And next time I will report it directly to the bug squad
(I didn't know broken links would classify as such).
Take care,
Gilberto
--
View this message in context:
Hi Valentin,
since lilynet.net is dead, it would be good to transfer the archives
someplace else (i've heard that you do have them?). We could probably
add the articles to the lilypond blog, either as archival posts or
pages.
I don't know how much time i could spend on this, but i wouldn't want
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
On 10/20/2013 06:08 PM, Marcos Press wrote:
Hi! I'm full of questions today :D
In these case, I have three times the same last ligature and when I
repeat it a fourth time, it doesn't print the same before like you can
see at the attached file.
Why?
\version 2.17.28
one = \relative
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
41 matches
Mail list logo
