Re: LilyPond Downloads broken?
You are correct on both counts. The SSH key wasn't copied over to the new server, and that's been a blessing since the account was compromised. Can you point the download link to lilypond.org directly? Bandwidth prices have gone down in the last 10 years, so I think we should be fine. On Wed, Mar 7, 2018 at 4:11 PM, Phil Holmes <m...@philholmes.net> wrote: > The lack of the latest files on the linuxaudio site isn't something I can > fix. My understanding is that the situation used to be that lilypond.org > used to run a cron job that scp'ed the binaries to linuxaudio. However, > this stopped working when a) Han-Wen changed the hosting of lilypond.org or > b) there was a problem with linuxaudio and it had to be rebuilt. I assume > that there is not the correct certificate on the new lilypond.org system. > > The cron job was set up by Jan, and the login I use has no access to it. > > The simplest solution might be to change to simply pointing all downloads to > the lilypond.org server. I think we didn't do this in the past to lower the > load on the server, but the new infrastructure might not see that as a > problem. > > Copied to Jan and Han-Wen for their thoughts. > > -- > Phil Holmes > > > > - Original Message - > From: Urs Liska > To: lilypond-u...@gnu.org ; bug-lilypond > Sent: Wednesday, March 07, 2018 3:00 PM > Subject: Re: LilyPond Downloads broken? > > (Cross-posting to bug-lilypond) > > > Am 07.02.2018 um 16:22 schrieb Phil Holmes: > > Available from http://lilypond.org/downloads/binaries/ currently. > > > Any information on how long this situation will last? I think we should > consider updating the website, even if it's temporary. > > Urs > > > > ___________ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
morgenlied stafflet snafu
I'm at commit 2728f57934651f8de7ae99064305b72d27990932 When I run input/regression/morgenlied through lilypond, I get a small bit of staff that shouldnt be there, -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
broken clef glyph
Hi there, my clef glyph looks broken (see attachment). I am on * commit 3c6b011ceedc9f3eb7908acac19cf7fe7bf54f5c (from Aug 25) * Fedora 19, which has MetaPost 1.802 (TeX Live 2013), on x86_64 anyone ideas where to find the cause? -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen attachment: brokenclef.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Current master non-deterministic
On Sun, Sep 16, 2012 at 5:06 AM, David Kastrup d...@gnu.org wrote: in order to a stable O(n lg n) uniq for which the structure of the final list does not depend on the memory order of the original elements. This certainly sounds like a better solution. However, rethinking this, it seems like a solution for not seeing the symptoms of a problem: we stabilize results artificially. rather than artificial stabilizing, you could explicitly destabilize them, so problems become more apparent. Insert from a random starting point into the hash table, and then serialize the hash table. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Shall we change the flags?
On Thu, Aug 9, 2012 at 7:59 AM, Karol Majewski karol.majew...@gmail.com wrote: Dear LilyPond friends! I have to say something that keeps me awake at night: Current LilyPond flags look bad! They look so bad that I have to use straight flags instead. The big problem for me is that flags on a single note have different shapes. The lower flag is wider than flag above. I talked to Janek Warchoł and he said that this output is intentional and explained to me everything. However, those christmas-tree-flags (as I call them now) still make me sick, because they look inaccurate. **Does anyone have the same feeling? And please take look at the atachment - this is how perfect flags should look like to me. In your example, the top hook looks larger than the other ones, especially in 32, 64 and 128, because it has nothing above it. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: random crashes in lilypond 2.14.2 on some Rosegarden, output
On Sat, Aug 4, 2012 at 1:17 PM, David Monniaux david.monni...@free.fr wrote: On 08/02/2012 06:00 PM, bug-lilypond-requ...@gnu.org wrote: How did you install LilyPond? Did you install a precompiled binary from lilypond.org, a package from your distribution, or did you compile yourself? Self-compiled with gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) Of even more importance is that you seem to be running a low-latency kernel (it seems so from -rt34 release tag). Which GNU/Linux distribution release do you use exactly? What is your hardware (x86_64) ? x86 Ubuntu 11.10 The kernel is also self-compiled. Could you get more information on the crash, like a stack trace or a core dump? Running lilypond under gdb seems to reliably prevent the crash. By running it from outside of gdb and reloading the core dump shows the following backtrace: #0 0xb77d0424 in __kernel_vsyscall () #1 0xb7185c8f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb71892b5 in __GI_abort () at abort.c:92 #3 0xb774df1c in scm_ithrow () from /usr/lib/libguile.so.17 #4 0xb76e1ac4 in scm_error_scm () from /usr/lib/libguile.so.17 #5 0xb76e1b61 in scm_error () from /usr/lib/libguile.so.17 #6 0xb76e1e6a in scm_wrong_type_arg () from /usr/lib/libguile.so.17 #7 0xb7714d9a in scm_sum () from /usr/lib/libguile.so.17 #8 0xb76f4190 in scm_gc_protect_object () from /usr/lib/libguile.so.17 This looks like GUILE problem. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond fails to compile music on mac, segfaults on Linux
On Thu, May 24, 2012 at 4:03 PM, Graham Percival gra...@percival-music.ca wrote: On Thu, May 24, 2012 at 02:18:54PM -0400, Ralph Palmer wrote: I need some help here. The voice structure is confusing to me. pianoRH looks like it might work, although it looks weird to me. pianoLH looks, The whole report looks like a non-Tiny example, so politely reject it and politely point the submitter at our bug reporting guidelines. For understanding segmentation faults, the size of the example is usually irrelevant. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
On Sat, Sep 3, 2011 at 12:05 PM, lilyp...@googlecode.com wrote: Comment #7 on issue 1858 by reinhold...@gmail.com: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 That commit turned on debugging in guile again... So the question now is, what was the case before Ian turned debugging off in february with commit 52bea08ef73a55ee? Guile debugging store a lot more information about the Scheme source code, so it could easily explain increased memory usage. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1618 in lilypond: unpredictable placement of rests
You can run valgrind on lilypond. You just need to disable the
warnings regarding garbage collection.
On Sun, Apr 17, 2011 at 5:24 AM, lilyp...@googlecode.com wrote:
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1618 by percival.music.ca: unpredictable placement of rests
http://code.google.com/p/lilypond/issues/detail?id=1618
This is split from issue 1609 (that issue was specifically about the problem
we saw in partcombine-midi.ly)
As the examples below illustrate, placement of such rests still changes
unpredictably. The score in example 2 produces different output with the
two command lines
lilypond test.ly
lilypond test.ly test.ly
while version 2.12.3 produces the same output in either case. Both versions
produce a warning too many colliding rests. See also issue 1547 and issue
384.
The variation in position of the rests appeared somewhere between 2.13.48
and .54
The completion- engravers are not essential, it is simply the fact that
LilyPond does not have a rule to place simultaneous rests with a note of
different durations (see issue 1547). Smaller example, which produces
different output depending on whether the file is alone on the command line
or second in a list of .ly files:
\version 2.12.3
\new Staff
\new Voice {
\voiceOne
r1 r1
}
\new Voice {
\voiceThree
c'2 e' g' b'
}
\new Voice {
\voiceTwo
r1 r1
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible regression in 2.13 series? no viable configuration warning
On Wed, Apr 20, 2011 at 4:56 AM, Valentin Villenave valen...@villenave.net wrote: The cross-staff beams look a bit odd (the first note has a really long stem). I'm surprised that there's problems as far back as 2.13.7, since the main beaming work was quite recent. Indeed. I suspect the vertical spacing (skyline and all) is at stake here, since in 2.12 the staves are printed further apart (and the beam slope is totally different). The message about viable configurations comes from the beam code which now takes the flat symbol into account. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: stemlength II
On Fri, Apr 15, 2011 at 7:30 AM, m...@apollinemike.com m...@apollinemike.com wrote: OK. http://code.google.com/p/lilypond/issues/detail?id=1613 I am testing a fix for this; it was an oversight of mine. Graham, this issue was exposed due to a (seemingly innocuous) one-line change by Mike. Can I ask that you branch off the 2.14 branch so the release candidate does not get disturbed by other one-liners with unintended effects? If you don't branch off a stable branch, 2.14 will never get finished. I agree - I think that if we branch off 2.14 after we fix the three remaining critical issues (all of which seem to have been recently introduced) and if everyone holds off on pushing new stuff for a bit (my MultiMeasureRest work, for example, won't make it into 2.14.0), we can still sit on it for a week or two before building it with GUB. During this incubation phase, we'd only apply patches that fix critical or high priority problems. The beauty of branching off is that nobody needs to hold off anything. You just continue to put stuff in master (2.15.0), and cherry-pick whatever needs to go to 2.14. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: stemlength II
On Thu, Apr 14, 2011 at 9:00 AM, Phil Holmes m...@philholmes.net wrote: could argue that lengthening a stem to avoid a collision that isn't a collision is a bug, but I wouldn't do so without Mike's input. Hm? A bug with an explanation and a workaround is still a bug as far as I can see. Mike's input may be needed in order to decide whether to OK. http://code.google.com/p/lilypond/issues/detail?id=1613 I am testing a fix for this; it was an oversight of mine. Graham, this issue was exposed due to a (seemingly innocuous) one-line change by Mike. Can I ask that you branch off the 2.14 branch so the release candidate does not get disturbed by other one-liners with unintended effects? If you don't branch off a stable branch, 2.14 will never get finished. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Nouveau projet et personne ressource
On Fri, Apr 8, 2011 at 10:56 AM, Valentin Villenave valen...@villenave.net wrote: Well, their financials are notoriously opaque, so I wouldn't be surprised if some money mysteriously gets lost in the process. There is a hilarious video by a belgian satire program, where they take on SABAM, the belgian society for collecting performance rights. article http://translate.google.com/translate?js=nprev=_thl=enie=UTF-8layout=2eotf=1sl=autotl=enu=http%3A%2F%2Fwww.gva.be%2Fnieuws%2Fmedia-en-cultuur%2Faid1011663%2Fbasta-sabam-maakt-facturen-voor-onbestaande-groepen.aspxact=url videos (dutch) http://www.een.be/programmas/basta/sabam-en-de-makro-artiesten Apparently, they have inspectors that actually go to people's houses when there are personal parties. They got back at them by organizing performances by Kimberly Clark (paper towel dispenser) and Kenwood (kitchen appliances). Shortly thereafter, SABAM got sued. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Simple bug report -- examples are out of date and require processing with the conversion script.
On Fri, Feb 11, 2011 at 3:23 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, Feb 11, 2011 at 11:34:00AM -0200, Han-Wen Nienhuys wrote: The examples have always been part of the /doc hierarchy By always, you mean until commit 4e92d8b035235815fc55f2fe76505ca3db0f890d which was on 2009-10-04, right? The important ones are still in the regression test directory - I think they could have a subdirectory of their own, btw. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.13.40 regtests
On Thu, Nov 25, 2010 at 12:45 PM, Phil Holmes m...@philholmes.net wrote: It wouldn't take me long to write a C# program (less than a day, I'd guess) that reproduced quite a lot of the regtest checker functionality and did a pixel-by-pixel check for image changes. I've done the latter bit in about 20 minutes on the figured bass png that started this discussion. The It would take me about 10 seconds; imagemagick has this functionality built in (the same one that is used to generate the current images of the regtest). http://www.imagemagick.org/script/compare.php?ImageMagick=cnagfba00ks4srknf1dt82ldo3 The reason I did not do it originally is that it moves the comparison farther away from lilypond itself and pixel-per-pixel changes are not calibrated for the size of the symbols: a large symbol moving place will generate a much higher difference score than a small score. It might have been a quicker way to get started with running comparison tests. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.13.40 regtests
On Fri, Nov 26, 2010 at 2:21 AM, Graham Percival gra...@percival-music.ca wrote: On Fri, Nov 26, 2010 at 02:15:22AM -0500, Han-Wen Nienhuys wrote: The reason I did not do it originally is that it moves the comparison farther away from lilypond itself and pixel-per-pixel changes are not calibrated for the size of the symbols: a large symbol moving place will generate a much higher difference score than a small score. It might have been a quicker way to get started with running comparison tests. True, but at the moment there's no way to catch problems due to ghostscript (or international fonts being installed / not being installed in GUB). Of course, hopefully GUB won't be changing all that often, but it _does_ happen. Would it be possible to have both kinds of regtest comparisons? Maybe not enabled in the usual make check, but adding a separate make pixelcheck or something like that? It should be trivial to add an imagemagick call to do pixel by pixel comparision to output-distance.py -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1067 in lilypond: Postfix syntax for repeats
Can we please not do this?
Syntax changes look cute, and in rare case even require little code,
but they are impossible to revert, since we'd be breaking user files.
This needs to be accompanied by a much more thorough analysis whether
this feature is worth the additional perl-esque syntax, all the
ensuing confusion between {c }*4, c*4 and c4*4, and the syntax
inconsistency (we don't have postfix music functions anywhere else).
Why dont we predefine a music function for this?
\R 4 {bla}
(perhaps \R #4 {..}) . With
{ .. }*4
users need to remember to insert a { before the repeated fragment
anyway, so postfix *4 really isnt any better than prefix \R 4.
On a more general note: can we stop the let's improve the syntax
discussions altogether? We've had them for over 10 years, they
generate a lot of heated bikeshedding discussions, and don't really
help anything, since they are fundamentally subjective.
If you are really interested in improving lilypond, improve some
collision algorithms so people require less manual tweaks.
On Fri, Apr 30, 2010 at 5:04 AM, lilyp...@googlecode.com wrote:
Status: Started
Owner: n.puttock
Labels: Type-Enhancement Priority-Medium Patch Syntax
New issue 1067 by v.villenave: Postfix syntax for repeats
http://code.google.com/p/lilypond/issues/detail?id=1067
Neil has posted an awesome patch that allows to have
{ music expression } * 4
instead of
\repeat unfold 4 { music expression }
http://lists.gnu.org/archive/html/lilypond-devel/2010-04/msg00467.html
We need to merge it and document the feature (and add a regtest). Then this
issue can be closed.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1067 in lilypond: Postfix syntax for repeats
On Fri, Apr 30, 2010 at 11:22 AM, Han-Wen Nienhuys hanw...@gmail.com wrote: On a more general note: can we stop the let's improve the syntax discussions altogether? We've had them for over 10 years, they generate a lot of heated bikeshedding discussions, and don't really help anything, since they are fundamentally subjective. If you are really interested in improving lilypond, improve some collision algorithms so people require less manual tweaks. On a related note: I am already expecting the discussions over comment syntax next. See also: http://www.haskell.org/haskellwiki/Wadlers_Law -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 838 in lilypond: Inconsistency in tests output size
On Sat, Mar 6, 2010 at 2:17 AM, lilyp...@googlecode.com wrote: I am not quite sure of the best solution. Maybe some of the interface of the Font_metric object could be changed, passing an Output_def object into text_stencil() so it can store any physical fonts loaded for this file. I have to think a bit more about this, but probably the whole font metric api could use some overhaul. It dates from the time that we used TeX, and all fonts had to be loaded explicitly by lilypond, while nowadays some fonts are loaded through Fontconfig/pango. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 838 in lilypond: Inconsistency in tests output size
On Wed, Mar 3, 2010 at 4:23 PM, lilyp...@googlecode.com wrote: Comment #8 on issue 838 by percival.music.ca: Inconsistency in tests output size http://code.google.com/p/lilypond/issues/detail?id=838 That is so weird. Do you have any clue why they put the (= (random 40) 1 in there? At some point we had code that figured out which font files were being used in a score, when outputting the .ps. See framework-ps.scm , look for load-fonts. It would be good to know why that stopped working. The idea was to not reload fonts for every .ly file, but we should have probably done profiling before going that complicated route. The 40 is just an arbitrary number, to force a garbage collect of loaded fonts. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Room to improvement for polyphonic rests
On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote: Rests are not centered with noteheads in other voices. This is intentional; only whole-measure rests should be centered. (Please provide scans of publications if you think otherwise) -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fixed MIME for images on tracker
Isnt it easier to just re-upload the old images? On Thu, Dec 17, 2009 at 7:52 PM, Patrick McCarty pnor...@gmail.com wrote: On Tue, Dec 15, 2009 at 12:57 PM, Reinhold Kainhofer reinh...@kainhofer.com wrote: Am Dienstag, 15. Dezember 2009 21:41:01 schrieb Patrick McCarty: It appears to be the age of the example. None of the images posted in 2006 display inline, for example. Yes, the cutoff date seems to be September 25 to 26, 2007. Images posted earlier are not displayed inline, later images are. I've posted a comment to that bug for the google support category, so maybe they can explain what is wrong or what we can do about it... Someone requested to open a new issue, so I reported it here: http://code.google.com/p/support/issues/detail?id=3425 Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: #852 - stop google from indexing old docs
On Wed, Dec 16, 2009 at 6:59 AM, Graham Percival gra...@percival-music.ca wrote: Disallow: /doc/v1.9/ Huh, I didn't reliaze we kept the old unstable directories around; they're not listed on http://lilypond.org/documentation anybody mind if I delete the unstable doc dirs? IIRC it is a symlink to the 2.0 documentation. We dont remove it to not break other people's links gratuitiously. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stem lenghts
On Mon, May 11, 2009 at 3:15 AM, Mark Polesky markpole...@yahoo.com wrote: And this is exactly the problem with the default LilyPond output - small white triangles. See the attachment in my previous post: http://lists.gnu.org/archive/html/bug-lilypond/2009-05/pngbNqzog15lv.png Perhaps we could add a patch to the beam-scoring algorithm that would penalize configurations that lead to small white triangles? Or if there's already one, increase the penalty? There is no code that penalizes for small white triangles on the inner stems. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stem lenghts
On Sun, May 10, 2009 at 5:56 PM, Mark Polesky markpole...@yahoo.com wrote: As far as implementing this, I have no idea. I don't know how LilyPond is set up to calculate these things, and I imagine making changes of this sort would be quite involved. I'll leave that to the developers. The rules in Ross' books are guidelines, and they certainly don't cover all the cases. LilyPond does not use a hardcoded set of rules; rather, it tries to score different configurations, and pick the one with the best scores. This is a technique that works much better than hardcoding different rules, but in some cases there are small divergences with the 'prescribed' quants. We even have a regtest for it, see input/regression/beam-quant-standard.ly It might be possible to tune the scoring parameters to copy Ross exactly, but probably some other configurations will fall over. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stem lenghts
On Sun, May 10, 2009 at 6:26 PM, Werner LEMBERG w...@gnu.org wrote: LilyPond does not use a hardcoded set of rules; rather, it tries to score different configurations, and pick the one with the best scores. This is a technique that works much better than hardcoding different rules, but in some cases there are small divergences with the 'prescribed' quants. We even have a regtest for it, see input/regression/beam-quant-standard.ly It might be possible to tune the scoring parameters to copy Ross exactly, but probably some other configurations will fall over. I can imagine that after the scoring there's a second pass to fine-tune the result, for example, to `snap' various parts of the beam to the staff lines where possible. No, that would not work; the snapped position was also scored and did not win, so in many cases there is something wrong with it. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stem lenghts
On Sun, May 10, 2009 at 6:44 PM, Mark Polesky markpole...@yahoo.com wrote: Han-Wen Nienhuys wrote: The rules in Ross' books are guidelines, and they certainly don't cover all the cases. Yes, but what about the too-short stem on the middle-line note: It could be that there is a bug; there is some logic to shorten stems in some cases (forced stem directions) that may be interfering here. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bus error with \bookpart
Can you verify that valgrind does not complain of your code? You'll need to silence GUILE GC related warnings. On Tue, Dec 9, 2008 at 6:36 PM, Nicolas Sceaux [EMAIL PROTECTED] wrote: BDM, I still can't reproduce, and can't see what's wrong in the backtrace. Does someone have an idea how I could reproduce it, maybe changing an optimization option? (I use -O2) -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: accidental shifts left as it nears a 2nd (interval)
Maybe we should increase the slope for the accidental skylines?
On Sun, Nov 9, 2008 at 6:18 AM, Mark Polesky [EMAIL PROTECTED] wrote:
accidental shifts left as it nears a 2nd (interval):
An accidental may move away from its note if there is
an interval of second nearby. The closer the second,
the further the accidental moves. This looks weird!
_
\version 2.11.63
\layout {
indent = #0
ragged-right = ##t
}
\relative {
g' a gis'! a b gis'! b c gis'! c d gis!
{
gis'! gis! gis! gis!
} \\ {
g, a a b b c c d
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Trojan Dropper TR/Dropper.Gen reported in guile.exe when installing on Windows
guile.exe is created on a Linux machine using cross-compilation. There is no way that it can be infected by anything. You need to complain with your a/v software vendor. On Sat, Oct 25, 2008 at 10:10 PM, Roberto Ordóñez [EMAIL PROTECTED] wrote: I'm not top posting. I just installed LilyPond 2.11.62-1 on Windows using the installer provided on your website (lilypond-2.11.62-1.mingw.exe). During the install, Avira AntiVir Premium reported TR/Dropper.Gen (a Trojan dropper) in guile.exe. Please check that out! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: undefined reference compile error in 2.11.60
This looks like a bug in LilyPond; it's not gcc's fault. On Fri, Sep 26, 2008 at 6:43 PM, Kilian A. Foth [EMAIL PROTECTED] wrote: Hello world, I can't seem to get lilypond 2.11.60 compiled with GCC 4.0.2 on Linux 2.6.13. The final linking step fails with ./out/axis-group-interface.o: In function `Axis_group_interface::relative_pure_height(Grob*, int, int)': /home/foth/src/lilypond-2.11.60/lily/axis-group-interface.cc:182: undefined reference to `Align_interface::has_interface(Grob*)' ./out/beam-quanting.o: In function `Beam::quanting(scm_unused_struct*, scm_unused_struct*)': /home/foth/src/lilypond-2.11.60/lily/beam-quanting.cc:190: undefined reference to `Align_interface::has_interface(Grob*)' -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: undefined reference compile error in 2.11.60
On Fri, Sep 26, 2008 at 6:43 PM, Kilian A. Foth [EMAIL PROTECTED] wrote:
I can't seem to get lilypond 2.11.60 compiled with GCC 4.0.2 on Linux 2.6.13.
The final linking step fails with
./out/axis-group-interface.o: In function
`Axis_group_interface::relative_pure_height(Grob*, int, int)':
/home/foth/src/lilypond-2.11.60/lily/axis-group-interface.cc:182: undefined
reference to `Align_interface::has_interface(Grob*)'
./out/beam-quanting.o: In function `Beam::quanting(scm_unused_struct*,
scm_unused_struct*)':
/home/foth/src/lilypond-2.11.60/lily/beam-quanting.cc:190: undefined
reference to `Align_interface::has_interface(Grob*)'
and seven more undefined references to symbols in the Align_interface
class. Do these functions exist somewhere other than the many object
files in lily/out/, or is my C++ version subtly incompatible?
align-interface.cc:
ADD_INTERFACE (Align_interface,
Order grobs from top to bottom, left to right, right to left
or bottom to top. For vertical alignment
grob-interface.hh
#define ADD_INTERFACE(cl, b, c) \
SCM cl::interface_symbol_; \
bool cl::has_interface (Grob *me) \
{ \
return me-internal_has_interface (interface_symbol_); \
} \
void cl ## _init_ifaces ()\
{ \
cl::interface_symbol_ = add_interface (#cl, b, c); \
} \
ADD_SCM_INIT_FUNC (cl ## ifaces, cl ## _init_ifaces);
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: markup override font selection not carried out
On Sun, Sep 28, 2008 at 7:51 AM, Didi Kanjahn [EMAIL PROTECTED] wrote: 3. Indeed the same font named 'Khmer Mondulkiri A' (as it should be for the rest of the world) instead of '.Mondulkiri A' produces the desired result. 4. The font with the period still worked as intended in Lilypond 2.10.33 I suspect we changed the fontconfig version (which does the font selection) since then. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in Unicode rendering
On Sun, Sep 28, 2008 at 8:34 AM, Didi Kanjahn [EMAIL PROTECTED] wrote: The rendering is actually done by pango. Can you verify whether the rendering looks correct in (for example) the Gedit of your system (which also uses pango)? The rendering is done with Pango? I'm using Windows XP. What happens there? It should use the same mechanism on Linux. The font is my own, I can mail it on request. Can you open a bug tracker issue and attach the font? Truth be said: I tried fixing a hebrew rendering issue some time ago, but failed, as it was very difficult for me to understand what was going wrong. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strict grace spacing is (still) broken
On Sun, Sep 28, 2008 at 6:17 PM, Zoltan Selyem [EMAIL PROTECTED] wrote: However, in Appendix B (B.13 Layout properties) the following is written about strict-grace-spacing: If set, grace notes are not spaced separately, but put before musical columns. I'm not sure about the meaning of a musical column, and The description of the property is incorrect. A musical columnt is the X-position corresponding to a point in time; clefs and time signature are on 'command columns' , notes on 'musical columns'. Each point time (including separate grace notes) has its own musical and command columns. strict-grace-spacing makes the musical columns for grace notes 'floating', ie. discoupled from the non-grace notes: first the normal notes are spaced, then the (musical columns of the) graces are put left of the musical columns for the main notes. Can someone update the documentation? thanks! by now I'm a bit confused about this strict-grace-spacing thing. I would assume that putting grace notes _on_ musical columns means that they should be aligned with other notes. Putting them _before_ musical columns might be what the latest version does. Maybe the current output is ok, maybe this is the intended behaviour. But in that case I don't understand the sentence in 1.2.6.1: ...to align with regular notes. Bye, Zoltan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: markup override font selection not carried out
On Sat, Sep 27, 2008 at 8:56 AM, Didi Kanjahn [EMAIL PROTECTED] wrote:
The font in the override is not used to render the text, but a default
font instead.
This worked fine in 2.6.5
es'2^\markup { \override #'(font-name . .Mondulkiri A) \fontsize #3
{ Bøw meRBI } }
}}
As I understand it, this is a font you created. I haven't been able to
find it though. The web points me to
http://projects.thedanielmay.com/khmerfonts/unicode.htm
which does not exist
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 679 in lilypond: eps bounding box ignores extra-offset
Not a bug - extra-offset is designed to be ignored by lily in spacing
calculations, including the calcultaion of bbox sizes.
On Wed, Sep 17, 2008 at 5:59 AM, [EMAIL PROTECTED] wrote:
Issue 679: eps bounding box ignores extra-offset
http://code.google.com/p/lilypond/issues/detail?id=679
New issue report by v.villenave:
% In the following snippet, the notehead with extra-offset is not printed.
% See attached picture.
\version 2.11.58
fixA =
{
\once \override Stem #'length = #9
\once \override Accidental #'extra-offset = #'(0.3 . 0)
}
fixB =
{
\once \override NoteHead #'extra-offset = #'(1.7 . 0)
\once \override Stem #'rotation = #'(45 0 0)
\once \override Stem #'extra-offset = #'(-0.2 . -0.2)
\once \override Stem #'flag-style = #'no-flag
\once \override Accidental #'extra-offset = #'(3.1 . 0)
}
\relative c' {
{ \fixA b d!8 } \\ { \voiceThree \fixB dis }
}
Attachments:
fix.png 1.5 KB
Issue attributes:
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path
On 9/13/08, KAWAN SEJAHTERA [EMAIL PROTECTED] wrote: Dapatkan mobil baru Innova. Tanpa uang muka. Pendaftaran hanya 60 ribu saja. Bulan ke-1 membayar Rp.130.000 Bulan ke-2 membayar Rp.124.000 Bulan ke-3 membayar Rp.105.000 Bulan ke-4 membayar Rp.120.000 Sudah cukup sampai di sini. Di bulan ke-9, mobil baru Innova akan menjadi milik Anda Info dan daftar di sini: http://www.bebasfinansial.com/?id=gagah -- Join with the best MLM on the world http://www.inovasibisnis.com/?id=aan -- Join with the best MLM on the world http://www.inovasibisnis.com/?id=aan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups opportunities at home group. To post to this group, send email to opportunities-at-home@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit end of msgBody class --> <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Han-Wen Nienhuys Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "000000"; //--> Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Han-Wen Nienhuys Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Han-Wen Nienhuys Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path Valentin Villenave Reply via email to
Re: Issue 665 in lilypond: Request: MusicXML backend
Hi, Priorities for these types of changes (oodles of work) does not change depending on user interest. We can un-postpone it if someone comes along to volunteer the necessary work. On Sun, Aug 24, 2008 at 8:18 PM, [EMAIL PROTECTED] wrote: Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #1 by v.villenave: Since we have more requests about it, I'm accepting it and slightly bumping the prio. Issue attribute updates: Status: Accepted Labels: -Priority-Postponed Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Help with debugging apparent error in parser
On Fri, Aug 8, 2008 at 8:57 PM, Neil Puttock [EMAIL PROTECTED] wrote: \ Changing line 827 from else if ((handle = scm_hashq_get_handle (chordmodifier_tab_, sym)) != SCM_BOOL_F) to else if ((YYSTATE == chords) (handle = scm_hashq_get_handle (chordmodifier_tab_, sym)) != SCM_BOOL_F) prevents it from returning an erroneous match in notemode so it can return a string instead. fix looks good. Can you write a regtest, fix and commit? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.55 strange exit on XP/seg fault
Thanks, this bug was already known (Neil had an outstanding patch), but I just pushed short fix which appears to work. If it is urgent, I can push a .55-2 or .56, but if not - I suggest to temporarily not remove staves. On Wed, Aug 6, 2008 at 6:01 AM, David Bobroff [EMAIL PROTECTED] wrote: The little bit of experimentation I've done seems to indicate that the problem arises between \remove Staff_symbol_engraver and any elongation of a note, whether it be a dot or a tie (slurs do work). As an added note; I ran the same input with the same Lily version on a Linux machine. It seg faults: Preprocessing graphical objects...Segmentation fault -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
doc suggestion
there is a the following snippet in
5.1.4 Saving typing with variables and functions
but the example doesn't show how the padText works. I think skylining
handles this automaticallly. Maybe you should find a different
example?
padText =
#(define-music-function (parser location padding) (number?)
#{
\once \override TextScript #'padding = #$padding
#})
\relative c''' {
c4^piu mosso b a b
\padText #1.8
c4^piu mosso d e f
\padText #2.6
c4^piu mosso fis a g
}
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.50 broken on PPC (and/or Windows?)
I built the .50-2 binary from scratch, but we are still seeing problem reports. The GUB environment itself has not changed 2.11.47, so this looks like something introduced in lilypond itself between .49 (please report: is this really the last version that worked correctly?) and .50 Here is a likely candidate, running git log -p release/2.11.49-1..release/2.11.50-1 -- lily/ shows that we have a patch to metronome engraver that does not initialize last_text_ in the constructor. On Sat, Jul 5, 2008 at 9:32 AM, Valentin Villenave [EMAIL PROTECTED] wrote: Greetings, I'm receiving several reports stating that the latest development release is broken on PPC and Windows. You mean: MacOS? I think linux-PPC is working correctly. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing checks in configure
On Sun, Jun 22, 2008 at 12:04 AM, Werner LEMBERG [EMAIL PROTECTED] wrote: We used to have checks for t1asm and fontforge implicitly, because they were dependencies for mftrace. Now that mftrace is no longer a requirement, we should have checks for those in the configure file. Yes. But those programs are no prerequisites for a normal build (this is, using a tarball), only for a build from the git sources. How so? We are not shipping the fonts in the tarball, and I don't think we should. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug status
On Tue, Jun 10, 2008 at 9:18 AM, Carl D. Sorensen [EMAIL PROTECTED] wrote: Issue attribute updates: Status: Verified Valentin, I may be wrong (after all, you're the bugmeister), but I think you are using status codes differently than they have been used in the past. It appears that you use Verified when a bug is fixed. In the past, I believe that Verified means that the bug report has been found to actually be a bug, and that Fixed is used when the bug is no longer occuring. This is almost a complete reversal of the meaning of Verified, from It really is a bug, and I've demonstrated it to The bug has gone away. As far as I can remember it was always like this. Maybe the label name can be enhanced. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil
2008/5/30 Mats Bengtsson [EMAIL PROTECTED]:
It cannot be that simple, since there are no font related settings on
TimeSignature in
scm/define-grobs.scm and the font related settings are done within
ly:time-signature::print
which ins't used here.
There are default font settings which enter the grob property list
through definitions in \layout{}
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions 2.11.46-1; script-center-seconds.ly
It's the note head at end (or beginning) of the stem. 2008/5/28 Stan Sanderson [EMAIL PROTECTED]: regressions 2.11.46-1; script-center-seconds.ly problem: word usage Current: text reads ...centered on the extremal note head but the word extremal is not in common use (it is used in mathematics). Suggest: ? perhaps ...centered on the leftmost note head (if that correctly describes it!) Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions 2.11.46-1; lyrics-no-notes.ly
it's actually an internal term, C++ class Paper_column, and Grobs PaperColumn and NonMusicalPaperColumn. Not sure how you would be describe this, though. 2008/5/28 Graham Percival [EMAIL PROTECTED]: This might be a bit too nitpicky, but applied. I checked to see if papercolumn was a specific lilypond-iternals term, but I couldn't find it in lily/*, whereas I found a couple of paper column. Cheers, - Graham On Wed, 28 May 2008 11:26:09 -0500 Stan Sanderson [EMAIL PROTECTED] wrote: regressions 2.11.46-1; lyrics-no-notes.ly problem: spelling Current: papercolumn Suggest: paper column Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions 2.11.46-1; music-function.ly
Generic music functions (so-called Music functions) can be used ... 2008/5/28 Graham Percival [EMAIL PROTECTED]: What's wrong with that? A is B, which can be used to C. (oh wait, the plurals don't match up... I've fixed that now) Cheers, - Graham On Wed, 28 May 2008 11:27:43 -0500 Stan Sanderson [EMAIL PROTECTED] wrote: regressions 2.11.46-1; music-function.ly problem: grammar Current: text reads Music function are... Suggest: omit Music functions are... Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions 2.11.46-1; spacing-packed.ly
Also note, we currently use ragged-right (with dash) everywhere. 2008/5/28 Stan Sanderson [EMAIL PROTECTED]: regressions 2.11.46-1; spacing-packed.ly problem: grammar, fourth sentence. Current: text reads ...If not in raggedright mode, lily will pack as much bars of music as possible... Suggest: replace with many ...If not in raggedright mode, lily will pack as many bars of music as possible... Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions 2.11.46-1; option-help.ly
thanks, fixed. 2008/5/28 Stan Sanderson [EMAIL PROTECTED]: regressions 2.11.46-1; option-help.ly problem: empty regression? Current: (no text, no code) Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Regression test different to normal compile.
2008/5/18 Neil Puttock [EMAIL PROTECTED]: 2008/5/18 Matthew Rowles [EMAIL PROTECTED]: As to how is it different? AFAIK it shouldn't be! that is why I'm confused, and wondering if it has anything to do with the error in pdfetex, or maybe lilypond-book, or my computer or anything that I've done It's probably the PNG output that's causing this; if you run the snippet as normal, but with the option -dpreview, you'll see that the PNG cropping doesn't take into account the extent of the bracket. Adding an outside staff object nearby forces visibility. that would be a bug. Could you file a bugreport for this? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: pitchedtrill accidental problem
2008/5/18 Valentin Villenave [EMAIL PROTECTED]: 2008/5/18 Mats Bengtsson [EMAIL PROTECTED]: Continuing this way, you half the number of possible alternatives in each iteration. Yes, I had an empirical knowledge of this method :-) Actually, I was mainly referring to the installing/uninstalling process: on Windows, for instance, such a thing would be practically impossible (the installation takes ages, and the uninstall is even worse). did you know you can run the (un)installer in batch mode if you supply the /S flag? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: IR: errors in Backend docs for Grobs
2008/4/30 Neil Puttock [EMAIL PROTECTED]: Hi there, For some reason I can't fathom, the autogenerated docs for layout objects display the wrong values for the properties 'axes and side-axis whenever the Y-axis is set. For example, in define-grobs.scm, TextScript has the the following setting for side-axis, (side-axis . ,Y), yet the docs imply that the setting would be ,X (or 1). huh? X=0, Y=1 -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: IR: errors in Backend docs for Grobs
2008/5/1 Neil Puttock [EMAIL PROTECTED]: huh? X=0, Y=1 Ah, no wonder I'm confused; it's just the descriptions for side-axis and direction that are topsy-turvy: If the value is #X (or equivalently 1), the object is placed horizontally next to the other object. If the value is #Y or 0, it is placed vertically. Like most quantities in lily, we start counting axes at 0. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: IR: errors in Backend docs for Grobs
2008/5/1 Neil Puttock [EMAIL PROTECTED]: If the value is #X (or equivalently 1), the object is placed horizontally next to the other object. If the value is #Y or 0, it is placed vertically. Like most quantities in lily, we start counting axes at 0. Now I'm really confused :) Are you saying that the above quote is correct? Because it seems to imply that #X = 1 and #Y = 0. no, it's wrong and that's why I cc-d Graham. X = 0, Y = 1 -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: part-combine-text.ly
It's probably a stray thing I inserted when I wanted to start insert mode in Viper, but was already in that mode :-) 2008/3/30, Stan Sanderson [EMAIL PROTECTED]: v2.11.43-2: regressions part-combine-text.ly issue: clarity current: The new part combiner detects a2, solo1 and solo2, and prints i texts accordingly. (To what does i refer?) Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: no compile on version 2.11.43 for Windows XP
Can you try 2.11.43-2 (uploaded today)? 2008/3/26, Tom Richard [EMAIL PROTECTED]: Version 2.10.33 for Windows XP compiles great. I have tried re-installing 2.11.43 3 times, carefully un-installing previous version every time. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond 2.11.42 Does not run on Win XP.
.43 is broken, probably for all platforms. I'll rm the binaries for now. 2008/3/26, Valentin Villenave [EMAIL PROTECTED]: 2008/3/26, Cesar Penagos [EMAIL PROTECTED]: Hi Cesar, No need to send this report to *three* mailing-lists... :) After download and install lilypond 2.11.43 in my win. xp sp2; I tried to run the Welcome lilypond file and instantly and a error windows can run the .exe file appears in my desk. Strange... This works here; can you try to download it again, and then tell us if the problem is still happening? Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-book 2.11.43 broken
2008/3/25, Graham Percival [EMAIL PROTECTED]: lilypond-book 2.11.43 from OSX GUB is broken for normal usage (ie I'm not complaining about the docs here. :) I don't quite know enough about python to figure out what you're trying to do on line 1633, sorry. is this py 2.3 or 2.4 ? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond 2.11.43 crashes
Hmm.. good point. I'm baking a fix right now. 2008/3/25, Thomas Scharkowski [EMAIL PROTECTED]: I get the following message (Win XPSP2): -- (lilypond.exe:1260): Pango-WARNING **: Failed to load Pango module 'C:/Programme/LilyPond/usr/bin/..//lib/pango/1.5.0/modules/pango- basic-fc' for id 'BasicScriptEngineFc' (lilypond.exe:1260): Pango-WARNING **: failed to find shape engine, expect ugly output. engine-type='PangoRenderFc', script='common' (lilypond.exe:1260): Pango-CRITICAL **: pango_fc_font_lock_face: assertion `PANGO_IS_FC_FONT (font)' failed Processing time: 6 seconds -- ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regression tests missing?
Hi, thanks for watching the regtests! It's incredibly important. I did a cleanup of lilypond-book which has broken the regtest compile. I'll have it fixed for .44. 2008/3/24, Stan Sanderson [EMAIL PROTECTED]: v2.11.43- regression tests missing Did I miss something? Both the local and on-line versions return file not found when a regression test or its associated image is selected. (just trying to do my job...) Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slow compile on Windows XP - font caching problem?
2008/3/21, Trevor Daniels [EMAIL PROTECTED]: Perhaps worth mentioning - my OS is Vista Home Premium, fully patched up to today. Is it possible to find out the differences between the three versions of libfontconfig-1.dll? Might this may have been upgraded for Vista, since the later version fails on XP but works fine on Vista, as the above demonstrates? There are certainly differences between these files, but they're not vista related; the whole build procedure runs on linux, and is for generic windows32. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slow compile on Windows XP - font caching problem?
2008/3/21, Trevor Daniels [EMAIL PROTECTED]: Some facts that might have a bearing: This was a clean install of Vista, not an upgrade. This was the very first LilyPond installation on this system. I had admin priviledges during the install, although removing them later has no effect on running LilyPond. The font cache was built in [user]/.lilypond-fonts.cache-2/ and contains the usual three files. I just love microsoft operating systems My best guess at this point is that this is some kind of permission problem. * Can you see what happens if you deinstall (as admin) and install (as admin) again? * Can you see what happens if you deinstall (as admin) and install (without admin rights) again? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slow compile on Windows XP - font caching problem?
2008/3/18, Trevor Daniels [EMAIL PROTECTED]: Not really. A couple of minor changes in fonts/fonts.conf but nothing that seems significant. can you post the diff anyway? However, I noticed that usr/bin/libfontconfig-1.dll changed between 34-1 and 35-1, and again between 35-2 and 36.1, looking at the module size. can you do a ls -l (or whatever it's called in vista?) An alternative is to build the cache, then delete or rename etc/fonts/font.config. This causes font-building to abort early with an error message, which also bypasses the timing problem. This also seems to have no adverse effect on a couple of simple tests, but I don't use any unusual fonts. I'll rebuild the 34-1 and check if I see any interesting anomalies compared to .42. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Tuplet brackets appear when I've asked them not to
2008/3/10, Trevor Daniels [EMAIL PROTECTED]: It seems to need more than a doc change and an example. Investigating this code uncovers a program exception under XP, which I have just reported. Perhaps the docs should be changed to say that \acciaccatura should not be placed within \times brackets. The code works fine when the acciaccatura is moved outside, like this: I fixed the exception. It still doesn't work (you get a bunch of errors and no bracket.) I suggest to avoid this: what does it mean for a grace note to be inside a \times ? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slow compile on Windows XP - font caching problem?
2008/3/13, Trevor Daniels [EMAIL PROTECTED]: Thanks Graham :( OK - here are the results: 2.11.34-1 Compiles in 15 secs Uses .fontconfig directory 2.11.35-1 Fails with libguile2-17.dll not found Copied this in, then Fails with error about ice-9/boot-9.scm not in load path 2.11.35-2 Compiles in 15 secs, but Lots of error messages like Pango CRITICAL FT_Get_Glyph_Name() error invalid argument Glyph has no name Skipping Glyph U+ ... Century-Schl-Roma.otf Uses .fontconfig directory 2.11.36-1, 37-1, 41-1, 42-1 All compile slowly - 65 secs All use .lilypond-fonts directory Dang, this happened after a big refactoring of our build system. Is there anything interesting (eg. by way of diff -r) of /program files/lilypond/usr/etc/ directory between .34 and .36 ? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Obsolete LILPONDPREFIX in lilycall.py
2008/3/16, aws [EMAIL PROTECTED]: Version 2.10 and 2.11 mac ppc current download tarballs. Patch to fix: 79c79 env['LILYPOND_DATADIR'] = prefix + '/share/lilypond/current' --- env['LILYPONDPREFIX'] = prefix + '/share/lilypond/current' The proper fix is to remove this entirely. AFAIK lilycall.py isn't really used anymore, since we put all the relocation logic in the lilypond binary itself. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slow compile on Windows XP - font caching problem?
this type of stuff is tricky. The last time we saw this, it was - dirs.push_back (lilypond_datadir + /fonts/otf/); - dirs.push_back (lilypond_datadir + /fonts/type1/); + /* Extra trailing slash suddenly breaks fontconfig (fc-cache 2.5.0) + on windows. */ + dirs.push_back (lilypond_datadir + /fonts/otf); + dirs.push_back (lilypond_datadir + /fonts/type1); can someone please post the exact version number where you've started seeing this? 2008/3/11, Valentin Villenave [EMAIL PROTECTED]: 2008/3/11, Trevor Daniels [EMAIL PROTECTED]: Yes, definitely a regression. I've gone back to using 2.11.34 which does not suffer this bug, as most of my documentation work is fiddling with tiny snippets, and a 1 minute delay every time I make a change makes it impossible to work. OK. That's it. I've opened a new issue: http://code.google.com/p/lilypond/issues/detail?id=588 Trevor: perhaps you should try the workaround described on http://code.google.com/p/lilypond/issues/detail?id=545#c1 Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: grace-stem-length.ly
yep. please fix 2008/3/9, Stan Sanderson [EMAIL PROTECTED]: 2.11.42 regressions: grace-stem-length.ly problem: clarity in text current: ...even if that would lead to beam quanting program. Should program be problems? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: markup-user.ly
2008/3/9, Stan Sanderson [EMAIL PROTECTED]: 2.11.42 regressions: markup-user.ly problem: clarity in text current: Own markup commands may be defined ... suggest: Markup commands may be defined... (or) Unique markup commands may be defined... (or) Special markup commands may be defined... Users may define nonstandard markup commands -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: property-nested-reverted.ly
2008/3/9, Stan Sanderson [EMAIL PROTECTED]: 2.11.42 regressions: property-nested-reverted.ly problem: reversion not complete- is there missing code? No, I think the objective is to show that you can revert individual nested properties, without affecting others. The implementation makes this trick. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: system-start-bracket.ly
2008/3/9, Stan Sanderson [EMAIL PROTECTED]: 2.11.42 regressions: system-start-bracket.ly problem (?): confusion in text The text reads, The piano brace should be shifted horizontally if it is enclosed in a bracket. I am confused by the ...if..., since the piano brace itself can obviously(?) not be enclosed in a bracket. If the intention is to convey that the piano brace is shifted to a position before the grand staff, then I would suggest the following: A piano context included within a staff group should cause the piano brace to be drawn to the left of the staff angle bracket. Looks ok to me. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Alignment problem with text crescendo in {...} {...} in 2.11
2008/2/26, Reinhold Kainhofer [EMAIL PROTECTED]: shows that in Line_spanner::calc_bound_info, the X value is really set to nan (i.e. bound_grob-extent (commonx, X_AXIS).linear_combination (attach)) returns nan). If I use g2\ instead of s2\, a value of 17,... is returned. I suppose this should robust_relative_extent() rather than extent() Exactly! Using robust_relative_extent instead really fixes the problem. Patch is attached. Okay to apply? looks good to me. We should really do an audit of all extent() calls and replace with robust_relative_extent() if necessary. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Regression comparisons: something rotten
2008/2/22, Alexander Deubelbeiss [EMAIL PROTECTED]: In http://lilypond.org/test/v2.11.40-1/compare-v2.11.39-1/index.html some of the regression tests show log files instead of notation images. Here's the list: volta-broken-left-edge chord-names-languages instrument-name multi-measure-rest-instr-name profile-property-access instrument-name-dynamic quote-cue-during alignment-vertical-spacing quote-during tag-filter quote instrument-name-markup clip-systems instrument-switch drums quote-grace instrument-name-hara-kiri prefatory-spacing-matter fret-boards option-help instrument-name-partial Nearly all of these do have images on the collated-files page, so the problem seems to be with the comparison setup rather than with actual tests breaking on the current version. no, this is on purpose. the .39 - .40 transitions generated lots of extra warning messages. This needs to be looked in to. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: song-reordering.ly
2008/1/7, Valentin Villenave [EMAIL PROTECTED]: I'll commit some texidoc explanations... as soon as I manage to get my rsa pubkey accepted by git. I approved you the day before yesterday. It should work right away. Can you post what is not working? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: song-reordering.ly
2008/1/5, Valentin Villenave [EMAIL PROTECTED]: 2008/1/5, Stan Sanderson [EMAIL PROTECTED]: regressions: song-reordering.ly : is this test a duplicate of song- reordering2.ly ? I think so. I decided to remove it, as it was obviously a duplicate. Please contact the author of the festival stuff about this. I have made a mistake, as the file was committed without a texidoc header, but it may test valuable behavior. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36/5 - workaround (not quite)
2007/12/31, Risto Vääräniemi [EMAIL PROTECTED]: I'll continue my monologue. :-) Hi, the quick fix is to patch out /type1/ and /otf/ which appear somewhere in the binary lilypond.exe: replace the trailing slash with a \0 character. I hope to release a new versions shortly, which will fix this. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Fwd: Fw: Request to mailing list bug-lilypond rejected
(and I wish you a merry musical christmas from a sunny Rio de Janeiro) -- Forwarded message -- From: Yotam Medini יותם מדיני [EMAIL PROTECTED] Date: 24 dec. 2007 18:05 Subject: Fw: Request to mailing list bug-lilypond rejected To: [EMAIL PROTECTED] Hello LilyPond bug-list moderator, I am really confused about the proper way to report bugs. The web site says, to use the GMane interface. So I did, and I even saw my posting there, See: http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/12057 but I have no idea what is the process that brings such GMane-repors to the (Google-code) tracker. I also perpared attachments, of source and image that I would like to add to the report, but it seems impossible to do that via the GMane interface. Please help me help LilyPond. regards -- yotam Begin forwarded message: Date: Mon, 24 Dec 2007 14:10:34 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Request to mailing list bug-lilypond rejected Your request to the bug-lilypond mailing list Posting of your message titled diacritic (Hebrew nikud) not well positioned has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: Non-members are not allowed to post messages to this list. Since you are not subscribed to this list, please use the Gmane interface at http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs for posting messages. Thank you, The LilyPond mailing list administrators Any questions or comments should be directed to the list administrator at: [EMAIL PROTECTED] -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 518 in lilypond: \oldaddlyrics broken
2007/12/18, Laura Conrad [EMAIL PROTECTED]:
\context Staff=default
{
\voicedefault
}
\addlyrics { \wordsdefaultVA }
This is pretty straightforward, and could be scripted for the
real-world case, although maybe not by convert-ly for the completely
general case. Is there some reason why this isn't as good as the
equivalent \lyricsto solution?
\addlyrics is implemented with \lyricsto. The problem is that
convert-ly cannot reliably handle the (possibly nesting) arguments to
\lyriccombine.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 519 in lilypond: PDF filesize has increased between 1.9.8 and 2.10
2007/12/6, [EMAIL PROTECTED] [EMAIL PROTECTED]: Issue 519: PDF filesize has increased between 1.9.8 and 2.10 http://code.google.com/p/lilypond/issues/detail?id=519 Comment #3 by gpermus: Shouldn't the PDFs be independent of OS? Presumably on windows we include the font so that the PDF will look the same on other systems; PDFs created on OSX should have the same compatibility stuff. I'm not sure if that is feasible when taken to its consequence. We'd have a to include a font that has coverage in all of unicode; it will be large, and there might be licensing problems. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond slowness?
2007/12/3, Iain Archibald [EMAIL PROTECTED]: Excellent: Questions for vista users: - do you have a \Documents and Settings\[username]\.fontconfig ? - If yes, do programs need special permissions to write there? - What happens if you change \Program Files\LilyPond\usr\etc\fonts\fonts.conf where it says cachedir~/.fontconfig/cachedir and modify the directory? eg. cachedir/bla/.fontconfig/cachedir after you create a c:\bla directory, of course? On my Vista system (with lilypond 2.10.33) there are two locations with a 'fontconfig' directory: C:\Users\[username]\AppData\Temp\fontconfig\cache C:\Users\[username\Documents\usr\var\cache\fontconfig Each of these locations contains files of type 'cache-2'; are these lilypond files? If they aren't then I don't know where the data is! They are but problaby from a previous version. Could you tell by the timestamps? Are they regenerated if you remove them and rerun LilyPond? The problem is that fontconfig keeps building the database over and over, leading to minutes of delay on every run - are you seeing that too? This suggests that the database files are not written, probably due to permission issues. The only other 'fontconfig' directory is: c:\Program Files\Lilypond\usr\var\cache\fontconfig and that is empty. that is strange: they should be called .fontconfig , not fontconfig (note leading period). Fontconfig actually looks at the environment variable $USERPROFILE -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Very Slow on Vista
2007/11/23, Jose Mena [EMAIL PROTECTED]: It's a simple one-line melody, and I'd expect this to take no time for LilyPond to compile. And in my Ubuntu 7.11 virtual machine, it does indeed take no time. My test had the code compiling in about 3.5 seconds. The astonishing thing is the difference in Windows Vista. This short code clocked in at 45 seconds of compile time. So, as I asked earlier: does anybody know what's going on here? It Yes, the fontconfig cache doesn´t get written, or it gets written, but does not get read on the second call. It would be nice if someone could post the output of running it from the commandline in windows with FC_DEBUG=255 in the environment. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 486 in lilypond: chord fonts in OSX
2007/10/1, Hans Aberg [EMAIL PROTECTED]: I think this was discussed, and it then looked like a problem with 'fondu'. But now it looks like a problem with the font Verdana. If I look into the /Library/Fonts/, Verdana does not have any file name extension. By contrast, /System/Library/Fonts/, the name is Helvetica.dfont, a fondu works with Helvetica (modulo that the accidentals are not printed). So it seems that fondu can handle some font formats that Mac OS X can handle, but not all. MacOS X has this weird scheme where data can be stored in different forks (IIRC resource or data fork). This makes it look as if the file has 0-bytes lenght, but the data is actually somewhere else in the filesystem. Can you check if this is the case for verdana? ls -l /Library/Fonts should tell you whether this the case. In any event, fondu should work with all types of mac dfonts. In any event, maybe should we ship a sans-serif font too, so chord names have uniform appearance across platforms. Any suggestions which would be the best font? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
2007/9/1, Trevor Bača [EMAIL PROTECTED]: Joe's looking at the inputfile, which is awesome. For future reference, is there any way to get an unstripped binary (one with all the debug messages not commented out, right?) from the website? Or is git the only way to go? (I've so far avoided using git because I've not been contributing patches; but I'm certainly comfortable running stuff in gdb if it would help.) Git is the only way to go; it's unfortunate, because compiling lilypond is such a PITA. We could look into making debug info available separately for the binary builds, but it would take a lot of space, for rare occasions. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
Joe Neeman escreveu: On Saturday 01 September 2007 09:00, Trevor Bača wrote: On 8/31/07, Joe Neeman [EMAIL PROTECTED] wrote: On Friday 31 August 2007 23:17, Trevor Bača wrote: Should I send the inputfile to either Joe or Han-Wen for testing against .31? I'd be happy to take a look at it. Thank you *so* much, Joe! Will send offlist ... I can't reproduce with git or the x86-linux binary. I get a segfault with the amd64 binary... in ghostscript (during the convert-to-pdf stage). If I take the .ps file and run it though the system's ghostscript, it works perfectly. So it seems to be a problem with the ghostscript that's included in the binary package. In the original report, it didn't crash in GS but in lily. It looks as if someone needs to build a macos binary without stripping. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
2007/8/31, Joe Neeman [EMAIL PROTECTED]: On Friday 31 August 2007 13:23, [EMAIL PROTECTED] wrote: Issue 430: Cross-staff beam craziness (when down-markup combines with down-articulation) http://code.google.com/p/lilypond/issues/detail?id=430 Comment #2 by hanwenn: Hi Joe, can you review my patch for this fix? My preferred way for dealing with these cyclic dependency issues is to mark something cross-staff. If a grob has the cross-staff property set to true, it gets ignored for all pure-height calculations, so it's a good way to break this sort of cycle (plus, it's encapsulated in its own grob property). Yes, but wouldn't this result in staves colliding if the script is really large? The advantage of doing it with Stem direction is that you break the cycle at the exact point where unnecessary information is requested. Of course, it would be best if we could have that idea encapsulated in a property by itself. One extreme idea could be to calculate up and down extents separately, perhaps with a Y-extent - (up-extent , down-extent) dependency, which we would have just for Stem for now. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
2007/8/31, Trevor Bača [EMAIL PROTECTED]: Hi, Crossposted as Google #433. Running 2.11.30 on a relatively large file (110 measures of six staves with 4559 lines of total input) causes the following segmentation fault. GNU LilyPond 2.11.30 Processing `/Users/trevorbaca/Documents/lilypond/pictures/1768.ly' Parsing... Interpreting music... [8][16][24] Preprocessing graphical objects.../Users/trevorbaca/Documents/lascaux/scr/lily: line 4: 14270 Segmentation fault I've been cutting out parts of the file all morning to produce a minimal snippet. But at this point it appears that the seg fault comes from the *size* of the inputfile rather than from the *musical contents*. (Ie, file compiles absolutely fine to and with measure 109; adding measure 110 *in any of the six musical staves* causes the seg fault.) One way of finding this out is to run the thing inside GDB and look at the stack trace. Unfortunately, for useful information, you have to do this in an unstripped binary, which is not included in the installer. Usually segfaults are writing to a null pointer, and I remember doing 500 mesaures of 64 staves without problems, so memory overflow seems unlikely. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Hello Joe,
can you look into fixing this problem, and merging the fixes into
master? Due to time-pressure, I don't want to delay 2.11.29 any
further, but shipping it breaks one of the major rules for lilypond
development: every release should be strictly better than the
preceding one.
thanks,
2007/8/6, Joe Neeman [EMAIL PROTECTED]:
On Monday 06 August 2007 16:33, Wilbert Berendsen wrote:
%{
LilyPond chooses too tight spacing: the stems of kneed notes are too close
and the spacing too tight. This also occurs in one of my larger projects,
where the stems even are in the wrong order and sometimes outside the
beams. It seems that the optical spacing of kneed beamed notes (put stems
at more equal distances) does not work fully correct, as of git 4 august
2007 %}
Does the problem still exist in the jneeman branch of git? If it does, I'd be
particularly interested in seeing examples with stems in the wrong order.
Joe
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 404s for the 2.11 docs
Argh! It was refreshed as part of the release, but something was botched in the build. I'll look into it. 2007/7/26, Trevor Bača [EMAIL PROTECTED]: Hi, The 2.11 user manual, reference manual and snippets have all been giving 404s for the last couple of hours. I assumed this was due to a doc (re)building process going on somewhere. But if not, could someone put the docs back online? Trevor. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: chordmode :13 leaving out 11
2007/7/19, Rune Zedeler [EMAIL PROTECTED]: Manual says thirds are added to the root until it reaches the specified number which would be the correct thing to do. But when specifying :13, the 11 is left out, so that the chord name printed is 9/add13 instead of 13 Yes, this was suggested by Amy Zapf a long time ago. In the standard chord, the 3 and 11 combine very badly, so ususally the 11 is dropped. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 381 in lilypond: input/regression/accidental-tie.ly
2007/7/5, Joe Neeman [EMAIL PROTECTED]: This seems to have been caused by commit b80bb48c. Before line breaking is done, tie-original () will always return 0, so the accidental will always suicide. I've reverted this in the jneeman branch but I don't want to merge it until I work out why the patch was originally made. The only things I can think of were that the accidental was interfering with spacing or with slur positioning. The spacing code deals with this situation explicitly -- it looks out for accidentals and leaves them out of skylines that they shouldn't be in. I think the proper solution is to make sure that print() isn´t called before line breaking, ie. make a common function create_stencil() that does the lookup but does not perform suicide, use that to do any stencil lookups before line breaking (eg. to compute width/height). Of course, you may look into why print() is called before line breaking. In general all before/after-line-breaking callbacks are not data-driven, so they should disappear. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in documentation
2007/7/3, Graham Percival [EMAIL PROTECTED]: Thanks for the report. This actually isn't a typo; the word is correctly typed as \tweak, but somewhere along the processing chain, \t is interpreted as a tab. I'm investigating the issue. This is lily's doing. You need to escape \ in lilypond strings, ie. the cmd \\tweak -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: ‹ Prev 7 of 7
Joe, can you have a look at this? 2007/7/3, Toine Schreurs [EMAIL PROTECTED]: segfault, programming error bad number of pages -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SVG text-anchor and font-style
Manuel Strehl escreveu: I'm not top posting. Hi there. I wanted to point out following bugs/enhancements in the SVG output: (Line numbers are related to v. 2.11.27) Hi there, it would be cool if you could submit a patch; the only current use for the SVG output is post-editing files in inkscape, and I don't know enough of SVG to effectively add or test these changes. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Weird beam-slope
Rune Zedeler escreveu: (not topposting) If beams are force-stretched to the middle staff-line I think they should be horizontal. In all cases current behaviour, where the 2nd beam starts below the 1st beam even though the pitches are higher, must be wrong. disagree, and so do most engravings. In the case you show, arguable the 1st beam should rather be slightly slanted -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.24 regression: last page sometimes missing
Arvid Grøtting escreveu: I'm not top-posting. I don't have a minimal example for this yet, but I've seen a regression with 2.11.24-2 (over 2.11.23-1) on MacOS X 10.3.9 PPC: A score that should take only three pages (or that did so with 2.11.23) with 9 systems, gets 7 widely- spaced systems over three pages, with the final 9 bars of music missing! With system-count = #9, the music fits on 3 pages (and has no vertical stretching). With the exact same line breaks added manually, the same 9 systems take up 4 pages. This is (of course) with ragged-last-bottom = ##f. It's also a choir piece on two staves, with four stanzas of lyrics. I'll try cooking up a minimal example. The following example is I have fixed this bug (I think), and am rolling a .25 to amend this brown-paper-bag bug -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: problems with long files
Joe Neeman escreveu: Is this the old page breaker (optimal-page-breaks) or the new one (ly:optimal-breaking)? There will be some dramatic speed increases in the new breaker in 2.11.24. what's your plan for this? I want to release .24 end of this weekend. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lyrics tie does not work
can you double check for me that whether this is a new fault in .23 ? 2007/5/2, Nancho Alvarez [EMAIL PROTECTED]: I am not top posting I have found a bug with the lyrics tie feature ( ~ in the lyrics section). lilypond can compile it perfectly to a .ps file, but the process of converting it to .pdf fails. The weird thing is that typing manually the command mentioned in the error message, the conversion works fine. I use debian etch. I think that I have all the fonts installed because I can see the ps perfectly. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: problems with long files
2007/5/2, Joe Neeman [EMAIL PROTECTED]: Well, I have seen that the Lilypond version 2.8.8 can easily be installed in the local directory, and with that, everything compiles in a couple of seconds with no fuss. Yes, I can confirm that 2.10 (and 2.11) seem to use a significant amount more memory than 2.8. AFAICR, 2.8 predates your changes to the pagebreaker; we keep all of the scores in memory now, which will signficantly increase memory use. However, it would be nice to know some more useful facts about the memory use. Here are some tips: - -ddebug-gc will print statistics of live objects in a file. Look at this to see what type of objects are using most memory - -dtrace-memory-frequency will sample memory use over time. Look at this to see which stages of the program use a lot of memory Another useful metric is to know when (which version, or better yet: which commit) introduced increased memory use. Unfortunately, I lack the time to investigate this deeply now, and I would be grateful if someone did a bit of legwork for me. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
