Skip to main content

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - Opagust

101
User Tools / Re: NWCCONVERTOR
Version 1.03 is available in https://www.opagust.be/content/nwcconvertor.

    - Connection of bar lines: always create group-barline tag, with 'yes' or 'no' as value.
    - Correction in the processing of fields concerning 'open output with' in the option window.
    - Adding <supports element="beam" type="yes"/> in the musicxml file to suppress automatic beaming in Musescore.
    - Bug fix in processing after unchecking a part in the setup window of xml to nwc conversion;
104
User Tools / Re: NWCCONVERTOR
WARNING:
Some bugs in the processing of the option window:
In the frames 'open output file with':
- you can choose a value via one of the combo boxes, but that has no effect;
- the regions left of the 'Browse' button is editable; this can cause a fatal error if it's changed to an invalid file name.

SO: changing via the 'Browse' button is the only valid and working way.

This will be fixed in the next version.
105
User Tools / Re: NWCCONVERTOR
A separate reply about the download. A number of people (including myself) have observed/complained that when they download the file, it gets the filename "download" rather than the intended name. The URL in the download link is:

https://www.opagust.be/?q=system/files/NWCCONVERTOR-1.0.2-amd64.msi

However, I think that if you change the URL to:

https://www.opagust.be/system/files/NWCCONVERTOR-1.0.2-amd64.msi

Then the file will be saved with the original name (although Windows might warn you that it's not a frequently downloaded file, and make you choose "Keep anyway")

I managed to change the URL's for the downloads.
106
User Tools / Re: NWCCONVERTOR
Tried it (needed a MusicXML for a colleague with another program).

1. A bug? In the resulting MusicXML, when opened with Musescore, the barlines of 1st and 2nd stave are connected; but not in the NWCTXT. Also a test conversion with https://nwc2musicxml.appspot.com/ does not connect them.

2. Eighths are not beamed in NWCTXT, but are beamed in the result (also with https://nwc2musicxml.appspot.com/). Would it be possible to suppress auto-beaming in Musescore via some info in the MusicXML?

H.M.
About 1.:  Apparently Musescore connects barlines for staves with orchestral brackets. In nwcconvertor I set group-barline to 'yes' if the bars are to be connected, but do nothing for non connected bars. So in the next version I will always create a group-barline tag, with either "yes" or "no" as value. (Remark: appspot seems to ignore the orchestral brackets).

About 2.: I can't find anything in the musicxml documentation about suppressing automatic beams. I don't know if this can be disabled in Musescore.
107
User Tools / Re: NWCCONVERTOR
A separate reply about the download. A number of people (including myself) have observed/complained that when they download the file, it gets the filename "download" rather than the intended name. The URL in the download link is:

https://www.opagust.be/?q=system/files/NWCCONVERTOR-1.0.2-amd64.msi

However, I think that if you change the URL to:

https://www.opagust.be/system/files/NWCCONVERTOR-1.0.2-amd64.msi

Then the file will be saved with the original name (although Windows might warn you that it's not a frequently downloaded file, and make you choose "Keep anyway")
Thanks, Mike

The download link is automatically generated by the website CMS(Drupal), when I upload a file.
I see two solutions:
1) I hide the original field where I download the file and add a field with the modified URL. Unfortunately, I can't modify the structure of exsting download pages. So I'l have to create a new sctucture and copy the existing pages.
OR:
2) Mention the changed URL in the forum topic

For now I go for the second solution.
111
User Tools / Re: NWCCONVERTOR
Version 1.0.2 is available at https://www.opagust.be/?q=content/nwcconvertor.

- 1.0.2: Bugfixes:
    - Clef, time and key were duplicated in further staves.
    - Correction test for inserting invisible rests.
    - Handling of quotes in text fields.
    - Interception of missing 'volume' in midi-instrument-tag.
    - Correction of processing last bar line of a staff.
112
User Tools / Re: NWCCONVERTOR
I added this text on my website:
Quote
REMARK: The name of the file after the download can (depending on the browser used) differ from the file name on the download page. If necessary you should add the extension.
113
User Tools / Re: NWCCONVERTOR
It looks a lot like the installer is searching some files... in the disk of Opagust!  :D  (absolute paths)

Well, it looks like but it's a bit more complicated (sofisticated?) than that. The installation file is created via the Python module cx_freeze.
When you run the installation file, not only an executable is created from the source files, but also copies of the source files and their original file names. Not to search for them, but to create a popup window when a fatal error occurs, in which the author (me in this case) is informed which instructions lead to the error, with file name and line number. And that helps me a lot to quickly find the cause of the error.
But as a consequence, the user can see some absolute paths from my computer.
So, if you can hack my computer, you'll know where to look if you want to solve the error yourself.  ;D
114
User Tools / Re: NWCCONVERTOR
The first update with bugfixes is available at https://www.opagust.be/?q=content/nwcconvertor

- 1.0.1: Bugfixes:
    - Interception FileNotFoundError when looking for register entries (bug reported by @Richard Woodroffe)
    - Recalculation of measure length for voice numbers > 1 (bug reported by @William Ashworth)
115
User Tools / Re: NWCCONVERTOR
To begin with: thank you!  :)

