Re: Programming error message
I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? Yes, thanks. I assume that it is not possible to add the offending text string to the warning message since a Pango warning is not visible to lilypond... Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
re: problem with textspan for controlled aleatorism
Dear community,
I think the snippet of my last example was too large, so probably nobody
could see the basic problem that is:
How can I have a textspanner that ends with an arrow over a line break?
Here is a much shorter snipper to illustrate my problem:
\version 2.12.2
\relative c'' {
\override TextSpanner #'bound-padding = #1.0
\override TextSpanner #'style = #'line
\override TextSpanner #'(bound-details right arrow) = ##t
\override TextSpanner #'bound-details #'left-broken #'text = ##f
\override TextSpanner #'bound-details #'right-broken #'text = ##f
\override TextSpanner #'(bound-details left text) = #fof
\override TextSpanner #'(bound-details right text) = #gag
\override TextSpanner #'(bound-details right padding) = #0.6
\override TextSpanner #'(bound-details right stencil-align-dir-y) =
#CENTER
\override TextSpanner #'(bound-details left stencil-align-dir-y) = #CENTER
a8\startTextSpan gis a4 b b, \break
g'4 c\stopTextSpan c2
}
**
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
On Sun, Feb 28, 2010 at 09:36:34AM +0100, Werner LEMBERG wrote: Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. This would certainly cut down on the number of questions asking how do I write an accented character?. OTOH, it might prompt confusion about how to save files in utf-8 in all sorts of editors, but this can be dealt with in the newbie documentation. I think such a checker would be a good idea. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange message with autochange
2010/2/28 James Bailey derhindem...@googlemail.com: The only problem I have with this is that I don't think that manual staff changes are supposed to work with autochange. That's what I thought too. But with a further look at the doc one can see, under Changing staff automatically (autochange): If additional control is needed over the individual staves, they can be created manually with the names up and down. The \autochange command will then switch its voice between the existing staves. So, according to the doc, it should be possible to mix automatic and manual staff changes. Or this sentence should be more explicit about what is implied with additional control... I could force things to work, but the known issues and warnings says that if you want high quality output, staff switches should be specified manually. From what I understand it is just because The staff switches may not end up in optimal places (listen, /with the automatic behaviour/). But if you can mix manual and automatic, then you can get over it. And yeah, I realize that for your 500 page fugue that sucks, but it's as easy as defining a variable, csu = \change Staff = up, and then using that variable when you want to have a staff change, \csu. According to the doc: The autochanger switches on the basis of the pitch (middle C is the turning point), and __it looks ahead **skipping over rests** to switch in advance__ So George_, your bug seems to be a side effect of this rest skipping functionality. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with textspan for controlled aleatorism
When built with 2.13.13 your example does put an arrow on the
TextSpanner at the line break...
Nick
On 28/02/10 19:55, Stefan Thomas wrote:
Dear community,
I think the snippet of my last example was too large, so probably
nobody could see the basic problem that is:
How can I have a textspanner that ends with an arrow over a line break?
Here is a much shorter snipper to illustrate my problem:
\version 2.12.2
\relative c'' {
\override TextSpanner #'bound-padding = #1.0
\override TextSpanner #'style = #'line
\override TextSpanner #'(bound-details right arrow) = ##t
\override TextSpanner #'bound-details #'left-broken #'text = ##f
\override TextSpanner #'bound-details #'right-broken #'text = ##f
\override TextSpanner #'(bound-details left text) = #fof
\override TextSpanner #'(bound-details right text) = #gag
\override TextSpanner #'(bound-details right padding) = #0.6
\override TextSpanner #'(bound-details right stencil-align-dir-y) =
#CENTER
\override TextSpanner #'(bound-details left stencil-align-dir-y) =
#CENTER
a8\startTextSpan gis a4 b b, \break
g'4 c\stopTextSpan c2
}
attachment: test.preview.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: re: problem with textspan for controlled aleatorism
kontrapunktstefan wrote: Dear community, I think the snippet of my last example was too large, so probably nobody could see the basic problem that is: How can I have a textspanner that ends with an arrow over a line break? your example already shows an arrow at the break! you can toggle the behavior of the text spanner at breaks with \override TextSpanner #'(bound-details right-broken arrow) = ##f i would recommend to always use the same syntactic pattern (which you did for the other items)! -- View this message in context: http://old.nabble.com/problem-with-textspan-for-controlled-aleatorism-tp27726210p27734216.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Staff reappearance callback?
Hi all, On 27/02/10 22:24, Reinhold Kainhofer wrote: Am Samstag, 27. Februar 2010 18:45:26 schrieb Kieren MacMillan: Hi Michael, It looks like break-related items of all sorts, including break-visibility, should have more than the 3 categories of before break, after break, and no break. Then might should distinguish levels of break, including staff reappearance and page break. Excellent point! We should list all possibilities: 1. before line break 2. after line break 3. before page break 4. after page break 5. before staff reappearance 6. after staff reappearance 7. Before staff disappearance (in harakiri staves) Given that all the other states appear to be on/off, doesn't it imply there should be this one 8. After staff disappearance (i.e. the staff is currently being suppressed). It's probably no practical use, but you may need it for completeness if you want to do a what-state-is-the-staff-currently-in type enquiry in the code. Cheers, Ian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange message with autochange
On 28.02.2010, at 10:56, Xavier Scheuer wrote: 2010/2/28 James Bailey derhindem...@googlemail.com: The only problem I have with this is that I don't think that manual staff changes are supposed to work with autochange. … So, according to the doc, it should be possible to mix automatic and manual staff changes. Or this sentence should be more explicit about what is implied with additional control... I think the additional control is actually controlling things that belong to the staff engraver. A more descriptive explanation wouldn't hurt. From what I understand it is just because The staff switches may not end up in optimal places (listen, /with the automatic behaviour/). But if you can mix manual and automatic, then you can get over it. I'm still not convinced that the autochanger was ever meant to be mixed with the manual changer. It seems that, if anything, the bug is that it's possible to have manual staff changes whilst using the autochanger. … The autochanger switches on the basis of the pitch (middle C is the turning point), and __it looks ahead **skipping over rests** to switch in advance__ So George_, your bug seems to be a side effect of this rest skipping functionality. I actually wouldn't call that a bug. I would call it the intended behavior. The autochanger looks to where it will put the next note, then places the previous rest on the same staff. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange message with autochange
On 28.02.2010, at 10:56, Xavier Scheuer wrote: 2010/2/28 James Bailey derhindem...@googlemail.com: The only problem I have with this is that I don't think that manual staff changes are supposed to work with autochange. … So, according to the doc, it should be possible to mix automatic and manual staff changes. Or this sentence should be more explicit about what is implied with additional control... I think the additional control is actually controlling things that belong to the staff engraver. A more descriptive explanation wouldn't hurt. From what I understand it is just because The staff switches may not end up in optimal places (listen, /with the automatic behaviour/). But if you can mix manual and automatic, then you can get over it. I'm still not convinced that the autochanger was ever meant to be mixed with the manual changer. It seems that, if anything, the bug is that it's possible to have manual staff changes whilst using the autochanger. … The autochanger switches on the basis of the pitch (middle C is the turning point), and __it looks ahead **skipping over rests** to switch in advance__ So George_, your bug seems to be a side effect of this rest skipping functionality. I actually wouldn't call that a bug. I would call it the intended behavior. The autochanger looks to where it will put the next note, then places the previous rest on the same staff. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Werner Icking Music Archive
Some news I thought to share here. The Werner Icking Music Archive has closed its doors (for good?). http://icking-music-archive.org/index.php -- mke ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
On Feb 28, 2010, at 1:56 AM, Patrick McCarty wrote: On 2010-02-27, Werner LEMBERG wrote: I don't see any non-ASCII characters in my file. Oh, I take that back now that I scrutinize closer... I have © in the input file. Well, that's easy to get rid of. And doing so eliminates the glyph complaint from Lilypond. Wow, eight or so complaints from one character! Any chance to add to the warning message a few words like This error most likely happens if you are using the wrong input encoding. Are you using UTF-8 encoding for your input file? IMHO there are too many questions on this list w.r.t. this warning message. I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? I haven't used 2.13 yet but I think that would be an improvement. It's nice when the error warnings provide interpretable information to the end user; usually these are written to be understandable just by the developers. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
A new LilyPond Report...
Greetings everyone, as some of the Elders in our community may remember, a legend says that there was a time, once, where the LilyPond community had a nice and fluffy newsletter called The LilyPond Report. Well, let's make this legend real (again)! (again.) (Again.) As you may remember, a call for submissions has been issued a few weeks ago, but hasn't received much success. I guess everybody here was to busy on silly useless stuff like writing patches or fixing bugs. Well, your loss guys: you've missed your only chance to get rich and famous once I'll have littered the website with ads :-) Now for the hors-d'œuvre : Yay, the Report is back, with a new team! It has been said that two heads are better than one — does it apply to newsletters as well? Read on and let us know! In this issue we’ll talk about websites and poetry, frogs and bugs, not to mention an extensive review of the Frescobaldi editor! Read the full issue on: http://news.lilynet.net/The-LilyPond-Report-17 From now on the Report will be published on a two-monthly basis. Which means you have, oh, about eight weeks to send us your contributions for the next issue. Looking forward to hearing from you guys! :-) Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 1.0.2 released
On Thu, Feb 18, 2010 at 9:25 AM, Wilbert Berendsen lily...@xs4all.nl wrote: Frescobaldi 1.0.2 has been released, fixing issues that arose when using Frescobaldi with KDE 4.4 and SIP 4.10. Greetings Wilbert, here's a (long-ish) review of Fresco 1.0.2: http://news.lilynet.net/The-LilyPond-Report-17#outil_sommaire_4 Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
On 2010-02-28, Werner LEMBERG wrote: I neglected to mention that in recent 2.13 versions, the warning messages for invalid character encoding look like this: (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() These warnings are generated by Pango. Is this an improvement? Yes, thanks. I assume that it is not possible to add the offending text string to the warning message since a Pango warning is not visible to lilypond... Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. It would be very simple to check for invalid UTF-8, since we can use GLib's g_utf_validate() function. In fact, Pango uses this same function in pango_layout_set_text(). Unfortunately, it would be much more complicated (I think) to output the offending string, since we would have to convert an arbitrarily encoded string to UTF-8, and then display it along with the warning/error. And this assumes we are dealing with a UTF-8 locale. What if we output a message like this instead: warning: invalid UTF-8 string found at row 3, column 10 I think this would be easier to implement. Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
separating music and tablature information
Hi all, in order to achieve different guitar tablature editions of the same piece of music I experimented with ghost voices consisting of spacer rests in combination with tablature information. Unfortunately it doesn't seem to be possible to use spacer rests in chord constructs such as s s s. In many cases I can use 's' instead and define a minimum Fret but some chords in higher playing positions contain open strings such as a\5 c'\3 b\2 e'\1. In this case it would be helpful to be able to use s\5 s\3 s\2 s\1 in a ghost voice and a c' b e' in the main voice to keep the music and tablature informations in separate voices. As a workaround I could use a\5 c'\3 b\2 e'\1 in the ghost voice and a c' b e' in combination with \once \override TabNoteHead #'stencil = ##f in the main voice because otherwise the string number indications in the ghost voice interfere with the automatic string calculation in the main voice. But then the ghost voice also contains some note names and durations which I wanted to avoid. Is there a more elegant solution to this problem? Thanks for any hint! patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
It would be very simple to check for invalid UTF-8, since we can use GLib's g_utf_validate() function. In fact, Pango uses this same function in pango_layout_set_text(). Good to know. What if we output a message like this instead: warning: invalid UTF-8 string found at row 3, column 10 This is probably even better than outputting the problematic string. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics across multi-voice sections
See the thread here. http://lists.gnu.org/archive/html/lilypond-user/
2009-02/msg00877.html
On 28.02.2010, at 22:46, Alberto Simões wrote:
Hello
I have a music where in some places the voice splits, like:
{ g2 ~ g8 } \\ { s8 e8[ dis d] cis }
I was trying to make lyrics align with the top voice of these splits.
I tried to use:
{ \voiceOne g2 ~ g8 } \\ { s8 e8[ dis d] cis }
but it is not working.
I think I asked this before, but I can't find any similar thing in all
my musics. So, sorry to (probably) repeat the question.
Cheers
Alberto
--
Alberto Simões
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics across multi-voice sections
2010/2/28 Alberto Simões al...@alfarrabio.di.uminho.pt:
Hello
I have a music where in some places the voice splits, like:
{ g2 ~ g8 } \\ { s8 e8[ dis d] cis }
I was trying to make lyrics align with the top voice of these splits.
I tried to use:
{ \voiceOne g2 ~ g8 } \\ { s8 e8[ dis d] cis }
Hi,
Voices in a { ... } \\ { ... } structure are both different than
voices outside that structure.
You should either name you main, outside Voice 1 (because in the
{ ... } \\ { ... } structure first Voice is called 1,
second 2 and so on...).
Either use explicit instantiated Voices, like this :
{ \voiceOne g2 ~ g8 }
\new Voice = blabla { \voiceTwo s8 e8[ dis d] cis }
\oneVoice
The first { ... } that appears in a ... with instanciated Voices
(i.e. without \\) is considered as the continuation as the main
Voice outside the ... structure.
Hope it is clear,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics across multi-voice sections
Alberto == Alberto Simões al...@alfarrabio.di.uminho.pt writes:
Alberto Hello I have a music where in some places the voice splits,
Alberto like:
Alberto { g2 ~ g8 } \\ { s8 e8[ dis d] cis }
Alberto I was trying to make lyrics align with the top voice of these
Alberto splits. I tried to use:
You need to tell LilyPond which voice is which.
The \\ construct creates two new voices, neither of which is aligned
with your lyrics. What you probably want is something like this:
\context Voice = tune { a b c
\context Voice = tune { \voiceOne g2 ~ g8 }
\context Voice = alternate { \voiceTwo s8 e8[ dis d] cis }
\oneVoice a b c
}
\lyricsto tune \theWords
Grahame, this is such a FAQ thaqt we either need to add a section to
the LM in `voices and vocals', or modify the `I'm hearing voices'
section, or add an explicit `implicit voice instantiation with vocals'
section. Or some other solution?
If you tell me which you'd prefer I'll try to whip yup a patch this week.
--
Dr Peter Chubb peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
All things shall perish from under the sky/Music alone shall live, never to die
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics across multi-voice sections
No worries. clearly you use this once a year. I just happen to have
all my emails easily searchable. If it makes you feel any better,
there was a more recent thread about this on the only 3 weeks ago.
You're not the only one.
http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00289.html
On 28.02.2010, at 22:58, Alberto Simões wrote:
/me blushes.
Thank you!
On 28/02/2010 21:59, James Bailey wrote:
See the thread
here. http://lists.gnu.org/archive/html/lilypond-user/2009-02/
msg00877.html
On 28.02.2010, at 22:46, Alberto Simões wrote:
Hello
I have a music where in some places the voice splits, like:
{ g2 ~ g8 } \\ { s8 e8[ dis d] cis }
I was trying to make lyrics align with the top voice of these
splits.
I tried to use:
{ \voiceOne g2 ~ g8 } \\ { s8 e8[ dis d] cis }
but it is not working.
I think I asked this before, but I can't find any similar thing
in all
my musics. So, sorry to (probably) repeat the question.
Cheers
Alberto
--
Alberto Simões
___
lilypond-user mailing list
lilypond-user@gnu.org mailto:lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Alberto Simões
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Programming error message
On Sun, Feb 28, 2010 at 1:13 PM, Tim McNamara tim...@bitstream.net wrote: On Feb 28, 2010, at 12:54 PM, Patrick McCarty wrote: What if we output a message like this instead: warning: invalid UTF-8 string found at row 3, column 10 I think this would be easier to implement. From the relatively naive user perspective, this would be very helpful. Since Emacs can be set to show the line the cursor is in, this would make tracking down the cause of the problem much easier. Thanks for your feedback. This is a little more involved than I was anticipating, so I've added a tracker issue: http://code.google.com/p/lilypond/issues/detail?id=1023 -Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics across multi-voice sections
2010/2/28 Peter Chubb lily.u...@chubb.wattle.id.au:
Grahame, this is such a FAQ thaqt we either need to add a section to
the LM in `voices and vocals', or modify the `I'm hearing voices'
section, or add an explicit `implicit voice instantiation with vocals'
section. Or some other solution?
Or wait that Kieren (or another lily dev) change the \\ construct
so that it behave like a shortcut for
% mainVoice
{ ... } % continuation of the main voice
\new Voice = mainVoiceName2 { % the name of the voice is a
personal suggestion
...
}
\oneVoice
;-)
There used to be a warning that said voices in a \\ structure
are different from voices outside and thus forbid slurs, hairpins, ...
to continue from voice outside the strucure to a voice inside.
But I must admit I couldn't find that warning again in the doc.
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange message with autochange
I could try that. But would it be possible to request a feature that allows
manual and automatic staff changes at the same time?
Thanks
George
James Bailey-4 wrote:
The only problem I have with this is that I don't think that manual
staff changes are supposed to work with autochange. I could force
things to work, but the known issues and warnings says that if you
want high quality output, staff switches should be specified
manually. And yeah, I realize that for your 500 page fugue that
sucks, but it's as easy as defining a variable,
csu = \change Staff = up,
and then using that variable when you want to have a staff change, \csu.
On 27.02.2010, at 23:08, George_ wrote:
Okay, I've put the snippet in the quote. Basically the first change
shows the
\change not working; the second one shows the \change working.
Regardless,
both produce errors in the log.
\version 2.13.7
\new PianoStaff {
\new Staff = up {
\autochange \relative c' {
\change Staff = up r16 b e g
\change Staff = down fis c
b a g
}
}
}
\change Staff = doesn't seem to apply to rests, even when in
written
as b16\rest instead of just r16. I'm not sure what other
information should
be put on, there's the rest of this thread, or just ask me if you
need more
info.
Thanks
George
--
View this message in context: http://old.nabble.com/Strange-message-
with-autochange-tp27710824p27731384.html
Sent from the Gnu - Lilypond - User mailing list archive at
Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
View this message in context:
http://old.nabble.com/Strange-message-with-autochange-tp27710824p27738547.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 1.0.2 released
Op zondag 28 februari 2010 schreef Valentin: here's a (long-ish) review of Fresco 1.0.2: http://news.lilynet.net/The-LilyPond-Report-17#outil_sommaire_4 Very nice! Thanks!! couple little notes: - you can browse locally installed docs with the built-in LilyPond Documentation Browser. Frescobaldi even tries to find locally installed documentation in /usr/share/doc, but if that fails, it just loads http://lilypond.org/doc instead. You can configure the default URL for the documentation in Settings-Paths (you can enter local or remote urls). - in the dev tree[1] of Frescobaldi setting keyboard shortcuts to articulations is already supported! [1] see http://frescobaldi.org/development - lilypond-kde4 does not contain a Kate plugin (it's just an automatic textedit:// url handler, an indent script and some icons). The package became unnecessary as textedit:// urls are handled by the Okular PDF component since KDE 4.2. Many thanks again! Wilbert Berendsen -- Frescobaldi, LilyPond editor for KDE: http://www.frescobaldi.org/ Nederlands LilyPond forum: http://www.lilypondforum.nl/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book not working after installing Python 3
Graham Percival wrote: By the way, I estimate that switching all our scripts to python 3.x would take 40 hours, with an additional 20 hours required to make GUB include python 3.x in the installers. I'm not much of a Pythonist alas, never mind the complexity of teaching myself properly how the internals of LP work; but it might be worth adding something to the documentation -- I guess the Windows install instructions? -- emphasising that Lilypond should be run with Python 2.4 or later, and NOT with Python 3.x (and perhaps explaining how people who need Python 3 can run/use it effectively without disturbing Lilypond). If that sounds good, where in the docs would you like it? Best wishes, -- Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Werner Icking Music Archive
On Sun, Feb 28, 2010 at 08:33:22AM -0600, M.E. wrote: Some news I thought to share here. The Werner Icking Music Archive has closed its doors (for good?). http://icking-music-archive.org/index.php Too much traffic. http://www.daimi.au.dk/~reccmo/usage/ I think there're some ongoing discussions on the relevant lists to move the archive somewhere else. Ciao, Kili -- Beware of the old, for they don't have anything left to loose. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange message with autochange
James Bailey-4 wrote: I'm still not convinced that the autochanger was ever meant to be mixed with the manual changer. It seems that, if anything, the bug is that it's possible to have manual staff changes whilst using the autochanger. I disagree. Once again citing my hypothetical 500-bar fugue, it seems incomprehensible to me that there should not be a compromise between the autochange function and manual staff changes. It just blows my mind that something so feature-rich as Lilypond should skimp on such a simple and intuitively straighforward idea. I actually wouldn't call that a bug. I would call it the intended behavior. The autochanger looks to where it will put the next note, then places the previous rest on the same staff. Even when it resists all efforts to move it to where I want it to go? On that note (no pun intended) using a spacer rest (r16*1/2 s16*1/2) screws up the barcheck for the rest of the piece. Xavier Scheuer wrote: From what I understand it is just because The staff switches may not end up in optimal places (listen, /with the automatic behaviour/). But if you can mix manual and automatic, then you can get over it. Agreed. The impression the docs give is certainly not one where I'm clear on the fact that either I leave it completely up to \autochange, or the staff changes are completely specified manually by me. And while both extremes may be useful in the short snippets that are in the docs, they are much less practical for the long, multivoice pieces that many Lilypond users would like to engrave. -- View this message in context: http://old.nabble.com/Strange-message-with-autochange-tp27710824p27740196.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
