MusicXML export omits cue notes entirely

[Dorico version: 6.2.30.6245 (Windows)]

I’m finding that cue notes — visible on screen with “Show Cues” enabled in Layout Options — are completely absent from MusicXML export. Not just simplified or resized: there’s no trace of them at all, not even a <cue/> marker or any other indication that a cue exists at that point.

I’ve tested this across every export path I could think of, all with the same result:

  • Individual instrument part export
  • Full score export
  • MIDI export (understandably, since cues are typically non-sounding — but confirms the data isn’t carried through anywhere)

Minimal reproduction: 2 instruments (Flauto, Oboe), 5 bars. The Oboe plays bars 1–3, then rests for bars 4–5. In those rest bars, a cue of the Flauto’s material is shown in the Oboe’s part (cue-size notation, “Show Cues” enabled for that layout).

Cue test.dorico (448.8 KB)

In the exported MusicXML for the Oboe part, bars 4–5 come out as plain whole-measure rests — nothing distinguishing them from ordinary silence.

Cue test - Full score - 01 Flow 1.musicxml (17.7 KB)

We rely on cues being present in the exported data for downstream processing (we need to “see” the actual cue notes), and in a real orchestral score this can affect a significant portion of the bars, e.g. 57 cues in the first movement (103 bars) of BWV 1065. (Exporting in SVG or PDF graphics is not a solution, because the notion of the musical elements disappears in these formats.)

Questions:

  1. Is this expected/known behavior, or a bug?
  2. Is there an export setting I’m missing that includes cues?
  3. If this is a genuine gap, is it something on the roadmap, or is there a structural reason (cues being derived/rendering-time data rather than independent note data) that makes it unlikely to be supported via MusicXML?
  4. Does any one see a workaround?

Thanks for any feedback and ideas!

It is indeed a known limitation of MusicXML export at the present time, yes. It’s on the roadmap for the future, but I can’t say when it will be implemented.

Thank you Daniel!

We are eagerly waiting for a version 7 (?) where that will be resolved :slight_smile: .