Skip to content

Known Limitations

The following limitations may be encountered while using VirtualScore. These are primarily due to edge cases, unaddressed issues in underlying technologies, or unsupported capabilities, often stemming from factors beyond VirtualScore’s direct control.

MusicXML Parsing Issues

MusicXML files may not parse perfectly due to inconsistent adherence to standards. Common issues include:

  • Repeating notes as multiple voices
  • Inaccurate indexing of voices (primarily in piano pieces)
  • Incorrect representation of tempo changes

MusicXML Rendered Scores Issues

These issues could occur during playback or interacting with the rendered MusicXML file:

  • Inability to place the cursor on a grace note
  • Inability to accurately place the cursor on short duration notes (1/16, 1/32, …)
  • Not fully adherent to MusicXML standard

Impact and Frequency

  • Most prevalent in highly complex pieces (grand staff)
  • Some music editing software exporters produce highly compatible MusicXML while others do not
  • Unlikely to occur in the majority of musical pieces

Root Causes

These issues often stem from how popular software exports MusicXML files, including:

  • Loose compliance with MusicXML standard
  • Underlying open-source score renderer incomplete compliance with MusicXML standard

Workaround

Adapt your MusicXML file to VirtualScore’s underlying renderer by:

  • Unarchiving the file, editing the internal XML file in locations where the issue manifests itself, then rearchive into .mxl again
  • Replace MusicXML elements with similar ones that the underlying renderer supports
  • Try a different software to export your MusicXML file