Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #19 on issue 665 by brownian.box: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Jack Cooper offers $75: http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00552.html There are some missed offers, I'll try to catch them too. Actually I am not sure that everyone who offers some bounty, means exactly this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #18 on issue 665 by fedel...@gmail.com: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 A recent discussion about this feature request: http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00435.html I offer 50 euro ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #17 on issue 665 by lilyli...@googlemail.com: Request: MusicXML
backend
http://code.google.com/p/lilypond/issues/detail?id=665
Does anybody know whether the old bounty offers are still valid?
If yes, they would by now up sum up to $600 (counting everything mentioned
in this issue report).
Add to it $50 from me.
I would really like to have a structural MusicXML export.
My 2cts to the discussion:
- I think we all are convinced of the superiority of Lilypond's engraving
output.
Nevertheless there are situations where one may need Lilypond scores
to be used with other programms.
See comment #6
or this discussion on -user ("my" thread):
http://lists.gnu.org/archive/html/lilypond-user/2010-06/msg00438.html
- To offer an export option is nice behaviour,
not to offer it may be regarded as arrogant.
So having it could improve Lilypond's acceptance.
- To have an at least semantically correct MusicXML file
(instead of one with Lilyponds's layout information)
would be plain better than not having it.
- Many of the possible uses of such a file wouldn't even be interested
in the superior layout information
So this is one more vote for this feature.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #16 on issue 665 by kie...@alumni.rice.edu: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 $100 here. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #15 on issue 665 by jan.nieuwenhuizen: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 You may want to look at input/regression/to-xml.ly and scm/to-xml.scm, some old and preliminary work there. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #14 on issue 665 by carlo.stemberger: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 50$ from me. http://nextsprocket.com/tasks/lilypond-music-xml-converter Regards, Carlo ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #13 on issue 665 by rogerdpack: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 $150 bounty from me. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Am Freitag 26 November 2010, um 22:51:59 schrieb lilyp...@googlecode.com: > Comment #12 on issue 665 by aleksandr.andreev: Request: MusicXML backend > http://code.google.com/p/lilypond/issues/detail?id=665 > > I'm working on a script that takes the raw Lilypond source and converts it > to XML. If anyone is interested in collaborating, shoot me an email. That approach will probably only work for relatively simple LilyPond files. Given the incredibly flexible syntax of lilypond files, I doubt that you can be able to get it right (that would basically involve duplicating the parsing and iterating stage of lilypond)... The better approach would be IMO to create dedicated engravers for XML export. Cheers, Reinhold -- -- Reinhold Kainhofer, Vienna University of Technology, Austria email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * Edition Kainhofer Music Publishing, http://www.edition-kainhofer.com/ * LilyPond music typesetting software, http://www.lilypond.org/ signature.asc Description: This is a digitally signed message part. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #12 on issue 665 by aleksandr.andreev: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'm working on a script that takes the raw Lilypond source and converts it to XML. If anyone is interested in collaborating, shoot me an email. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Updates: Owner: --- Labels: -Priority-Postponed Priority-Low musicxml Comment #11 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 What about implementing the pure-music-stream export as a first step? Can't be (much) worse than our current MIDI export, can it? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #10 on issue 665 by reinhold.kainhofer: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 There have been some discussions on lilypond-devel and lilypond-user. Here is a short excerpt from one of my mails, outlining how such a MusicXML backend could/would be implemented: The only problem is that the lilypond structure is not ideally suited for full MusicXML 2.0 export: All other graphical output formats (eps, ps, pdf, png, svg) simply export some graphical objects with a fixed position on a page, so at that stage the musical information is no longer available, so MusicXML export has to hook in earlier. The pure musical structure can probably be easily extracted from the music stream (e.g. by an engraver, listening to all kinds of events), but at that stage the page layout has not been done, so the great layout of lilypond scores could not be exported directly. On the other hand, the final graphical objects don't have any link to the music object that caused them, so one would also have to add such a link to the grobs. The MusicXML export would then work in two stages in a lilypond run: 1) In an engraver create the xml tree for the pure musical content 2) at the same time, also listen to created graphical objects and add a pointer to the corresponding xml node 3) After the layout is done, a MusicXML backend goes through the graphical object and exports all positioning information (most of which is new in MusicXML 2.0) to their linked xml nodes. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #9 on issue 665 by brownian.box: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'll happily make it 300, by the way. Here in Kyiv, Ukraine is preferable option though, but others are possible, i hope. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Comment #8 on issue 665 by hopkin...@ldschurch.org: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 My organization is looking at possibly using LilyPond, especially for its nice music typesetting and Unicode text support. However, we would absolutely need it to not only import MusicXML, but to export it as well. The reason for this is that we want to export the music and Unicode lyric text, etc. to a Web music product called Music Player by musicRAIN (see http://musicrain.com/ and http://www.lds.org/churchmusic). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Comment #7 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Yet some unexpected news from Hu Haipeng: apparently, the professor who's in charge of BrailleMuse has gone missing lately, and since it's an online tool the source files cannot be fetched. However, the FreeDots project [1], that is fully Free Software, now has support for both ASCII and unicode output, and seems to be evolving fast. (Of course, that doesn't solve our need of a MusicXML output for LilyPond though.) [1] http://delysid.org/freedots.html -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Comment #6 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New comment from Hu Haipeng: The best way for you all is, to make a MusicXml backend. This feature has the following three advantages, two of which can't be approached by making a much terrible and hopeless (complicated, because the ones who know braille don't know programming, while the ones who program don't know braille!) braille backend: 1. Musicxml can be accepted by most [free and non-free] notation programs. 2. LilyPond just focuses on music typesetting, its midi output is really not ideal. Every time I give my music to a composer, he/she will complain about the bad balance, suspecting my orchestration technique. Using Sibelius or Finale's VST plugin can get good sound output, including legato, staccato, glissando and smooth dynamic changes. It is a very important thing for the composer to hear what he/she have written. The more it's real, the better scoring result he/she can approach. 3. It's a good thing to view our own compositions with braille. Ly2brl is extremely difficult, and we have to begin from 0. Why don't we borrow other's fruits? I use the BrailleMuse web-application, that is the most powerful musicxml2braille program now. I have helped this Japanese project to improve their program for nearly a year, and now, most of the musicxml files less than 20M can be processed. The only limitation is no lyrics (english version, but the Japanese one can only output Japanese texts), and the output is Ascii, which I like very much. You can adjust several formattings to fit your paper, change many settings to fit your preference. http://gotoh-lab.jks.ynu.ac.jp/braille_music_score_english/e-top-new.html#Service%20condition -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Comment #5 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New comment from Ralph Little: http://lists.gnu.org/archive/html/lilypond-devel/2008-11/msg00293.html "I have been approached by a programmer who is interested in helping me with my efforts to produce braille output by going the XML approach.[...] Currently, using Erik's interface method, structure could be exported in a fairly straightforward manner, but positional information from Lilypond's layout engine would be much harder to extract. For the purposes of what we require [for braille conversion], the layout information is not really required. Therefore, we propose to just extract the structure and leave the positional information for a later time. I think the back-end implementation would be largely the same anyway. We propose to link to the LGPL MusicXML library if there are no objections: http://libmusicxml.sourceforge.net This library is pretty mature and covers all the bases I think." -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #4 by v.villenave: I'll happily make it 200, by the way. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #3 by v.villenave: Jonathan Kulp has offered a $100 bounty on -devel. Issue attribute updates: Labels: Bounty -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Hi, Priorities for these types of changes (oodles of work) does not change depending on user interest. We can un-postpone it if someone comes along to volunteer the necessary work. On Sun, Aug 24, 2008 at 8:18 PM, <[EMAIL PROTECTED]> wrote: > Issue 665: Request: MusicXML backend > http://code.google.com/p/lilypond/issues/detail?id=665 > > Comment #1 by v.villenave: > Since we have more requests about it, I'm accepting it and slightly bumping > the prio. > > > Issue attribute updates: >Status: Accepted >Labels: -Priority-Postponed Priority-Medium > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings > > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond > -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #1 by v.villenave: Since we have more requests about it, I'm accepting it and slightly bumping the prio. Issue attribute updates: Status: Accepted Labels: -Priority-Postponed Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 665 in lilypond: Request: MusicXML backend
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New issue report by v.villenave: This feature has been proposed by Reinhold Kainhofer on -devel: http://lists.gnu.org/archive/html/lilypond-devel/2008-06/msg00129.html More recently, an user shared his experience on -user: http://lists.gnu.org/archive/html/lilypond-user/2008-08/msg00838.html Some highlights: Han-Wen: "The last time we looked at this, I think the resolution was to dump a music stream from LilyPond and postprocess that." Reinhold: "unfortunately, the stream does only contain the musical content in time-sorted order. MusicXML, however, also contains (or rather, can contain) full information about page layout, breaks, object positioning and similar settings [...] Since Lilypond produces a layout that is far superior, I'd also like to include that information in the xml files..." Han-Wen: "you would probably have to use some sort of dual approach, where you store the stream, label each event, and then you trace back the grobs during output stage to their originating events. You can use the ordering from the stream to output the XML elements in the correct order." Issue attributes: Status: New Owner: v.villenave Labels: Type-Enhancement Priority-Postponed Usability -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
