Hello all.
I can’t seem to get any 1/4 tones to export to musicXML from OM6.10 on OSX El Cap. I tried patching it with the patch that Jean uploaded in the tuples-export thread, but that didn’t fix the problem. Thanks for your thoughts!
Best,
N
Hello - Thanks for the report. Will be corrected soon.
This happens (I guess) only when you export from the voice editor.
Using the EXPORT-MUSICXML function from your patch (+ set the ‘aprox’ argument to 4) should work
Jean
Hi,
I have noticed a similar issue when exporting using 1/8 tones, either from the export option within the editor, or using the EXPORT-MUSICXML function. Strangely enough, some of the accidentals are right, but some other aren’t (for instance, an high E+1/4 is right, but a middle G+1/4 always shows up as G# in Finale). As a workaround, I use the ETF export format, which still works properly, but I have to keep running a fairly older version of Finale in parallel (because ETF are no longer supported since a while), and it’s just clumsy…
Is it something that has already been reported? Is there some settings we should try in Finale to ensure a proper import? I tried to look inside de Key Signature Tool, but everything seems to be set to default values, even in the 1/8-tone XML-imported file…
Thanks for you help!
Jimmie
Hello Jimmie,
Yes, known bug. Will be fixed in the forthcoming update.
All best,
Jean
Thank you very much for the quick reply!
By the way, about the save-as-etf option: I have noticed that the first measure of the Voice object (or the first bar of the top voice of a Poly) is somehow deleted when imported in Finale. I fixed it for me by adding an empty Voice on top of the others I actually wanted to export, but I was wondering if it was a known issue, and if there were other solutions to it. This being said, and at the same time, I was also wondering whether the etf format was still supposed to be supported in the future, or not?
Thank you very much again,
Jimmie
You’re right, you should actually not rely on ETF exchange updates anymore.