Re: musicxml2ly stops making chords after some timing errors
On 06.07.2013, at 23:18, Pavel Roskin pro...@gnu.org wrote: Quoting pls p.l.schm...@gmx.de: I don't care how the faulty markup looks. But MuseScore got the second measure right. It could recover and musicxml2ly could not. that's because of the faulty MusicXML markup you provided. the first measure contained the duration of five quarter notes instead of four. that's why all the following measures were affected. Oh well, this puts me between the rock and the hard place. musicxml2ly cannot deal with MusicXML errors reliably. On the other hand, MuseScore can read broken MusicXML but makes broken Lilypond output (missing braces). One possible approach is to open and save MusicXML in MuseScore and then use musicxml2ly on the saved file. I checked it quickly, the chords are not lost, but I need to see if anything else is preserved. I don't know how to persuade you that musicxml2ly could and should do better. You don't need to persuade me that musicxml2ly is far from perfect. (I know the script very well.) The problem you describe is not really a bug in musixml2ly but an ill-defined feature request. You are basically asking for an automated correction of false values in duration elements in combination with an automated corrective assignment of notes to voices. This is non-trivial – especially in polyphonic parts with more than two voices. -- Regards, Pavel Roskin ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
tempo error
I'm not top posting.
% Entering a tempo different from 4 = 120
% generates an empty c++ error promt.
\version 2.17.21
\language deutsch
melody = \relative c' {
\clef treble
\key c \major
\time 4/4
\tempo 4 = 96
c2 d
e4. d8 c2
}
\score {
\new Staff \melody
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Marks right-aligned in unstable
Marks are aligned to the right edge of objects in unstable release, whereas they are centred in the stable release in agreement with the documentation. Compare, for example, the arrow above the treble clef in the example near the end of http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-text#text-marks with http://www.lilypond.org/doc/v2.17/Documentation/notation/writing-text#text-marks ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tempo error
Bastian bastianloeh...@gmail.com wrote in message
news:loom.20130707t095919-...@post.gmane.org...
I'm not top posting.
% Entering a tempo different from 4 = 120
% generates an empty c++ error promt.
\version 2.17.21
\language deutsch
melody = \relative c' {
\clef treble
\key c \major
\time 4/4
\tempo 4 = 96
c2 d
e4. d8 c2
}
\score {
\new Staff \melody
}
Which operating system are you using? On my Windows system, this behaves
very much like http://code.google.com/p/lilypond/issues/detail?id=3432
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly stops making chords after some timing errors
Pavel Roskin pro...@gnu.org wrote in message news:20130706171855.91mxat93pycg440g-ceb...@webmail.spamcop.net... Quoting pls p.l.schm...@gmx.de: I don't care how the faulty markup looks. But MuseScore got the second measure right. It could recover and musicxml2ly could not. that's because of the faulty MusicXML markup you provided. the first measure contained the duration of five quarter notes instead of four. that's why all the following measures were affected. Oh well, this puts me between the rock and the hard place. musicxml2ly cannot deal with MusicXML errors reliably. On the other hand, MuseScore can read broken MusicXML but makes broken Lilypond output (missing braces). One possible approach is to open and save MusicXML in MuseScore and then use musicxml2ly on the saved file. I checked it quickly, the chords are not lost, but I need to see if anything else is preserved. I don't know how to persuade you that musicxml2ly could and should do better. -- Regards, Pavel Roskin Surely the correct approach is to ensure that the output from Sharpeye is correct. This can often be done by adding extra rests (which you subsequently delete/replace with spacers). Is Sharpeye warning of timing errors? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tempo error
Bastian bastianloeh...@gmail.com writes:
I'm not top posting.
% Entering a tempo different from 4 = 120
% generates an empty c++ error promt.
\version 2.17.21
\language deutsch
melody = \relative c' {
\clef treble
\key c \major
\time 4/4
\tempo 4 = 96
c2 d
e4. d8 c2
}
\score {
\new Staff \melody
}
Can't reproduce. Can you copypaste the error message? Which LilyPond
version, operating system? Is this the official binary?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Broken x-refs in translated docs
Le 06/07/2013 19:48, Jean-Charles Malahieude disait : Le 06/07/2013 15:45, Phil Holmes disait : Jean-Charles Malahieude wrote... I'll try to narrow this large window (slowly because of my box's power) and let you know. If you have less of a restriction with download limits, http://download.linuxaudio.org/lilypond/binaries/documentation/ might be of help? Unfortunately there is no tarball between 2.12.3 (Jan. 2010) and 2.14.0 (June 2011). And the only from the 2.13 series on my box are 2.13.1 (May 2009) and 2.13.45 (Jan. 2011). I've no other option than rewinding... and try to have a successful compilation. Too bad, resetting more than 2 years ago is a good idea; each compile fails and I suspect upgrades to the compiling tools don't like this much of going back in time. Another track would be to try each modification of either lilypond-texi2html.init or extract_texi_filenames.py between 2010/01/13 and 2011/01/03 in order to locate the culprit. I'll do it as soon as the master-translation-staging merge is checked and pushed (80mn for each make make doc). Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Marks right-aligned in unstable
2013/7/7 Timothy Lanfear lanf...@costamagna.demon.co.uk: Marks are aligned to the right edge of objects in unstable release, whereas they are centred in the stable release in agreement with the documentation. Compare, for example, the arrow above the treble clef in the example near the end of http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-text#text-marks with http://www.lilypond.org/doc/v2.17/Documentation/notation/writing-text#text-marks ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Hi Timothy, thanks for your report, seems this doesn't work accurately since some time. 2.12.3 was good. With 2.14.2 aligning to time-signature went wrong. Same with 2.16.2. 2.17.21 aligns all wrong. Workaround: Add \once \override Score.grob-to-align #'break-align-anchor-alignment = #CENTER Where grob-to-align should be replaced by the grob-name of the grob from: \override Score.RehearsalMark #'break-align-symbols = #'(grob-to-align Attached the slightly modified file from the NR \sourcefilename aligning-marks-with-various-notation-objects.ly lily-f5397883.ly (I modified it to make it work with every version since 2.12.3, coloring red the observed misalignments and printing the used version as instrumentName. It contains the commented workaround.) Also attaching previews from 2.12.3 2.14.2 2.16.2 2.17.21 Please note: I didn't test alignment with other circumstabces. Cheers, Harm attachment: 2-12-3-aligning-marks-with-various-notation-objects-bug.preview.pngattachment: 2-14-2-aligning-marks-with-various-notation-objects-bug.preview.pngattachment: 2-16-2-aligning-marks-with-various-notation-objects-bug.preview.pngattachment: 2-17-21-aligning-marks-with-various-notation-objects-bug.preview.png aligning-marks-with-various-notation-objects-bug.ly Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
No warning for misspelled properties.
Hi,
although they're misspelled, neither of the commands in the following
code returns a warning, nor does 2.16.2 (apart from the _expected_
syntax error).
Selfcompiled 2.17.22 doesn't throw an error, too.
\version 2.17.21
{
\override Score.RehearsalMark #'verticalll-skylinesss = #'()
\override Score.RehearsalMark.verticalll-skylinesss = #'()
\override Score.RehearsalMark #'horizontall-skylinesss = #'()
\override Score.RehearsalMark.horizontall-skylinesss = #'()
\mark \default
R1
}
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 3363: Scripts misplaced with cross-staff slurs
2013/7/2 Timothy Lanfear lanf...@costamagna.demon.co.uk I'm not top posting. Issue 3363 has reappeared in 2.17.20; 2.17.19 was fine. I'm using Windows 32-bit. this issue was reopened by Keith end of May so no need to open a new one ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Marks right-aligned in unstable
2013/7/7 Thomas Morley thomasmorle...@gmail.com thanks for your report, seems this doesn't work accurately since some time. 2.12.3 was good. With 2.14.2 aligning to time-signature went wrong. Same with 2.16.2. 2.17.21 aligns all wrong. Many thanks for your analysis! I've marked it as a regression: https://code.google.com/p/lilypond/issues/detail?id=3443 BTW, I've never received the email from Timothy (spam folder already checked). I think that it's not the first time that happens. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No warning for misspelled properties.
2013/7/7 Thomas Morley thomasmorle...@gmail.com
although they're misspelled, neither of the commands in the following
code returns a warning, nor does 2.16.2 (apart from the _expected_
syntax error).
Selfcompiled 2.17.22 doesn't throw an error, too.
\version 2.17.21
{
\override Score.RehearsalMark #'verticalll-skylinesss = #'()
\override Score.RehearsalMark.verticalll-skylinesss = #'()
\override Score.RehearsalMark #'horizontall-skylinesss = #'()
\override Score.RehearsalMark.horizontall-skylinesss = #'()
\mark \default
R1
}
thanks Harm, here's the report:
https://code.google.com/p/lilypond/issues/detail?id=3444
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Marks right-aligned in unstable
2013/7/7 Federico Bruni fedel...@gmail.com: BTW, I've never received the email from Timothy (spam folder already checked). I think that it's not the first time that happens. Hmm. Have you got http://lilypond.1069038.n5.nabble.com/Clef-changes-in-retrograde-will-only-print-a-new-clef-note-positions-will-not-change-to-accommodate-f-td147272.html ff ? -Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Marks right-aligned in unstable
2013/7/7 Thomas Morley thomasmorle...@gmail.com 2013/7/7 Federico Bruni fedel...@gmail.com: BTW, I've never received the email from Timothy (spam folder already checked). I think that it's not the first time that happens. Hmm. Have you got http://lilypond.1069038.n5.nabble.com/Clef-changes-in-retrograde-will-only-print-a-new-clef-note-positions-will-not-change-to-accommodate-f-td147272.html ff ? no, I haven't that's another case where I received only your reply ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Clef changes in retrograde, will only print a new clef. note positions will not change to accommodate the new clef
2013/6/23 Thomas Morley thomasmorle...@gmail.com So yes, \retrograde should be improved. I'd call it an enhancement-request. added here: https://code.google.com/p/lilypond/issues/detail?id=3445 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Clef changes in retrograde, will only print a new clef. note positions will not change to accommodate the new clef
2013/7/6 Thomas Morley thomasmorle...@gmail.com General policy-question: Sometimes I reply to some mails on this list, before a bug-squad-member answered. (To do some analysis; solve a problem, which would have better sent to the user-list; etc) Is this ok? Or should I let a bug-squad-member answer first? your replies help us to create a detailed report, so please go on this way :-) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
