Re: MEI to MusicXML

[Werner LEMBERG]

>> Thanks for the link(s) to this repository, and sorry for the very
>> late reply.  I'm going to try
>> 
>>  https://github.com/cemfi/meico
>> 
>> which uses the 'music-encoding' XLST stylesheets, AFAIK, and,
>> according to the release news (from last week) is now able to read
>> and write MusicXML – let's see how this will work!  I still have
>> some Java issues, but I guess this can be ironed out soon.
> 
> Java is my native habitat, so if you need assistance in ironing out
> issues feel free to reach out.

Thanks for your kind offer!  On my OpenSUSE box I could make Meico
start after installing 'java-1_8_0-openjdk' and 'java-1_8_0-openjfx'.
It doesn't seem to work properly, though, but I won't pursue this
further due to lack of interest.

While the GUI has already support for MEI to MusicXML conversion, the
functionality for it is actually still missing, unfortunately.  I was
told that the Verovio developers are working on a MEI to MusicXML
plugin for MuseScore, to be published in autumn – if I get more
information I will share it here.


Werner

Re: MEI to MusicXML

[Hans Aikema]

> On 25 May 2023, at 10:47, Werner LEMBERG  wrote:
> 
> 
> Hello Jean and Silvain,
> 
> 
>>> for a blind student of mine I would like to convert MEI files from
>>> the Digital Mozart Edition
>>> 
>>> https://dme.mozarteum.at/movi/en
>>> 
>>> to MusicXML, which he can convert to something readable on his
>>> Braille terminal.
>>> 
>>> Any idea how to do that?
>> 
>> Apparently there is this tool, no idea how well developed or
>> maintained it is: https://github.com/music-encoding/encoding-tools
> 
> Thanks for the link(s) to this repository, and sorry for the very
> late reply.  I'm going to try
> 
>  https://github.com/cemfi/meico
> 
> which uses the 'music-encoding' XLST stylesheets, AFAIK, and,
> according to the release news (from last week) is now able to read and
> write MusicXML – let's see how this will work!  I still have some Java
> issues, but I guess this can be ironed out soon.

Java is my native habitat, so if you need assistance in ironing out issues feel 
free to reach out

Re: MEI to MusicXML

[Werner LEMBERG]

Hello Jean and Silvain,


>> for a blind student of mine I would like to convert MEI files from
>> the Digital Mozart Edition
>>
>>  https://dme.mozarteum.at/movi/en
>>
>> to MusicXML, which he can convert to something readable on his
>> Braille terminal.
>>
>> Any idea how to do that?
>
> Apparently there is this tool, no idea how well developed or
> maintained it is: https://github.com/music-encoding/encoding-tools

Thanks for the link(s) to this repository, and sorry for the very
late reply.  I'm going to try

  https://github.com/cemfi/meico

which uses the 'music-encoding' XLST stylesheets, AFAIK, and,
according to the release news (from last week) is now able to read and
write MusicXML – let's see how this will work!  I still have some Java
issues, but I guess this can be ironed out soon.


Werner

Re: MEI to MusicXML

[Silvain Dupertuis]

I have no idea...
but when I record an HTML page, I can see that the score is hard encoded in SVG format 
(must be created by a JavaScript library from an MEI file), and it contains this information:
/The present encoding in MEI 4.0.1 (with some minor customizations) is based on a previous 
encoding in DOX format. The DOX data were gained from optical music recognition (OMR) and 
proofreading processes developed and carried out by The Packard Humanities Institute, Los 
Altos, CA./

/
/
I tried to look at/
/
https://music-encoding.org/

Maybe something can be found at this page:
https://music-encoding.org/resources/tools.html

I only find conversion tools the other way...
https://www.verovio.org/musicxml.html

This page indicate scripts for both ways...
https://github.com/gburlet/musicxml-mei-conversion






Le 28.04.23 à 10:18, Werner LEMBERG a écrit :

Folks,


for a blind student of mine I would like to convert MEI files from the
Digital Mozart Edition

   https://dme.mozarteum.at/movi/en

to MusicXML, which he can convert to something readable on his Braille
terminal.

Any idea how to do that?


 Werner



--
Silvain Dupertuis
Route de Lausanne 335
1293 Bellevue (Switzerland)
tél. +41-(0)22-774.20.67
portable +41-(0)79-604.87.52
web: silvain-dupertuis.org <https://perso.silvain-dupertuis.org>

Re: MEI to MusicXML

[Jean Abou Samra]

> Le 28 avr. 2023 à 10:19, Werner LEMBERG  a écrit :
> 
> 
> Folks,
> 
> 
> for a blind student of mine I would like to convert MEI files from the
> Digital Mozart Edition
> 
>  https://dme.mozarteum.at/movi/en
> 
> to MusicXML, which he can convert to something readable on his Braille
> terminal.
> 
> Any idea how to do that?


Apparently there is this tool, no idea how well developed or maintained it is: 
https://github.com/music-encoding/encoding-tools

MEI to MusicXML

[Werner LEMBERG]

Folks,


for a blind student of mine I would like to convert MEI files from the
Digital Mozart Edition

  https://dme.mozarteum.at/movi/en

to MusicXML, which he can convert to something readable on his Braille
terminal.

Any idea how to do that?


Werner

Re: MusicXML and Lilypond, any news?

[Andrew Bernard]

Hello Omer,

This has become a sort of FAQ. Lilypond does not fully support MusicXML 
and Frescobaldi's support is also experimental. That's due to limited 
resources of the development team, and because implementing a 
spectacularly good MusicXML export does not actually benefit the core 
functionality of Lilypond, which is ,ore important to do at this stage. 
Export mostly only benefits other programs and user of those programs. 
That is why this does not have a lot of development. The other comment I 
would make is that MusicXML has a lot of known limitations and never 
turned into the global and universal music interchange format that was 
hoped for, like PDF is for documents. That's because music is vastly 
more complex that text documents and there is much that it misses out 
on. I don't think this situation is going to change.


You'll find similar threads on the Dorico forum - even the Steinberg 
development team for that product does not have the resources for 
MusicXML full support and ongoing development.


Sadly a lot of 'big name' publishing houses want MusicXML from composers 
(and they want the composers to do the work now!), as they don't use 
Dorico or Lilypond and so on. This is all very unsatisfactory.


Not that it answers your question directly, but some people find 
MuseScore has reasonable MusicXML capabilities.


Andrew

On 11/10/2022 3:29 am, Omer Katzir wrote:

Is there any news about incorporating MusicXML into Lilypond? I need to share 
my engravings between several people, most aren’t using Lilypond. I know 
there’s musicxml2ly but I need it the other way around.

Thanks in advance for any tips.

Re: MusicXML and Lilypond, any news?

[Jean Abou Samra]

Le 10/10/2022 à 18:29, Omer Katzir a écrit :

Is there any news about incorporating MusicXML into Lilypond? I need to share 
my engravings between several people, most aren’t using Lilypond. I know 
there’s musicxml2ly but I need it the other way around.

Thanks in advance for any tips.



The latest thread about this was not very long ago, you could start by 
reading this.


https://lists.gnu.org/archive/html/lilypond-user/2022-10/msg00014.html

Best,
Jean

MusicXML and Lilypond, any news?

[Omer Katzir]

Is there any news about incorporating MusicXML into Lilypond? I need to share 
my engravings between several people, most aren’t using Lilypond. I know 
there’s musicxml2ly but I need it the other way around. 

Thanks in advance for any tips.

Re: Musescore/musicxml questions

[Kira Garvie]

Thank you, Jacques! That does help.
I work with this system, that creates both printable online files and
downloadable xml files, but lately I have been having formatting issues...
I wish we used something other than MuseScore! (Lilypond is used for a
different part of the project!)
https://my.hymnary.org/song/62/o-come-all-ye-faithful?header=auto=full=None;

On Thu, Jun 30, 2022 at 4:44 PM Jacques Menu  wrote:

> Hello Kira,
>
> I’ve looked at the two files you posted, and the MusicXML export is
> actually not reflecting the exact layout of the original.Converting it to
> LilyPond with xml2ly gives the same layout as when the exported file is
> re-imported in Musecore.
>
> This is a difficult issue at any rate, to be submitted to the MuseScore
> team at https://musescore.com/user/login?destination=%2Fcas%2Flogin.
>
> HTH!
>
> JM
>
> > Le 30 juin 2022 à 18:50, Kira Garvie  a écrit :
> >
> > Hey all,
> > I know this is a bit off-topic but it's on-topic for me... also I don't
> know who else to ask, the muse-score forums aren't very helpful.
> > I use Lilypond, Musescore, and musicxml files for my work. Please, no
> comments on the quality of Musescore, the decision to use it was above my
> paygrade. I am having issues exporting an xml file and having it keep its
> formatting. Is there anyone who has experience with this and can help me
> off the list? Or should I just can it and keep googling stuff until I
> stumble on an answer?
> > Here are the files.
> > Thank you!
> > 
>
>

Re: Musescore/musicxml questions

[Jacques Menu]

Hello Kira,

I’ve looked at the two files you posted, and the MusicXML export is actually 
not reflecting the exact layout of the original.Converting it to LilyPond with 
xml2ly gives the same layout as when the exported file is re-imported in 
Musecore.

This is a difficult issue at any rate, to be submitted to the MuseScore team at 
https://musescore.com/user/login?destination=%2Fcas%2Flogin.

HTH!

JM

> Le 30 juin 2022 à 18:50, Kira Garvie  a écrit :
> 
> Hey all,
> I know this is a bit off-topic but it's on-topic for me... also I don't know 
> who else to ask, the muse-score forums aren't very helpful.
> I use Lilypond, Musescore, and musicxml files for my work. Please, no 
> comments on the quality of Musescore, the decision to use it was above my 
> paygrade. I am having issues exporting an xml file and having it keep its 
> formatting. Is there anyone who has experience with this and can help me off 
> the list? Or should I just can it and keep googling stuff until I stumble on 
> an answer? 
> Here are the files.
> Thank you!
> 

Re: Musescore/musicxml questions

[Karlin High]

On 6/30/2022 11:50 AM, Kira Garvie wrote:

I am having issues exporting an xml file and having it keep its formatting.


Can you further describe the workflow, source and destination of the export?
--
Karlin High
Missouri, USA

Musescore/musicxml questions

[Kira Garvie]

Hey all,
I know this is a bit off-topic but it's on-topic for me... also I don't
know who else to ask, the muse-score forums aren't very helpful.
I use Lilypond, Musescore, and musicxml files for my work. Please, no
comments on the quality of Musescore, the decision to use it was above my
paygrade. I am having issues exporting an xml file and having it keep its
formatting. Is there anyone who has experience with this and can help me
off the list? Or should I just can it and keep googling stuff until I
stumble on an answer?
Here are the files.
Thank you!


SSS2019-13.musicxml
Description: Binary data


SSS2019-13.mscz
Description: application/musescore

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jan-Peter Voigt]

> Am 08.10.2021 um 12:04 schrieb David Kastrup :
> 
> Jan-Peter Voigt  writes:
> 
>> Hi all,
>> 
>> probably what I am writing now is not new to most of you. About a year
>> ago there was a discussion regarding the license of Lilypond, triggered
>> by Urs' question about the future of OLL. Again and again the
>> documentation was referred to, which says that Lilypond is a compiler
>> that translates the source code into a PDF. For God's sake, I don't want
>> to discuss the licensing consequences again, but I want to point out
>> that this representation is not exactly complete. In fact, each source
>> file is translated into a Lilypond internal executable, the execution of
>> which then generates the PDF.
> 
> Uh, no?  Calling LilyPond's internal representation of music an
> "executable" is nonsensical since it does not imply any actions but is a
> structural representation of music.
Ok, my designation as internal executable is certainly not a good picture.
My point is that this process is not a pure translation language A to language 
B.
Whatsoever, this is not the topic I want to discuss.
> There never is any linear
> representation being "executed", and source files are interpreted rather
> than compiled, with no file-level representation ever being explicit.
Well at least a (Scheme) Engraver can be used to instruct that a note head be
painted red if it is the third moment in the measure. Alternatively, this 
information
can be given to each affected notehead via override. The source file is 
interpreted,
as you write, and not compiled, as written in the documentation.
(https://lilypond.org/windows.html, https://lilypond.org/macos-x.html, 
https://lilypond.org/unix.html: "Compiling a file")
> That's not an academic difference since it is a non-trivial question
> just what the structure of a MusicXML file is supposed to represent from
> a given LilyPond input file.
Yes, that is essentially what I wanted to say.

Jan-Peter

Re: Export from LilyPond to MusicXML (Thomas Morley)

[David Kastrup]

Jan-Peter Voigt  writes:

> Hi all,
>
> probably what I am writing now is not new to most of you. About a year
> ago there was a discussion regarding the license of Lilypond, triggered
> by Urs' question about the future of OLL. Again and again the
> documentation was referred to, which says that Lilypond is a compiler
> that translates the source code into a PDF. For God's sake, I don't want
> to discuss the licensing consequences again, but I want to point out
> that this representation is not exactly complete. In fact, each source
> file is translated into a Lilypond internal executable, the execution of
> which then generates the PDF.

Uh, no?  Calling LilyPond's internal representation of music an
"executable" is nonsensical since it does not imply any actions but is a
structural representation of music.  There never is any linear
representation being "executed", and source files are interpreted rather
than compiled, with no file-level representation ever being explicit.

That's not an academic difference since it is a non-trivial question
just what the structure of a MusicXML file is supposed to represent from
a given LilyPond input file.

-- 
David Kastrup

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jan-Peter Voigt]

Hi all,

probably what I am writing now is not new to most of you. About a year
ago there was a discussion regarding the license of Lilypond, triggered
by Urs' question about the future of OLL. Again and again the
documentation was referred to, which says that Lilypond is a compiler
that translates the source code into a PDF. For God's sake, I don't want
to discuss the licensing consequences again, but I want to point out
that this representation is not exactly complete. In fact, each source
file is translated into a Lilypond internal executable, the execution of
which then generates the PDF. This architecture is representable in XML,
if it is possible at all, only with extensions to MEI or MusicXML. So
the goal should only be to implement the graphical representation
accordingly.
But this also means that structures that serve a better organization of
the lilypond source code will most likely be lost during export and
re-import.

Several solutions for the export have now been mentioned. Behind these
are three concepts, all of which have their justification:
1. convert source-based (python-ly accessible through frescobaldi).
2. lilypond internal generation of an intermediate code
3. scheme based generation of an intermediate code

