Re: Proposal: Make Sibelius Dolet MusicXML plugin open source

I understood that the Sibelius plugin format is proprietary, non-standard and subject to change, which also is true of Sibelius itself.
Difficult to see how this could be the basis for a 'reference' implementation of anything.

I guess MakeMusic would be unwilling to lose control and revenue from this valuable software.

best regards
James Sutton
Dolphin Computing
http://www.dolphin-com.co.uk <http://www.dolphin-com.co.uk/>
http://www.seescore.co.uk <http://www.dolphin-com.co.uk/>
http://www.playscore.co <http://www.dolphin-com.co.uk/>




> On 16 Oct 2017, at 12:55, Jeremy Sawruk <jeremy.sawruk@gmail.com> wrote:
> 
> I strongly agree with this. Ideally, I think that both the Finale and Sibelius plugins should be open source so that the MusicXML community has reference implementations.
> 
> However, if MakeMusic does not want to open source these plugins, I think the community should still work to create open source reference implementations of its own. It may take a while for those implementations to reach the same level of Dolet, but at least they would be truly open source.
> 
> On Mon, Oct 16, 2017 at 5:17 AM, Andrew Hankinson <andrew.hankinson@gmail.com <mailto:andrew.hankinson@gmail.com>> wrote:
> I wholeheartedly agree with this proposal.
> 
> I can also recommend the plgToMSS tool, developed by Tido, as a way of making developing in ManuScript suck a whole lot less and make it much easier to use standard text editors and IDEs.
> 
> https://github.com/tido/plgToMSS <https://github.com/tido/plgToMSS>
> 
> -Andrew
> 
> > On 16 Oct 2017, at 10:08, Adrian Holovaty <adrian@holovaty.com <mailto:adrian@holovaty.com>> wrote:
> >
> > I believe it's in our community's interest for the Dolet Sibelius plugin (http://www.musicxml.com/dolet-plugin/ <http://www.musicxml.com/dolet-plugin/>) to be open source.
> >
> > The plugin routinely produces better MusicXML than Sibelius' native exporter — I encourage all my customers to use it, if they use Sibelius — but it still can be improved.
> >
> > As far as I can tell, the plugin is developed by a single person. As I find bugs in the plugin's generated markup, I'd love to be able to report them via a public tracker and perhaps even directly contribute fixes to the code myself. Please accept my offer of free labor! :-)
> >
> > This would benefit *everybody* in the world of MusicXML, for obvious reasons. The plugin will get better, faster — which means everybody using Sibelius gets better interoperability across the MusicXML ecosystem.
> >
> > There's also prior art for this: an open-source Sibelius plugin for generating MEI. https://github.com/music-encoding/sibmei <https://github.com/music-encoding/sibmei>
> >
> > Who agrees with me? Can we make this happen?
> >
> > (To preempt arguments that this is out of scope for this working group: I'd argue this is clearly within "the spirit" of this group's mission, if not necessarily within "the letter." We all want to reduce friction with day-to-day MusicXML workflows.)
> >
> > Adrian
> >
> > --
> > Adrian Holovaty
> > Soundslice: https://www.soundslice.com/ <https://www.soundslice.com/>
> > Personal: http://www.holovaty.com/ <http://www.holovaty.com/>
> 
> 
>