> I remember dismissing my approach (adding notes directly to the Rosegarden > data structures while parsing the XML, SAX-style) when I found out about > some of the more advanced MusicXML constructs.
I had a closer look to your code and I am on a similar route. File are parsed using SAX2 and the Rosegarden event are created on the fly. So far anything seems implementable. Just to inform you, the current implemented features are: - Midi instrument mapping - Partwise scores - support for <divisions> - Key/Clef import - Note/rest events - Most of the Rosegarden marks (like tenuto) - Tuplet [3:2, x:y although there might be some problems left) - Lyrics - Slurs - Most of the dynamics. Most of items are not fully implemented yet (as ALL marks, ALL text events) but more a "proove of concept". For now I concentrate on implementing several MusicXML constructs to see how far I get and fill in the gaps later on. This might save time when come to a dead and I'm forced to reconsider my approach. Next constructs to explore are multistaff instruments and voices (layers?). I am working parallel on both MusicXML export and import per feature although the export has a headstart. > However I haven't seen > Niek's approach yet, and certainly don't want to discourage him even when > he's also going this rout Don't warry, I am not that easy to discourage :-) Best regards, Niek ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
