Troubleshooting Guide

Error: "Failed to decompress MXL file"

Cause: The .mxl file may be corrupted or in an unsupported format.

Solution:

1. Try re-exporting the file from your notation software
2. Verify the file isn't corrupted (check file size, try opening it in your notation software)
3. As an alternative, export as uncompressed MusicXML (.xml or .musicxml)
4. Upload the new file

Error: "This doesn't appear to be a valid XML file"

Cause: The uploaded file is not XML format (might be a MIDI file, PDF, or corrupted file).

Solution:

• Verify you exported as MusicXML, not MIDI or other format
• Try opening the file in a text editor - it should start with <?xml
• Re-export from your notation software
• Make sure the file wasn't corrupted during download/transfer

Error: "The file appears to be empty"

Cause: The file has no content or the export failed.

Solution:

• Check the file size - it should be at least a few KB
• Re-export from your notation software
• Make sure your score actually has notes before exporting

Error: "No <part> nodes found in the MusicXML"

Cause: The MusicXML file doesn't contain any parts/staves.

Solution:

• Make sure your score has at least one staff before exporting
• Try exporting again from your notation software
• Open the XML in a text editor and look for <part id="..."> tags

Error: "Roadmap expansion exceeded max steps"

Cause: Your score has infinite loops or extremely complex repeat structures.

Solution:

• Check your score for repeat signs that create endless loops
• Simplify complex D.S./D.C. structures
• Try turning OFF "Follow Roadmap" for a linear conversion
• Consider "unfolding" repeats in your notation software before export

Conversion succeeds but output looks wrong

Possible causes and solutions:

• Missing notes: Check that all notes in your score have valid pitches and durations
• Wrong timing: Look for time signature or tempo marking issues in your original score
• Repeated sections missing: Verify repeat signs and roadmap marks are correctly placed
• Lyrics in wrong places: Check lyric syllabification and placement in original score

No lyrics appear in the output

Diagnosis:

• Check if your original score has lyrics attached to notes
• Make sure lyrics are on the correct verse number
• Verify the "Export Verses" setting is correct

Solution:

• Add lyrics to your score in the notation software
• Re-export the MusicXML file
• If using multiple verses, try the "Export Verses: All" setting

Lyrics are incorrect or scrambled

Common causes:

• Incorrect syllabification in the original score
• Lyrics placed on wrong notes or voices
• Mixed up verse numbers in multi-verse scores

Solution:

• Review lyric placement in your notation software
• Use proper hyphenation for multi-syllable words (e.g., "beau-ti-ful")
• Make sure each syllable is attached to the correct note
• Re-export and convert again

Too many dashes (-) in the output

Cause: Notes are being marked as sustained when they shouldn't be.

Solution:

• Check for unnecessary ties in your score
• Verify that slurs are used correctly (for melismas only)
• Make sure each syllable has its own note when appropriate

Multi-part score: lyrics only on one voice

Cause: Parts aren't grouped for lyric sharing.

Solution:

1. Click "Define Groups" before converting
2. Give all parts that should share lyrics the same group name
3. Convert again

Repeats aren't working / music doesn't repeat

Diagnosis:

• Check if "Follow Roadmap" is enabled
• Verify repeat signs are properly placed in your score
• Check the "Default Repeat Times" setting

Solution:

• Enable "Follow Roadmap" setting
• Make sure your notation software includes repeat barlines in the export
• Increase "Default Repeat Times" if needed

1st and 2nd endings aren't working correctly

Possible issues:

• Ending brackets not properly marked in original score
• Ending numbers incorrect or missing
• "Follow Roadmap" is disabled

Solution:

• In your notation software, clearly mark 1st and 2nd endings with the ending tool
• Make sure ending numbers are set correctly (1, 2, etc.)
• Enable "Follow Roadmap"
• Re-export and convert

D.S. al Coda or D.C. al Coda not working

Note: These are complex structures that don't always export correctly from notation software.

Solution:

• Make sure ALL elements are present: Segno (or beginning), "To Coda", D.S./D.C. al Coda marking, and Coda
• The converter attempts auto-detection for Finale scores - check console for messages
• If auto-detection fails, you may need to "unfold" the score manually in your notation software
• Alternatively, disable "Follow Roadmap" and manually arrange the file

SA/TB voices aren't being separated

Solution:

• Enable "Separate 2-voice Staves" setting
• Make sure your score uses proper two-voice notation (stems up/down)
• Convert again

Voices separated incorrectly or notes missing

Cause: Complex voice crossing or ambiguous notation.

Solution:

• Try disabling "Separate 2-voice Staves" for a simpler output
• Or, separate the voices into different staves in your notation software before export
• Make voice assignments clear in the original score

Too many or too few tracks in output

Diagnosis:

• The converter creates one track per voice part found
• "Separate 2-voice Staves" doubles the count for split staves

Solution:

• Remove unwanted instrumental staves from your score before export
• Toggle "Separate 2-voice Staves" based on your needs
• Merge or delete tracks in Synthesizer V after import if needed

SVP file won't open in Synthesizer V

Solution:

• Make sure you're using Synthesizer V Studio (any version)
• Check that you have the latest version of Synthesizer V
• Try opening the JSON in a text editor to verify it's valid
• Re-download the SVP file (it may have been corrupted)

No sound when playing back in Synthesizer V

Cause: No voice database is assigned to the tracks.

Solution:

1. Click on each track in Synthesizer V
2. In the Voice panel, select a voice database (e.g., Eleanor, Solaria, etc.)
3. Choose the appropriate language for your lyrics
4. Play back to test

Pronunciation sounds wrong or unnatural

This is normal! The converter provides text lyrics, but pronunciation is determined by Synthesizer V's AI.

Solution:

• Select notes and edit the phoneme sequence manually
• Use Synthesizer V's dictionary feature for common words
• Adjust individual phonemes for fine control
• Try different voice databases - they may pronounce differently