Then, in case you want to process automatically also the .nwc files, you can ask NWC itself.
Thanks, Flurmy.

I'll have to find out how to invoke that within my Python program and receive a result. But a user can always open a nwc file in NWC and save it as a nwctxt file.
116
User Tools / Re: NWCCONVERTOR
Download worked fine (a bit slow), but Win10 just named it "download" - I had to rename it to the name you gave it. You might want to look into that. Haven't run the installer yet - I'll let you know if there are any issues when I get to it, but it's probably going to be much later in the day.

I was already informed about this via a comment on my website. It has apparently to do with the way your browser handles the download. I found out that Google Chrome named it 'dowload'. Indeed you have to add the extension '.msi' to execute it.
In Firefox, you get a random name, but with the right extension, so you can execute it. I didn't try any other browsers.
117
User Tools / Re: NWCCONVERTOR
Installation went OK (after assuring Windows that it wasn't going to destroy my hard drive or steal my identity). However, a simple .nwctxt file (a song for voice and guitar) generated multiple errors and refused to convert to musicxml after several tries. The error log is apparently uncapturable from the program; I'd be willing to send you a copy of the log if you release a new version with an option to save the log as a text file. In any event, this version of nwcconvertor will be deleted, and  I'll go back to  using http://nwc2musicxml.appspot.com/. Too bad: if it worked, it would be a great addition to my tool set.
If a 'real' error occurs, a popup is shown and the program is aborted. So there is now way to save that log within the program. But then you can copy that popup within Windows.
In the program itself there is e logging frame that logs the actions that were performed, it isn't an error log. Next to it is the warning frame, that shows 'possible' errors or that things that couldn't be converted. You can always copy that via CTRL-A, CTRL-C.

But the simplest way to solve this is that you send me a copy of the input file. I have send you a personel message with my email adress.
118
User Tools / NWCCONVERTOR
With this program you can convert NWC text files to Musicxml files and vice versa.
You can download it athttps://www.opagust.be/?q=content/nwcconvertor
In order to download the file, you'll have to be logged in.
You may use an account I created:
- username: 'NWC User'
- password: 'Usertools'
Or you can create your own account, so you can be informed of future updates.

INSTALLATION:
    Download and run the installation file. (REMARK: The name of the file after the download can (depending on the browser used) differ from the file name on the download page. If necessary you should add the extension.)
    During installation, the target folder is shown and can be modified.
    After installation, a shortcut 'NWCCONVERTOR' will be created on your desktop.

___________________

The first time tou run this program, you'll see the options window. When you click 'OK', your choices will be saved.

On the main window you see a row of action buttons, a loggings frame and a warnings frame.
In the loggings frame the stages of the processing are shown, the warnings frame is used for reporting situations
that demand your attention.
Depending on the progress of the processing, each button will be enabled or disabled.

Upon installation a shortcut icon was created on your desktop. You can drag and drop a file upon that icon,
or double click it and manually select the file to be converted via the button 'Select a file to convert'.

- The input file must be a either a NWC text file (extension '.nwctxt') or a musicxml file (extensions: '.musicxml',
  '.xml' or '.mxl'. Files with extension .mxl are compressed files; they will automatically be unpacked in a .xml file.
- A musicxml file is converted into a '.nwctxt' file.
- A nwc file is converted into a '.musicxml' or '.xml' file (according to the options).

The input file is analyzed and a setup window is displayed. The setup window consists of 2 tabs: a titlepage tab and
a staves/parts or part/staves tab. They differ according to the direction of the conversion.
Press the appropriate button on the right side to show detailed explanation.

After pressing 'CONVERT' on the setup window, the conversion process is started. Press the appropriate button to show
detailed information concerning the conversion for each direction.

When the conversion is completed, you can save or 'save as...' the output file. The file name is determined as follows:
 - the dot of the extension is turned into a dash:
 - the extension is added:
    ° '.nwctxt' for the Musicxml -> NWC conversion,
    ° the extension from the options for the NWC to Musicxml conversion.

Next you can directly open that file without leaving the program, via the button 'OPEN the converted file'.
The file will be opened within the program you specified in the options.

120
General Discussion / Re: Question for musicxml experts: representation of flow directions
Well, it seems I did kwew it back in 2021 :o .
Here's what I found in the coding I wrote for the musicxml to Noteworthy  convertor:

Code: [Select · Download]
def convert_tag_direction_end(element):
    object_line = {
        'dynamic': '|Dynamic|Style:mp|Pos:7',
        'dynamic_variance-sfz': '|DynamicVariance|Style:Sforzando|Pos:7',
        'dynamic_variance-rfz': '|DynamicVariance|Style:Rinforzando|Pos:7',
        'dynamic_variance_text': '|Text|Text:sfp|Pos:7',
        'segno': '|Flow|Style:Segno|Pos:8',
        'coda': '|Flow|Style:Coda|Pos:8',
        'D.C. al Fine': '|Flow|Style:DCalFine|Pos:8|Justify:Right',
        'D.S. al Fine': '|Flow|Style:DSalFine|Pos:8|Justify:Right',
        'D.C. al Coda': '|Flow|Style:DCalCoda|Pos:8|Justify:Right',
        'D.S. al Coda': '|Flow|Style:DSalCoda|Pos:8|Justify:Right',
        'To Coda': '|Flow|Style:ToCoda|Pos:8|Justify:Right',
        'D.C.': '|Flow|Style:DaCapo|Pos:8|Justify:Right',
        'fine': '|Flow|Style:Fine|Pos:8',
        'pedal': '|SustainPedal|Pos:-11|Wide:Y'

    }
    ...
126
Object Plugins / Re: PrintConfiguration (0.1)
Thanks! (maybe I use local staffName = staff.AddStaff.Opts.Name.Text or staff.AddStaff.Opts.Name ...).This nested Text objects baffled me anyway, but it is there in my 2.75a.2

H.M.

That seems a bit neater. It's been a while since I last programmed in lua, I'm in love with Python now, but that's the way I would write in Python too.
127
Object Plugins / Re: PrintConfiguration (0.1)
Hi Heinrich,

I got this error when I ran the user tool:
Quote
C:\ProgramData\Noteworthy Software\nwc2\UserPlugins\PrintConfiguration.hmm.nwcuser.lua:145: attempt to concatenate local 'staffName' (a nil value)

When I removed the '.Text' at the end of line 142, the error didn't occur any more.
But I think it has to do with the version of nwc (mine is 2.8 beta 1).
So maybe this is the best solution:
Code: [Select · Download]
    local staffName = staff.AddStaff.Opts.Name.Text
    if staffname == nil then staffname = staff.AddStaff.Opts.Name
That works for me.
129
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Are you certain you uploaded the new file to your website? I downloaded and reinstalled the program, and I'm getting the same behavior as before.
Shame on me :-[ !
I downloaded and reinstalled it myself and you're absolutely right.
I suppose I forgot to push te save button after uploading the new version.

I now have changed the version number to 1.1.1.0, uploaded this version to my website, pushed the save button, then downloaded and reinstalled it on my computer and tested it on your file and it seems now to be OK.
I sincerely hope you agree with me.
130
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
I'm seeing the correct slur handling for the sample file I sent you, but I'm getting the same mangled |Text and |Tempo objects as before (line break inserted before |Pos)
Edit: My bad, I just realized that the sample file I sent you already had the line breaks stripped out  :-[  Let me forward a copy of the original XML that hasn't been fixed.
Hi Mike,
Let this be a comfort for you: I also made a mistake. I tested on '/n' instead of '\n'.

Version 1.1.1 is now updated.
132
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
A great tool - very helpful right now for getting (parts of) PDFs via Audiveris to NWC, for my crank organ arrangements.

I have another problematic MXL file; Audiveris already stumbles on many things in the score, creates a "corrupted" MXL, which I could load into MuseScore and then "beautify" a little. However MXML2NWC then exits with an exception ... I have attached the error message and the MXL file - hopefully you can see what the problem is!

H.M.

The error is caused by these elements in part 'P1':
Code: [Select · Download]
    <measure number="36" width="187.79">
      <attributes>
        <clef>
          <sign>F</sign>
          <line>5</line>
          </clef>
        </attributes>

The 'sign' and 'line' elements are used to determine a key for this dictionary in my program :
Code: [Select · Download]
CLEF_SIGNS = {
    'G,2': 'Treble',
    'F,4': 'Bass',
    'C,3': 'Alto',
    'C,4': 'Tenor',
    'percussion,None': 'Percussion'
}is


So 'F,5' is an invalid key.
IMHO this can be caused by:
  • The score has a bass clef positioned one line above the 'normal' bass clef. NWC does not support it, neither does my program.
  • Or: Audiveris incorrectly read the position. (In part 'P2', measure number "0", I found  a normal 'F,4' clef)

So maybe I could change my program to ignore the line number (except for the 'C' clefs) and print a warning if the line number differs from the 'normal' one? 
 

135
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
And here is the Help text :

- The input file must be a score-partwise musicxml file; extensions: .musicxml, .xml or .mxl. Files with
    extension *mxl are compressed but will automatically unpacked in a .xml file.
- The output file is a nwctxt file.
- Different voices are placed on different (layered) staves.
- For some features that aren't supported in NWC itself, a 'user object' is used. You may see a popup that alerts you
  to download a missing plugin.

Upon installation a shortcut icon was created on your desktop. You can drag and drop a musicxml file upon that icon,
or double click it and manually select the file to be converted via the button 'Select a musicxml file'.

The processing consists of a few consecutive stages, which are logged in the 'Loggings' frame.
There's also a 'Warnings' frame to draw your attention on possibly incorrect input or processing. Each warning always
includes the staff name and measure number.

The input file is read and analysed, after which a 'Setup' window appears.
This will give you the opportunity to:
 - Check or uncheck some processing options via the 'Options' tab.
 - Tune the title page, via the 'Title Page' tab.
 - Deselect parts, change staff properties and/or deselect lyric lines, via the 'Staves' tab.
More detailed help info is available via the help buttons on these tabs.

After pressing 'CONVERT' on the setup window, the conversion process is started.
When the conversion is completed, you can save or 'save as...' the output file.
Next you can directly open that file in NWC (without leaving the program), via the appropriate button (on condition
that NWC is installed in 'C:/Program Files (x86)/Noteworthy Software/NoteWorthy Composer 2/NWC2.exe').
If you had warnings in the warning frame, you can easily switch between MXML2NWC and NWC to check these measures.


And the help windows for the setup tabs in attachments:
136
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Version 1.1 is now available on https://www.opagust.be/?q=content/mxml2nwc

Changes are:
    - Some bug fixes.
    - Revised lyrics treatment.
    - The input file name can be passed as command line argument.
    - Major changes:
        * After the input file is selected, it will be analysed and a setup window is presented.
        * Via this setup window, one can set options, configure the title page and deselect/select parts, change
            the staff properties and start or cancel the conversion process.
        * Two frames for loggings and warnings are added.
        * A new button to directly open the saved file in NWC.
        * Help buttons on main window and on each tab of the etup window.
137
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Hi Rich,

As I said, I'm working on the next version.

I think it's not too difficult to include a 'look ahead' and search for a divisions element further in a staff, before starting to  process the first measure.
That should solve the problem.

I hope to publish the next version soon.

In the meanwhile, if you have the same problem in another xml file:
- Open the file in a text editor and look for the first occurence of  '<attributes>
- Before that you'll find a preceding line with '<measure number =...'
- If it's the same error situation, that measure number will be > 1.
- Then copy all the lines from '<attributes>' to '</attributes>', as in your file:
Code: [Select · Download]
	
<attributes>
<divisions>2</divisions>
<key>
<fifths>-4</fifths>
</key>
<clef>
<sign>G</sign>
<line>2</line>
</clef>
</attributes>
- Now look higher in the file for a line with '<measure number="1">'
- Paste the copied lines after that line
- Save the file with another name.
138
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Hi Richard,

The error occurs in the first measure, when trying to determine the length of the first element. This is done  by means of the <duration> element.

Excerpts from the musicmxl reference:
<duration>:
"Duration is a positive number specified in division units."

<divisions>
"Parent element: <attributes>
Musical notation duration is commonly represented as fractions. The <divisions> element indicates how many divisions per quarter note are used to indicate a note's duration. "

<attributes>
"The <attributes> element contains musical information that typically changes on measure boundaries. This includes key and time signatures, clefs, transpositions, and staving."

So, in order to determine the length of a note or rest, the division unit must be known, which is part of a <attributes> element.
In your file, the first <attributes> element occurs for the first time in measure 6, so the division unit is not known before that.

When I moved the <attributes> element to the start of measure 1 in your xml file, the error didn't occur anymore.
I'll send you a personal mail with the corrected xml file and the resulting nwctxt file (happy tune, by the way).
140
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Hi, Heinrich.
Just a short "still working on it" message on my behalf:
I'm working on version 1.1 of MWML2NWC, in which the conversion is done in 3 phases: analyse, setup and convert.
In the setup phase a window with 2 tabs is shown, that enables the user to setup the Title Page layout and the staff properties, see attachments.
I will add a checkbox for system and page breaks.
Any further suggestions from your side are very welcome.

I also added a 'Loggings' and 'Warnings' frame that are filled during the conversion, see third attachment.

142
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
It might be that a more useful process is actually: Remove everything except notes and rests (probably with a user tool), create a correct "naked score" from these; and finally add all the "small things" (and not so small ones) - either manually or, at a few places, by copying something over from the "ORM-ed" score.

The whole enterprise is certainly not for the faint-hearted, at least with this Audiveris+Converter pipeline; where the main "problem", but also "heavy-weight-lifter" is Audiveris: What it can and cannot do essentially defines the result. So be it. I'll see what I learn ...

Indeed, I agree that the output of Audiveris is the main problem here.
Maybe I can add a window to MXML2NWC where you can select/deselect the item types to convert ?

As for the sometimes missed notes or dots: In audiveris the measures that are too short after the transcription are colored pink, so that should be a help to locate them quickly in the nwctxt file.
143
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Kospoth's symphony worked nicely* for the 1st, 2nd and 3rd movement. The mxls produced by Audiveris already have a fair share of problems (however, some are from untypical notations in the score), but the result is quite usable. However, the 4th movement stumps MXML2NWC 1.0.2 (I hope - I just installed it over the previous one; does the installer replace it? ... it would be nice if there were a version info somewhere), with another Python error. The zipped .mxls are in the attachment (however, due to renaming, the XMLs stored inside the mxls do have strange names from my scanning operation - I hope this is fine).

* However, there are a few things where I stumble
a) The first staff of each NWCTXT contains "a million" PgTxts at  the start (see NWCTXT result of second movement in the attachment).
b) When opening, the files require a font "Default" which I apparently don't have.
c) Opening another .mxl file often (always?) crashes MXML2NWC later. You can try it with the symphony: First, convert and save movement 1; then, press "SELECT ..." again and open movement 3. "CONVERT" will result in an error - see attachment.

H.M.

The new version (1.0.3) is available on https://www.opagust.be/?q=content/mxml2nwc

  • Yes, the installer replaces the previous one.
    The window title bar now shows the version number.
  • I fixed the errors. The first one (list index out of scope) was a real bug. The second one was a beam property 'backward hook' that NWC can't digest. Unknown beam properties will now be ignored.
  • The "million" PgTxts are derived from the <credit-words> tags in the xml file. Audiveris seems to create these tags for everything that it can't recognize as musical symbol? Example:
     "<credit-words default-x="1686" default-y="11" font-family="sans-serif" font-size="198" font-weight="bold">—-—wv—~'—-</credit-words>"
  • The font 'Default' is derived from the tag "<lyric-font font-family="Default" font-size="10"></lyric-font>". I now replace it with 'Times New Roman'.
  • Opening an converting more than one file in the same run can cause some problems. Probable cause is that some variables are not properly restored. I found it to much effort to spit this out, so now I keep the select button disabled after opening a file. So you'll have to exit and restart the program, which seems to me not a big effort to ask for.
  • Your fourth movement prodced a lot of popups for invalid chords (caused by identical chord members in one chord object). So I replaced the multiple popups by showing these warnings in one extra window, tat doesn't halt the execution.
144
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
b) In the attachment are (in a single .zip) two more .mxl files produced by Audiveris. The input for this was a scan of Ruth Elaine Schram's arrangement of "Go, Tell It On The Mountain" (see http://www.hmmueller.de/Scans/RuthSchram_GoTellItOnTheMountain.pdf - "permanently out of print", according to the publisher). I'd like to create a rehearsal voice/mp3 for a soloist singer from this via NWC. Audiveris produces two "movements", where the latter is the separate coda starting on the last page but one. Giving the first file to MXML2NWC 1.0.2 unfortunately creates another Python stacktrace ... Maybe you could look into this.

