Double note tremolos should not be treated as beams in all situations

[GustafLundell]

Dorico does not recognise tremolos in musicXml files

Hi @dspreadbury, I just tried a possible workaround. I activated the Beam Groups setting in the MusicXML import preferences and imported the MusicXML file. The double note tremolos was imported. I choose Select All and then Reset Beaming to get Doricos beaming rules. I think this really should work. BUT, when I do the reset the imported double note tremolos disappear from the score. This is true even if I create the double note tremolos in Dorico (not just the imported ones). Conclution It…

From the thread above, I have a wish regarding double note tremolos.

Because double note tremolos are imported from MusicXML files only if the MusicXML import preference Beam groups is activated, and deleted if you use Reset Beaming, it’s clear that they are implemented as beams.

Maybe that’s correct in a technical point of view because they looks like beams if they are connected to the stems. But double note tremolos should not be treated as beam in all situations. They should always be imported, and not deleted when you reset beams.

[dspreadbury]

We’re not going to change the way tremolos are implemented in Dorico any time soon, since we are satisfied that the current implementation is an acceptable technical solution.

We can look into importing two-note tremolos from MusicXML when beamed groups are otherwise not imported, but if you subsequently invoke Reset Beaming, two-note tremolos will be removed.

[GustafLundell]

Thanks Daniel!
Importing two-note tremolos from MusicXML, when beamed groups are otherwise not imported, is all I need. If you can implement that, it would be great!

[DE_YU]

It’s been 4 years; I would like to ask whether the team still remembers this feature request. I use Dorico as my de facto engraving standard and want to avoid importing beam groups from other notation software; a dedicated checkbox in the MusicXML import preferences would help a lot.

I do understand that changing the implementation for two-note trems may be complex and likely will break backward compatibility, but adding an if statement in the MusicXML importing workflow that preserves beam groups only for two-note trems shouldn’t be that complex.