If the sources comply, i.e. do not contain Scheme, then the python-ly
solution is quite charming, fast and batchable. But I would find the
internal generation of an intermediate code, as envisioned and developed
by Jacques, the nicest. The Scheme based solution I started from the
pragmatic consideration that if it works, it can be quickly adapted and
deployed in different environments.

I'm very glad to see this discussion revisited. Maybe something more can
be developed together in this direction. For this reason, I am also
pushing the discussion to the devel list. ;-)

I'll be on the road for the next week, but I plan to get back to the
topic after that.

Cheers,

Jan-Peter


Am 07.10.21 um 22:51 schrieb Thomas Morley:
> Am Do., 7. Okt. 2021 um 13:32 Uhr schrieb Jean Abou Samra 
> :
>>
>> Harm,
>>
>> Le 07/10/2021 à 11:46, Thomas Morley a écrit :
>>> Not sure Jan-Peter's approach is the best method ...
>>
>> What makes you think so?
>>
>> Best,
>> Jean
>
> Maybe my wording was misleading.
>
> I tested ly->musicxml with
> (1) openlilylib, i.e. Jan-Peter
> (2) python-ly
> (3) Frescobaldi
> (4) https://github.com/de-wolff/lilypond.git
>
> Then tried reimporting the resulting xml-file via
> (a) musicxml2ly
> (b) xml2ly
>
> All results were terrible. Here I stopped frustrated.
> I did not look into any code, thus I simply don't know which one is
> the most promising approach.
>
> Cheers,
>   Harm
>

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jan-Peter Voigt]

Hello Peter, and all,

I spotted the problem with the OLL export-solution in 2.22+:
In api.scm ll. 278,279 the call to ly:grob-properties fails. In that
acknowledger block the stem direction is recorded. I'll look how to fix
that later. If you like to try it out, you can temporarily just delete
or comment that block (ll. 274-281).

Cheers,

Jan-Peter

Am 07.10.21 um 11:49 schrieb Jan-Peter Voigt:
> Hello Peter,
>
> yes, I still receive the messages from the list, but since I have
> changed jobs, my commitment to Lilypond has fallen behind a bit.
> But I hope to curate and update my code soon so that it can serve as a
> starting point for further development. Of course, Jacque's work should
> not be lost sight of, as native support would be nice. But maybe the
> scheme-engraver based solution can push the issue a bit.
> This topic has been on my mind for quite some time. Since Lilypond does
> not offer XML export, its use is problematic in many areas. If I want to
> offer something to a publisher, I can't get anywhere with Lilypond in
> most cases. If I want to archive the notes in a structured way, I can
> come up with 1001 solutions in Scheme that fill a database. But if I
> have curated data in MEI format (or MusicXML), I can systematically feed
> a database (e.g. eXist) with it and provide a REST API afterwards to
> build fancy Webapps.
>
> Best regards,
>
> Jan-Peter
>
>
>
> Am 07.10.21 um 11:30 schrieb Peter Toye:
>> The potential need has gone away now - my Sibelius user has told me that
>> he uses ScoreMuse to export the PDF into a suitable format for Sibelius.
>> Looks to me like an expensive way of doing it, but if he can afford
>> Sibelius he can probably afford ScoreMuse as well.
>>
>>  
>>
>> I agree that exchanging music information between different engravers is
>> an extremely complex problem and I don't underestimate the difficulty.
>>
>>  
>>
>> I tried Jan-Peter's code on Github, but it seems to be broken on recent
>> versions of LilyPond. I'm told it works on 19.0  but I don't have
>> that version any more. And I don't have a contact for him to ask - is he
>> on this mailing list?
>>
>>
>> Best regards,
>>
>>
>> Peter
>>
>> mailto:lilyp...@ptoye.com <mailto:lilyp...@ptoye.com>
>>
>> www.ptoye.com <https://www.ptoye.com>
>>
>>
>> -
>>
>> Wednesday, October 6, 2021, 8:05:12 PM, Jean Abou Samra wrote:
>>
>>
>> Le 05/10/2021 à 13:08, Peter Toye a écrit :
>>
>>
>> Sorry - edited subject to get the linking correct
>>
>>
>>  Harm,
>>
>>
>> 
>> https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
>> 
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>
>>  >
>> 
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
>> 
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>>
>>  has
>> > a discussion about this as well. I've started looking at >
>> the OpenLilyLib solution at the bottom of the thread but it
>> doesn't > work on later versions of LilyPond.
>>
>>
>> It would seem to me that using LP's parsing mechanisms is the
>> right > way to go about it, and I'd offer to help if my health
>> allowed. Is > there anyone on this mailing list who knows about it?
>>
>>
>>
>>
>> About the parsing? Certainly, but the potentiel
>> project spans many different areas of LilyPond.
>> And he design space is vast.
>>
>>
>> With Jacques Menu, we some had private discussions
>> about this. It may be feasible to implement XML export
>> by utilizing Jacque's musicformats library (see
>> his post). So far I only have rough ideas about
>> the LilyPond part, and it is not my current priority.
>>
>>
>> I think the most advanced solution so far is Jan-Peter's
>> https://github.com/openlilylib/lilypond-export
>> <https://github.com/openlilylib/lilypond-export>
>> https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html
>> <https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html>
>> (CCing him). One could start off from that.
>>
>>
>> It's something I will probably need soon.
>>
>>
>>
>>
>> By do means do try to help out, but don't
>> hold your breathe for it. It is a large
>> endeavor.
>>
>>
>> Best,
>> Jean
>>
>
>

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jacques Menu]

Hello Thomas,

> Le 7 oct. 2021 à 22:51, Thomas Morley  a écrit :
> 
> Am Do., 7. Okt. 2021 um 13:32 Uhr schrieb Jean Abou Samra 
> :
>> 
>> Harm,
>> 
>> Le 07/10/2021 à 11:46, Thomas Morley a écrit :
>>> Not sure Jan-Peter's approach is the best method ...
>> 
>> What makes you think so?
>> 
>> Best,
>> Jean
> 
> Maybe my wording was misleading.
> 
> I tested ly->musicxml with
> (1) openlilylib, i.e. Jan-Peter
> (2) python-ly
> (3) Frescobaldi
> (4) https://github.com/de-wolff/lilypond.git
> 
> Then tried reimporting the resulting xml-file via
> (a) musicxml2ly
> (b) xml2ly
> 
> All results were terrible. Here I stopped frustrated.
> I did not look into any code, thus I simply don't know which one is
> the most promising approach.

Were the bad results due to 1-4 essentially, or were a and b part of the 
quality problem?

JM

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jean Abou Samra]

Le 07/10/2021 à 22:51, Thomas Morley a écrit :

Am Do., 7. Okt. 2021 um 13:32 Uhr schrieb Jean Abou Samra :

Harm,

Le 07/10/2021 à 11:46, Thomas Morley a écrit :

Not sure Jan-Peter's approach is the best method ...

What makes you think so?

Best,
Jean

Maybe my wording was misleading.

I tested ly->musicxml with
(1) openlilylib, i.e. Jan-Peter
(2) python-ly
(3) Frescobaldi



I thought these two were equivalent — aren't they?



(4) https://github.com/de-wolff/lilypond.git

Then tried reimporting the resulting xml-file via
(a) musicxml2ly
(b) xml2ly

All results were terrible. Here I stopped frustrated.
I did not look into any code, thus I simply don't know which one is
the most promising approach.



If you want my take: Jan-Peter's. Translators are the
only reliable way to get all special timing right (lyrics,
quoted music, combined parts, etc.) without a lot of code
duplication with iterators.

Best,
Jean

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Thomas Morley]

Am Do., 7. Okt. 2021 um 13:32 Uhr schrieb Jean Abou Samra :
>
> Harm,
>
> Le 07/10/2021 à 11:46, Thomas Morley a écrit :
> > Not sure Jan-Peter's approach is the best method ...
>
> What makes you think so?
>
> Best,
> Jean

Maybe my wording was misleading.

I tested ly->musicxml with
(1) openlilylib, i.e. Jan-Peter
(2) python-ly
(3) Frescobaldi
(4) https://github.com/de-wolff/lilypond.git

Then tried reimporting the resulting xml-file via
(a) musicxml2ly
(b) xml2ly

All results were terrible. Here I stopped frustrated.
I did not look into any code, thus I simply don't know which one is
the most promising approach.

Cheers,
  Harm

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jean Abou Samra]

Harm,

Le 07/10/2021 à 11:46, Thomas Morley a écrit :

Not sure Jan-Peter's approach is the best method ...


What makes you think so?

Best,
Jean

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Peter Toye]

Thanks very much Harm, but as I no longer need it, I shan't go ahead. If I need 
it later I'll resurrect this thread.
 
The reason I like Jan-Peter's approach is that it appears to abstract the music 
from the details of presentation. But I've not looked into it much. 


Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Thursday, October 7, 2021, 10:46:44 AM, Thomas Morley wrote:

> Am Do., 7. Okt. 2021 um 11:30 Uhr schrieb Peter Toye :


>> The potential need has gone away now - my Sibelius user has told me that he 
>> uses ScoreMuse to export the PDF into a suitable format for Sibelius. Looks 
>> to me like an expensive way of doing it, but if he can afford Sibelius he 
>> can probably afford ScoreMuse as well.

>> I agree that exchanging music information between different engravers is an 
>> extremely complex problem and I don't underestimate the difficulty.

>> I tried Jan-Peter's code on Github, but it seems to be broken on recent 
>> versions of LilyPond. I'm told it works on 19.0  but I don't have that 
>> version any more. And I don't have a contact for him to ask - is he on this 
>> mailing list?

> Not sure Jan-Peter's approach is the best method ...
> Anyway, applying the following diff makes it work with recent versions
> (although you'll get a bunch of messages):

> ~/openlilylib/lilypond-export (master)$ git diff
> diff --git a/api.scm b/api.scm
> index 8307dc5..3bfa69a 100644
> --- a/api.scm
> +++ b/api.scm
> @@ -275,8 +275,8 @@
>           (let ((musicstep (ly:context-property context ctprop::export-step))
>                 (staff-id (ly:context-property context ctprop::staff-id))
>                 (voice-id (ly:context-property context ctprop::voice-id)))
> -           (ly:message "stem info ~A" (map car (ly:grob-properties grob)))
> -           (tree-set! musicstep `(,staff-id ,voice-id stem dir)
> (ly:grob-properties grob)) ;(ly:stem::calc-direction grob))
> +           (ly:message "stem info ~A" (map car
> (ly:grob-basic-properties grob)))
> +           (tree-set! musicstep `(,staff-id ,voice-id stem dir)
> (ly:grob-basic-properties grob)) ;(ly:stem::calc-direction grob))
>             ))
>          )


> Cheers,
>   Harm

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Peter Toye]

Hello Jan-Peter,
 
As I wrote, my personal immediate need has now gone away.
 
Everyone seems to agree that some form of exchange mechanism between music 
engravers is needed, but there are many different exchange formats and with 
such a complex subject writing an exporter is a really heavy task. I can only 
admire and thank you for your work and hope it can continue. Let's hope that it 
can be done without too many people pulling in different directions. I wish I 
were able to help.


Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-

> Message: 2
> Date: Thu, 7 Oct 2021 11:49:29 +0200
> From: Jan-Peter Voigt 
> To: lilypond-user@gnu.org
> Subject: Re: Export from LilyPond to MusicXML (Thomas Morley)
> Message-ID: 
> Content-Type: text/plain; charset=utf-8

> Hello Peter,

> yes, I still receive the messages from the list, but since I have
> changed jobs, my commitment to Lilypond has fallen behind a bit.
> But I hope to curate and update my code soon so that it can serve as a
> starting point for further development. Of course, Jacque's work should
> not be lost sight of, as native support would be nice. But maybe the
> scheme-engraver based solution can push the issue a bit.
> This topic has been on my mind for quite some time. Since Lilypond does
> not offer XML export, its use is problematic in many areas. If I want to
> offer something to a publisher, I can't get anywhere with Lilypond in
> most cases. If I want to archive the notes in a structured way, I can
> come up with 1001 solutions in Scheme that fill a database. But if I
> have curated data in MEI format (or MusicXML), I can systematically feed
> a database (e.g. eXist) with it and provide a REST API afterwards to
> build fancy Webapps.

> Best regards,

> Jan-Peter



> Am 07.10.21 um 11:30 schrieb Peter Toye:

>> The potential need has gone away now - my Sibelius user has told me that
>> he uses ScoreMuse to export the PDF into a suitable format for Sibelius.
>> Looks to me like an expensive way of doing it, but if he can afford
>> Sibelius he can probably afford ScoreMuse as well.

>>  

>> I agree that exchanging music information between different engravers is
>> an extremely complex problem and I don't underestimate the difficulty.

>>  

>> I tried Jan-Peter's code on Github, but it seems to be broken on recent
>> versions of LilyPond. I'm told it works on 19.0  but I don't have
>> that version any more. And I don't have a contact for him to ask - is he
>> on this mailing list?

>> Best regards,

>> Peter

>> mailto:lilyp...@ptoye.com <mailto:lilyp...@ptoye.com>

>> www.ptoye.com <https://www.ptoye.com>

>> -

>> Wednesday, October 6, 2021, 8:05:12 PM, Jean Abou Samra wrote:

>>     Le 05/10/2021 à 13:08, Peter Toye a écrit :

>>         Sorry - edited subject to get the linking correct

>>          Harm,

>>         
>> https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
>>         
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>
>>  >
>>         
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
>>         
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>>
>>  has
>>         > a discussion about this as well. I've started looking at >
>>         the OpenLilyLib solution at the bottom of the thread but it
>>         doesn't > work on later versions of LilyPond.

>>         It would seem to me that using LP's parsing mechanisms is the
>>         right > way to go about it, and I'd offer to help if my health
>>         allowed. Is > there anyone on this mailing list who knows about it?

>>     About the parsing? Certainly, but the potentiel
>>     project spans many different areas of LilyPond.
>>     And he design space is vast.

>>     With Jacques Menu, we some had private discussions
>>     about this. It may be feasible to implement XML export
>>     by utilizing Jacque's musicformats library (see
>>     his post). So far I only have rough ideas about
>>     the LilyPond part, and it is not my current priority.

>>     I think the most advanced solution so far is Jan-Peter's
>>     https://github.com/openlilylib/lilypond-export
>>     <https://github.com/openlilylib/lilypond-export>
>>     https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html
>>     <https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html>
>>     (CCing him). One could start off from that.

