I just spent time writing up a bug to report the MusicXML tuplet tremolo problems and the forum rejected the post. Your forum software doesn’t let me link to older posts and lets me paste in images that subsequently generate an error when I try to post. Anyway - I am out of time to re-post it, so I emailed the problem.
There are better, inexpensive, modern forum tools available that are much more capable and user-friendly than the software you are currently using (including Xenforo and vB).
You could try to post your report - without the links and attachments. Afterwards edit the post to add the links and add images.
I never (ever) had problems linking to older threads btw. May be your experience was a temporary forum software hiccup?
The forum said that my post was rejected because of links and images. It wasn’t a glitch - just a lack of functionality - or incorrectly restricted functionality. I linked to a previous forum post citing the same tuplet issue in 2019 with Dorico 2, and I pasted in pictures of what the problem looked like in my current setup with Dorico 6. There is no reason why my post shouldn’t have succeeded.
Honestly speaking, there are much better, more fully-featured forum tools to run these kinds of support forums (like xenforo) and Steinberg could easily address this issue and get rid of the inadequate homegrown solution. The onus shouldn’t be on users to have to tip-toe around all the forum software deficiencies in order to create basic posts, especially when they are already spending their time to try to improve the product.
Here is the link to a previous post about failed MusicXML tuplet tremolo import:
Nope - didn’t work…again. Here’s what I see
If anyone wants to find the old post - the title is:
“Dorico does not recognise tremolos in musicXml files” Post #121336 from Jan 2019.
Anyway - it would be great if Steinberg would fix the long-standing, failed tuplet tremolo import issue from MusicXML and use a better forum software platform.
OK - since I can include images…we’ll see if my saved post will work without the link.
Nope - can’t include all the images - I see this error and now have to waste more time trying to deal with forum software implementation/restrictions:
Do you want people to be able to report detailed bugs here?
Problem: When trying to import MusicXML scores that contain tuplet tremolos into Dorico 6, Dorico fails to import the note values correctly, and the import also fails (blank score after it fails a bunch of tuplet tremolo measures). At the point of failure, Dorico inserts a measure with extra beats (in this case a 5/4 measure where a 3/4 measure should be) to try to make up time. The same MusicXML file works fine when importing into Finale.
Config: Windows 11, Dorico Version 6.2.30.6245 (May 29 2026)
Here is how the MusicXML file looks after importing into Finale:
See Example 1 below.
n.b. All the tuplet tremolos are correct.
Here is what it looks like after importing into Dorico 6 (with tuplet signposts turned on) - 16th note tuplet tremolos in 3/4:
See Example 2 below.
Instead of showing dotted half-note tremolos, Dorico incorrectly shows barred dotted quarters.
Dorico has this problem on tuplet tremolos with 16ths, 8ths and also unmeasured tremolo (or 32nds/3 bars as Dorico sees them - but in the latter case, duration doesn’t matter).
Here is a spot showing the imported 8th note tuplet tremolos in 3/4:
See Example 3 below.
-> incorrect
Here are “unmeasured” tuplet tremolos in 3/4 in Dorico 6:
See Example 4 below.
-> incorrect
In this case, Dorico 6 gradually accumulates meter errors and inserts a 5/4 measure into a 3/4 key signature. After that, the rest of the import fails (blank staves).
See Example 5 below.
-> incorrect and very confused - the fact that Dorico is able to insert a 5/4 measure into 3/4 also points to other coding errors beyond the tuplet tremolo.
Please review and fix this issue so that Dorico 6 can provide better support for MusicXML files. This issue represents core functionality with MusicXML and it is unusable for import without lots of after-the-fact repair on an orchestral score that should just work.
I guess that unless you can provide the XML you used, it remains uncertain if the problem is in the export, the import, or both.
What’s the origin of your XML?
Did you test with creating a tremolo in Dorico, export that in XML, and reimport that?
I should have been able to make a single post with no churn. Is making users create 5 posts with 1 image each and lost context, not to mention not being able to include the link to the previously-reported issue, better than 1 post with 5 images in the correct context and with the documentation link? It might be worth rethinking the forum assumptions and user class restrictions.
TonH - I did supply the XML yesterday. I sent it to Ulf and Steinberg has it. And this problem was reported 7 years ago. Why hasn’t it been fixed?
Also, Steinberg appears to have removed the tuplet tremolo beam grouping options in the Notation Options section that were present in version 2. Or, I can’t find it.
To prevent spam, there are restrictions, which get lifted once a user is more active reading and writing on the forum. It might you’re hitting those.
Well, then be patient. Yesterday was Saturday, today is Sunday. Don’t expect them to react to you in the weekend.
The user class assumptions are flawed. If I sign up as a registered user and have a Steinberg product, why would be a risk as forum link spammer? Also, I joined over a year ago. Am I spammer if my account age is > 1 year and I have never spammed? Highly unlikely.
The user restrictions and classes are poorly-defined, need re-thinking and are preventing users from being able to easily report bugs and engage in back-and-forth communication without having to jump through hoops.
And, having to make all of these posts (including separate image posts) instead of just making 1 post with a clear bug report and no churn or wasted time+frustration is arguably 1000x worse and harder to parse. It’s dumb.
TonH - besides the bug, the problem and frustration derive from the forum interface and repeated attempts to try to report the same bug. I am happy to wait for a response - totally fine. I have no expectation of speed since this issue has existed for 7 years and has apparently remained unresolved across 4 major Dorico releases (which is surprising to me).
This is just the way that the Discourse forum software works – it’s not something specific to Steinberg.
I’m sure @Ulf will pass the xml to the appropriate member of the team. (He is the audio engine expert and not involved with the notation side of things)
But if the problem is caused by the Finale export, there’s not much the importing program can do about it. MusicXML is an imperfect, but improving, format. There are many problems that have been reported in transfers between all the programs that use the format.
The forum platform is a 3rd party app and common across the Steinberg product range. Your trust level is dependent on your activity on the forum, not your status as a customer.
I think Daniel explained that in the thread @KeyCats seems to refer to.
You are right. (Sorry, I didn’t follow that link). So this is a situation where Dorico would have to interpret a very particular MusicXML formulation produced by Finale
