- From: Jeremy Sawruk <jeremy.sawruk@gmail.com>
- Date: Thu, 31 Aug 2017 14:18:01 -0400
- To: "mogens@lundholm.org" <mogens@lundholm.org>
- Cc: public-music-notation-contrib@w3.org
- Message-ID: <CANRG7pSN6A7u2_1tKQUOUxKBTVmUOjhCwXUa3cka0yh=qqNQHA@mail.gmail.com>
I'm sorry, but I personally am not clear on what MusicXML data is not being preserved. Could you please provide an example file? On Thu, Aug 31, 2017 at 2:02 PM, mogens@lundholm.org <mogens@lundholm.org> wrote: > I am sorry but I just didn't reach what I wanted to do with the testing of > MusicXML 3.1. But I am working on it. > > Using Finale to make new MusicXML-3.1-files seems to bring a common > problem up again: Finale (and all other programs) does not preserve the > MusicXML-data. In my case it concerns the time-only attribute for lyrics. > > To claim that notation programs should preserve MusicXML is not realistic > and maybe not even desirably. But this means that some the improvements in > 3.1 may never be implemented. > > My job now is to identify changes, that affects playing. Among these I > shall identify those, that can be implemented in MIDI. But I do not believe > this may cause new issues. > > I think that MusicXML 3.1 could be finalised, but hope there will come a > MusicXML version 3.1.1 - if issues appear. It should not end up like MIDI - > where they forgot a clef-definition and now, thirty years later, there is > still no clef-definition. (as stated in the book "Beyond MIDI") > > So go ahead with 3.1. > > Regards > Mogens > > PS: I am not using code generation from the XSD yet. Look forward to have > "fun" with grace-cue-notes. > > On 23 Aug 2017, at 16:11, Michael Good <mgood@makemusic.com> wrote: > >
Received on Thursday, 31 August 2017 18:18:23 UTC