Re: musicxml2ly --nd doing what?

> the following musicxml file contains a element, which I > hoped would be ignored if I run musicxml2ly with the --nd option, > but it's not. So either this is a bug, or I misunderstand what is > --nd supposed to do. The term 'direction' has two meanings, which is slightly confusing, I admit: E

Re: musicxml2ly incorrect duration syntax

> Sorry, I should have said that I was using 2.25.12, which I > considered fairly new and didn't bother to download a newer one. For `musicxml2ly`, it really makes a difference, since I'm working on it almost constantly the last few months. Werenr

Re: musicxml2ly incorrect duration syntax

Sorry, I should have said that I was using 2.25.12, which I considered fairly new and didn't bother to download a newer one. You're correct that 2.25.20 produces a valid output. Sorry, I'll be more careful next time. Best, AS

Re: musicxml2ly incorrect duration syntax

> Converting the attached .musicxml file to .ly via musicxml2ly > produces r4*9.0 in voice P3, which LilyPond doesn't like and says > syntax error, unexpected REAL You don't say which version you use... Please try the current development snapshot (i.e., 2.25.21), which has this fixed. BTW, to

Re: musicxml2ly unitialised variable

> Further research is required. In MuseScore 4 (and I guess in MuseScore 3, too) you can select the the output format while saving the file (i.e., selecting the proper file name extension). You have to select 'MusicXML'. This output file should then be readable by `musicxml2ly` (with some hicc

Re: musicxml2ly unitialised variable

On 25/09/2024 14:36, Werner LEMBERG wrote: I am converting a PDF to XML with Musescore and then trying to import it into Lilypond. The original PDF is not the most marvellous, but this fails at the import stage with an "Unbound local variable" error. Your `score.xml` file is not a valid M

Re: musicxml2ly unitialised variable

On 25/09/2024 14:36, Werner LEMBERG wrote: I am converting a PDF to XML with Musescore and then trying to import it into Lilypond. The original PDF is not the most marvellous, but this fails at the import stage with an "Unbound local variable" error. Your `score.xml` file is not a valid M

Re: musicxml2ly unitialised variable

> I am converting a PDF to XML with Musescore and then trying to > import it into Lilypond. The original PDF is not the most > marvellous, but this fails at the import stage with an "Unbound > local variable" error. Your `score.xml` file is not a valid MusicXML file: It contains stuff like ```

Re: musicxml2ly unitialised variable

Hi Raphael, it seems you're using our latest stable version. Could you please give our latest development version a try? The MusicXML import script has been improved a lot meanwhile. http://lilypond.org/development.html Michael Am 25.09.2024 um 13:19 schrieb Raphael Mankin: I am converting a

Re: musicxml2ly: direction element (words+dashes) wrongly converted to markup with trillspan

> I have a musicxml export from Musescore where I have added a > crescendo line “cresc. _ _ _ _ _ _ “ spanning several notes. > > When converting that musicxml to ly (musicxml2ly 2.24.3) it will be > rendered as a trill with span: [...] Please try the current development version of LilyPond inst

Re: musicxml2ly fails on line 824 -> dirty fix

> I'm surprised by your answer as with 2.24.3 there is a clear error > and with the fix I proposed the output is usable (also far from > being perfect). Please define 'usable': I've tried to execute `musicxml2ly` from version 2.24.3 on your input file, and I couldn't process the output `.ly` fil

Re: musicxml2ly fails on line 824 -> dirty fix

Thanks for the answer, I'm surprised by your answer as with 2.24.3 there is a clear error and with the fix I proposed the output is usable (also far from being perfect). Anyway, please don't consider it as a help request, as I'm aware that the file is invalid, but as a bug fix proposal. So if you

Re: musicxml2ly fails on line 824 -> dirty fix

> Hello, I have a file for which `musicxml2ly` fails, because in line > 824 variable `i2` is `None`. Changing line 824 from `if i1 > i2:` > to `if not i2 or i1 > i2:` fixed my issue. > > I'm sorry, but I don't have time to investigate this issue more > (just went in "don't think, fix it mode").

Re: musicxml2ly fails on line 824 -> dirty fix

> Hello, I have a file for which `musicxml2ly` fails, because in line 824 > variable `i2` is `None`. Which LilyPond version? And yes, please provide the input file for testing (you might send it privately to me if necessary). Werner

Re: musicxml2ly chord names

On Mon, Jan 29, 2024 at 12:55 AM Silvain Dupertuis < silvain-dupert...@bluewin.ch> wrote: > I could write an issue... but the webpage did recomment to write a message > first > This is now issue https://gitlab.com/lilypond/lilypond/-/issues/6694 -- Knute Snortum

Re: musicxml2ly chord names

I could write an issue... but the webpage did recomment to write a message first Here is a folder with an example you will find the orignal MuseScore, with it’s PDF and mxl export (mxl is just a compressed archive containing the xml file) and the import into Lilypond plus PDF export https://next

Re: musicxml2ly chord names

On Sun, Jan 28, 2024 at 8:50 AM Silvain Dupertuis < silvain-dupert...@bluewin.ch> wrote: > These first 2 lines of the dictionary for chords in musicxml2ly > contains a faulty 5 for simple major and minor chords > (I discovered it with a conversion from a MuseScore sheet converted into > xml) > > c

Re: musicxml2ly

Il giorno mer 9 nov 2022 alle 09:14:44 +0100, Denis Penard ha scritto: So I use your program musixml2py. It works very well. I would like to have no repetition of note duration, for example if I have four c8, I would like to get c8 c c c in lily. I have studied the python code, but I am not ve

Re: musicxml2ly does not support non-numeric lyric numbers which are (accidentally) allowed by the MusicXML spec

Hello On 11/09/2021 11:52, Hans Aikema via bug-lilypond wrote: Running a MusicXML-to-lilypond conversion for a score I received from the arranger as a Sibelius 8.3.0 MusicXML export (Direct export, not from Dolet) I encoutered breaking errors due to Sibelius’ use of none-numerical lyric number

Re: musicxml2ly does not honour --no-rest-positions option

Am Dienstag, den 28.07.2020, 17:15 +1000 schrieb jostle: > If musicxml2ly is invoked with the '--no-rest-positions' option it still > generates output in the form > > 'c4 \rest' instead of 'r4' > > The following change seems to fix the problem, > > ~/src/lilypond-git$ git diff origin/master > d

Re: musicxml2ly

Am Montag, den 25.05.2020, 16:17 +0200 schrieb Lukas-Fabian Moser: > On Sat, 23 May 2020, Martin Tarenskeen wrote: > > > > There must be something seriously broken if musicxml2ly can't convert > > > > this > > > > > > P.S. I just tried downgrading to lilypond 2.19.84 (from Fedora repo) and > > > t

Re: musicxml2ly

Lukas-Fabian Moser writes: > On Sat, 23 May 2020, Martin Tarenskeen wrote: There must be something seriously broken if musicxml2ly can't convert this >>> P.S. I just tried downgrading to lilypond 2.19.84 (from Fedora repo) and >>> the problem disappeared. So it does look like a regressi

Re: musicxml2ly

On Sat, 23 May 2020, Martin Tarenskeen wrote: There must be something seriously broken if musicxml2ly can't convert this P.S. I just tried downgrading to lilypond 2.19.84 (from Fedora repo) and the problem disappeared. So it does look like a regression to me. Thanks Martin; I’ve opened this tra

Re: musicxml2ly

On Mon, 25 May 2020, Valentin Villenave wrote: Thanks Martin; I’ve opened this tracker page: https://gitlab.com/lilypond/lilypond/-/issues/5994 It seems weird that such a problem wasn’t caught by our pretty-extensive test suite, so I’m wondering what might be particular to your test file. M

Re: musicxml2ly

On 5/23/20, Martin Tarenskeen wrote: > > On Sat, 23 May 2020, Martin Tarenskeen wrote: >> There must be something seriously broken if musicxml2ly can't convert >> this > > P.S. I just tried downgrading to lilypond 2.19.84 (from Fedora repo) and > the problem disappeared. So it does look like a reg

Re: musicxml2ly fails on with multiple

On Tue, 19 May 2020 at 12:18, Valentin Villenave wrote: > As far as I can see it doesn’t break anything from our regression > tests, so unless someone more knowledgeable than me objects, it should > be merged in the next version (2.21.2). Thanks! ___

Re: musicxml2ly fails on with multiple

On 5/18/20, Noam Postavsky wrote: >> > Ping? >> Ping?? > Ping??? Greetings Noam, thanks for being so persistent; I’m not very familiar with musicxml2ly but I submitted your patch here on your behalf: https://gitlab.com/lilypond/lilypond/-/merge_requests/65 As far as I can see it doesn’t break a

Re: musicxml2ly fails on with multiple

On Sun, 26 Apr 2020 at 13:12, Noam Postavsky wrote: > > > The attached example-musicxml-display-part-bug.xml shows a minimal > > > example to trigger the bug. It gives this output: > > > > > get_maybe_exist_typed_child > > > raise "More than 1 child", klass > > > Ping? > Ping?? Ping???

Re: musicxml2ly Pitch Changing Potential Bug

Alex Hansen wrote > I think I have found a bug. The following musicXML, when run through > musicxml2ly, produces lilypond which has entirely different pitches. I've > cut out as much of the XML as possible to ensure it is a minimal example. > Note that the musicXML specifies a single D whole note,

Re: musicxml2ly fails on with multiple

On Tue, 24 Mar 2020 at 18:38, Noam Postavsky wrote: > > On Thu, 5 Mar 2020 at 22:45, Noam Postavsky wrote: > > > > The attached example-musicxml-display-part-bug.xml shows a minimal > > example to trigger the bug. It gives this output: > > > get_maybe_exist_typed_child > > raise "More than 1

Re: musicxml2ly fails on with multiple

On Thu, 5 Mar 2020 at 22:45, Noam Postavsky wrote: > > The attached example-musicxml-display-part-bug.xml shows a minimal > example to trigger the bug. It gives this output: > get_maybe_exist_typed_child > raise "More than 1 child", klass > The original case where I ran into this is > http:/

Re: musicxml2ly unsupported unicode range

> While I am not an apologist for any operating system, I fear folks are being far too quick to blame Windows here. > Like any current operating system concerned with internationalization, Windows and NTFS handles and supports filenames with Unicode characters just fine. There are o

Re: musicxml2ly unsupported unicode range

On 2020-03-06 9:13 am, Torsten Hämmerle wrote: Jean ABOU SAMRA wrote You likely have a special character in the name of your file. Windows handles this poorly and LilyPond (actually Python, behind the scenes) can't do much for this. Try removing special characters from the file name,

Re: musicxml2ly unsupported unicode range

Hi again I could indeed solve the issue by changing the filename to another ;-)) Another issue was that musicxml2ly on windows 10 could not open compressed xml files (zlib module missing). But that it is not a big problem. Uncompressed worked OK. So now I can continue my work with an adapte

Re: musicxml2ly unsupported unicode range

Jean ABOU SAMRA wrote >You likely have a special character in the name of your file. >Windows handles this poorly and LilyPond (actually Python, >behind the scenes) can't do much for this. Try removing >special characters from the file name, it should solve >your problem. I ca

Re: musicxml2ly unsupported unicode range

> Hi > I have for some time as a musicshool teacher been a busy user > of lilypond on my Linux Desktop. Recently my employer have forced > me to work on windows 10. I have got a working setup but > musicxml2ly gives the following error: > > Starting python-windows.exe...

Re: [musicxml2ly] handling empty staffs

On 6/14/19, 9:35 AM, "Florian" wrote: Hi again, Carl Sorensen-3 wrote > I believe that this is less a bug in musicxml2ly and more a limitation of > musicxm2ly. MusicXML and Lilypond have fundamentally different concepts > of the structure of music. These differ

Re: [musicxml2ly] handling empty staffs

Hi again, Carl Sorensen-3 wrote > I believe that this is less a bug in musicxml2ly and more a limitation of > musicxm2ly. MusicXML and Lilypond have fundamentally different concepts > of the structure of music. These differences lead to inability to exactly > render the MusicXML in LilyPond fo

Re: [musicxml2ly] handling empty staffs

On 6/10/19, 12:00 PM, "Florian" wrote: Hi Aaron, Aaron Hill wrote > Seems to be a case of the first context not being alive by the time the > other notes come along. If you manually added some spacer rests of > suitable length to the upper Staff... >

Re: Aw: Re: [musicxml2ly] handling empty staffs

Hi Aaron, Aaron Hill wrote > Seems to be a case of the first context not being alive by the time the > other notes come along. If you manually added some spacer rests of > suitable length to the upper Staff... > > > \context Staff = "1" << >\mergeDifferentlyDottedOn \mergeD

Re: Aw: Re: [musicxml2ly] handling empty staffs

On 2019-06-09 2:14 am, Florian Grundig wrote: ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Seems to be a case of the first context not being alive by the time the other notes come along. If y

Aw: Re: [musicxml2ly] handling empty staffs

StaffErrorExample.ly Description: Binary data StaffErrorExample.musicxml Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [musicxml2ly] handling empty staffs

Hello Florian, On 09/06/2019 09:46, Florian Grundig wrote: Hi Bug Squad, I’ve encountered a very strange behaviour when converting a musicxml file to ly and then to svg… Lilipond version 2.19.83 The musicxml file has two measures in a grand staff with two voices. In the first measure both v

Re: [musicxml2ly] duplicated dynamics and hairpins when using multiple voices

Hi Florian, thanks for your report. Am So., 28. Apr. 2019 um 17:31 Uhr schrieb Florian : > > Hi, > Third attempt via nabble.com :) A remark: Ther are still no _attachments_. You do all inline, with the consequence making it impossible for me to simply download the musicxml-file. In the end I use

Re: [musicxml2ly] duplicated dynamics and hairpins when using multiple voices

Hi, Third attempt via nabble.com :) 1. The musicxml file test.musicxml 2. The generated ly file test.ly 3. Screenshot from generated svg :

Re: [musicxml2ly] duplicated dynamics and hairpins when using multiple voices

Am So., 28. Apr. 2019 um 14:39 Uhr schrieb Florian Grundig : > > Hi, > > I don’t know why the first time sending files to the mailing list didn’t work > - here’e my second attempt - I attached four files: > 1. The musicxml file > 2. The generated ly file > 3,4 The generated svg and pdf file Still

Re: [musicxml2ly] duplicated dynamics and hairpins when using multiple voices

Hi, I don’t know why the first time sending files to the mailing list didn’t work - here’e my second attempt - I attached four files: 1. The musicxml file 2. The generated ly file 3,4 The generated svg and pdf file With kind regards /Florian > On 24 Apr 2019, at 07:23, Federico Bruni wrote:

Re: [musicxml2ly] duplicated dynamics and hairpins when using multiple voices

Hi Florian I can't see your attachments. Can you send them again? Il giorno mar 23 apr 2019 alle 18:54, Florian Grundig ha scritto: Hi all, I’ve encountered a strange behaviour when converting a musicXml document (exported from MuseScore 3.0.5) with two or more voices per staff in combinat

Re: musicxml2ly produces unexpected EOF in .ly file

Knut On 27/08/18 16:14, Federico Bruni wrote: Il giorno dom 26 ago 2018 alle 16:12, David Kastrup ha scritto: Victor Rouanet writes:  Le 26/08/2018 à 15:15, Victor Rouanet a écrit :  Same result for me. According to Phil Homes in the lilypond-user  topic, the shlex module (used by musi

Re: musicxml2ly produces unexpected EOF in .ly file

Il giorno dom 26 ago 2018 alle 16:12, David Kastrup ha scritto: Victor Rouanet writes: Le 26/08/2018 à 15:15, Victor Rouanet a écrit : Same result for me. According to Phil Homes in the lilypond-user topic, the shlex module (used by musicxml2ly in utilities.py) didn't support unico

Re: musicxml2ly produces unexpected EOF in .ly file

Victor Rouanet writes: > Le 26/08/2018 à 15:15, Victor Rouanet a écrit : >> Same result for me. According to Phil Homes in the lilypond-user >> topic, the shlex module (used by musicxml2ly in utilities.py) didn't >> support unicode input prior to Python 2.7.3. > According to David Wright* > I mis

Re: musicxml2ly produces unexpected EOF in .ly file

Le 26/08/2018 à 15:15, Victor Rouanet a écrit : Same result for me. According to Phil Homes in the lilypond-user topic, the shlex module (used by musicxml2ly in utilities.py) didn't support unicode input prior to Python 2.7.3. According to David Wright* I misread. _

Re: musicxml2ly produces unexpected EOF in .ly file

Le 26/08/2018 à 12:56, Federico Bruni a écrit : Victor, please keep the list in Cc. Sorry, newbie error :-) I was using lilypond packaged by Fedora, which uses python2 installed on the system (currently 2.7.15). I've now installed 2.19.82 from lilypond.org, which uses the bundled python .

Re: musicxml2ly produces unexpected EOF in .ly file

Victor, please keep the list in Cc. I was using lilypond packaged by Fedora, which uses python2 installed on the system (currently 2.7.15). I've now installed 2.19.82 from lilypond.org, which uses the bundled python . There's something wrong: $ file jafanosumu.ly jafanosumu.ly: data There's

Re: musicxml2ly produces unexpected EOF in .ly file

Il giorno ven 24 ago 2018 alle 12:11, Paul Hodges ha scritto: I was planning to report this. What's happening is that strings are being converted to 16-bit Unicode instead of UTF8, and so they are interspersed with nulls. If you remove the nulls with a capable editor, then that issue goe

Re: musicxml2ly produces unexpected EOF in .ly file

I was planning to report this.  What's happening is that strings are being converted to 16-bit Unicode instead of UTF8, and so they are interspersed with nulls.  If you remove the nulls with a capable editor, then that issue goes away (you can do it with Frescobaldi, but it's non-intuitive - cop

Re: musicxml2ly produces unexpected EOF in .ly file

Il giorno ven 24 ago 2018 alle 11:33, Victor Rouanet <"victor.rouanet"@gmx.fr> ha scritto: Good morning, I'm having an issue with musicxml2ly, installed with a manually downloaded version on lilypond 2.19.82. I exported a musicxml file from Musescore, then converted it to lilypond source

Re: musicxml2ly writes UTF16 BE in header texts

"Tobias Kretschmar" wrote in message news:loom.20160714t222848-...@post.gmane.org... musicxml2ly 2.19.45 writes any header text (and some more) as UTF16 BE in the ly file. This will lead to errors when running lilypond with this file. error: EOF found inside string error: syntax error, unexpec

Re: musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'

Alright, by adding the lines I had to remove from Reunion.xml to the "Hello World" example from the MusicXML tutorial, I managed to reproduce this traceback with a much smaller example. Of course, I don't know enough MusicXML to tell if the result is supposed to make sense or not; it's kind of nons

Re: musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'

Attaching the MusicXML file, since musescore.com requires an account for downloads. Copyright © 2012 Marc Sabatella Licensed under the Creative Commons Attribution 3.0 License On Tue, Jun 14, 2016 at 7:12 PM, Dag Odenhall wrote: > Sorry, I utterly failed to mention that I'm on LilyPond 2.19.43.

Re: musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'

Sorry, I utterly failed to mention that I'm on LilyPond 2.19.43. Tested both with the binaries from the website and the Fedora 23 package. On Tue, Jun 14, 2016 at 7:11 PM, Dag Odenhall wrote: > Hello list, > > I get this traceback trying to convert the Reunion demo score from > MuseScore: > > mu

Re: musicxml2ly doesn't handle nested tuplets

On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska wrote: > When dealing with export of nested tuplets to MusicXML ( > https://github.com/wbsoft/python-ly/issues/25) I realized that the > exported MusicXML can be properly read by Finale but not be reimported > through musicxml2ly. > > https://github.com/

Re: musicxml2ly doesn't handle nested tuplets

Am 05.06.2015 um 15:09 schrieb Urs Liska: I can't tell from the LilyPond documentation whether MusicXML - either >import, export, or both - is explicitly supported by LilyPond. Before I >submit this as an issue, can someone please confirm for me that >LilyPond >does support MusicXML? Well, the

Re: musicxml2ly doesn't handle nested tuplets

Am 5. Juni 2015 13:55:04 MESZ, schrieb Ralph Palmer : >On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska wrote: > >> When dealing with export of nested tuplets to MusicXML ( >> https://github.com/wbsoft/python-ly/issues/25) I realized that the >> exported MusicXML can be properly read by Finale but not

Re: musicxml2ly doesn't handle nested tuplets

On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska wrote: > When dealing with export of nested tuplets to MusicXML ( > https://github.com/wbsoft/python-ly/issues/25) I realized that the > exported MusicXML can be properly read by Finale but not be reimported > through musicxml2ly. > > https://github.com/

Re: musicxml2ly tremolo tag on notes shorter than quarter

On Tue, 12 May 2015, pls wrote: For example what happened with the Philomenos musixcml2ly-dev fork? Yes, Philomelos is still alive and I’m about to update the musicxml2ly-dev Github repo.  Over at least three years I have written almost 100 bug reports  and many test cases for

Re: musicxml2ly tremolo tag on notes shorter than quarter

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

Re: musicxml2ly tremolo tag on notes shorter than quarter

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 musicxml2ly? For example what happened with the Philomenos musixcml2ly-d

Re: musicxml2ly tremolo tag on notes shorter than quarter

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 musicxml2ly? For example what happened with the Philomenos musixcml2ly-dev fork? -- MT __

Re: musicxml2ly tremolo tag on notes shorter than quarter

On 07/05/15 23:21, pls wrote: > 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. > > tha

Re: musicxml2ly tremolo tag on notes shorter than quarter

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

Re: [musicxml2ly] breath mark inside beam

On 12/01/14 17:50, pls wrote: 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_ manual beam br

Re: [musicxml2ly] breath mark inside beam

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_ >> manual beam brackets instead of

Re: [musicxml2ly] breath mark inside beam

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_ > manual beam brackets instead of _after_ the right square bracket. Most of that is total

Re: [musicxml2ly] breath mark inside beam

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. >>> >Hello! >>> >I have this example file.xml: >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> >

Re: [musicxml2ly] breath mark inside beam

On 12/01/14 07:57, pls wrote: 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 >

Re: [musicxml2ly] breath mark inside beam

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 >

Re: musicxml2ly output indentation style

Hello, 2013/11/27 Martin Tarenskeen > The *.ly files that are produced using musicxml2ly use an indentation > style that does not conform to LilyPond's common practice. > > Musicxml2ly does not un-indent closing brackets. > > Thank you for the report, this has been added as http://code.google.co

Re: musicxml2ly stops making chords after some timing errors

"Pavel Roskin" wrote in message news:20130706171855.91mxat93pycg440g-ceb...@webmail.spamcop.net... 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 markup yo

Re: musicxml2ly stops making chords after some timing errors

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 markup you provided. the first >> measure co

Re: musicxml2ly stops making chords after some timing errors

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 markup you provided. the first measure contained the duration of five quarter notes instead of four. t

Re: musicxml2ly stops making chords after some timing errors

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 input, not just the pdf). > >> The problem

Re: musicxml2ly stops making chords after some timing errors

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 input, not just the pdf). The problem here is that SharpEye 2 obviously has issues with its MusicXML e

Re: musicxml2ly stops making chords after some timing errors

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. SharpEye 2 > expo

Re: musicxml2ly stops making chords after some timing errors

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

Re: [musicxml2ly] beams and lost lyric syllables

Hello, 2012/10/6 pls > I forgot to mention that syllables don't get lost when musicxml2ly is used > with the option --no-beaming. But this is only a dirty workaround as > LilyPonds' autobeaming algorithm overrides the beaming information provided > by the .xml-file. Beyond that we implemented a

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

Hello, 2012/10/3 pls > > now the summaries and descriptions of the issues got mixed up. I suggest > the following: > > Issue 2879: [musicxml2ly] spurious staff > if an .xml file contains only elements with value "1" (i.e. > 1) AND no element in a chorded note musicxml2ly > erroneously thinks th

Re: [musicxml2ly] beams and lost lyric syllables

I forgot to mention that syllables don't get lost when musicxml2ly is used with the option --no-beaming. But this is only a dirty workaround as LilyPonds' autobeaming algorithm overrides the beaming information provided by the .xml-file. Beyond that we implemented a new musicxml2ly feature to

Re: [musicxml2ly] middle syllables aligned to slurred notes get lost

thanks for the report, Patrick this has been added as https://code.google.com/p/lilypond/issues/detail?id=2881&thanks=2881&ts=1349439027 to the tracker Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/musicxml2ly-middle-syllables-aligned-to-slurred-notes-get-lost-t

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

Hi Marek, now the summaries and descriptions of the issues got mixed up. I suggest the following: Issue 2879: [musicxml2ly] spurious staff if an .xml file contains only elements with value "1" (i.e. 1) AND no element in a chorded note musicxml2ly erroneously thinks that there are several sta

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

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://code.google.com/p/lilypond/issues/detail?id=2879 - please, check it. It is not easy for me to create proper tracker issue for the first

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

Hello, 2012/9/30 pls > My test files obviously got lost. :( > Am 29.09.2012 um 14:24 schrieb pls: > > There is no new bug report here I gues, am I right? Could you please add comment to the issue, instead of writing to bug-lilypond after the issue was added? Marek, bug squad member _

Re: [musicxml2ly] wrong durations in chorded notes with time-modifications

Hello, 2012/9/30 pls > 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)

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

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 >>> -element causes an additional empty staff above

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

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: >> >> >> (unwanted) result: >> >> >> The w

Re: [musicxml2ly] unwanted staves and voices [was: missing -element in chorded note leads to unwanted additional staff]

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. > > In this case musicxml2ly pu

Re: [musicxml2ly] missing -element in chorded note leads to unwanted additional staff

Hello, 2012/9/28 pls > A -element containing a - and a -element but no > -element causes an additional empty staff above the defined one. > > musicxml2ly should be taught to be tolerant and automatically assign notes > containing -elements to the voice of the first note of the chord. > (This f

Re: musicxml2ly

On Wed, May 16, 2012 at 10:42:09AM +0200, pls wrote: > > 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 s

Re: musicxml2ly

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

Re: musicxml2ly

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 printe

  1   2   >