>>         It's something I will probably need soon.

>>     By do means do try to help out, but don't
>>     hold your breathe for it. It is a large
>>     endeavor.

>>     Best,
>>     Jean




> --

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jan-Peter Voigt]

Hello Peter,

yes, I still receive the messages from the list, but since I have
changed jobs, my commitment to Lilypond has fallen behind a bit.
But I hope to curate and update my code soon so that it can serve as a
starting point for further development. Of course, Jacque's work should
not be lost sight of, as native support would be nice. But maybe the
scheme-engraver based solution can push the issue a bit.
This topic has been on my mind for quite some time. Since Lilypond does
not offer XML export, its use is problematic in many areas. If I want to
offer something to a publisher, I can't get anywhere with Lilypond in
most cases. If I want to archive the notes in a structured way, I can
come up with 1001 solutions in Scheme that fill a database. But if I
have curated data in MEI format (or MusicXML), I can systematically feed
a database (e.g. eXist) with it and provide a REST API afterwards to
build fancy Webapps.

Best regards,

Jan-Peter



Am 07.10.21 um 11:30 schrieb Peter Toye:
> The potential need has gone away now - my Sibelius user has told me that
> he uses ScoreMuse to export the PDF into a suitable format for Sibelius.
> Looks to me like an expensive way of doing it, but if he can afford
> Sibelius he can probably afford ScoreMuse as well.
>
>  
>
> I agree that exchanging music information between different engravers is
> an extremely complex problem and I don't underestimate the difficulty.
>
>  
>
> I tried Jan-Peter's code on Github, but it seems to be broken on recent
> versions of LilyPond. I'm told it works on 19.0  but I don't have
> that version any more. And I don't have a contact for him to ask - is he
> on this mailing list?
>
>
> Best regards,
>
>
> Peter
>
> mailto:lilyp...@ptoye.com <mailto:lilyp...@ptoye.com>
>
> www.ptoye.com <https://www.ptoye.com>
>
>
> -
>
> Wednesday, October 6, 2021, 8:05:12 PM, Jean Abou Samra wrote:
>
>
> Le 05/10/2021 à 13:08, Peter Toye a écrit :
>
>
> Sorry - edited subject to get the linking correct
>
>
>  Harm,
>
>
> 
> https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
> 
> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>
>  >
> 
> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
> 
> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>>
>  has
> > a discussion about this as well. I've started looking at >
> the OpenLilyLib solution at the bottom of the thread but it
> doesn't > work on later versions of LilyPond.
>
>
> It would seem to me that using LP's parsing mechanisms is the
> right > way to go about it, and I'd offer to help if my health
> allowed. Is > there anyone on this mailing list who knows about it?
>
>
>
>
> About the parsing? Certainly, but the potentiel
> project spans many different areas of LilyPond.
> And he design space is vast.
>
>
> With Jacques Menu, we some had private discussions
> about this. It may be feasible to implement XML export
> by utilizing Jacque's musicformats library (see
> his post). So far I only have rough ideas about
> the LilyPond part, and it is not my current priority.
>
>
> I think the most advanced solution so far is Jan-Peter's
> https://github.com/openlilylib/lilypond-export
> <https://github.com/openlilylib/lilypond-export>
> https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html
> <https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html>
> (CCing him). One could start off from that.
>
>
> It's something I will probably need soon.
>
>
>
>
> By do means do try to help out, but don't
> hold your breathe for it. It is a large
> endeavor.
>
>
> Best,
> Jean
>

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Thomas Morley]

Am Do., 7. Okt. 2021 um 11:30 Uhr schrieb Peter Toye :
>
> The potential need has gone away now - my Sibelius user has told me that he 
> uses ScoreMuse to export the PDF into a suitable format for Sibelius. Looks 
> to me like an expensive way of doing it, but if he can afford Sibelius he can 
> probably afford ScoreMuse as well.
>
>
>
> I agree that exchanging music information between different engravers is an 
> extremely complex problem and I don't underestimate the difficulty.
>
>
>
> I tried Jan-Peter's code on Github, but it seems to be broken on recent 
> versions of LilyPond. I'm told it works on 19.0  but I don't have that 
> version any more. And I don't have a contact for him to ask - is he on this 
> mailing list?

Not sure Jan-Peter's approach is the best method ...
Anyway, applying the following diff makes it work with recent versions
(although you'll get a bunch of messages):

~/openlilylib/lilypond-export (master)$ git diff
diff --git a/api.scm b/api.scm
index 8307dc5..3bfa69a 100644
--- a/api.scm
+++ b/api.scm
@@ -275,8 +275,8 @@
  (let ((musicstep (ly:context-property context ctprop::export-step))
(staff-id (ly:context-property context ctprop::staff-id))
(voice-id (ly:context-property context ctprop::voice-id)))
-   (ly:message "stem info ~A" (map car (ly:grob-properties grob)))
-   (tree-set! musicstep `(,staff-id ,voice-id stem dir)
(ly:grob-properties grob)) ;(ly:stem::calc-direction grob))
+   (ly:message "stem info ~A" (map car
(ly:grob-basic-properties grob)))
+   (tree-set! musicstep `(,staff-id ,voice-id stem dir)
(ly:grob-basic-properties grob)) ;(ly:stem::calc-direction grob))
))
 )


Cheers,
  Harm

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Peter Toye]

The potential need has gone away now - my Sibelius user has told me that he 
uses ScoreMuse to export the PDF into a suitable format for Sibelius. Looks to 
me like an expensive way of doing it, but if he can afford Sibelius he can 
probably afford ScoreMuse as well.
 
I agree that exchanging music information between different engravers is an 
extremely complex problem and I don't underestimate the difficulty.
 
I tried Jan-Peter's code on Github, but it seems to be broken on recent 
versions of LilyPond. I'm told it works on 19.0  but I don't have that version 
any more. And I don't have a contact for him to ask - is he on this mailing 
list?

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Wednesday, October 6, 2021, 8:05:12 PM, Jean Abou Samra wrote:

> Le 05/10/2021 à 13:08, Peter Toye a écrit :


>> Sorry - edited subject to get the linking correct

>>  Harm,

>> https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
>>  > 
>> <https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706>
>>  has > a discussion about this as well. I've started looking at > the 
>> OpenLilyLib solution at the bottom of the thread but it doesn't > work on 
>> later versions of LilyPond.

>> It would seem to me that using LP's parsing mechanisms is the right > way to 
>> go about it, and I'd offer to help if my health allowed. Is > there anyone 
>> on this mailing list who knows about it?


> About the parsing? Certainly, but the potentiel
> project spans many different areas of LilyPond.
> And he design space is vast.

> With Jacques Menu, we some had private discussions
> about this. It may be feasible to implement XML export
> by utilizing Jacque's musicformats library (see
> his post). So far I only have rough ideas about
> the LilyPond part, and it is not my current priority.

> I think the most advanced solution so far is Jan-Peter's
> https://github.com/openlilylib/lilypond-export
> https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html
> (CCing him). One could start off from that.

>> It's something I will probably need soon.


> By do means do try to help out, but don't
> hold your breathe for it. It is a large
> endeavor.

> Best,
> Jean

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Jean Abou Samra]

Le 05/10/2021 à 13:08, Peter Toye a écrit :


Sorry - edited subject to get the linking correct

 Harm,

https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706 
<https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706> has 
a discussion about this as well. I've started looking at 
the OpenLilyLib solution at the bottom of the thread but it doesn't 
work on later versions of LilyPond.


It would seem to me that using LP's parsing mechanisms is the right 
way to go about it, and I'd offer to help if my health allowed. Is 
there anyone on this mailing list who knows about it?





About the parsing? Certainly, but the potentiel
project spans many different areas of LilyPond.
And he design space is vast.

With Jacques Menu, we some had private discussions
about this. It may be feasible to implement XML export
by utilizing Jacque's musicformats library (see
his post). So far I only have rough ideas about
the LilyPond part, and it is not my current priority.

I think the most advanced solution so far is Jan-Peter's
https://github.com/openlilylib/lilypond-export
https://lists.gnu.org/archive/html/lilypond-devel/2018-10/msg00068.html
(CCing him). One could start off from that.


It's something I will probably need soon.




By do means do try to help out, but don't
hold your breathe for it. It is a large
endeavor.

Best,
Jean

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Peter Toye]

Agreed, but it's possible that someone here might know more about this project 
and now it's getting on.


Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Tuesday, October 5, 2021, 12:53:43 PM, m.tarensk...@kpnmail.nl wrote:

> lilypond-to-musicxml export is a frequentlly asked, but easier said than 
> done, feature request, that pops up from time to time. And everytime it 
> doesn't reach a point beyond discussions and experimental or quite incomplete 
> implementations. Apparently both MusicXML and LilyPond are complex beasts - I 
> am not complaining.

> MT



> Verzonden vanaf mijn Huawei mobiele telefoon

Re: Export from LilyPond to MusicXML (Thomas Morley)

[m.tarensk...@kpnmail.nl]

lilypond-to-musicxml export is a frequentlly asked, but easier said than done, feature request, that pops up from time to time. And everytime it doesn't reach a point beyond discussions and experimental or quite incomplete implementations. Apparently both MusicXML and LilyPond are complex beasts -  I am not complaining.MTVerzonden vanaf mijn Huawei mobiele telefoon

Re: Export from LilyPond to MusicXML (Thomas Morley)

[Peter Toye]

Sorry - edited subject to get the linking correct
 
 Harm,
 
 
https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706
 has a discussion about this as well. I've started looking at the OpenLilyLib 
solution at the bottom of the thread but it doesn't work on later versions of 
LilyPond.
 
It would seem to me that using LP's parsing mechanisms is the right way to go 
about it, and I'd offer to help if my health allowed. Is there anyone on this 
mailing list who knows about it? It's something I will probably need soon.


Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Tuesday, September 28, 2021, 6:58:40 AM, lilypond-user-requ...@gnu.org wrote:


> --

> Message: 2
> Date: Tue, 28 Sep 2021 00:53:16 +0200
> From: Thomas Morley 
> To: Jacques Menu 
> Cc: "lilypond-user Mailing List (lilypond-user@gnu.org)"
>         , Dominique Fober 
> Subject: Re: Export from LilyPond to MusicXML
> Message-ID:
>         
> Content-Type: text/plain; charset="UTF-8"

> Hi Jacques,

> Am Mo., 27. Sept. 2021 um 00:48 Uhr schrieb Jacques Menu
> :


>> Hello folks,

>> The recent posts on this subject show there is interest in the matter. Sorry 
>> for the length of this one...

> Tbh, most of the mor detailed stuff is way over my head..


>> My work was initially homed by Grame’s libmusicxml2 library as an example of 
>> what it could be used for, in the lilypond branch at 
>> https://github.com/grame-cncm/libmusicxml/tree/lilypond.

>> Dom Fober, the author and maintainer of libmusicxml2, and I decided some 
>> time ago to separate things for practical reasons, and I now push to the 
>> GitHub repository I created at https://github.com/jacques-menu/musicformats.

> Good to know.

>> I’m currenly finalizing version 1.0.0, which explains why the test and 
>> master branches are not up to date - only the dev branch is currently.


>> The musicformats library is structured along the lines shown at page 16 in 
>> https://github.com/jacques-menu/musicformats/blob/dev/doc/maintainersGuideToMusicFormats/maintainersGuideToMusicformats.pdf
>>  (the users’s guide is not yet ‘usable’, sorry).

>> The central component of musicformats is MSR (Music Score Representation), 
>> from which various formats can be obtained.

>> In this picture, we see that we could create MusicXML output from within the 
>> LilyPond implementation going along the LilyPond - LPSR - MSR - MXSR  - 
>> MusicMXL path. The missing part would be the creation of an LPSR (LilyPond 
>> Score Representation), the others already exist.

>> As an example, the LPSR representation and LilyPond output produced by:

>> xml2ly basic/HelloWorld.xml -display-lpsr > LPSR_contents.txt 2>&1

>> are in the attached LPSR_contents.txt file.

>> The resulting score is:

>> Jean and I have had discussions as to how the export to MusicXML could be 
>> tackled on the LilyPond side, but nothing concrete yet. Some of the 
>> information needed is readily accessible inside LilyPond, but grabbing the 
>> remaining part is not easy.

>> The musicformats repository contains examples using the library to create 
>> scores in C++ applications, among them:

>> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
>> Mikrokosmos3Wandering -a
>> What Mikrokosmos3Wandering does:

>>     This multi-pass generator creates a textual representation
>>     of Zoltán Kodály's Mikrokosmos III Wandering score.
>>     It performs various passes depending on the output generated.

>>     Other passes are performed according to the options, such as
>>     displaying views of the internal data or printing a summary of the score.

>>     The activity log and warning/error messages go to standard error.

>> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
>> Mikrokosmos3Wandering -apropos generate
>> --- Help for atom "generate" in subgroup "Generated output"
>>     -generate, -gen GENERATED_OUTPUT_KIND
>>           Generate GENERATED_OUTPUT_KIND code to the output.
>>             The 5 generated output kinds available are:
>>             braille, guido, lilypond, midi and musicxml.
>>             The default is 'LilyPond output'.

>> (midi output is actually not yet available, though)

>> For example, one can run:

>> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
>> Mikrokosmos3Wandering -generate  musicxml  -o Mikrokosmos3Wandering.xml 
>> -trace=passes

>> %--
>>   Pass 1: Creating the MSR score

Re: musicXML: 2 staves, piano

[Jacques Menu]

Le 28 sept. 2021 à 07:53, Ivanov Dmitry <usr...@gmail.com> a écrit :What kind of programmed scores handling are you aiming at?Standard piano score with 2 staves and 4 voices: 2 voices per staff.OK, but you mentioned reading/manipulating music with programs, or did I get it wrong?Stangely enough, opening hello2.xml with MuseScore, which displays the score alright, and then exporting it to MusicXML gives the attached hello2_FROM_MUSE_SCORE.xml  which, compiled with musicxml2ly, produces hello2_FROM_MUSE_SCORE.ly. And the latter looks fine once compiled with LilyPond… The only real difference are the extra  elements, which shouldn’t matter.That beats me...JM

hello2_FROM_MUSE_SCORE.xml
Description: XML document


hello2_FROM_MUSE_SCORE.ly
Description: Binary data


hello2_FROM_MUSE_SCORE.pdf
Description: Adobe PDF document

Re: musicXML: 2 staves, piano

[Ivanov Dmitry]

What kind of programmed scores handling are you aiming at?


