[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 16 May 2012 09:18:49 +0100
On Wed, May 16, 2012 at 09:33:09AM +0200, Martin Tarenskeen wrote:
> >>>The good news is that in many cases only a little editing of
> >>>the .ly file is required to turn a bad conversion into a good
> >>>one. For example, all lead sheets from Wikifonia that I have
> >>>tried have the Chords printed below instead of above the
> >>I remember this had been fixed in one of the previous lilypond
> >>2.15.x versions, but with musicxml2ly from Lilypond 2.15.37 I am
> >>still (again?) having this problem.
> >Same with 2.15.38
> I did not see a reaction to this question, so I try again. What
> happened with this musicxml2ly bug ? First chords were printed below
> the staff, then I think it was fixed, and now the chords are below
> the staff again. Regression?
That must be very frustrating for you. Sorry that I can't help you, as
I'm not familiar with musicxml2ly. It appears to be central to
Patrick's project so I would imagine he or his colleagues are working
hard on this.
There are a number of issue trackers relating to musicxml2ly but I see
no issue tracker for this bug, Martin.
I'd like to at least record the bug. We can create a tracker if you
supply these details:
1. A version of lilypond/musicxml2ly and a specific lead sheet from Wikifonia
in MusicXML format that together exhibit the bug.
2. A version of lilypond/musicxml2ly from the 2.15.x series which does not
exhibit the bug.
- Re: musicxml2ly,
Colin Hall <=