H.M.

The Python stacktrace was due to the fact that Audiveris interpreted a chord symbol as a lyric syllable in lyric line 3 on a staff without  lyric lines 1 nor 2.
So in the next version of MXML2NWC  (coming soon, I hope), I will ignore lyrics assigned to lyric lines that  are 'out of order'.

P.S. I managed to download and install Audiveris. I used your pdf as input and I saw a lot of pink areas after transcription. I think these are the places where Audiveris had some difficulties to correctly 'read' the score and as a consequence may lead to incorrect areas  in the resulting NWCTXT file after running MXML2NWC.
145
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
The new version (1.0.2) is available on https://www.opagust.be/?q=content/mxml2nwc

Quote
I zipped the MXL, because the forum does not accept .mxl files. Opening the .mxl with MXML2NWC does not work - it seems that it does not see that this is a zipped file which needs unzipping (and yes, MXML2NWC does not accept .mxl as a standard extension for files it wants to open, so this is an "advertised feature"). Still, I have the (small) feature request that .mxl files are accepted, i.e. unzipped and then worked on the XML.
A zipped *.mxl file is now accepted as input. An unzipped *.xml file will be generated and processed. The *.xml file will be saved  in the same directory as the input file.

Quote
Manual unzipping of the .mxl yielded an XML file, which MXML2NWC actually digested, with a host of messages which I ignored (and did not read; and maybe would not have understood).
When I unzipped your first file and used it as input for MXML2NWC, I had 2 popups with an error message 'Invalid Chord Error' with techincal information, that I happened to understand. Twice it concerned a generated nwctxt line that was not a legal NWCTXT object.
With the information in the popups I could find the cause in the input file: in 2 places a chord with two identical chord elements.
In this new version I replaced the error popups with information (see attachment) wich is hopefully more readable. It contains the staff name and measure number, the erroneous nwctxt line and the one that was generated instead.

