Alle 09:45, domenica 30 luglio 2006, Donald Axel ha scritto:
>This is an edited reposting of a bugreport. I am reposting so that
> it is not forgotten amidst a long thread.
Thank you Donald, for confirming the bug and putting it in evidence!
Marc
Alle 01:51, giovedì 27 luglio 2006, Donald Axel ha scritto:
> I hope you get the point: friendly and positive mail-tone is
> essential for a mail-list cooperation. Do not assume that I
> do not want to understand your point. And excuse me if I am wrong,
> after all I (or others) could be helped to
Alle 00:11, mercoledì 26 luglio 2006, Donald Axel ha scritto:
> Don't be annoyed, you can get your money back if you want;-)
Of course you didn't get the point and don't want to. I only said I think the
program may lead to unwanted results.
I'm not annoyed by Lilypond, i'm only annoyed by answers
Alle 21:02, mercoledì 19 luglio 2006, hai scritto:
> Please read the section on "Automatic accidentals" in the manual.
>
>/Mats
"modern
This rule corresponds to the common practice in the 20th century. This rule
prints the same accidentals as default, but temporary accidentals also are
cance
I attach an image of the output. As you can see only the last note have
cautionary accidental, not the previous
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Look at the attached example, I'm using modern cautionary accidentals
Why is the cautionary accidental on the last note, and not on the previous
one?
This doesn't happen if you delete the first note.
sorry if the bug was solved after 2.8.0
% Lily was here -- automatically converted by /usr/bin/
> * If you report a release somewhere, please send a note to
> lilypond-devel to prevent double work.
did it in www.ziobudda.net
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Alle 09:48, mercoledì 22 marzo 2006, Marco Gusy ha scritto:
> (ignoring ties)
I meant ignoring slurs, ties are ok
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Alle 17:25, giovedì 23 marzo 2006, Mats Bengtsson ha scritto:
> Now I see what you have in mind. Still, using "_" to specify melismas
> directly in the lyrics does not currently in any way influence the way
> the notes are typeset and I suspect that there's quite much hacking involved
> to make it
Alle 13:09, giovedì 23 marzo 2006, Mats Bengtsson ha scritto:
> If you want the beaming to be determined based on the
> syllables,
> then LilyPond needs some other method to figure out the duration of each
> syllable.
I meant that the method to deterine syllable duration in lyrics is already
im
Alle 13:09, giovedì 23 marzo 2006, Mats Bengtsson ha scritto:
> My point is that if you want LilyPond to break a beam whenever there is
> a new
> syllable, then it has to know how long each syllable is. If you use
> \lyricsto, then
> LilyPond figures out the duration of each syllable based on inf
Alle 21:34, mercoledì 22 marzo 2006, hai scritto:
> I don't really understand what you mean. If you don't want
> any connection between the lyrics and the notes, just skip
> \lyricsto and specify the duration of each syllable. If you want
> information from the lyrics to affect the notes, then you
Alle 15:16, venerdì 17 marzo 2006, Marco Gusy ha scritto:
> >
> > By default, LilyPond supports the opposite, namely that when you
> > use \lyricsto it interprets all manually inserted beams as melismas and
> > only attach one syllable to each beam.
>
> But the
>
> By default, LilyPond supports the opposite, namely that when you
> use \lyricsto it interprets all manually inserted beams as melismas and
> only attach one syllable to each beam.
But there's an issue: a melisma isn't always entirely tied in a beam (look at
the example in my previous post,
Hi, I would like to hear what you think about lilypond and beaming in vocal
music.
I'm quite sure it's common in traditional engraving to beam together only
notes of a melisma. The rule is: two syllabes never are beamed together. I
attach a picture as an example. This is Bach Magnificat, the "M
Alle 23:09, lunedì 26 settembre 2005, Han-Wen Nienhuys ha scritto:
> I'm discussing further microtonal extensions, with a double bass player
> from NY, who specifically needs support for Turkish music, where
> alterations are measured in 9ths of a whole tone. I believe they're
> called komas.
(ver
et similar)
-how to install fonts/ where lilypond looks for fonts
would be great.
This because many users don't have a deep knowledge of lilypond and can't
figure out how to do this using lilypond reference section.
Marco Gusy
___
lily
Here is a working ebuild
jusage:
cp lilypond-2.5.20.ebuild /usr/portage/media-sound/lilypond
cd /usr/portage/media-sound/lilypond
ebuild lilypond-2.5.20.ebuild digest
emerge lilypond
Don't know why... it complained me once about bad digest... if this happens
repeat last two steps
Happy compili
Alle 11:32, lunedì 18 aprile 2005, Mats Bengtsson ha scritto:
> it's a pity that Gentoo lists 2.5.2 as the latest.
Gentoo is a great updated distro, lilypond maintainer should relase ebuilds
more often.
Marco
___
lilypond-devel mailing list
lilypond
Alle 06:13, domenica 7 novembre 2004, J L ha scritto:
> I don't know anything about Lilypond's code, but was just wondering how
> much/whether Lilypond 2.4.x still uses TeX for typesetting of text on
> scores?
Yes it does, but there is a plan to have direct .ps output.. see "battle-plan
for 2.5 d
Alle 01:28, sabato 30 ottobre 2004, Han-Wen Nienhuys ha scritto:
> sorry, was in a grumpy mood. I've committed a fix, no promises that
> it works, though.
It's easy at 00:32 am ;-)
Thanks, i'll check in next release
___
lilypond-devel mailing list
[E
Alle 22:48, venerdì 29 ottobre 2004, Han-Wen Nienhuys ha scritto:
> > Is this bug fixed in latest version?
>
> Yes. I've added a note that this is not supported.
Ouch!
I think autocompletion is very useful when writing renaissance polyphony.
Often that music have accents every two or three beats
Alle 22:22, venerdì 15 ottobre 2004, Marco Gusy ha scritto:
> Hi all,
> in my example if I rip off the
>
> \with { \remove "Note_heads_engraver"
>\consists "Completion_heads_engraver" }
>
> lyrics is placed correctly, otherwise every note of the system
Midi2ly creates files with \notes command (not used anymore, right?)
Marco
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Midi2ly creates files with \notes command (not used anymore, right?)
Marco
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I think it's a bug, i wish i didn't make any syntax mistake in my input
Marco Gusy
<>
\header {
title = "Maria Magdalene"
composer = "Andrea Gabrieli"
}
\version "2.3.18"
#(se
I think it's a bug, i wish i didn't make any syntax mistake in my input
Marco Gusy
<>
\header {
title = "Maria Magdalene"
composer = "Andrea Gabrieli"
}
\version "2.3.18"
#(se
Alle 23:38, giovedì 20 maggio 2004, Edward Sanford Sutton, III ha scritto:
> http://mail.gnu.org/archive/html/lilypond-user/2004-04/msg00039.html
> and
> http://mail.gnu.org/archive/html/lilypond-user/2004-04/msg00040.html
> should make for some quick reading material for you; its recent too.
Ops
One feature I always looked for in a score program was colored notes
(unsuccesfully, of course).
It seems a stupid feature, but I think it could be very useful in fugues
studying: with this technique you could highlight subject, answers,
countersubjects. Do you think this is possible to impleme
Alle 21:48, mercoledì 31 marzo 2004, hai scritto:
> It seems there is no melisma in this reg. test
> http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1611551125.ly
>
> I mean the syllable extender line shouldn't it be "bla bla___ bla"?
Sorry for repating me in this post, but I would
It seems there is no melisma in this reg. test
http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1611551125.ly
I mean the syllable extender line shouldn't it be "bla bla___ bla"?
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mai
Alle 23:37, mercoledì 24 marzo 2004, Erik Sandberg ha scritto:
> There are problems with this setup: your .ly files will not be compatible
> with future lilypond versions. If Lilypond will change its autobeaming
> code, and you try to use your old file with the new lilypond, then the
> lyrics may b
Alle 23:37, mercoledì 24 marzo 2004, Erik Sandberg ha scritto:
> This might be true for the music you are typesetting, but there is other
> music which uses different rules. Much of the vocal music I have typeset
> does not use beaming to indicate melisma, simply because it's easier to
> read beame
Alle 14:52, mercoledì 24 marzo 2004, hai scritto:
> As you yourself wrote in your previous email, beams are sometimes
> used instead of slurs to indicate melismas. In that case, it's likely
> that the automatic beams often don't give the desired melismas.
I think they should always do. Look at the
I noticed that lyricsto listens to manual beams in lyrics-melisma-beam.ly
regression test. Why only manual ones?
By the way, there isn't the melisma in that example...
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listin
Hi, I think /addlyrics behavior should be revisited.
Currently (correct me if i'm worng) it follows only slurs to skip syllables.
The right behavior should be this:
if note duration <= eight (notes with possible beaming):
follow beaming: commonly two syllables are NEVER tied in a beam
I agree, when notes exit form penthagram staccato should be nearer (beware
when stem direction is forced outside)
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1485554506.ly
Same as subject... only a bug report
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
% In the second note from the right ( a-. ) the staccato dot collides with
% rows extension (dash)
\version "2.1.26"
\paper {
linewidth = 200\pt
}
\score {
\context Staff = violino { #(set-accidental-style 'modern)
\notes \relative c''' {
\overr
I have the same problem. Slurs collide with articulation marks. I posted a
message like yours a couple of weeks ago and I had no answer.
Maybe this problem is difficult to solve without manual hacks and developers
are busy to solve problems with higer priority.
We'll wait.. they did such a great
40 matches
Mail list logo