Standard piano score with 2 staves and 4 voices: 2 voices per staff.


signature.asc
Description: PGP signature

Re: musicXML: 2 staves, piano

[Jacques Menu]

Hello Dmitry,

It looks like you’re struggling with the tools instead of going ahead using 
them. 

What kind of programmed scores handling are you aiming at? There are various 
ways, such as python-ly (https://pypi.org/project/python-ly/), ABC notation 
(https://en.wikipedia.org/wiki/ABC_notation) or Humdrum **kern, see 
http://kern.ccarh.org. 

If LilyPond is the answer, much can be done with Scheme.

JM

> Le 28 sept. 2021 à 00:44, Thomas Morley  a écrit :
> 
> Am Mo., 27. Sept. 2021 um 17:05 Uhr schrieb Ivanov Dmitry :
>> 
>> Something is not right. I installed lilypond 2.23.3 and processed
>> hello2.xml. I still have an incorrect result.
>> 
>> Here is what I do and what I get:
>> 
>> $ musicxml2ly ./hello2.xml
>> musicxml2ly: Reading MusicXML from ./hello2.xml ...
>> musicxml2ly: Converting to LilyPond expressions...
>> musicxml2ly: warning: Negative skip -1/2 (from position 1/2 to 0)
>> musicxml2ly: Output to `hello2.ly'
>> musicxml2ly: Converting to current version (2.23.3) notations ...
>> 
>> $ lilypond ./hello2.ly
>> GNU LilyPond 2.23.3
>> Fontconfig warning:
>> "/etc/fonts/conf.avail/66-wqy-zenhei-sharp-no13px.conf", line 11: Having
>> multiple values in  isn't supported and may not work as expected
>> Fontconfig warning: "/etc/fonts/conf.avail/66-wqy-zenhei-sharp.conf",
>> line 10: Having multiple values in  isn't supported and may not
>> work as expected
>> Processing `./hello2.ly'
>> Parsing...
>> Interpreting music...
>> ./hello2.ly:15:13: warning: cannot find context to change to: Staff = 2
>>2
>>  \change Staff="2" }
>>  Preprocessing graphical objects...
>>  Finding the ideal number of pages...
>>  Fitting music on 1 page...
>>  Drawing systems...
>>  Converting to `hello2.pdf'...
>>  Success: compilation successfully completed
>> 
>> Can someone try to process hello2.xml and attach .ly and .pdf files he
>> gets?
> 
> Hi,
> 
> did you read Jacques' reply?
> https://lists.gnu.org/archive/html/lilypond-user/2021-09/msg00480.html
> I can confirm this.
> Likely there's a bug in musicxml2ly.
> 
> Thus, you could try Jacques' xml2ly, otoh my own recent test showed
> that xml2ly is not perfect either ...
> 
> Cheers,
>  Harm

Re: Export from LilyPond to MusicXML

[Thomas Morley]

Hi Jacques,

Am Mo., 27. Sept. 2021 um 00:48 Uhr schrieb Jacques Menu
:
>
> Hello folks,
>
> The recent posts on this subject show there is interest in the matter. Sorry 
> for the length of this one...

Tbh, most of the mor detailed stuff is way over my head..
>
> My work was initially homed by Grame’s libmusicxml2 library as an example of 
> what it could be used for, in the lilypond branch at 
> https://github.com/grame-cncm/libmusicxml/tree/lilypond.
>
> Dom Fober, the author and maintainer of libmusicxml2, and I decided some time 
> ago to separate things for practical reasons, and I now push to the GitHub 
> repository I created at https://github.com/jacques-menu/musicformats.

Good to know.

> I’m currenly finalizing version 1.0.0, which explains why the test and master 
> branches are not up to date - only the dev branch is currently.
>
> The musicformats library is structured along the lines shown at page 16 in 
> https://github.com/jacques-menu/musicformats/blob/dev/doc/maintainersGuideToMusicFormats/maintainersGuideToMusicformats.pdf
>  (the users’s guide is not yet ‘usable’, sorry).
>
> The central component of musicformats is MSR (Music Score Representation), 
> from which various formats can be obtained.
>
> In this picture, we see that we could create MusicXML output from within the 
> LilyPond implementation going along the LilyPond - LPSR - MSR - MXSR  - 
> MusicMXL path. The missing part would be the creation of an LPSR (LilyPond 
> Score Representation), the others already exist.
>
> As an example, the LPSR representation and LilyPond output produced by:
>
> xml2ly basic/HelloWorld.xml -display-lpsr > LPSR_contents.txt 2>&1
>
> are in the attached LPSR_contents.txt file.
>
> The resulting score is:
>
>
> Jean and I have had discussions as to how the export to MusicXML could be 
> tackled on the LilyPond side, but nothing concrete yet. Some of the 
> information needed is readily accessible inside LilyPond, but grabbing the 
> remaining part is not easy.
>
> The musicformats repository contains examples using the library to create 
> scores in C++ applications, among them:
>
> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
> Mikrokosmos3Wandering -a
> What Mikrokosmos3Wandering does:
>
> This multi-pass generator creates a textual representation
> of Zoltán Kodály's Mikrokosmos III Wandering score.
> It performs various passes depending on the output generated.
>
> Other passes are performed according to the options, such as
> displaying views of the internal data or printing a summary of the score.
>
> The activity log and warning/error messages go to standard error.
>
> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
> Mikrokosmos3Wandering -apropos generate
> --- Help for atom "generate" in subgroup "Generated output"
> -generate, -gen GENERATED_OUTPUT_KIND
>   Generate GENERATED_OUTPUT_KIND code to the output.
> The 5 generated output kinds available are:
> braille, guido, lilypond, midi and musicxml.
> The default is 'LilyPond output'.
>
> (midi output is actually not yet available, though)
>
> For example, one can run:
>
> jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > 
> Mikrokosmos3Wandering -generate  musicxml  -o Mikrokosmos3Wandering.xml 
> -trace=passes
>
> %--
>   Pass 1: Creating the MSR score with the functions
> %--
> *** MusicXML warning *** :91: The staffMeasuresSlicesSequence of staff 
> "Part_OnlyPart_Staff_One" is null
> *** MusicXML warning *** :91: The staffMeasuresSlicesSequence of staff 
> "Part_OnlyPart_Staff_Two" is null
>
> %--
>   Pass 2: Convert the MSR score into a second MSR
> %------
>
> %--
>   Pass 3: Translating the MSR into an MXSR
> %--
>
> %--
>   Pass 4: Convert the MXSR into MusicXML text
> %--
>
> Opening file 'Mikrokosmos3Wandering.xml' for writing
> Warning message(s) were issued for input line 91
>
>
> This creates file Mikrokosmos3Wandering.xml, attached.
>
>
> The functionality of musicformats is available as API C++ functions. For 
> example, conversion from MusicXML data to LilyPond

Re: musicXML: 2 staves, piano

[Thomas Morley]

Am Mo., 27. Sept. 2021 um 17:05 Uhr schrieb Ivanov Dmitry :
>
> Something is not right. I installed lilypond 2.23.3 and processed
> hello2.xml. I still have an incorrect result.
>
> Here is what I do and what I get:
>
> $ musicxml2ly ./hello2.xml
> musicxml2ly: Reading MusicXML from ./hello2.xml ...
> musicxml2ly: Converting to LilyPond expressions...
> musicxml2ly: warning: Negative skip -1/2 (from position 1/2 to 0)
> musicxml2ly: Output to `hello2.ly'
> musicxml2ly: Converting to current version (2.23.3) notations ...
>
> $ lilypond ./hello2.ly
> GNU LilyPond 2.23.3
> Fontconfig warning:
> "/etc/fonts/conf.avail/66-wqy-zenhei-sharp-no13px.conf", line 11: Having
> multiple values in  isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.avail/66-wqy-zenhei-sharp.conf",
> line 10: Having multiple values in  isn't supported and may not
> work as expected
> Processing `./hello2.ly'
> Parsing...
> Interpreting music...
> ./hello2.ly:15:13: warning: cannot find context to change to: Staff = 2
> 2
>   \change Staff="2" }
>   Preprocessing graphical objects...
>   Finding the ideal number of pages...
>   Fitting music on 1 page...
>   Drawing systems...
>   Converting to `hello2.pdf'...
>   Success: compilation successfully completed
>
> Can someone try to process hello2.xml and attach .ly and .pdf files he
> gets?

Hi,

did you read Jacques' reply?
https://lists.gnu.org/archive/html/lilypond-user/2021-09/msg00480.html
I can confirm this.
Likely there's a bug in musicxml2ly.

Thus, you could try Jacques' xml2ly, otoh my own recent test showed
that xml2ly is not perfect either ...

Cheers,
  Harm

Re: musicXML: 2 staves, piano

[Ivanov Dmitry]

Something is not right. I installed lilypond 2.23.3 and processed
hello2.xml. I still have an incorrect result.

Here is what I do and what I get:

$ musicxml2ly ./hello2.xml 
musicxml2ly: Reading MusicXML from ./hello2.xml ...

musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: warning: Negative skip -1/2 (from position 1/2 to 0)
musicxml2ly: Output to `hello2.ly'
musicxml2ly: Converting to current version (2.23.3) notations ...

$ lilypond ./hello2.ly
GNU LilyPond 2.23.3
Fontconfig warning:
"/etc/fonts/conf.avail/66-wqy-zenhei-sharp-no13px.conf", line 11: Having
multiple values in  isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.avail/66-wqy-zenhei-sharp.conf",
line 10: Having multiple values in  isn't supported and may not
work as expected
Processing `./hello2.ly'
Parsing...
Interpreting music...
./hello2.ly:15:13: warning: cannot find context to change to: Staff = 2
   2 
 \change Staff="2" }

 Preprocessing graphical objects...
 Finding the ideal number of pages...
 Fitting music on 1 page...
 Drawing systems...
 Converting to `hello2.pdf'...
 Success: compilation successfully completed

Can someone try to process hello2.xml and attach .ly and .pdf files he
gets?


hello2.xml
Description: XML document
\version "2.23.3"
% automatically converted by musicxml2ly from ./hello2.xml
\pointAndClickOff

\header {
}

\layout {
\context { \Score
autoBeaming = ##f
}
}
PartPOneVoiceOne =  \relative c' {
\clef "treble" \time 2/4 \key g \major | % 1
2 \change Staff="2" }


% The score definition
\score {
<<

\new PianoStaff
<<
\set PianoStaff.instrumentName = "Music"

\context Staff = "1" << 
\mergeDifferentlyDottedOn\mergeDifferentlyHeadedOn
\context Voice = "PartPOneVoiceOne" {  \PartPOneVoiceOne }
>> \context Staff = "2" <<
\mergeDifferentlyDottedOn\mergeDifferentlyHeadedOn
>>
>>

>>
\layout {}
% To create MIDI output, uncomment the following line:
%  \midi {\tempo 4 = 100 }
}



hello2.pdf
Description: Adobe PDF document


signature.asc
Description: PGP signature

Re: musicXML: 2 staves, piano

[Jacques Menu]

Hello Dmitry,

xml2ly and MuseScore handle hello2.xml alright : the problem you have can be 
reproduced here with musicxml2ly (2.23.0-1) here.

JM

> Le 27 sept. 2021 à 10:46, Ivanov Dmitry  a écrit :
> 
> I can't reproduce your results. I tried to put your XML into hello2.xml and 
> compile it. But it produced pdf with the same error, Your lilypond file is 
> compiling correctly for me. Can you try my xml? Is anything wrong with it? My 
> lilypond version is 2.22.1.
> 

Re: musicXML: 2 staves, piano

[Ivanov Dmitry]

I can't reproduce your results. I tried to put your XML into hello2.xml and
compile it. But it produced pdf with the same error, Your lilypond file is
compiling correctly for me. Can you try my xml? Is anything wrong with it?
My lilypond version is 2.22.1.

http://www.musicxml.org/dtds/partwise.dtd;>

  

  Music
  
Piano
  

  
  

  
1

  1


  2
  4

2

  G
  2


  F
  4

  
  

  C
  0
  4

2
half
1
  
  
2
  
  

  D
  0
  3

2
half
2
  

  

\version "2.22.1"
% automatically converted by musicxml2ly from ./hello2.xml
\pointAndClickOff

\header {
}

\layout {
\context { \Score
autoBeaming = ##f
}
}
PartPOneVoiceOne =  \relative c' {
\clef "treble" \time 2/4 \key g \major | % 1
2 \change Staff="2" }


% The score definition
\score {
<<

\new PianoStaff
<<
\set PianoStaff.instrumentName = "Music"

\context Staff = "1" << 
\mergeDifferentlyDottedOn\mergeDifferentlyHeadedOn
\context Voice = "PartPOneVoiceOne" {  \PartPOneVoiceOne }
>> \context Staff = "2" <<
\mergeDifferentlyDottedOn\mergeDifferentlyHeadedOn
>>
>>

>>
\layout {}
% To create MIDI output, uncomment the following line:
%  \midi {\tempo 4 = 100 }
}



hello2.pdf
Description: Adobe PDF document

Export from LilyPond to MusicXML

[Jacques Menu]

Hello folks,The recent posts on this subject show there is interest in the matter. Sorry for the length of this one...My work was initially homed by Grame’s libmusicxml2 library as an example of what it could be used for, in the lilypond branch at https://github.com/grame-cncm/libmusicxml/tree/lilypond.Dom Fober, the author and maintainer of libmusicxml2, and I decided some time ago to separate things for practical reasons, and I now push to the GitHub repository I created at https://github.com/jacques-menu/musicformats.I’m currenly finalizing version 1.0.0, which explains why the test and master branches are not up to date - only the dev branch is currently.The musicformats library is structured along the lines shown at page 16 in https://github.com/jacques-menu/musicformats/blob/dev/doc/maintainersGuideToMusicFormats/maintainersGuideToMusicformats.pdf (the users’s guide is not yet ‘usable’, sorry).The central component of musicformats is MSR (Music Score Representation), from which various formats can be obtained.In this picture, we see that we could create MusicXML output from within the LilyPond implementation going along the LilyPond - LPSR - MSR - MXSR  - MusicMXL path. The missing part would be the creation of an LPSR (LilyPond Score Representation), the others already exist.As an example, the LPSR representation and LilyPond output produced by:	xml2ly basic/HelloWorld.xml -display-lpsr > LPSR_contents.txt 2>&1are in the attached LPSR_contents.txt file. The resulting score is:Jean and I have had discussions as to how the export to MusicXML could be tackled on the LilyPond side, but nothing concrete yet. Some of the information needed is readily accessible inside LilyPond, but grabbing the remaining part is not easy. The musicformats repository contains examples using the library to create scores in C++ applications, among them:jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > Mikrokosmos3Wandering -aWhat Mikrokosmos3Wandering does:    This multi-pass generator creates a textual representation    of Zoltán Kodály's Mikrokosmos III Wandering score.    It performs various passes depending on the output generated.    Other passes are performed according to the options, such as    displaying views of the internal data or printing a summary of the score.    The activity log and warning/error messages go to standard error.jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > Mikrokosmos3Wandering -apropos generate--- Help for atom "generate" in subgroup "Generated output"    -generate, -gen GENERATED_OUTPUT_KIND          Generate GENERATED_OUTPUT_KIND code to the output.            The 5 generated output kinds available are:            braille, guido, lilypond, midi and musicxml.            The default is 'LilyPond output'.(midi output is actually not yet available, though)For example, one can run:jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxml > Mikrokosmos3Wandering -generate  musicxml  -o Mikrokosmos3Wandering.xml -trace=passes%--  Pass 1: Creating the MSR score with the functions%------*** MusicXML warning *** :91: The staffMeasuresSlicesSequence of staff "Part_OnlyPart_Staff_One" is null*** MusicXML warning *** :91: The staffMeasuresSlicesSequence of staff "Part_OnlyPart_Staff_Two" is null%--  Pass 2: Convert the MSR score into a second MSR%--%--  Pass 3: Translating the MSR into an MXSR%--%------  Pass 4: Convert the MXSR into MusicXML text%--Opening file 'Mikrokosmos3Wandering.xml' for writingWarning message(s) were issued for input line 91This creates file Mikrokosmos3Wandering.xml, attached.The functionality of musicformats is available as API C++ functions. For example, conversion from MusicXML data to LilyPond, as used by xml2ly and Grame’s experimental web site at https://libmusicxml.grame.fr, is available through these functions:/*!  \brief Converts a MusicXML representation to the LilyPond format.  \param file a file name  \param out the output stream  \return an error code (\c musicFormatsError::k_NoError when success)*/EXP musicFormatsError musicxmlfile2lilypond (  const char *file, const optionsVector& options, std::ostream& out, std::ostream& err);/*!  \brief Converts a MusicXML representation to the LilyPond format.  \param fd a file descriptor  \param out the output stream  \return an error code (\c musicFormatsError::k_NoError when success)*/EXP musicFormatsError musicxmlfd2lilypond (  FILE* fd, const optionsVector& opt

Re: musicXML: 2 staves, piano

[Paul Hodges]

I'm not the person of whom the question was asked, but I have myself 
just been asked about MusicXML export.

I am retired, with time on my hands, and have for some time used 
LilyPond to prepare music editions for the choir I sing in - so I am 
fluent with it for "straightforward" choral music with piano 
accompaniment (I've also made up percussion and harp parts which have 
been required).  My son is a concert pianist specialising in modern and 
contemporary music.  A composer he knew died last year; he had never 
acquired much of a following, and much of his music is unpublished, and 
much else only in facsimile of imperfect manuscripts.  So my son (who 
has been willed his manuscripts) is on a mission to arrange for some of 
his music to be typeset for possible publication.  He has asked other 
friends (who use I don't know what software), and I mentioned to him 
that I use LilyPond, and feel that it is capable of producing scores 
which are publication ready.  So he suggested I might like to try 
setting a piece for solo flute, which I have completed - and I then 
started on a much larger piece for two pianos.  Both pieces are 
stretching my knowledge of LilyPond, but with the help of this list I 
have been forging ahead.

My idea was simply to challenge myself, and if something useful came of 
it I'd be satisfied - even if it just ended up as a more legible edited 
score for a future typesetter.  It seems to me, though, that my score of 
the flute piece could be published, with perhaps some tweaks to fit a 
publisher's house style more closely, maybe using a different font (I've 
proffered alternatives).  Anyway, my son talked about it with a 
publisher earlier this week.  Out of the discussion came two questions: 
(1) could I change the glyphs for the treble clef and the accent, and 
(2) can I provide a MusicXML export.  On the second I mentioned that I 
don't believe a MusicXML export would fully represent the score (there 
are non-standard barlines, for instance, which are specially drawn; also 
some unusual brackets).

I don't know whether even a good MusicXML export would make my work 
usable when it otherwise might not be - I just pass on the story to 
illustrate a possible reason for wanting to try it.

Paul

On 25/09/2021 15:24:12, "Jean Abou Samra"  wrote:

>Hi Harm,
>
>Le 24/09/2021 à 22:52, Thomas Morley a écrit :
>>I was tempted to offer a very high bounty to get a working xml-export.
>>Alas, we already have
>>https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
>>offered bounties are not that low ...
>
>Out of curiosity, what would be your own use case for MusicXML export?
>
>Cheers,
>Jean
>

Re: musicXML: 2 staves, piano

[Thomas Morley]

Am Sa., 25. Sept. 2021 um 16:24 Uhr schrieb Jean Abou Samra
:
>
> Hi Harm,
>
> Le 24/09/2021 à 22:52, Thomas Morley a écrit :
> > I was tempted to offer a very high bounty to get a working xml-export.
> > Alas, we already have
> > https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
> > offered bounties are not that low ...
>
> Out of curiosity, what would be your own use case for MusicXML export?
>
> Cheers,
> Jean

Hi Jean,

I need to collaborate with colleagues owning various music-typesetting
software, mostly Sibelius and Finale.

I'd love to tell them "Use LilyPond and all will be fine", but as long
as LilyPond is a dead end with regard to xml-export this is a
showstopper.

The other one is the missing Mac-64-bit support, I know it's possible
to get LilyPond there, but reading the threads explaning the howto, I
have to say it's way to complicated. My collegues are musicians not
interested in solving computer-issues. If something is not working
out-of-the-box, people will trash it and look for something else...

Cheers,
  Harm

Re: musicXML: 2 staves, piano

[Jean Abou Samra]

Hi Harm,

Le 24/09/2021 à 22:52, Thomas Morley a écrit :

I was tempted to offer a very high bounty to get a working xml-export.
Alas, we already have
https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
offered bounties are not that low ...


Out of curiosity, what would be your own use case for MusicXML export?

Cheers,
Jean

Re: musicXML: 2 staves, piano

[Ivanov Dmitry]

Jacques Menu:
Dmitry, how do you generate MusicXML data?


I do it manually.


signature.asc
Description: PGP signature

Re: musicXML: 2 staves, piano

[Carl Sorensen]

On 9/24/21, 3:52 PM, "Lukas-Fabian Moser"  wrote:


> I was tempted to offer a very high bounty to get a working xml-export.
> Alas, we already have
> https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
> offered bounties are not that low ...

One thing I noted while skimming through that issue and the linked 
conversations: There were statements along the lines of "once we can use 
guile2, it gets easier" (because of the sxml module). Now we know since 
(I think) May that it is possible to produce a production-quality 
LilyPond using Guile 2.2. (I used Jonas' experimental binary release for 
quite some time over the summer in my everyday work, without any problems.)

So, while there are no regular official binary releases with Guile2 yet, 
I think it would now be quite acceptable to use Guile2 features in a 
possible XML export engine.

I totally agree that it would be acceptable to use Guile2 features.

Unfortunately, I think that Guile2 only helps with the Scheme structure to xml 
conversion, making the "routine" part of the programming much easier.

I don't think that Guile2 will provide any help with what I think the 
challenging parts of the problem are -- converting Lilypond data structures 
into an appropriate Scheme structure for moving to xml.  But I could be 
completely wrong.  Jacques certainly would know more about this than me.

Thanks,

Carl
 

Re: musicXML: 2 staves, piano

[Lukas-Fabian Moser]

I was tempted to offer a very high bounty to get a working xml-export.
Alas, we already have
https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
offered bounties are not that low ...


One thing I noted while skimming through that issue and the linked 
conversations: There were statements along the lines of "once we can use 
guile2, it gets easier" (because of the sxml module). Now we know since 
(I think) May that it is possible to produce a production-quality 
LilyPond using Guile 2.2. (I used Jonas' experimental binary release for 
quite some time over the summer in my everyday work, without any problems.)


So, while there are no regular official binary releases with Guile2 yet, 
I think it would now be quite acceptable to use Guile2 features in a 
possible XML export engine.


Lukas

Re: musicXML: 2 staves, piano

[Carl Sorensen]

On 9/24/21, 2:52 PM, "Thomas Morley"  wrote:

Am Fr., 24. Sept. 2021 um 22:33 Uhr schrieb Carl Sorensen 
:
>
> We have automatic tests for xml2ly that check compliance with the 
musicXML standard.
>
> I'm fairly certain it's a problem with your musicXML, rather than xml2ly.
>
> Unfortunately, I'm not expert enough on musicXML to find the mistakes.
>
> Why are your writing your own musicXML and then using xml2ly, instead of 
just writing in lilypond?
>
> Carl
>
>
>

Hi Carl,

iiuc, xml2ly converts an .xml-file to a .ly-file, not the other way round.

Yes, I know this.  As far as I can see, Dmitry is writing musicXML files by 
hand (which I cannot imagine doing) and then importing them to lilypond using 
xml2ly.



Speaking of it, I recently tested several methods to convert ly to xml:
(1) openlilylib (with lilypond-export, Jan-Peter)
(2) python-ly
(3) Frescobaldi
(4) de Wolff (https://github.com/de-wolff/lilypond.git)

and converted the resulting files back to ly with musicxml2ly
(builtin) and xml2ly (https://github.com/grame-cncm/libmusicxml.git,
xml2ly by Jacques)

The results were terrible :((

I totally agree that the musicXML export tools are really not good at all.

I was tempted to offer a very high bounty to get a working xml-export.
Alas, we already have
https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
offered bounties are not that low ...

I think that a good musicXML export project is likely a 6-month, full-time 
project for an expert in lilypond.  For that kind of effort, a 1,000 euro 
bounty is not big.

Thanks,

Carl
 

Re: musicXML: 2 staves, piano

[Thomas Morley]

Am Fr., 24. Sept. 2021 um 22:33 Uhr schrieb Carl Sorensen :
>
> We have automatic tests for xml2ly that check compliance with the musicXML 
> standard.
>
> I'm fairly certain it's a problem with your musicXML, rather than xml2ly.
>
> Unfortunately, I'm not expert enough on musicXML to find the mistakes.
>
> Why are your writing your own musicXML and then using xml2ly, instead of just 
> writing in lilypond?
>
> Carl
>
>
>

Hi Carl,

iiuc, xml2ly converts an .xml-file to a .ly-file, not the other way round.

Speaking of it, I recently tested several methods to convert ly to xml:
(1) openlilylib (with lilypond-export, Jan-Peter)
(2) python-ly
(3) Frescobaldi
(4) de Wolff (https://github.com/de-wolff/lilypond.git)

and converted the resulting files back to ly with musicxml2ly
(builtin) and xml2ly (https://github.com/grame-cncm/libmusicxml.git,
xml2ly by Jacques)

The results were terrible :((

I was tempted to offer a very high bounty to get a working xml-export.
Alas, we already have
https://gitlab.com/lilypond/lilypond/-/issues/665 and the there
offered bounties are not that low ...

Cheers,
  Harm

Re: musicXML: 2 staves, piano

[Carl Sorensen]

On 9/24/21, 2:37 PM, "Ivanov Dmitry"  wrote:

On 21-09-24 20:33:05, Carl Sorensen wrote:
>Why are your writing your own musicXML and then using xml2ly, instead of 
just writing in lilypond?

I am writing software for harmonization and XML is a better language for
computers to read then lilypond.

OK.  I'm not sure I agree, but that's a personal opinion.

I believe you are having the problem because you are misusing musicXML.  I 
think for the piano, you need to have two staves, one for the upper staff, and 
one for the lower staff.  Instead, you only have one staff, and use /backup 
(which I know was recommended on this list, but I think is not the correct way 
to do it.

Please see this link for an example of how piano music is stored in musicXML:  
https://www.w3.org/2021/06/musicxml40/tutorial/notation-basics/

When I'm done looking at this example, it's very hard for me to see that 
musicXML is easier to deal with than lilypond syntax...

I hope this link will help you.


Carl

Re: musicXML: 2 staves, piano

[Ivanov Dmitry]

On 21-09-24 20:33:05, Carl Sorensen wrote:

Why are your writing your own musicXML and then using xml2ly, instead of just 
writing in lilypond?


I am writing software for harmonization and XML is a better language for
computers to read then lilypond.


signature.asc
Description: PGP signature

Re: musicXML: 2 staves, piano

[Carl Sorensen]

We have automatic tests for xml2ly that check compliance with the musicXML 
standard.

I'm fairly certain it's a problem with your musicXML, rather than xml2ly.

Unfortunately, I'm not expert enough on musicXML to find the mistakes.

Why are your writing your own musicXML and then using xml2ly, instead of just 
writing in lilypond?

Carl

musicXML: 2 staves, piano

[Ivanov Dmitry]

I was experimenting with a simple musicXML for a stadard piano score
with 2 staves. I attached the sample file. Everything seems to be fine, but 
after I run

musicxml2ly ./hello1.xml
lilypond ./hello1.ly

I get incorrect result. Is it musicxml2ly working incorrectly?


hello1.xml
Description: XML document


hello1.pdf
Description: Adobe PDF document


signature.asc
Description: PGP signature

musicXML: 2 voices in 1 measurement

[Ivanov Dmitry]

Re: musicXML: 2 voices in 1 measurement

[Ivanov Dmitry]

Hello Ivanov,

You probably miss a  élément, will post an example tonight.



Thanks, I fixed the code myself already.


signature.asc
Description: PGP signature

Re: musicXML: 2 voices in 1 measurement

[Jacques Menu]

Hello Ivanov,

You probably miss a  élément, will post an example tonight.

JM

Envoyé de mon iPhone

> Le 22 sept. 2021 à 23:04, Ivanov Dmitry  a écrit :
> 
> I am trying to create a musicXML file with 2 voices:
> 
> 
> "-//Recordare//DTD MusicXML 4.0 Partwise//EN"
>"http://www.musicxml.org/dtds/partwise.dtd;>
> 
>  
>
>  Music
>
>  
>  
>
>  
>1
>
>  1
>
>
>  4
>  4
>
>
>  G
>  2
>
>  
>  
>1
>
>  F
>  1
>  4
>
>2
>half
>  
>  
>
>  G
>  0
>  4
>
>1
>2
>half
>  
>  
>
>  C
>  0
>  4
>
>2
>2
>half
>  
>  
>
>  A
>  0
>  3
>
>2
>2
>half
>  
>
>  
> 
> 
> It seems ok to me: the notes are in the same measure. But when I use
> musicxml2ly and then lilypond I get the second voice shifted to the
> next measurement. What is wrong?
> 

Re: musicXML: 2 voices in 1 measurement

[Hans Aikema]

>>> On 22 Sep 2021, at 23:05, Ivanov Dmitry  wrote:
>>> 
>> I am trying to create a musicXML file with 2 voices:
>> 
>> 
>> >"-//Recordare//DTD MusicXML 4.0 Partwise//EN"
>>"http://www.musicxml.org/dtds/partwise.dtd;>
>> 
>>  
>>
>>  Music
>>
>>  
>>  
>>
>>  
>>1
>>
>>  1
>>
>>
>>  4
>>  4
>>
>>
>>  G
>>  2
>>
>>  
>>  
>>1
>>
>>  F
>>  1
>>  4
>>
>>2
>>half
>>  
>>  
>>
>>  G
>>  0
>>  4
>>
>>1
>>2
>>half
>>  
>>  
>>
>>  C
>>  0
>>  4
>>
>>2
>>2
>>half
>>  
>>      
>>
>>  A
>>  0
>>  3
>>
>>2
>>2
>>half
>>  
>>
>>  
>> 
>> 
>> It seems ok to me: the notes are in the same measure. But when I use
>> musicxml2ly and then lilypond I get the second voice shifted to the
>> next measurement. What is wrong?
>> 
> 
> Every note in musicxml moves the time-pointer forward, so your musicxml 
> represents two voices that follow eachother. To make them parallel you need 
> to  a full measure before the notes of voice 2 to reset the 
> time-pointer to the start of the measure.
> https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/backup/

musicXML: 2 voices in 1 measurement

[Ivanov Dmitry]

I am trying to create a musicXML file with 2 voices:


http://www.musicxml.org/dtds/partwise.dtd;>

  

  Music

  
  

  
1

  1


  4
  4


  G
  2

  
  
1

  F
  1
  4

2
half
  
  

  G
  0
  4

1
2
half
  
  

  C
  0
  4

2
2
half
  
  

  A
  0
  3

2
2
half
  

  


It seems ok to me: the notes are in the same measure. But when I use
musicxml2ly and then lilypond I get the second voice shifted to the
next measurement. What is wrong?

Re: Export to musicxml

[Werner LEMBERG]

> What is the current state of the art with musicxml export? Any work
> being done on that?

I think the best stuff currently avaible is what Jacques is working on
in the (external) `libmusicxml` git repository (in the `lilypond`
branch).


Werner

Export to musicxml

[Andrew Bernard]

What is the current state of the art with musicxml export? Any work
being done on that?

Andrew

MusicXML to braille music conversion

[Jacques Menu]

Hello folks,

There have been posts in the past on this subject in the Lily users’ list.

I now have a first draft of such a translator producing braille music in Ascii 
BRF and Unicode files. It translates the basic elements, such as time 
signatures, measures, notes, etc.

This development was frozen some time ago though: the mail I sent to ask who 
could provide technical information about such files generation was mostly 
never answered by the various individuals and organisms I sent it to, and I got 
discouraged.

DAISY Consortium is very active in the field of braille music, see 
https://daisy.org/activities/projects/music-braille/. 
According to the contacts I’ve had with them, they aim at an integrated 
graphical braille score editor, that would take the score structure into 
account. They already have done work with Veia Progetti, see 
https://www.youtube.com/watch?v=Sf60CpZQ_Iw. Of course, they have resources I 
don’t have.

The good news on my side is that I met two interested people at the Salzburg 
conference. Also, the bicentenial of the first braille book published by Louis 
Braille himself will take place in 2025, and that could raise interest for 
braille music.

A former braille music teacher told me that he is pessimistic for braille music 
teaching in the future, though: it is quite difficult for the blind people to 
learn, and efforts to integrate the blind in society, such as providing music 
in audio format, may undermine it.

I’m interested in knowing what you think and maybe hope in this area.

A nice day!

JM

MusicXML beat-repeat question

[Jacques Menu]

Hello folks,

I’m trying to understand how  is working in MusicXML.

The example at 
https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beat-repeat.htm 
is the only one I found, and:

- the first measure has three two-notes chords, and a fourth one is 
missing;

- adding the fourth one leads to the following with the attached file:
- musicxml2ly crashes, see below;
- MuseScore and Sibelius 7.1.3 produce 4 two-notes chords, but 
no slashes;
- Finale 2014 produces 4 slashes, but no notes.

I’ve been wondering whether this example has ever been tested actually.

Can someone supply me with a functional beat repeat example?

Thanks!

JM

—

menu@macbookprojm: ~/libmusicxml-git/files/samples/musicxml > musicxml2ly 
repeats/BeatRepeat.xml 
musicxml2ly: Reading MusicXML from repeats/BeatRepeat.xml ...
Traceback (most recent call last):
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
3297, in 
main()
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
3291, in main
voices = convert(filename, options)
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
3168, in convert
(voices, staff_info) = get_all_voices(parts)
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
2766, in get_all_voices
all_voices = voices_in_part_in_parts(parts)
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
2756, in voices_in_part_in_parts
voices = voices_in_part(p)
  File "/Applications/LilyPond.app/Contents/Resources/bin/musicxml2ly", line 
2743, in voices_in_part
part.interpret()
  File 
"/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/python/musicxml.py",
 line 1361, in interpret
int(attributes_dict.get('divisions').get_text()))
AttributeError: 'NoneType' object has no attribute ‘get_text’




BeatRepeat.xml
Description: XML document



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: .musicxml suffix

[Jacques Menu]

Hello Timothy and Graeme,

Thanks for the information!

JM

> Le 27 avr. 2019 à 21:22, Timothy Lanfear  a écrit :
> 
> On 27/04/2019 05:39, Jacques Menu wrote:
>> Hello folks,
>> 
>> Who decided to switch from .xml to .musicxml, and what was the supposed gain 
>> in the move? I now find that some text editors don’t propose such files in 
>> their file open dialog..
> 
> The change is recorded on the MusicXML GitHub page 
> https://github.com/w3c/musicxml/issues/191, which also points to a a 
> recording to the working group discussion.
> 
> -- 
> 
> Timothy Lanfear, Bristol, UK.
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: .musicxml suffix

[Timothy Lanfear]

On 27/04/2019 05:39, Jacques Menu wrote:

Hello folks,

Who decided to switch from .xml to .musicxml, and what was the supposed gain in 
the move? I now find that some text editors don’t propose such files in their 
file open dialog..


The change is recorded on the MusicXML GitHub page 
https://github.com/w3c/musicxml/issues/191, which also points to a a 
recording to the working group discussion.


--

Timothy Lanfear, Bristol, UK.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: .musicxml suffix

[Graeme St.Clair]

Found this in the Wiki on MusicXML 
https://www.theregister.co.uk/2015/12/30/music_as_mark_up/ .  News to me, 
tho maybe not to anyone else.


For convenience:  https://en.wikipedia.org/wiki/MusicXML .

Rgds, G.

-Original Message- 
From: Jacques Menu

Sent: Saturday, April 27, 2019 12:39 AM
To: LilyPond Users
Subject: .musicxml suffix

Hello folks,

Who decided to switch from .xml to .musicxml, and what was the supposed gain 
in the move? I now find that some text editors don’t propose such files in 
their file open dialog..


Thanks!

JM


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user 




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

.musicxml suffix

[Jacques Menu]

Hello folks,

Who decided to switch from .xml to .musicxml, and what was the supposed gain in 
the move? I now find that some text editors don’t propose such files in their 
file open dialog..

Thanks!

JM


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Fwd: [MEI-L] A WordPress plugin for displaying very easily a MEI (or MusicXML or PAE) score in a WordPress page

[Urs Liska]

 Ursprüngliche Nachricht 
Von: "Etienne Fréjaville" 
Gesendet: 24. Juni 2018 00:31:43 MESZ
An: Music Encoding Initiative 
Betreff: [MEI-L] A WordPress plugin for displaying very easily a MEI (or 
MusicXML or PAE) score in a WordPress page

Dear MEI community,

I'm happy to inform you that I have published a WordPress plugin allowing to
display very easily a MEI (or MusicXML or PAE) score in a WordPress page.

Do you own a WordPress site and publish frequently music fragments, incipits
or small music sheets ?

This plugin is done for you… and it's free!!

It allows you by writing directly your MEI, MusicXML or PAE code between two
shortcode tags [pn_msv] and [/pn_msv] in the text of a WordPress page or
post, to have it rendered directly in your page.

Is the code too big to be placed directly in our page ? Upload a file on
your site and have it rendered the same way.

The plugin is powered by Verovio for the score rendering, and generates for
you the cumbersome JavaScript code necessary to invoke Verovio JavaScript
toolkit with the appropriate parameters.

Moreover, it facilitates greatly the display in the appropriate size of your
score, without having to specify any score dimensioning.

Even if all Verovio options are not accessible on the shortcode (this is not
the goal, the use must be simplified at the maximum), some options are
allowed on the plugin and are fully described at
http://www.partitionnumerique.com/music-sheet-viewer-wordpress-plugin/

The plugin is freely available in the WordPress plugins directory
https://wordpress.org/plugins/music-sheet-viewer/  or can be installed
directly from your WordPress site by going to the plugin’s administration
page and entering « Music Sheet Viewer » in the plugin’s search field.

At last, all donations are welcome for supporting my work.

All the best.

Etienne Fréjaville
 http://www.partitionnumerique.com
L'avenir de la partition musicale



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: MusicXML

[Jan-Peter Voigt]

ah yes ofcourse, I forgot to mention that.

Am 29.05.2018 um 14:53 schrieb Karlin High:

On 5/29/2018 7:45 AM, David Kastrup wrote:

Varun Soontornniyomkij  writes:


Is it possible, using Lilypond, to save/export a score as a MusicXML
file?


Not at the current point of time.


No MusicXML export from LilyPond itself. But there are supporting 
programs for LilyPond that may or may not be enough for your needs.


Hidden experimental feature in Frescobaldi...
<https://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00240.html>

...which uses the python-ly library.
<https://github.com/wbsoft/python-ly>




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: MusicXML

[Karlin High]

On 5/29/2018 7:45 AM, David Kastrup wrote:

Varun Soontornniyomkij  writes:


Is it possible, using Lilypond, to save/export a score as a MusicXML
file?


Not at the current point of time.


No MusicXML export from LilyPond itself. But there are supporting 
programs for LilyPond that may or may not be enough for your needs.


Hidden experimental feature in Frescobaldi...
<https://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00240.html>

...which uses the python-ly library.
<https://github.com/wbsoft/python-ly>

--
Karlin High
Missouri, USA

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: MusicXML

[Jan-Peter Voigt]

Hello Varun,

currently this is not natively supported. I have been working on some 
code that is able to write some XML for simple scores and I am going to 
extend that: https://github.com/jpvoigt/lilypond-export/
To try it you have to prepare/install open-lilylib: 
https://github.com/openlilylib/oll-core


There have been some other attempts I don't recall right now.

HTH
Jan-Peter

Am 29.05.2018 um 08:09 schrieb Varun Soontornniyomkij:

Is it possible, using Lilypond, to save/export a score as a MusicXML file?


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: MusicXML

[David Kastrup]

Varun Soontornniyomkij  writes:

> Is it possible, using Lilypond, to save/export a score as a MusicXML
> file?

Not at the current point of time.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

MusicXML

[Varun Soontornniyomkij]

Is it possible, using Lilypond, to save/export a score as a MusicXML file?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Non standard MusicXML tuplet question

[Menu Jacques]

Hello folks,

In 23c-Tuplet-Display-NonStandard.xml, part of the unofficial LP MusicXML 
suite, there’s:


  

  C
  5

136
1
eighth

  3
  2
  breve


  

  7
  quarter
  


  5
  quarter
  

  

  

musicxml2ly ignores the 7 and 5 parts, and produces a regular 3/2 tuplet.

My question is: how is that supposed to be displayed in the score? The DTD’s 
don’t help much in this case...

Thanks for you help!

JM

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Converting musicxml files

[Mike Dean]

Thanks--Mike
(I was that close to just starting from scratch in LilyPond.)

\version "2.19.80"
\language "english"
#(set-default-paper-size "letter")

\header {
  title = "Pastoral: The Great Physician"
  composer = "John Hart Stockton"
  arranger = "arr. Mike Dean"
}

\score {
\relative c'' {
 \clef treble
 \key c \major
 \time 6/8
 \tempo "Moderately"
\override Score.BarNumber.break-visibility = #end-of-line-invisible
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 5)
\set Score.markFormatter = #format-mark-circle-numbers
\override BreathingSign.text = \markup {
\musicglyph #"scripts.caesura.straight" }
 c4. b |
 c e,4 f8 |
 g a g f4 a8 |
 g4 c,8 c'4 b8 |
%5
 a g a e4 f8 |
 g f g e4 c8 |
 d4. g |
 g4 f8 e4 g8 |
 c4. g |
%10
 e8 d e c4 g'8 |
 a4. f4 a8 |
 g4 c,8 c'4 b8 |
 a4. e~  |
 e8 d e c4 g'8 |
%15
 f4 e8 d4. |
 c2.~  |
 c4 r8 r4 g'8 \bar "||" \mark \default
 g4  e8 c4 d8 |
 e4 f8 g4 g'8 |
%20
 g4 c,8 e4 c8 |
 d4. c4 g8 |
 g4 e8 c4 d8 |
 e4 f8 g4 g'8 |
 g4 c,8 e4 c8 |
%25
 d4. c |
 g8 a b c4 b8 |
 b4 a8 g4 r8 |
 g a b c4 b8 |
 b4 a8 g4 r8 |
%30
 g4 e8 c4 d8 |
 e4 f8 g4 g'8 |
 g4 c,8 e4 c8 |
 d4. c~  \bar "||" \mark \default
 c g |
%35
 e8 d e c4 g'8 |
 a8.( g16 f8 f8. g16) a8 |
 g4 c,8 c'4 b8 |
 a4. e~  |
 e8 d e c4 g'8 |
%40
 f4 e8 d c' b |
 c g' f e d c |
 b c d e4 c8 |
 c g' f e d c |
 b c b a4 e8~  |
%45
 e d e c c' b |
 a4 b8 c4 d8 |
 e4 c8 e4 b8 |
 a b a g4 b8 |
 e,2. |
%50
 e4 fs8 gs4 a8 |
 b4. b |
 d8 c b a b c |
 b4. e~ |
 e8 d c b4 e8 |
%55
 a,4. d~  |
 d8 c b a4 d8 |
 g,4. g |
 b8 a g f d g \bar "||" \mark \default
 c4. g |
%60
 e8 d e c4 g'8 |
 a4 f8~  f8. g16 a8 |
 g4 c,8 c'4 b8 |
 a4. e |
 fs8 e fs d4 a'8 |
%65
 b4. g4 b8 |
 a4 d,8 d'4 cs8 |
 b4. fs~ |
 fs8 e fs d d' cs |
 b4 a8 g4 fs8 |
%70
 e4.~  e4 a8 \bar "||" \mark \default
 \key d \major
 a4 fs8 d4 e8 |
 fs4 g8 a4 a'8 |
 a4 d,8 fs4 d8 |
 e4. d4 a8 |
%75
 a4 fs8 d4 e8 |
 fs4 g8 a4 a'8 |
 a4 d,8 fs4 d8 |
 e4. d~  |
 d~  d8 r r |
%80
 a' b cs d4 a8 |
 cs4 b8 a4 r8 |
 a b cs e d a |
 cs4 b8 a4 r8 |
 a4 fs8 d4 e8 |
%85
 fs4 g8 a4-\fermata \breathe r8 |
 a,4 d,8 fs4 d8 |
 e4. d~  \bar "||" \mark \default
 d  a' |
 fs8 e fs d4 a'8 |
%90
 b4. g4 b8 |
 a4 d,8 d'4 cs8 |
 b4. fs |
 fs8 e fs d4 a'8 |
 g4<> _\markup \italic\bold {"rit." } fs8 e4. |
%95
 d2.~  |
 d4.~  d8 r r \bar "|."
}}


Mike Dean

On Mon, Dec 11, 2017 at 4:51 PM, Jacques Menu Muzhic 
wrote:

> Hello Dean,
>
> Another version that runs fine with 2.19.
>
> JM
>
> —
>
>
> \version "2.19"
>
> % Comment or adapt next line as needed (default is 20)
> #(set-global-staff-size 19.9465)
>
> \header {
>   title  = "Title"
>   composer   = "Composer"
>   software   = "MuseScore 2.1.0"
>   encodingDate   = "2017-12-11"
> }
>
> \paper {
>   paper-width  = 22\cm
>   paper-height = 28\cm
>   top-margin   = 0.63\cm
>   bottom-margin= 0.63\cm
>   left-margin  = 0.63\cm
>   right-margin = 0.63\cm
>   indent   = 1.7\cm
>   short-indent = 1.3\cm
>
>   %page-count  = 1
>   %system-count= 1
> }
>
> \layout {
>   \context {
> \Score
> autoBeaming = ##f % to display tuplets brackets
>   }
> }
>
> % Pick your choice from the next two lines as needed
> myBreak = { \break }
> %myBreak = { }
>
> % Pick your choice from the next two lines as needed
> myPageBreak = { \pageBreak }
> %myPageBreak = { }
>
> P_POne_Staff_One_Voice_One = \relative {
>   \language "nederlands"
>   \key c \major
>   \numericTimeSignature \time 6/8
>   \clef "treble"
>   c''4. b | % 1
>   c4. e,4 f8 | % 2
>   g8 [ a g ] f4 a8 | % 3
>   g4 c,8 c'4 b8 | % 4
>   a8 [ g a ] e4 f8 | % 5
>   g8 [ f g ] e4 c8 | % 6
>   d4. g | % 7
>   g4 f8 e4 g8 | % 8
>   c4. g | % 9
>   \barNumberCheck #10
>   \myBreak | % 10
>
>   e8 [ d e ] c4 g'8 | % 10
>   a4. f4 a8 | % 11
>   g4 c,8 c'4 b8 | % 12
>   a4. e ~ | % 13
>   e8 [ d e ] c4 g'8 | % 14
>   f4 e8 d4. | % 15
>   c2. ~ | % 16
>   c4 r8 r4 g'8 | % 17
>
>
>   \mark\markup {\box {"1"}}
>   g4 e8 c4 d8 | % 18
>   \barNumberCheck #19
>   \myBreak | % 19
>
>   e4 f8 g4 g'8 | % 19
>   g4 c,8 e4 c8 | % 20
>   d4. c4 g8 | % 21
>   g4 e8 c4 d8 | % 22
>   e4 f8 

Re: Converting musicxml files

[Mike Dean]

For what it is worth, I ended the Frescobaldi-invoked Lilypond (and didn't
get an error log), so I'm not sure if I need to add something to my
Frescobaldi 3.0.1/Lilypond 2.19.80 installation to get the conversion
working properly (On the other hand, I don't have a need to import musicxml
files for the forseeable future)

Mike Dean

On Mon, Dec 11, 2017 at 12:51 PM, Mike Dean <dean...@aquinas.edu> wrote:

> Yes, I meant import...Meanwhile the Frescobaldi-invoked Lilypond is still
> running (and can challenge the Energizer Bunny in an 8K)
> Richard: Thank you for attaching the output...I am going to take a knee on
> the current operation.
>
> Mike Dean
>
> On Mon, Dec 11, 2017 at 12:41 PM, Richard Shann <rich...@rshann.plus.com>
> wrote:
>
>> On Mon, 2017-12-11 at 11:22 -0500, Mike Dean wrote:
>> > Observation:
>> > Frescobaldi 3.0 is not playing nicely at all with musicxml file
>> > export
>>
>> Did you mean *import* ???
>>
>> > (no new developments from this
>> > page: https://github.com/wbsoft/frescobaldi/issues/910)
>> > II'm looking to do the import directly from lilypond, but am not sure
>> > how to go about it...
>> > the musicxml files (uncompressed and compressed) are attached
>>
>> I thought it would be interesting to try to convert you musicXML to
>> LilyPond with Denemo - attached is the result...
>>
>> Richard
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Converting musicxml files

[Mike Dean]

Yes, I meant import...Meanwhile the Frescobaldi-invoked Lilypond is still
running (and can challenge the Energizer Bunny in an 8K)
Richard: Thank you for attaching the output...I am going to take a knee on
the current operation.

Mike Dean

On Mon, Dec 11, 2017 at 12:41 PM, Richard Shann <rich...@rshann.plus.com>
wrote:

> On Mon, 2017-12-11 at 11:22 -0500, Mike Dean wrote:
> > Observation:
> > Frescobaldi 3.0 is not playing nicely at all with musicxml file
> > export
>
> Did you mean *import* ???
>
> > (no new developments from this
> > page: https://github.com/wbsoft/frescobaldi/issues/910)
> > II'm looking to do the import directly from lilypond, but am not sure
> > how to go about it...
> > the musicxml files (uncompressed and compressed) are attached
>
> I thought it would be interesting to try to convert you musicXML to
> LilyPond with Denemo - attached is the result...
>
> Richard
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Converting musicxml files

[Mike Dean]

Am not sure how long Lilypond is to be running before expecting output
(error messages or otherwise), but am hoping that it is not hanging...

Mike Dean

On Mon, Dec 11, 2017 at 12:10 PM, Mike Dean <dean...@aquinas.edu> wrote:

> Hi Martin:
> I am not sure if I was doing the steps correctly (was working with
> Frescobaldi 3.01 and LP 2.19.42; have since updated to 2.19.80)
> Am trying the steps again; in 2.19.42 I got no output
>
>
>1. Menu File > Import MusicXML
>2. Select a MusicXML file
>3. Execute musicxml2ly
>
> Expect: The import dialog disappears and a new code window with the
> generated ly file should open
> Actual: The import dialog disappears but nothing else
>
> In 2.19.80 LP is running (and says it can take some time...), so will post
> another after the process completes 
>
> Mike Dean
>
> On Mon, Dec 11, 2017 at 12:02 PM, Martin Tarenskeen <
> m.tarensk...@zonnet.nl> wrote:
>
>>
>>
>> On Mon, 11 Dec 2017, Mike Dean wrote:
>>
>> Observation:Frescobaldi 3.0 is not playing nicely at all with musicxml
>>> file export
>>> (no new developments from this page: https://github.com/wbsof
>>> t/frescobaldi/issues/910)
>>> II'm looking to do the import directly from lilypond, but am not sure
>>> how to go about it...
>>> the musicxml files (uncompressed and compressed) are attached
>>>
>>
>> Frescobaldi calls musicxml2ly to do the conversion. musicxml2ly is a
>> python script that is part of the LilyPond distribution.
>>
>> I tried your musicxml file and it seems to convert to lilypond files fine
>> on my system. Could you be more specific than just "not playing nice at
>> all"?
>>
>> --
>>
>> MT
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Converting musicxml files

[Mike Dean]

Hi Martin:
I am not sure if I was doing the steps correctly (was working with
Frescobaldi 3.01 and LP 2.19.42; have since updated to 2.19.80)
Am trying the steps again; in 2.19.42 I got no output


   1. Menu File > Import MusicXML
   2. Select a MusicXML file
   3. Execute musicxml2ly

Expect: The import dialog disappears and a new code window with the
generated ly file should open
Actual: The import dialog disappears but nothing else

In 2.19.80 LP is running (and says it can take some time...), so will post
another after the process completes 

Mike Dean

On Mon, Dec 11, 2017 at 12:02 PM, Martin Tarenskeen <m.tarensk...@zonnet.nl>
wrote:

>
>
> On Mon, 11 Dec 2017, Mike Dean wrote:
>
> Observation:Frescobaldi 3.0 is not playing nicely at all with musicxml
>> file export
>> (no new developments from this page: https://github.com/wbsof
>> t/frescobaldi/issues/910)
>> II'm looking to do the import directly from lilypond, but am not sure how
>> to go about it...
>> the musicxml files (uncompressed and compressed) are attached
>>
>
> Frescobaldi calls musicxml2ly to do the conversion. musicxml2ly is a
> python script that is part of the LilyPond distribution.
>
> I tried your musicxml file and it seems to convert to lilypond files fine
> on my system. Could you be more specific than just "not playing nice at
> all"?
>
> --
>
> MT
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unofficial MusicXML test suite access problem

[Phil Holmes]

- Original Message - 
From: "Menu Jacques" <imj-...@bluewin.ch>

To: "Mailinglist Lilypond" <lilypond-user@gnu.org>
Cc: "Menu Jacques" <imj-...@bluewin.ch>
Sent: Thursday, May 25, 2017 10:07 PM
Subject: Unofficial MusicXML test suite access problem



Hello folks,

— For your information —

The links in that page:

http://lilypond.org/doc/v2.19/input/regression/musicxml/collated-files.html

seem to be broken or to lead to a zip archive containing an empty « home » 
directory.


The same holds for:

http://lilypond.org/doc/v2.18/input/regression/musicxml/collated-files.html

JM


The link looks fine to me - an HTML list of test files and output.

--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Unofficial MusicXML test suite access problem

[Menu Jacques]

Hello folks,

— For your information —

The links in that page:


http://lilypond.org/doc/v2.19/input/regression/musicxml/collated-files.html

seem to be broken or to lead to a zip archive containing an empty « home » 
directory.

The same holds for:


http://lilypond.org/doc/v2.18/input/regression/musicxml/collated-files.html

JM



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

LilyPond MusicXML export

[Menu Jacques]

Hello Folks,

A newbie question : does there exist something simililar to \displayMusic, that 
would display the structure of \score blocks? This could be a starting point 
for such an export.

And also : has it been considered/studied to perform a two-pass compilation of 
LP, with the first pass creating some internal form as Scheme data (hence the 
question above) and the second pass creating the grobs from the latter? Such a 
separation of concerns could also help I guess, even though it might involve 
much work.

JM


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi MusicXML import

[imj-muz...@bluewin.ch]

Hello Johan,

... but Jeep the original line breaks, to ease score fine tuning.

Jacques Menu, iPhone

> Le 9 août 2016 à 12:34, Johan Vromans <jvrom...@squirrel.nl> a écrit :
> 
> With MusicXML, import could you please add --no-stem-directions to the
> settings?
> 
> Maybe even better (and easier) if MusicXML2ly had a power option to "Ignore
> everything that LilyPond can do better".
> 
> -- Johan
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Frescobaldi MusicXML import

[Johan Vromans]

With MusicXML, import could you please add --no-stem-directions to the
settings?

Maybe even better (and easier) if MusicXML2ly had a power option to "Ignore
everything that LilyPond can do better".

-- Johan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[Urs Liska]

Am 10. April 2016 16:32:33 MESZ, schrieb Martin Tarenskeen 
:
>
>
>On Sun, 10 Apr 2016, mj wrote:
>
>> Hi all,
>> Anyway, thanks for the helping to find the option in frescobali.
>
>P.S. Frescobaldi uses the python-ly library. It's part of the
>Frescobaldi 
>installer (I guess).
>
>There is also a standalone commandline utility called "ly" (python
>script) 
>that can do this, and several other tricks with lilypond files, without
>
>frescobaldi. (It has exactly the same flaws off coarse)

And FWIW I'm currently writing a Node.js wrapper for python-ly which will give 
access to the library for web developers.

Urs 

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[Martin Tarenskeen]

On Sun, 10 Apr 2016, mj wrote:


Hi all,
Anyway, thanks for the helping to find the option in frescobali.


P.S. Frescobaldi uses the python-ly library. It's part of the Frescobaldi 
installer (I guess).


There is also a standalone commandline utility called "ly" (python script) 
that can do this, and several other tricks with lilypond files, without 
frescobaldi. (It has exactly the same flaws off coarse)


--

MT

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[Urs Liska]

Am 10. April 2016 12:52:19 MESZ, schrieb mj <li...@merit.unu.edu>:
>Hi all,
>
>On 04/09/2016 11:34 PM, Martin Tarenskeen wrote:
>> Warning: It's hidden as "experimental" with a reason. Don't expect
>> miracles from it.
>>
>
>Played with it a little bit, and yes, agreed... it is still a little
>bit 
>bumpy, yes... :-)
>
>Leaving out \chordmode improves the musicxml output quite a bit, btw. 
>The only error that remains is "Unknown command \break", and the 
>resulting file imports ok into musescore, for example.
>
>Reason I like musicxml (besides being able to import lilypond stuff
>into 
>other programs) is that Gustaf (https://gogustaf.com) uses it as it's 
>native file format. It would be useful to be able to import my lilypond
>
>files into my digital sheet music library there.
>
>Unfortunately I am no programmer myself, so I can't help out
>practically.

You *can* help by opening issues with concrete examples and descriptions at 
https://github.com/wbsoft/python-ly/issues.

Urs

>
>Anyway, thanks for the helping to find the option in frescobali.
>
>MJ
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[mj]

Hi all,

On 04/09/2016 11:34 PM, Martin Tarenskeen wrote:

Warning: It's hidden as "experimental" with a reason. Don't expect
miracles from it.



Played with it a little bit, and yes, agreed... it is still a little bit 
bumpy, yes... :-)


Leaving out \chordmode improves the musicxml output quite a bit, btw. 
The only error that remains is "Unknown command \break", and the 
resulting file imports ok into musescore, for example.


Reason I like musicxml (besides being able to import lilypond stuff into 
other programs) is that Gustaf (https://gogustaf.com) uses it as it's 
native file format. It would be useful to be able to import my lilypond 
files into my digital sheet music library there.


Unfortunately I am no programmer myself, so I can't help out practically.

Anyway, thanks for the helping to find the option in frescobali.

MJ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[mj]

Thanks for the quick responses!

MJ

On 04/09/2016 11:27 PM, Urs Liska wrote:



Am 09.04.2016 um 23:03 schrieb mj:

Hi,

I noticed that there is musicxml2ly, but is there also some
ly2musicxml functionality?

I use frescobaldi, but also there (version 2.18.2) the function is not
present.

Does lilypond only IMPORT musicxml?


In Frescobaldi you have to enable "Experimental features" in the
Preferences dialog to access the MusicXML export.
And as this suggests: it is still very experimental.
But by using it (and sending reports) you can help improve it.

HTH
Urs



Regards,
MJ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[Martin Tarenskeen]

On Sat, 9 Apr 2016, mj wrote:


Hi,

I noticed that there is musicxml2ly, but is there also some ly2musicxml 
functionality?


I use frescobaldi, but also there (version 2.18.2) the function is not 
present.


The function is present, but hidden because it is still an experimental 
feature.


In Frescobaldi you enable it in

Edit -> Preferences... -> General Preferences: Experimental Features

Warning: It's hidden as "experimental" with a reason. Don't expect 
miracles from it.


--

MT

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: musicxml export

[Urs Liska]

Am 09.04.2016 um 23:03 schrieb mj:
> Hi,
>
> I noticed that there is musicxml2ly, but is there also some
> ly2musicxml functionality?
>
> I use frescobaldi, but also there (version 2.18.2) the function is not
> present.
>
> Does lilypond only IMPORT musicxml?

In Frescobaldi you have to enable "Experimental features" in the
Preferences dialog to access the MusicXML export.
And as this suggests: it is still very experimental.
But by using it (and sending reports) you can help improve it.

HTH
Urs

>
> Regards,
> MJ
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

musicxml export

[mj]

Hi,

I noticed that there is musicxml2ly, but is there also some ly2musicxml 
functionality?


I use frescobaldi, but also there (version 2.18.2) the function is not 
present.


Does lilypond only IMPORT musicxml?

Regards,
MJ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[N. Andrew Walsh]

Second that. My only plea is to continue improving and developing lily's
MusicXML capabilities. My project is going to a publisher who explicitly
refuses to accept Lilypond files, and will only accept the project if I can
provide a MusicXML export that his in-house engraver can then open.

I guess my question would be: what is the current outlook for MusicXML,
what are the current issues, and what progress have we made?

Cheers,

A

On Wed, Apr 15, 2015 at 8:53 AM, Martin Tarenskeen m.tarensk...@zonnet.nl
wrote:



 On Wed, 15 Apr 2015, Urs Liska wrote:

  Hi all,

 if anyone has questions about, issues with or suggestions for MusicXML
 (LilyPond related or not) you may call me privately until this afternoon 5
 PM CEST (= UTC+2).
 I have the opportunity to meet Michael Good who's open to that. (Of
 course this doesn't include how do I ...? or other questions that should
 rather be posted on stackexchange.)


 I don't really have much useful to contribute, sorry. But if your post
 suggests that there is still at least the wish and intention to continue
 developing and improving MusicXML support for LilyPond I can only encourage
 this.

 Now we only need more active developers who want to spend their precious
 time in this important but apparently complex stuff.

 Compared to other opensource projects like MuseScore and Willem Vree's
 abc2xml/xml2abc LilyPond's MusicXML import/export-support is far behind.

 --

 MT








 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Kieren MacMillan]

Hi all,

 I'm not sure if this is the right time/place/thread, but I think it would
 be easier to have a kind of MusicXML-Light that only contains information
 about notes and lyrics

That first step would make a huge difference.

 well, in addition you would surely want slurs, articulations, dynamic
 markings, ornaments (anything else that occurs repeatedly throughout the
 music that you would not wish to go over adding by hand).
 
 This is what I meant with information about notes and lyrics”.

To piggy-back on my recent “content versus presentation” post, the request here 
is that MusicXML-Light output content [only].

Cheers,
Kieren.
___

Kieren MacMillan, composer
www:  http://www.kierenmacmillan.info
email:  i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Richard Shann]

On Wed, 2015-04-15 at 15:52 +0200, N. Andrew Walsh wrote:
 Second that. My only plea is to continue improving and developing
 lily's MusicXML capabilities. My project is going to a publisher who
 explicitly refuses to accept Lilypond files, and will only accept the
 project if I can provide a MusicXML export that his in-house engraver
 can then open.
 
The crunch would come when his in-house engraver tried to open a foreign
piece of MusicXML. Is it looking for instruction on how to do the
beaming for example, how wide the margins are ... if so the PDF would be
the way to go. If not, you are in the MusicXML-light category that Johan
just referred to in his email. There are many ways to describe the same
piece of music with MusicXML and I suspect there will never be a program
that could read and make sense of all of them.

Richard

 
 I guess my question would be: what is the current outlook for
 MusicXML, what are the current issues, and what progress have we made?
 
 
 Cheers,
 
 
 A
 
 On Wed, Apr 15, 2015 at 8:53 AM, Martin Tarenskeen
 m.tarensk...@zonnet.nl wrote:
 
 
 On Wed, 15 Apr 2015, Urs Liska wrote:
 
 Hi all,
 
 if anyone has questions about, issues with or
 suggestions for MusicXML (LilyPond related or not) you
 may call me privately until this afternoon 5 PM CEST
 (= UTC+2).
 I have the opportunity to meet Michael Good who's open
 to that. (Of course this doesn't include how do
 I ...? or other questions that should rather be
 posted on stackexchange.)
 
 I don't really have much useful to contribute, sorry. But if
 your post suggests that there is still at least the wish and
 intention to continue developing and improving MusicXML
 support for LilyPond I can only encourage this.
 
 Now we only need more active developers who want to spend
 their precious time in this important but apparently complex
 stuff.
 
 Compared to other opensource projects like MuseScore and
 Willem Vree's abc2xml/xml2abc LilyPond's MusicXML
 import/export-support is far behind.
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Johan Vromans]

On Wed, 15 Apr 2015 08:53:18 +0200 (CEST)
Martin Tarenskeen m.tarensk...@zonnet.nl wrote:

 Compared to other opensource projects like MuseScore and Willem Vree's 
 abc2xml/xml2abc LilyPond's MusicXML import/export-support is far 
 behind.

I'm not sure if this is the right time/place/thread, but I think it would
be easier to have a kind of MusicXML-Light that only contains information
about notes and lyrics but does not have all the technical details about
breaks and placements. The reason we (I, at least) want to be able to import
music data from (e.g.) Sibelius into LilyPond is to have LP do the superior
typesetting.

-- Johan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Richard Shann]

On Wed, 2015-04-15 at 16:47 +0200, Johan Vromans wrote:
 On Wed, 15 Apr 2015 08:53:18 +0200 (CEST)
 Martin Tarenskeen m.tarensk...@zonnet.nl wrote:
 
  Compared to other opensource projects like MuseScore and Willem Vree's 
  abc2xml/xml2abc LilyPond's MusicXML import/export-support is far 
  behind.
 
 I'm not sure if this is the right time/place/thread, but I think it would
 be easier to have a kind of MusicXML-Light that only contains information
 about notes and lyrics 

well, in addition you would surely want slurs, articulations, dynamic
markings, ornaments (anything else that occurs repeatedly throughout the
music that you would not wish to go over adding by hand).

Richard

 but does not have all the technical details about
 breaks and placements. The reason we (I, at least) want to be able to import
 music data from (e.g.) Sibelius into LilyPond is to have LP do the superior
 typesetting.
 
 -- Johan
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Johan Vromans]

[Quoting Richard Shann, on April 15 2015, 16:04, in Re: Any current Musi]
  I'm not sure if this is the right time/place/thread, but I think it would
  be easier to have a kind of MusicXML-Light that only contains information
  about notes and lyrics 
 
 well, in addition you would surely want slurs, articulations, dynamic
 markings, ornaments (anything else that occurs repeatedly throughout the
 music that you would not wish to go over adding by hand).

Exactly. This is what I meant with information about notes and
lyrics.

-- Johan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Piaras Hoban]

Hi all,

 I'm not sure if this is the right time/place/thread, but I think it
would
 be easier to have a kind of MusicXML-Light that only contains
information
 about notes and lyrics

 That first step would make a huge difference.


I think the Music Encoding Initiative has this very thing in mind, amongst
other goals.

I think it's possibly quite relevant to the discussion of Lilypond's
MusicXML support.

http://music-encoding.org/home

piaras


On 15 April 2015 at 16:21, Kieren MacMillan kieren_macmil...@sympatico.ca
wrote:

 Hi all,

  I'm not sure if this is the right time/place/thread, but I think it
 would
  be easier to have a kind of MusicXML-Light that only contains
 information
  about notes and lyrics

 That first step would make a huge difference.

  well, in addition you would surely want slurs, articulations, dynamic
  markings, ornaments (anything else that occurs repeatedly throughout the
  music that you would not wish to go over adding by hand).
 
  This is what I meant with information about notes and lyrics”.

 To piggy-back on my recent “content versus presentation” post, the request
 here is that MusicXML-Light output content [only].

 Cheers,
 Kieren.
 ___

 Kieren MacMillan, composer
 www:  http://www.kierenmacmillan.info
 email:  i...@kierenmacmillan.info


 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Urs Liska]

Am 15. April 2015 18:25:06 MESZ, schrieb Piaras Hoban phoba...@googlemail.com:
Hi all,

 I'm not sure if this is the right time/place/thread, but I think it
would
 be easier to have a kind of MusicXML-Light that only contains
information
 about notes and lyrics

 That first step would make a huge difference.


I think the Music Encoding Initiative has this very thing in mind,
amongst
other goals.

I think it's possibly quite relevant to the discussion of Lilypond's
MusicXML support.

http://music-encoding.org/home

piaras


Actually this is part of the discussion on several related threads on the 
frescobaldi and python-ly issue trackers.

And we will be present with a talk at the upcoming Music Encoding Conference in 
May. I hope we will be able to raise dome mutual interest. Or actually to 
activate dome mutual intetest I know of.

Urs


On 15 April 2015 at 16:21, Kieren MacMillan
kieren_macmil...@sympatico.ca
wrote:

 Hi all,

  I'm not sure if this is the right time/place/thread, but I think
it
 would
  be easier to have a kind of MusicXML-Light that only contains
 information
  about notes and lyrics

 That first step would make a huge difference.

  well, in addition you would surely want slurs, articulations,
dynamic
  markings, ornaments (anything else that occurs repeatedly
throughout the
  music that you would not wish to go over adding by hand).
 
  This is what I meant with information about notes and lyrics”.

 To piggy-back on my recent “content versus presentation” post, the
request
 here is that MusicXML-Light output content [only].

 Cheers,
 Kieren.
 ___

 Kieren MacMillan, composer
 www:  http://www.kierenmacmillan.info
 email:  i...@kierenmacmillan.info


 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Any current MusicXML questions/issues/suggestions?

[Martin Tarenskeen]

On Wed, 15 Apr 2015, Urs Liska wrote:


Hi all,

if anyone has questions about, issues with or suggestions for MusicXML 
(LilyPond related or not) you may call me privately until this afternoon 5 PM 
CEST (= UTC+2).
I have the opportunity to meet Michael Good who's open to that. (Of course 
this doesn't include how do I ...? or other questions that should rather be 
posted on stackexchange.)


I don't really have much useful to contribute, sorry. But if your post 
suggests that there is still at least the wish and intention to continue 
developing and improving MusicXML support for LilyPond I can only 
encourage this.


Now we only need more active developers who want to spend their precious 
time in this important but apparently complex stuff.


Compared to other opensource projects like MuseScore and Willem Vree's 
abc2xml/xml2abc LilyPond's MusicXML import/export-support is far 
behind.


--

MT







___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Any current MusicXML questions/issues/suggestions?

[Urs Liska]

Hi all,

if anyone has questions about, issues with or suggestions for MusicXML 
(LilyPond related or not) you may call me privately until this afternoon 
5 PM CEST (= UTC+2).
I have the opportunity to meet Michael Good who's open to that. (Of 
course this doesn't include how do I ...? or other questions that 
should rather be posted on stackexchange.)


Best
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Frescobaldi] Re: Frescobaldi musicxml export

[Peter Bjuhr]

On 01/10/2014 07:37 AM, Martin Tarenskeen wrote:



On Thu, 9 Jan 2014, j...@post.cz wrote:


Hi,
I am new to this forum and also new to Lilypond  Frescobaldi. Still
learning the basics...
I would like to ask for some help with xml import/export since I am 
not able

to get it to work.


First you need to know that musicxml import (musicxml2ly) is usable, 
but far from perfect yet.


The situation for musixml export is in a VERY early stage of 
development and not yet suitable for serious work. Too many even basic 
elements of music notation are not implemented. But at least someone 
is working on it and the future looks promising.




TypeError: set_time() takes exactly 3 arguments (2 given)


My guess is that you have not specified a time signature in you 
testing score:


\time 4/4

Lilypond assumes 4/4 by default when time signature is given, but you 
version of Frescobaldi's musicxml importer doesn't. (has been fixed in 
development by now)




Like Martin writes, the issue I think you're referring to was not fixed 
until quite recently. So you need to update to the latest development 
version for this to work. Sorry about the inconvenience!


I also like to express that all usage report and feedback is inspiring 
for further development, thanks!


Best
Peter

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user