Hey all,
the item t:number in fret diagrams (usage described here:
http://lilypond.org/doc/v2.15/Documentation/notation/instrument-specific-markup)
leads to the following error:
.../Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/fret-diagrams.scm:852:37:
In procedure c
Hey all,
we have been working on solutions for old musicxml2ly-bugs and some new
functions. We have published our efforts on
https://github.com/Philomelos/lilypond-musicxml2ly-dev. We will continue
working on musicxml2ly but there are far more bugs than we could ever handle on
our own. So i
A -element containing a - and a -element but no
-element causes an additional empty staff above the defined one.
Tiny example:
missing_voice-element_in_a_chorded_note_leads_to_empty_second_staff.xml
Description: XML document
(unwanted) result:
<>
The wrong MusicXML-markup was caused by Sib
Am 28.09.2012 um 12:09 schrieb pls:
> A -element containing a - and a -element but no
> -element causes an additional empty staff above the defined one.
>
> Tiny example:
>
>
> (unwanted) result:
>
>
> The wrong MusicXML-markup was caused by Sibelius 7.0.0.
Sorry, this is killing me. :(
Am 29.09.2012 um 13:19 schrieb pls:
>
> Am 28.09.2012 um 12:09 schrieb pls:
>
>> A -element containing a - and a -element but no
>> -element causes an additional empty staff above the defined one.
>>
>> Tiny example:
>>
&g
Hey all,
Sibelius 7.0.0 exports wrong duration values for chorded notes in tuplets. The
exported value in this example
(https://www.dropbox.com/s/vrvdabwym9tezd0/time-modification_and_chorded_notes.xml)
is 256 instead of 170 for a quarter note in a triplet of eighths
(256). 170 is not an op
My test files obviously got lost. :(
Am 29.09.2012 um 14:24 schrieb pls:
> Sorry, this is killing me. :(
> Am 29.09.2012 um 13:19 schrieb pls:
>
>>
>> Am 28.09.2012 um 12:09 schrieb pls:
>>
>>> A -element containing a - and a -element but no
>>> -e
x.com/s/8bep4ly69xfwfmt/unwanted_voices.xml
hth
patrick
Am 03.10.2012 um 22:22 schrieb Marek Klein:
> Hello, Patrick
> 2012/10/3 pls
> Hi,
> I described two issues and posted two test files in this thread.
> hth
> patrick
>
>
> I have added the second issue as
> http
Hey all,
middle syllables aligned to slurred notes are swallowed by musicxml2ly i.e.
they get lost during the conversion e.g.:
middle
la
Test file:
https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/mast
Hey all,
syllables under beamed notes are swallowed by musicxml2ly (LilyPond v2.17.3).
This seems to be a close relative of Issue 2881.
Test File:
https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSuite/beams-lyrics.xml
Result of the conversion of the test file (s
10.2012 um 23:06 schrieb pls:
> Hey all,
>
> syllables under beamed notes are swallowed by musicxml2ly (LilyPond v2.17.3).
> This seems to be a close relative of Issue 2881.
>
> Test File:
> https://github.com/Philomelos/lilypond-musicxml2ly-dev/blob/master/MusicXML-TestSui
Hey all,
I just discovered a command line option that is not mentioned in the docs: It's
possible to append "landscape" to a paper size, e.g.
$ lilypond -dpaper-size=\"a6landscape\" inputfile.ly
There are a few error messages and lots of warnings but basically it seems to
work.
Parsing...
pro
Am 13.12.2012 um 19:02 schrieb pls :
> Hey all,
>
> I just discovered a command line option that is not mentioned in the docs:
> It's possible to append "landscape" to a paper size, e.g.
>
> $ lilypond -dpaper-size=\"a6landscape\" inputfile.ly
>
Hey all,
I just discovered a command line option that is not mentioned in the docs: It's
possible to append "landscape" to a paper size, e.g.
$ lilypond -dpaper-size=\"a6landscape\" inputfile.ly
There are a few error messages and lots of warnings but basically it seems to
work.
Parsing...
pro
Hey all,
in http://code.google.com/p/lilypond/issues/detail?id=3023 I wrote:
I'm not too sure what "Automatic scaling to paper size" means
(http://lilypond.org/doc/v2.17/Documentation/notation/paper-size-and-automatic-scaling).
Does it mean that only some \paper variables are scaled to the new
Richard,
you are right it should be 64 divisions but for some reason the result is
correct. So it's not the worst musicxml2ly bug!
Cheers
patrick
Am 07.02.2013 um 10:46 schrieb Richard Lanyon :
> The last note in the file "02a-Rests-Durations.xml" is a dotted 128th note,
> but
> the file is se
Laura,
you are right. For the time being you will have to unzip the file manually and
run musicxml2ly on the .xml file. The conversion with musicxml2ly will be
successful (no error messages) but unfortunately the compilation with LilyPond
(v2.17.15) will fail due to a segmentation fault. (Som
Hi Pavel,
musicxml2ly does not like wrong timing information. The problem here is that
SharpEye 2 obviously has issues with its MusicXML export. SharpEye 2 exported
the wrong duration value in the backup element in the first measure. It also
assigned the f (half note) to the same voice as d
oops, note f should be assigned to 1 and note d to
2 to fix the wrong stem direction.
On 06.07.2013, at 20:58, pls wrote:
> Hi Pavel,
>
> musicxml2ly does not like wrong timing information. The problem here is that
> SharpEye 2 obviously has issues with its MusicXML export.
On 06.07.2013, at 22:26, Pavel Roskin wrote:
> Quoting pls :
>
>> Hi Pavel,
>>
>> musicxml2ly does not like wrong timing information.
>
> That's understandable. What's not understandable is corrupting the rest of
> the output (I mean the lilypond
On 06.07.2013, at 23:18, Pavel Roskin wrote:
> Quoting pls :
>
>>> 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
Hey all,
I think I found a bug. Please have a look at the following example:
\version "2.17.28"
{
R1 |%1
R1 |%2
r2 r4 r8 r16 r32 r64 r128 r128 |%3
}
For no good reason (IINM) there is an automatic line break after the first full
measure rest. The same happens in the first example on
http://
Hey all,
in case this is not a known issue: all examples on
http://www.lilypond.org/doc/v2.17/input/regression/musicxml/collated-files#top
lead to a 404 Not Found Error. It says e.g.
The requested URL /doc/v2.17/input/regression/musicxml/19/lily-4197d4c2.xml
was not found on this server.
On 11.10.2013, at 16:30, Eluze wrote:
> I'm not sure this is a bug, I rather think LP tries to keep the measures
> approximately the same length and in this case it leads to this unlucky
> break.
Hm, but why are there line breaks after every R1? e.g.:
R1*12
r2 r4 r8 r16 r32 r64 r128 r128
The me
On 11.10.2013, at 18:10, Trevor Daniels wrote:
>
> "pls" wrote Friday, October 11, 2013 4:26 PM
>
> Hm, but why are there line breaks after every R1? e.g.:
>
> R1*12
> r2 r4 r8 r16 r32 r64 r128 r128
>
> It's due to the artificial nature of this ex
On 25.11.2013, at 14:34, Kai Lautenschläger wrote:
> As you can see in the following not so tiny example inserting the ambitus
> makes the \RemoveEmptyStaves command ineffective.
I reduced your example quite a bit and the problem is still there:
\RemoveEmptyStaves does not show any effect in sta
On 12.01.2014, at 03:52, Andre Soares wrote:
>> I'm not top posting.
> Hello!
> I have this example file.xml:
>
>
>
>
>
>
>
>
>C
>4
>
>2
>begin
>
Hey all,
looks like we are having a problem with our website. I just got this error in
various browsers (Google Chrome, Firefox and Safari):
The webpage at http://lilypond.org/ has resulted in too many redirects.
Clearing your cookies for this site or allowing third-party cookies may fix the
On 12.01.2014, at 15:27, Federico Bruni wrote:
> 2014/1/12 Federico Bruni
> 2014/1/12 pls
> looks like we are having a problem with our website. I just got this error
> in various browsers (Google Chrome, Firefox and Safari):
>
> yes, my fault:
> https://code.google.
On 12.01.2014, at 13:29, James wrote:
> On 12/01/14 07:57, pls wrote:
>> On 12.01.2014, at 03:52, Andre Soares wrote:
>>
>>>> >>I'm not top posting.
>>
On 12.01.2014, at 18:07, David Kastrup wrote:
> pls writes:
>
>> Hm, it's rather a conversion error of expressive marks in general in
>> combination with manual beaming (see file attached).
>> musicxml2ly places breath marks, dynamics, fermatas, etc. _within_
&g
On 06.04.2014, at 12:49, David Kastrup wrote:
> Nicolas Sceaux writes:
>
>> With lilypond 2.19.3, applying a music function to a bass figure
>> causes a syntax error. At least until 2.17.24 (I have not tested
>> later versions), that was not the case.
>
> 2.19.0 is ok, so I suspect 2.18 woul
Hey all,
if this is a bug it might be related to issue 460: in the following tiny
example no bar numbers are printed in the line after a line break in the middle
of a repeated measure. Obviously the bar numbers are only invisible because
they are counted correctly:
\version "2.19.3"
{
\repe
On 23.05.2014, at 19:39, Jakob Schöttl wrote:
>> I'm not top posting.
>
> LilyPond crashes:
>
>> Starte lilypond-windows.exe 2.18.2 [Eigenes.ly] ...
>> »D:/Daten/Temp/Eigenes.ly« wird verarbeitet
>> Analysieren...
>> Interpretation der Musik...[8][16][24][32][40][48][56][64][72][80]
>> Wurde m
James,
Andreas is right. 01b-Pitches-Intervals.xml was not correct. musicxml2ly is
very tolerant here so the error doesn’t show in the pdf. I
* added missing elements
* fixed a typo in the title
* added missing elements (They represent the actual notated
accidentals. Without these elements
Hm, my attachment obviously got lost on the way…
http://www.musicxml.org/dtds/partwise.dtd";>
Various pitches and interval sizes
All pitch intervals in ascending
jump size.
MusicXML Part
1
0
Hey all,
there seems to be a bug in LilyPond 2.19.14: in the following example the
composer is center-aligned instead of right-aligned:
\version "2.19.14"
\header {
composer = "composer"
}
\score {
c'1
}
hth
patrick
___
bug-lilypond mailing list
Hey all,
yesterday I stumbled across this example in the Learning Manual:
http://lilypond.org/doc/v2.19/Documentation/learning/piano-centered-lyrics. In
my opinion it can and should be simplified. Obviously there’s no need anymore
for a GrandStaff to accept Lyrics. \consists “Bar_engraver” ha
On 25.04.2015, at 16:09, Trevor Daniels wrote:
>
> "pls" wrote Saturday, April 25, 2015 11:31 AM
>
>> yesterday I stumbled across this example in the Learning Manual:
>> http://lilypond.org/doc/v2.19/Documentation/learning/piano-centered-lyrics.
>&g
Hey all,
at http://www.lilypond.org/doc/v2.19/Documentation/extending/scheme-variables
it says:
Note that both the value 2 and the guile prompt guile showed up on the same
line. This can be avoided by calling the newline procedure or displaying a
newline character.
guile> (display a)
On 26.04.2015, at 11:20, David Kastrup wrote:
> pls writes:
>
>> Hey all,
>>
>> at
>> http://www.lilypond.org/doc/v2.19/Documentation/extending/scheme-variables
>> it says:
>>
>> Note that both the value 2 and the guile prompt guile showe
On 26.04.2015, at 11:20, David Kastrup wrote:
> So maybe we should instead advertise
>
> (format #t "~a\n" a)
>
> here? Or put a (begin ...) around this example?
I’d favor the latter because it works without readline and it illustrates an
easy way to combine multiple expressions.
patrick
This looks like a regression to me. See
https://codereview.appspot.com/4176056/ (allow non numeric fingers (e.g. for
thumb))
http://lilypond.org/doc/v2.19/input/regression/dd/lily-caf6e8f6.ly (the “P” is
not printed)
hth
patrick
On 03.05.2015, at 17:35, Stephen MacNeil wrote:
> Hi Harm
> Th
stakes drive me crazy !
>
> Thanks
> Stephen
>
> On Mon, May 4, 2015 at 2:43 AM, pls wrote:
> This looks like a regression to me. See
>
> https://codereview.appspot.com/4176056/ (allow non numeric fingers (e.g. for
> thumb))
> http://lilypond.org/doc/v2.19/input/re
Hi Arnold,
On 05.05.2015, at 14:42, ArnoldTheresius wrote:
> pls wrote
>> ...
>> This line doesn’t show when I use Ghostscript 9.14 to interpret the
>> following file (I obviously had to change some values because PostScript
>> normally uses units of "points"
if applied) other transformation markup
> command (e.g. \scale and \rotate) encapsulating your \postscript markup. The
> current point is set to the coordinate 0 0 (it is not undefined!).
>
>
> pls-2 wrote
>> Hi Arnold,
>> ...
>> True! But why is the result correct in
Hi Jörn,
On 03.05.2015, at 00:23, Jörn Eichler wrote:
>> I'm not top posting.
>
> For music XML input "2" on an eighth note
> of C, musicxml2ly creates "c8 :16" which, I think, is incorrect, because the
> 2 tremolo marks make it a 32th tremolo.
thanks for the report!
Yes, you are right, it’s
On 12.05.2015, at 12:18, James wrote:
> Martin,
>
>
>
> On 11/05/15 23:33, Martin Tarenskeen wrote:
>>
>>
>> On Mon, 11 May 2015, James Lowe wrote:
>>
>>> https://code.google.com/p/lilypond/issues/detail?id=4390
>>
>>
>> Bug reports are a good thing, but is anyone actually working on mus
Hi all,
in another thread I mentioned that I believe that the default vertical
alignment of the fret labels in fret diagrams is currently wrong. The fret
labels appear to be placed one fret above the lowest fret they are referring
to. Carl asked me to post a bug report, so here it is:
\versi
Hi all,
here’s another issue I posted somewhere and Carl answered:
>>
>> P.P.S.: On a different note: some day I would like to get to know the
>> reason why in \chordmode the absolute pitches are one octave higher than
>> in note mode. For chord names correct absolute pitches don¹t matter. But
On 23.05.2015, at 16:57, David Kastrup wrote:
> pls writes:
>
>> Hi all,
>>
>> here’s another issue I posted somewhere and Carl answered:
>>
>>>>
>>>> P.P.S.: On a different note: some day I would like to get to know the
>>>
, at 18:08, Colin Campbell wrote:
> On 2015-05-23 07:58 AM, pls wrote:
>
> Could you re-post with the .PNG attached, please? As a non-guitarist, I think
> a tracker will be clearer with pictures, so I'll set it up as soon as your
> images arrive.
>
> Cheers,
> Colin
*sigh*
On 23.05.2015, at 18:19, pls wrote:
> Colin,
>
> they were attached but obviously got lost on their way. They are actually
> rather small (29 KB and 16 KB) so I haven’t got a clue why they didn’t get
> through. I try it one more time to attach both files. It t
On 23.05.2015, at 18:19, pls wrote:
> Colin,
>
> they were attached but obviously got lost on their way. They are actually
> rather small (29 KB and 16 KB) so I haven’t got a clue why they didn’t get
> through. I try it one more time to attach both files. It that fails aga
On 23.05.2015, at 18:40, David Kastrup wrote:
> pls writes:
>
>> On 23.05.2015, at 16:57, David Kastrup wrote:
>>
>>> pls writes:
>>>
>>>> Hi all,
>>>>
>>>> here’s another issue I posted somewhere and Carl answered:
Hey all,
in chord mode the basic seventh step added to a tonic is the flattened seventh
(e.g. c:1.7). Diminished sevenths and major sevenths can be achieved by
suffixing a '-' or '+' to the number (e.g. c:1.7- or c:1.7+). But this
interpretation changes when the notes extend beyond the range
Hey all,
the following code produces an unwanted capo indication in the first
fret of the fret diagram (thick bar that covers all the strings):
\version "2.19.30"
\markup
\override #'(size . 5)
\override #'(fret-diagram-details . ((finger-code . in-dot)))
\fill-line {
\fret-diagram-v
Hey all,
here is a patch:
>From f7aff314562a1dfa709cef8923ddf1266b9e5a41 Mon Sep 17 00:00:00 2001
From: pls
Date: Sun, 1 Nov 2015 17:40:03 +0100
Subject: [PATCH] Fixed some typos and links.
---
Documentation/contributor/administration.itexi | 15 ++-
Documentation/contributor/
David Kastrup writes:
> While replacing "a a" with "a" seems like a good idea, this is actually
> "a\na" which you replace so you should break the line somewhere close to
> the change. The formatted output will likely be the same, but avoiding
> an overfull source line is better style.
Thanks f
Hi Harm,
looks like fret label values are not computed correctly when
predefined fretboards contain text strings instead of fingering indications.
This small issue only shows when alternate fretboards are defined and
used. That's why my minimal example is not really tiny!
\version "2.19.31"
% Ma
Palmer Ralph writes:
> Greetings Patrick and LilyPonders - Thanks for the report, Patrick. This has
> been
> submitted as issue 4654 : https://sourceforge.net/p/testlilyissues/issues/
> Ralph
Thanks, Ralph!
___
bug-lilypond mailing list
bug-lilypond
Thomas Morley writes:
> 2015-11-06 18:10 GMT+01:00 pls :
>> Palmer Ralph writes:
>>
>>> Greetings Patrick and LilyPonders - Thanks for the report,
>>> Patrick. This has been
>>> submitted as issue 4654 : https://sourceforge.net/p/testlilyissues/iss
Thomas Morley writes:
> 2015-11-07 0:06 GMT+01:00 David Kastrup :
>>>
>>> Let's put relevant info in the issue on the tracker, as I've done right now.
>>> I'd call the info about tablature relevant, ofcourse.
Will do.
>>>
>>> Although, I don't think the bug is triggered by text (vs numbers) or
Hey all,
Compilation with LilyPond v2.15.14 fails when an element of the score header of
a converted MusicXML-file contained a single word directly followed by a
punctuation mark (I tested it with '.', '!', ','. There is no problem with
question marks.). Solution: musicxml2ly should automatical
Hey all,
the command \eyeglasses is neither part of the command index nor of the general
index.
hth
patrick
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Am 21.10.2011 um 16:58 schrieb Neil Puttock:
> On 21 October 2011 15:48, pls wrote:
>
>> the command \eyeglasses is neither part of the command index nor of the
>> general index.
>
> It's documented automatically as a slashed command in both indices:
>
Am 21.10.2011 um 17:51 schrieb David Kastrup:
> Neil Puttock writes:
>
>> On 21 October 2011 16:24, pls wrote:
>>
>>> It's not that it isn't documented. I found it eventually but it's
>>> neither included here
>>>
>>>
Am 22.10.2011 um 07:16 schrieb Colin Campbell:
> I'm not sure what sort of error to look for, Patrick. When I run your file
> on my system, I don't see any errors reported on the console, either from
> musicxml2ly or lilypond itself. The resulting .ly compiles with only one
> error: the lack
Am 22.10.2011 um 13:32 schrieb Reinhold Kainhofer:
> The culprit is:
> [...]
> % The score definition
> \new StaffGroup \with { systemStartDelimiter = #'f } <<
>\new Staff <<
> [...]
>
> Setting systemStartDelimiter to #'f is just plain wrong (it's the symbol "f",
> not the boolean value, an
Hey all,
I tried to compile the following two snippets from the NR:
snippet 1
mynotes = {
c'4 e' g' c'' |
e''4 g'' b'' c'''
}
<<
\new Staff {
\clef treble
\mynotes
}
\new TabStaff {
\contextStringTuning #'custom-tuning
\mynotes
}
>>
Hi David,
thanks for your help and sorry for the noise. I just compiled the 2.15.19 NR
and found the new syntax. Thanks for the interface! Nice work, indeed!
patrick
Am 14.11.2011 um 16:48 schrieb David Kastrup:
> David Kastrup writes:
>
>> pls writes:
>>
>>> H
Hey all,
I guess this is related to Issue 2061
(http://code.google.com/p/lilypond/issues/detail?id=2061). Even though the
status of Issue 2061 is set to fixed long monosyllabic words still collide with
barlines in LilyPond v2.15.27. (Short) syllables don't collide:
\version "2.15.27"
global =
Hey all,
this is a weird one! Chord symbols collide with the staff when the score
contains more than one stanza/verse. For some reason the effect only shows up
after the first line break. It doesn't matter whether it's a manual or
automatic break. Even stranger: there is no collision after the
Hey all,
musicxml2ly v2.15.29 currently does not automatically include a(n)
(out-commented) midi-block in the generated .ly-file when there is
* only one -element.
* a element (with or without a -element).
The latter is true for the file midi-block-part-group.xml (attached) but not
necessari
Hey all,
musicxml2ly v2.15.29 currently places chord symbols below staffs instead of
above.
Will submit a patch asap.
hth
patrick
chordnames-placement-bug.xml
Description: XML document
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://li
Hey all,
musicxml2ly v2.15.29 always converts elements as trill spans, i e
wavy lines are always typeset in combination with a trill mark even when no
trill mark is wanted/requested:
wavy-line.xml
Description: XML document
<>
The correct MusicXML markup for a trill mark in combination with
Hey all,
header elements containing several lines of text including line breaks, e.g.
John Francis Wade (1711–1786)
German: Friedrich Heinrich Ranke (1798–1876)
Latin: John Francis Wade (1711–1786)
are converted by musicxml2ly v2.15.29 into single lines of text without line
breaks,
Hey all,
there can be multiple tags with or without one of the three values
"music", "words" or "arrangement" in the identification element of a score.
musicxml2ly v2.15.29 dumps all of them in the LilyPond variable copyright
without mentioning the type. The content of this variable is typeset
Am 14.02.2012 um 23:13 schrieb -Eluze:
>
>
> pls-2 wrote:
>>
>> Hey all,
>>
>> header elements containing several lines of text including line breaks,
>> e.g.
>>
>> John Francis Wade (1711–1786)
>> German: Friedrich Heinri
It's not a regression. It has never been officially fixed. A while ago I posted
a bug report and a minimal example:
http://old.nabble.com/musicxml2ly%3A-chordnames-placement-bug-td33309393.html.
Here is a solution for the chord symbol bug:
http://codereview.appspot.com/5697059/. I still haven't
Hey all,
in the Internal Reference it says in
http://lilypond.org/doc/v2.15/Documentation/internals/tunable-context-properties:
middleCClefPosition (number)
The position of the middle C, as determined only by the clef. This can be
calculated by looking at clefPosition and clefGlyph.
Shouldn't
Thanks, got it!
Am 12.06.2012 um 17:26 schrieb Reinhold Kainhofer:
> On 12/06/2012 16:00, pls wrote:
>> The position of the clef is two half spaces (-2) below the center of the
>> staff. The position of the middle C is 6 half spaces below the center of the
>> staff. I lo
82 matches
Mail list logo
