You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(11) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Dominique F. <fo...@gr...> - 2020-01-13 08:44:08
|
Dear all, A new version of the MusicXML library is available from GitHub: https://github.com/grame-cncm/libmusicxml/releases <http://code.google.com/p/libmusicxml/downloads/list> Main changes: • improved version of the guido converter (version 3.0) • improved version of the lilypond converter (version 0.92) • new xml2brl (Braille Music representation) converter (experimental) Note that the javascript library (actually WASM) is available from npm: https://www.npmjs.com/package/@grame/libmusicxml Best regards, Dominique Fober |
From: Dominique F. <fo...@gr...> - 2018-10-25 13:03:24
|
Dear all, A new version of the MusicXML library is available at the following address: https://github.com/grame-cncm/libmusicxml/releases <http://code.google.com/p/libmusicxml/downloads/list> The library has been updated to version 3.1 of the MusicXML format. The package includes also a new converter from musicxml to lilypond. Many thanks to Jacques Menu for his huge work on ‘xml2ly’. See the change log for more details. Best regards, Dominique Fober |
From: Dominique F. <fo...@gr...> - 2017-03-16 09:07:05
|
Hi all, The libmusicxml src code is now part of the grame account (https://github.com/grame-cncm <https://github.com/grame-cncm>). You have to change your remote origin to https://github.com/grame-cncm/libmusicxml.git i.e. > git remote set-url origin https://github.com/grame-cncm/libmusicxml.git All the best, — Dominique |
From: Dominique F. <fo...@gr...> - 2017-03-13 15:47:24
|
Hi all, The libmusicxml src code will move from my personal account (https://github.com/dfober <https://github.com/dfober>) to the grame account (https://github.com/grame-cncm <https://github.com/grame-cncm>). In order to make you life easier with the migration, I invite you to synchronize your local repository. The migration will be launched on Thursday 16 around 9am (french time i.e. GMT+1) All the best, — Dominique ps: you’ll only have to set your origin url to use the new location (i.e. > git remote -set-url origin “the new url”) |
From: Dominique F. <fo...@gr...> - 2016-09-22 08:17:24
|
> Le 22 sept. 2016 à 10:02, Arshia Cont <ars...@an...> a écrit : > > Dominique, > > I will definitely. In parallel, it would help me if you could point me out to where I can learn about dx dy coordinates in Guido (where’s the zero-point to start with etc.). Actually, I think there is no such description available, apart in the source code. One way to get it could be to use a score with all the elements of interest, without displacement. I’ll try to extract that. It could be also the opportunity to normalize if it deviates from classical recommendations. — Dom > >> On 22 Sep 2016, at 09:38, Dominique Fober <fo...@gr...> wrote: >> >> Did you try to post your question to the musicxml list? >> — >> Dom >> >>> Le 14 sept. 2016 à 10:55, Arshia Cont <ars...@an...> a écrit : >>> >>> Hello list, >>> >>> In my attempt to improve the xml2guido, I have run into a MusicXML related problem for which I have difficulties finding an answer online! So I thought I would ask here. >>> >>> Let’s take Articulations as an example. in MusicXML you can have “default-y”, “placement” and “relative-y” attributes for an articulation. The meaning of both default-y and relative-y seem to change as a function of “placement”! >>> >>> Can anyone point me to a document explaining how these actually relate to each other? >>> >>> My goal is to infer correct “dx”, “dy” (and “position” if available) parameters in Guido once and for all! >>> >>> Thanks in advance, >>> >>> >>> Arshia Cont >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Libmusicxml-devel mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel >> > |
From: Arshia C. <ars...@an...> - 2016-09-22 08:03:08
|
Dominique, I will definitely. In parallel, it would help me if you could point me out to where I can learn about dx dy coordinates in Guido (where’s the zero-point to start with etc.). > On 22 Sep 2016, at 09:38, Dominique Fober <fo...@gr...> wrote: > > Did you try to post your question to the musicxml list? > — > Dom > >> Le 14 sept. 2016 à 10:55, Arshia Cont <ars...@an...> a écrit : >> >> Hello list, >> >> In my attempt to improve the xml2guido, I have run into a MusicXML related problem for which I have difficulties finding an answer online! So I thought I would ask here. >> >> Let’s take Articulations as an example. in MusicXML you can have “default-y”, “placement” and “relative-y” attributes for an articulation. The meaning of both default-y and relative-y seem to change as a function of “placement”! >> >> Can anyone point me to a document explaining how these actually relate to each other? >> >> My goal is to infer correct “dx”, “dy” (and “position” if available) parameters in Guido once and for all! >> >> Thanks in advance, >> >> >> Arshia Cont >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Libmusicxml-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel > |
From: Dominique F. <fo...@gr...> - 2016-09-22 07:38:50
|
Did you try to post your question to the musicxml list? — Dom > Le 14 sept. 2016 à 10:55, Arshia Cont <ars...@an...> a écrit : > > Hello list, > > In my attempt to improve the xml2guido, I have run into a MusicXML related problem for which I have difficulties finding an answer online! So I thought I would ask here. > > Let’s take Articulations as an example. in MusicXML you can have “default-y”, “placement” and “relative-y” attributes for an articulation. The meaning of both default-y and relative-y seem to change as a function of “placement”! > > Can anyone point me to a document explaining how these actually relate to each other? > > My goal is to infer correct “dx”, “dy” (and “position” if available) parameters in Guido once and for all! > > Thanks in advance, > > > Arshia Cont > ------------------------------------------------------------------------------ > _______________________________________________ > Libmusicxml-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel |
From: Dominique F. <fo...@gr...> - 2016-09-14 15:01:13
|
> Le 14 sept. 2016 à 10:02, Arshia Cont <ars...@an...> a écrit : > > Dominique: > >> It looks like your branch is based on the master branch. I’ve merged the ‘dev’ branch to your branch (just a couple of changes), it provides the make utilities in the build folder as well as some improvements (see the change log). >> The merged branch has been pushed back to github. >> >> In order to maintain the changes history, could you put your improvements into the CHANGELOG.txt file as well as check the versions numbers (in versions.cpp), the xml2guido version should be increased. >> >> Should I merge your changes to the ‘dev’ branch or should I wait for more tests? > > You can go ahead and merge into the Dev branch. And I’ll take things from there following your suggestions. that’s done > > See some thoughts on Lyrics conversion below. > > >> In a second step, new binary packages will be published and everything merged to the master branch. >> >> Here comes the question of validation: in samples/musixml, there is already a set of xml files and a makefile that converts them to gmn files. You could add files that include the new handled elements. Now validation itself is still manual: you have to open the output file and look for correctness. >> That could be made a bit more automatic by comparison with a set of reference files. What do you think ? > > I can add test files. I have some “unit tests” that I can add but most “problems” appear on “complex scores” meaning real pieces where we see details here and there. I’ll try to reduce them to unit tests as much as I can when you merge to the Dev. > > Note on Lyrics conversion: > > I had to make a design choice for this as Lyrics in XML are declared on each note and continuation is assured by “syllabic” tags. Whereas in Guido, the Lyrics tag can embed a sequence of notes and a phrase. > > If you choose the Guido way (Lyrics on sequences) you’ll very quickly run into Spacing problems. This is simply because the Guido renderer does NOT consider lyric words in horizontal spacing of the score. This leads to words overlapping quite often. > > So I had to convert lyrics on a note-by-note basis and use heuristics (such as associated note duration and word length) to add a Space tag between them. > > This works totally fine on a simple one-staff score. But the result is not acceptable if your system has (e.g.) two staves and lyrics (with manual spacing) on the first. The Space tag on the first staff changes things on the second and the result is not appealing. of course, this is because voices should remain graphically synchronized. Actually, the problem is not trivial and has no general solution (see Gould - Behind bars p.440) > > Conclusion: We should in the long run get rid of the manual/heuristic Space tag in the Lyrics conversion. To do this, we’d need to consider lyrics as first-class citizens in the Guido Renderer. I agree. One hypothesis in this direction would be to add springs and rods to lyrics. > And we are willing to contribute on this. you’re welcome ! — Dom > > > Cheers, > > > Arshia > |
From: Arshia C. <ars...@an...> - 2016-09-14 08:56:08
|
Hello list, In my attempt to improve the xml2guido, I have run into a MusicXML related problem for which I have difficulties finding an answer online! So I thought I would ask here. Let’s take Articulations as an example. in MusicXML you can have “default-y”, “placement” and “relative-y” attributes for an articulation. The meaning of both default-y and relative-y seem to change as a function of “placement”! Can anyone point me to a document explaining how these actually relate to each other? My goal is to infer correct “dx”, “dy” (and “position” if available) parameters in Guido once and for all! Thanks in advance, Arshia Cont |
From: Arshia C. <ars...@an...> - 2016-09-14 08:02:17
|
Dominique: > It looks like your branch is based on the master branch. I’ve merged the ‘dev’ branch to your branch (just a couple of changes), it provides the make utilities in the build folder as well as some improvements (see the change log). > The merged branch has been pushed back to github. > > In order to maintain the changes history, could you put your improvements into the CHANGELOG.txt file as well as check the versions numbers (in versions.cpp), the xml2guido version should be increased. > > Should I merge your changes to the ‘dev’ branch or should I wait for more tests? You can go ahead and merge into the Dev branch. And I’ll take things from there following your suggestions. See some thoughts on Lyrics conversion below. > In a second step, new binary packages will be published and everything merged to the master branch. > > Here comes the question of validation: in samples/musixml, there is already a set of xml files and a makefile that converts them to gmn files. You could add files that include the new handled elements. Now validation itself is still manual: you have to open the output file and look for correctness. > That could be made a bit more automatic by comparison with a set of reference files. What do you think ? I can add test files. I have some “unit tests” that I can add but most “problems” appear on “complex scores” meaning real pieces where we see details here and there. I’ll try to reduce them to unit tests as much as I can when you merge to the Dev. Note on Lyrics conversion: I had to make a design choice for this as Lyrics in XML are declared on each note and continuation is assured by “syllabic” tags. Whereas in Guido, the Lyrics tag can embed a sequence of notes and a phrase. If you choose the Guido way (Lyrics on sequences) you’ll very quickly run into Spacing problems. This is simply because the Guido renderer does NOT consider lyric words in horizontal spacing of the score. This leads to words overlapping quite often. So I had to convert lyrics on a note-by-note basis and use heuristics (such as associated note duration and word length) to add a Space tag between them. This works totally fine on a simple one-staff score. But the result is not acceptable if your system has (e.g.) two staves and lyrics (with manual spacing) on the first. The Space tag on the first staff changes things on the second and the result is not appealing. Conclusion: We should in the long run get rid of the manual/heuristic Space tag in the Lyrics conversion. To do this, we’d need to consider lyrics as first-class citizens in the Guido Renderer. And we are willing to contribute on this. Cheers, Arshia |
From: Dominique F. <fo...@gr...> - 2016-09-14 07:42:07
|
> Le 13 sept. 2016 à 18:46, Arshia Cont <ars...@an...> a écrit : > > Hello all, > > I just pushed a new brach on the Github dealing with MusicXML to Guido conversion, including (but not limited to): > > - Importing Rehearsal Marks using the new Enclosure attribute of Mark in Guido > > - Improving articulations on ‘chords’ > > - Importing Lyrics as close as possible to MusicXML (note that there are 2 design choices, where the most Guido-esque is commented). excellent ! I’ve got it and the result is fine. It looks like your branch is based on the master branch. I’ve merged the ‘dev’ branch to your branch (just a couple of changes), it provides the make utilities in the build folder as well as some improvements (see the change log). The merged branch has been pushed back to github. In order to maintain the changes history, could you put your improvements into the CHANGELOG.txt file as well as check the versions numbers (in versions.cpp), the xml2guido version should be increased. Should I merge your changes to the ‘dev’ branch or should I wait for more tests? In a second step, new binary packages will be published and everything merged to the master branch. Here comes the question of validation: in samples/musixml, there is already a set of xml files and a makefile that converts them to gmn files. You could add files that include the new handled elements. Now validation itself is still manual: you have to open the output file and look for correctness. That could be made a bit more automatic by comparison with a set of reference files. What do you think ? — Dom > > I’ll be pushing more to this branch in the coming weeks as we test and improve. > > Hope people will find it useful. > > > Arshia > ------------------------------------------------------------------------------ > _______________________________________________ > Libmusicxml-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel |
From: Arshia C. <ars...@an...> - 2016-09-13 16:46:34
|
Hello all, I just pushed a new brach on the Github dealing with MusicXML to Guido conversion, including (but not limited to): - Importing Rehearsal Marks using the new Enclosure attribute of Mark in Guido - Improving articulations on ‘chords’ - Importing Lyrics as close as possible to MusicXML (note that there are 2 design choices, where the most Guido-esque is commented). I’ll be pushing more to this branch in the coming weeks as we test and improve. Hope people will find it useful. Arshia |
From: Arshia C. <ars...@an...> - 2016-09-06 10:21:06
|
Hello list, In my attempt to enrich the xml2guido convertor, I’m looking at converting more markups in MusicXML to Guido. As such, “tempo markups” are currently missing. If I understand correctly they are in the WORDS tag, part of direction_type tag of MusicXML. For the time being, I’m inserting these strings if they exist, and if their “placement” is “above”, into the TEMPO tag of Guido (and mix them with Metronome if it exists). Is this the correct recommended way to convert? Is there also a way to infer the font attributes of WORDS into Guido’s Tempo tag? Also, since I’m at it: What would be the correct tag for conversion of WORDS with “placement” = “below”? I’m guessing just TEXT tag in Guido? Ofcourse, once everything passes tests I’ll push into Github. Arshia Cont |
From: Dominique F. <fo...@gr...> - 2016-09-02 11:08:49
|
Hi Arshia, > Le 2 sept. 2016 à 12:29, Arshia Cont <ars...@an...> a écrit : > > Hello Dominique et al > > I managed to implement a pretty coherent addition to libmusicxml that adds Lyrics for xml2guido convertor. I use the Advanced Guido Lyric stuff for this and everything works so far. That’s excellent! > > Is there any guidelines for submitting code to the repository? I suspect that we should no longer use Google Code?! right, google code is closed for a while the src code is now on github: https://github.com/dfober/libmusicxml <https://github.com/dfober/libmusicxml> I can add you as a collaborator and next I suggest you to create a branch where you can commit your changes. Do you have a github account? — Dom > > >> On 28 Jul 2016, at 14:22, Dominique Fober <fo...@gr...> wrote: >> >> >>> Le 28 juil. 2016 à 11:27, Arshia Cont <ars...@an...> a écrit : >>> >>> Thanks Dominique for the response. >>> >>>>> Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? >>>> >>>> no guideline but the sample code (and existing code for the conversion) should be clear enough. >>> >>> Can you point me to the sample code in question? >> >> see the ‘samples’ folder and connotes.cpp or partsummary.cpp for simple visitors samples >> regarding the global architecture, see also ‘doc/presentation/libmusicxml2.pdf' >> the guido converter is in src/guido >> >>> >>> Also, would you mind making a TODO list for the xml2guido visitors to implement? >> >> probably more easy to maintain a list of what is converted, I’ll do it >> >>> >>> I was also wondering how you’d recommend converting XML lyrics to Guido. I see documentations on MusicXML’s Lyrics encoding here: >>> http://www.musicxml.com/tutorial/the-midi-compatible-part/lyrics/ >>> Hard to find an equivalent for the \lyrics(…) in Guido to write a useful convertor… or maybe Google is not helping me.. >> >> that’s the tricky part: it’s sometimes quite awkward to convert from one representation to another one >> regarding guido side, lyric specification is in 'doc/advanced-guido-draft/lyrics.htm’ >> you can also find sample gmn code in 'gmn-examples/lyrics’ >> one of the problems is that there is no ‘verse’ notion in guido (although you can write them, but arranged in the graphic space) >> >> — >> Dom >> >> > |
From: Arshia C. <ars...@an...> - 2016-09-02 10:29:22
|
Hello Dominique et al I managed to implement a pretty coherent addition to libmusicxml that adds Lyrics for xml2guido convertor. I use the Advanced Guido Lyric stuff for this and everything works so far. Is there any guidelines for submitting code to the repository? I suspect that we should no longer use Google Code?! > On 28 Jul 2016, at 14:22, Dominique Fober <fo...@gr...> wrote: > > >> Le 28 juil. 2016 à 11:27, Arshia Cont <ars...@an...> a écrit : >> >> Thanks Dominique for the response. >> >>>> Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? >>> >>> no guideline but the sample code (and existing code for the conversion) should be clear enough. >> >> Can you point me to the sample code in question? > > see the ‘samples’ folder and connotes.cpp or partsummary.cpp for simple visitors samples > regarding the global architecture, see also ‘doc/presentation/libmusicxml2.pdf' > the guido converter is in src/guido > >> >> Also, would you mind making a TODO list for the xml2guido visitors to implement? > > probably more easy to maintain a list of what is converted, I’ll do it > >> >> I was also wondering how you’d recommend converting XML lyrics to Guido. I see documentations on MusicXML’s Lyrics encoding here: >> http://www.musicxml.com/tutorial/the-midi-compatible-part/lyrics/ >> Hard to find an equivalent for the \lyrics(…) in Guido to write a useful convertor… or maybe Google is not helping me.. > > that’s the tricky part: it’s sometimes quite awkward to convert from one representation to another one > regarding guido side, lyric specification is in 'doc/advanced-guido-draft/lyrics.htm’ > you can also find sample gmn code in 'gmn-examples/lyrics’ > one of the problems is that there is no ‘verse’ notion in guido (although you can write them, but arranged in the graphic space) > > — > Dom > > |
From: Dominique F. <fo...@gr...> - 2016-07-28 12:22:39
|
> Le 28 juil. 2016 à 11:27, Arshia Cont <ars...@an...> a écrit : > > Thanks Dominique for the response. > >>> Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? >> >> no guideline but the sample code (and existing code for the conversion) should be clear enough. > > Can you point me to the sample code in question? see the ‘samples’ folder and connotes.cpp or partsummary.cpp for simple visitors samples regarding the global architecture, see also ‘doc/presentation/libmusicxml2.pdf' the guido converter is in src/guido > > Also, would you mind making a TODO list for the xml2guido visitors to implement? probably more easy to maintain a list of what is converted, I’ll do it > > I was also wondering how you’d recommend converting XML lyrics to Guido. I see documentations on MusicXML’s Lyrics encoding here: > http://www.musicxml.com/tutorial/the-midi-compatible-part/lyrics/ > Hard to find an equivalent for the \lyrics(…) in Guido to write a useful convertor… or maybe Google is not helping me.. that’s the tricky part: it’s sometimes quite awkward to convert from one representation to another one regarding guido side, lyric specification is in 'doc/advanced-guido-draft/lyrics.htm’ you can also find sample gmn code in 'gmn-examples/lyrics’ one of the problems is that there is no ‘verse’ notion in guido (although you can write them, but arranged in the graphic space) — Dom |
From: Arshia C. <ars...@an...> - 2016-07-28 09:27:14
|
Thanks Dominique for the response. >> Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? > > no guideline but the sample code (and existing code for the conversion) should be clear enough. Can you point me to the sample code in question? Also, would you mind making a TODO list for the xml2guido visitors to implement? I was also wondering how you’d recommend converting XML lyrics to Guido. I see documentations on MusicXML’s Lyrics encoding here: http://www.musicxml.com/tutorial/the-midi-compatible-part/lyrics/ Hard to find an equivalent for the \lyrics(…) in Guido to write a useful convertor… or maybe Google is not helping me.. |
From: Dominique F. <fo...@gr...> - 2016-07-28 09:18:34
|
Hi Arshia, > Le 27 juil. 2016 à 12:45, Arshia Cont <ars...@an...> a écrit : > > Hello list, > > And thanks for the great work! > > I am using MusicXML to Guido convertor in this library and I noticed that not all MusicXML features are actually converted to Guido/GMN files whereas they exist in both sides. One of them which would be very useful in my case would be the Lyrics (which also exist in Guido format). > > After a quick look into the code, I realised that there is no visitor for XML Lyrics (to undertake conversions) and I also noticed that (I might be wrong) that there is also no visitor for TRILLs and such. right, there is a significant set of elements that are note converted (including lyrics) > > Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? no guideline but the sample code (and existing code for the conversion) should be clear enough. > > Also: I’m sending this message here and not to the Guido list since I thought it’s most appropriate. Please advice if otherwise. that’s the right place Best — Dom > > Thanks in advance, > > > Arshia Cont > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Libmusicxml-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel |
From: Arshia C. <ars...@an...> - 2016-07-27 10:45:10
|
Hello list, And thanks for the great work! I am using MusicXML to Guido convertor in this library and I noticed that not all MusicXML features are actually converted to Guido/GMN files whereas they exist in both sides. One of them which would be very useful in my case would be the Lyrics (which also exist in Guido format). After a quick look into the code, I realised that there is no visitor for XML Lyrics (to undertake conversions) and I also noticed that (I might be wrong) that there is also no visitor for TRILLs and such. Is there any Guideline on how to add this conversion for xml2guido, or maybe it exists already and I’m doing something wrong? Also: I’m sending this message here and not to the Guido list since I thought it’s most appropriate. Please advice if otherwise. Thanks in advance, Arshia Cont |
From: Dominique F. <fo...@gr...> - 2015-10-28 18:54:16
|
Can you tell me a bit more about what you try to compile and how. Normally, everything should be compiled within the cmake folder, including the tools and the xml2guido converter. But the tools are not installed by the ‘install’ target. Best — Dominique > Le 28 oct. 2015 à 18:03, Dorien Herremans <dor...@gm...> a écrit : > > As an update, I compiled with the header specified: > > g++ xml2guido.cpp -I/usr/local/include/libmusicxml > > It gives me a different error now. > > In function main': xml2guido.cpp:(.text+0xf9): undefined reference to musicxmlfd2guido' xml2guido.cpp:(.text+0x115): undefined reference to `musicxmlfile2guido' collect2: error: ld returned 1 exit status > > Not really sure why it can't find this library... > > On 28 October 2015 at 15:28, Dorien Herremans <dor...@gm... <mailto:dor...@gm...>> wrote: > Hello, > > Thanks for making this library! > > I am trying to run the musicxml1guido script on Ubuntu 15.04. > > Since I think the binary is for an older version, I have compiled the source (cmake, make, make install). All went well and a bunch of files where copied: > > Install the project... > -- Install configuration: "" > -- Installing: /usr/local/lib/libmusicxml2.so.3.00 > -- Installing: /usr/local/lib/libmusicxml2.so > -- Installing: /usr/local/include/libmusicxml/musicxmlfactory.h > -- Installing: /usr/local/include/libmusicxml/sortvisitor.h > -- Installing: /usr/local/include/libmusicxml/xmlreader.h > ... etc > > When I try to compile the script with g++ it tells me: > > libmusicxml.h: No such file or directory > > Should I have set a path variable or something? > > Many thanks for any help, > > Dorien > > > > -- > Dorien Herremans > > > > -- > Dorien Herremans > ------------------------------------------------------------------------------ > _______________________________________________ > Libmusicxml-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmusicxml-devel |
From: Dorien H. <dor...@gm...> - 2015-10-28 17:04:05
|
As an update, I compiled with the header specified: *g++ xml2guido.cpp -I/usr/local/include/libmusicxml* It gives me a different error now. *In function main': xml2guido.cpp:(.text+0xf9): undefined reference to musicxmlfd2guido' xml2guido.cpp:(.text+0x115): undefined reference to `musicxmlfile2guido' collect2: error: ld returned 1 exit status* Not really sure why it can't find this library... On 28 October 2015 at 15:28, Dorien Herremans <dor...@gm...> wrote: > Hello, > > Thanks for making this library! > > I am trying to run the musicxml1guido script on Ubuntu 15.04. > > Since I think the binary is for an older version, I have compiled the > source (cmake, make, make install). All went well and a bunch of files > where copied: > > Install the project... > -- Install configuration: "" > -- Installing: /usr/local/lib/libmusicxml2.so.3.00 > -- Installing: /usr/local/lib/libmusicxml2.so > -- Installing: /usr/local/include/libmusicxml/musicxmlfactory.h > -- Installing: /usr/local/include/libmusicxml/sortvisitor.h > -- Installing: /usr/local/include/libmusicxml/xmlreader.h > ... etc > > When I try to compile the script with g++ it tells me: > > libmusicxml.h: No such file or directory > > Should I have set a path variable or something? > > Many thanks for any help, > > Dorien > > > > -- > Dorien Herremans > -- Dorien Herremans |
From: Dorien H. <dor...@gm...> - 2015-10-28 15:28:40
|
Hello, Thanks for making this library! I am trying to run the musicxml1guido script on Ubuntu 15.04. Since I think the binary is for an older version, I have compiled the source (cmake, make, make install). All went well and a bunch of files where copied: Install the project... -- Install configuration: "" -- Installing: /usr/local/lib/libmusicxml2.so.3.00 -- Installing: /usr/local/lib/libmusicxml2.so -- Installing: /usr/local/include/libmusicxml/musicxmlfactory.h -- Installing: /usr/local/include/libmusicxml/sortvisitor.h -- Installing: /usr/local/include/libmusicxml/xmlreader.h ... etc When I try to compile the script with g++ it tells me: libmusicxml.h: No such file or directory Should I have set a path variable or something? Many thanks for any help, Dorien -- Dorien Herremans |
From: Dominique F. <fo...@gr...> - 2015-03-14 21:05:51
|
Hi all, The source code of libmusicxml has moved from google code to github: https://github.com/dfober/libmusicxml <https://github.com/dfober/libmusicxml> This is due to the planned shutting down of google code. cvs and svn repositories are still available on sourceforge but for history only (they are outdated) All the best, — Dominique |
From: Dominique F. <fo...@gr...> - 2013-04-16 10:20:02
|
Dear all, Up to now, the musicxml library has been available under the LGPL license and that was starting to be problematic for platforms where dynamic link was not allowed (actually IOS). In order to solve this problem and also to provide more flexibility for the library use, the license has been changed to the Mozilla Public License. This license allows static link without contaminating the whole project. For more information: http://en.wikipedia.org/wiki/Mozilla_Public_License http://www.mozilla.org/MPL/2.0/ Best, -- Dominique Fober |
From: Dominique F. <fo...@gr...> - 2012-11-20 11:07:02
|
Dear all, A new version of the MusicXML library is available at the following address: http://code.google.com/p/libmusicxml/downloads/list The library has been updated to version 3.0 of the MusicXML format. Best regards, Dominique Fober |