Quote
I also opened the .mxl file coming out of Audiveris in Musescore. Musescore complained that this was not a valid MusicXML file, but after pressing "Ignore" it also gobbled it up and created a score, which I again exported as MusicXML ---> see "20210922-ch+p.Rutter_DormiJesu_ReexportedFromMusescore.mxl.zip. Once more, I had to manually unpack the .mxl. Now, when I gave this to MXML2NWC, it ran into some Pythonian error.
The Pythonian error when using your second, Musescore, file,- was again due to the presence of a decimal number where my program expected an integer. I fixed that and also a few other places where I thought a decimal number could be admitted. After running this new MXML2NWC version on your 2nd file, I got the same 2 popups as for your 1st file, so my conclusion is that the reason is due to the output of Audiveris.
146
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
Accepting (unzipped) .mxl files will be a piece of (apple) cake.

I will soon download, unzip and run your files to see what messages and error they will generate.
And hopefully I will be able to explain the messages and correct the error.
147
User Tools / Re: MUSICXML TO NOTEWORTHY CONVERTER
  • Thanks for your positive respons.
    Because I never found a unambiguous syntax description for MXML files, I had to develop this tool with trial and error, testing with files from different sources.
    I did not know about XML files generated by Capella before, so I'm glad it worked out so well.
  • As to the 'unknown publisher' fact: My website has no commercial intention. The majority of the downloads are NWC related, and I suppose the NWC users 'know' me enough from the forum. The other downloads are intented for my personal friends and family (but  not exclusively of course).  So if someone cancels the install process because I'm unkwown, so be it.
  • Removing the 1.0 version before I got a positive respons seemed a little premature.