Re: Dolet 6 Plugin for Sibelius

Hi all,

That modification later got incorporated into the currently shipping Dolet for Sibelius plug-in, so I doubt that’s the cause of the issue.

Maybe there was something in a recent Windows update that is causing the problem. Since nobody supports such an old version of Sibelius or Dolet, though, I can’t see it getting fixed.

My recommendation would be to install the current version of Sibelius on the same machine, and use that version for the MusicXML exports using Dolet 8 for Sibelius. With the latest version of Sibelius you can install the Dolet 8 plug-in just like any other 3rd-party plug-in. Dolet 8 has been updated to support MusicXML 4.0 and the features added to ManuScript through 2022. So the MusicXML files exported should work better than what you could export from Sibelius 6 back when the plug-in was working reliably for you.

I don’t recall there being a problem with having the old and new versions installed on the same machine, as they get installed to different locations on Windows and use different registry entries.

Best regards,
Michael

On Sep 12, 2023, at 8:43 AM, Martin Marris <mmarris@notecraft.com> wrote:

Greetings,

I wrote that code a decade ago. I suppose it might cause issues although we have never found any problems with it. The net result is to take advantage of some then-new features in Sibelius 6 ManuScript (IIRC, support for global arrays) and the speed improvement is substantial (it runs several times faster). We provided the revised version to Hal Leonard at the time (but to no-one else).

If Austin has not tried it yet, perhaps uninstall this custom version of Dolet and (if you can find it) install, instead, the original Recordare version instead. I did have a brief conversation with Michael Good at the time that I wrote this code and he was aware of the alteration.

But again, I would be a bit dubious as to whether the modifications that I made, on their own, would cause the problems Austin is experiencing. (BTW, I cannot remember for sure, but I may have made other alterations in another Method from the plugin.)

Best regards,

Martin Marris

From: Jeremy Sawruk <jeremy.sawruk@gmail.com<mailto:jeremy.sawruk@gmail.com>>
Sent: Tuesday, September 12, 2023 16:05
To: Daniel Spreadbury <D.Spreadbury@steinberg.de<mailto:D.Spreadbury@steinberg.de>>
Cc: Austin Melcher <amelcher@halleonard.com<mailto:amelcher@halleonard.com>>; public-music-notation@w3.org<mailto:public-music-notation@w3.org>; Kimberly Brand <kbrand@halleonard.com<mailto:kbrand@halleonard.com>>
Subject: Re: Dolet 6 Plugin for Sibelius

Could you remove the custom "alterations to it by an outside party for the plugin to work faster"? It's more likely that the issue is in this additional code rather than in the code released by MakeMusic. After examining the corrupted MusicXML file that you sent, I noticed there was an issue encountered while writing a <pitch> element. The output of this section is a stream of null bytes (0x00). I don't know what could have caused this, but looking at the WriteXML function, I noticed there was the following code block:

// ==========================================
// The following two lines of code added by Notecraft Services LLC in November 2012
// They load the lines of XML code into a global array
// Note that this only works in Sibelius 6 and later
// ==========================================

counter = gsa_XMLMyWriteLine.Length;

gsa_XMLMyWriteLine[counter] = sData;

While I cannot say this is where the error is occurring, it would be the first place I would investigate. I would like to echo Daniel's previous sentiment that there probably isn't much the group can do to help in this case. I would recommend either reaching out to the original developer or reverting to the original code that MakeMusic provided.

On Tue, Sep 12, 2023 at 3:54 AM Daniel Spreadbury <D.Spreadbury@steinberg.de<mailto:D.Spreadbury@steinberg.de>> wrote:
Hi Austin,

Unfortunately I doubt there’s much that we can do to help here – Michael Good was the original author of the Dolet plug-in for Sibelius, and the latest version was released under an open source license when he retired at the beginning of 2023, but I don’t believe older versions of the plug-in are included in that release, and in any case, debugging and fixing a plug-in in a nearly-15-year-old version of Sibelius might be a tall order.

Do you know what the nature of the brokenness is, when it occurs? What specifically goes wrong with the problematic MusicXML files? Does the same Sibelius score produce a different result when using the same plug-in on a different system?

Daniel

From: Austin Melcher <amelcher@halleonard.com<mailto:amelcher@halleonard.com>>
Date: Tuesday, 12 September 2023 at 07:34
To: public-music-notation@w3.org<mailto:public-music-notation@w3.org> <public-music-notation@w3.org<mailto:public-music-notation@w3.org>>
Cc: Kimberly Brand <kbrand@halleonard.com<mailto:kbrand@halleonard.com>>
Subject: Dolet 6 Plugin for Sibelius
Hello there,

I am a music engraver and have been using the plugin in Sib 6.2 for a few years, with some alterations to it by an outside party for the plugin to work faster for our application needs. Our department has been using the same plugin for about 10 years now and there haven’t been any issues until just this calendar year.

But so far this year, the plugin has been creating files (more often than not) that are incomplete and broken when uploaded to Noteflight, as well as not being processed properly in our archiving system. I am wondering if there is anyone that might know something about the plugin not being compatible with newer computers/operating systems? (I am running updated Windows 10 with an 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz   1.38 GHz on a less than 3 year old Dell Latitude 5520.) My co-workers and manager haven’t been having anywhere near this same level of issue. I’m including a pair of .xml files for your consideration, one broken and the other was uploaded/archived with no issues, as well as our copy of the plugin that had been altered to work faster for us.

And to address one of the most obvious solutions…at this time, upgrading and using newer versions of Sibelius isn’t an option due to other issues with scorch compatibility.

Please feel free to ask any other specific questions that I might not have answered already to, hopefully, find some kind of solution to this odd issue.

Austin Melcher
Music Engraver
[signature_703998378]
7777 W Bluemound Rd,
Milwaukee WI, 53213
Phone: 414-774-3630x5283
amelcher@halleonard.com<mailto:amelcher@halleonard.com>
www.halleonard.com<http://www.halleonard.com/>

Product Marketing Manager
Phone: +44 20 3696 1811
Steinberg Media Technologies GmbH
Beim Strohhause 31, 20097 Hamburg, Germany
Managing Directors: Clyde Sendke, Yoshiyuki Tsugawa, Marco Papini
Registration Court: Hamburg HR B 86 534 | VAT ID: DE118677139
Visit the Steinberg website<http://www.steinberg.net/> or connect with us on Facebook<http://www.facebook.com/Steinberg>, Twitter<http://twitter.com/steinbergmedia>, Instagram<http://www.instagram.com/steinbergmedia> and SoundCloud<http://www.soundcloud.com/steinbergmedia>.
Watch our Cubase<https://www.youtube.com/cubase>, Dorico<https://www.youtube.com/dorico>, Mobile Apps<https://www.youtube.com/mobile_apps_steinberg>, Nuendo<https://www.youtube.com/nuendo>, Steinberg<https://www.youtube.com/user/SteinbergSoftware>, Audio Interfaces<https://www.youtube.com/audiointerfaces>, VST Instruments & Plug-Ins<https://www.youtube.com/VSTinstrumentsplugins> and WaveLab<https://www.youtube.com/WaveLab> videos on YouTube.