#49 Imports

open
nobody
None
1
2012-09-16
2003-07-18
No

Rosegarden has a lot of export formats, but few import
formats. It would be convenient if it could handle
Lilypond files, though I quite understand if that
support might take a while ;) However, it would also
be convenient if it could import MusicXML, and perhaps
some of the other formats.

Discussion

  • Arnout Engelen

    Arnout Engelen - 2007-09-11

    Logged In: YES
    user_id=392382
    Originator: NO

    I added some preliminary MusicXML importing code to my local tree - single-track files with notes/rests, pitches, durations and keys seem OK, ties, accidentals and clefs are there but need some refinement. I haven't started on metadata, multitrack files, other elements (like lyrics, chord symbols, beaming, etc) and the mapping to MIDI instruments yet.

    I intend to postpone committing until after the upcoming release is out of the door - if anyone is interested in taking a look at it before then, drop me a note.

     
  • Chris Cannam

    Chris Cannam - 2007-09-12

    Logged In: YES
    user_id=13489
    Originator: NO

    Can I suggest creating a new Subversion branch and committing it there?

    It doesn't matter how rough your code is, as I don't expect anyone will really look at it anyway unless you specifically ask them to. I think it's very handy to have the code somewhere on the SourceForge server -- it means if anyone else does get inspired to look at it, it's available -- especially useful if you happened to end up abandoning it yourself.

    Also, at least I find when working on a new bit of code, having a branch is useful because then I know where to find it -- I'm quite good at losing code (at least temporarily) otherwise. But that might not be a problem for you.

    http://rosegarden.wiki.sourceforge.net/Branching

     
  • Arnout Engelen

    Arnout Engelen - 2007-09-13

    Logged In: YES
    user_id=392382
    Originator: NO

    (committed to a newly created 'musicxml' branch in SVN)

     
  • D. Michael McIntyre

    Logged In: YES
    user_id=663564
    Originator: NO

    We're sorry, but there is no chance anyone presently on our staff will have time to consider this request. Perhaps you'd like to buy your way onto our staff by presenting us with this request re-expressed in patch form.

     
  • Peter Howard

    Peter Howard - 2012-02-03

    I' ve taken the code on the 'musicxml' branch, and gotten it working against the current trunk. Ever-so-slightly cleaner than the code on the branch, but still not necessarily merge-quality. I was going to attach the patch here to get some feedback but there doesn't appear to be a trivial way for me to attach it here. So can someone suggest a place to put the patch for comments? Dev mailing list (quoting ID)? Other? I'm assuming I don't automatically have permission to push a branch and the existing musicxml one is old enough I fear trying to merge the current trunk into it.

     
  • Niek van den Berg

    When working on the MusicXML exported last year I started a MusicXML importer as wel. I had a look at the code of Arnout but decided to start more or less from scratch because using some code of the existing branch.
    I could import a lot of notes but ran into problems with the more global structure of the piece (repeats DC/Dal Segno and so on). In the same time the linked segments were introduced so I decided to concentrate on the exporter.
    Maybe we can combine forces on the importer.

     

Log in to post a comment.