How to open .SCO files on Android
To open .SCO files on Android, android typically will not render a .SCO score by itself; open it only as text in a compatible editor, or move it to a desktop system with Csound to generate audio.
Step-by-step instructions
- Android typically will not render a .SCO score by itself; open it only as text in a compatible editor, or move it to a desktop system with Csound to generate audio.
Common issues
It opens in a media player but there is no sound (or it won’t play)
.SCO is usually not an audio recording; it is a Csound score that must be processed by Csound to create audio output.
- Open the file in a text editor to confirm it contains score lines (text).
- Use Csound to run the .sco together with its matching .orc (or use a .csd that contains both) to render audio.
Csound errors about missing orchestra (.orc) or instruments
A score typically depends on instrument definitions in an orchestra file; without the correct .orc (or a combined .csd), Csound can’t interpret the score’s instrument references.
- Locate the corresponding .orc file that belongs to the project and run Csound with both files.
- If you don’t have an .orc, request it (or a unified .csd) from the file’s source.
Csound can’t find files referenced by the project (paths, includes, samples)
Projects may rely on relative paths; running Csound from a different working directory can cause missing-file errors.
- Run Csound from the project folder so relative paths resolve correctly.
- Check the score/orchestra for referenced filenames and correct the paths if necessary.
The file looks like garbled characters in a text editor
While .sco is commonly plain text, the file may be in an unexpected encoding or may not actually be a Csound score.
- Try opening it with a text editor that lets you choose the encoding (e.g., UTF-8 vs. legacy encodings).
- Confirm with the source that the file is intended for Csound; if it is not, treat .sco as ambiguous and identify it by context rather than extension.
Security note
.SCO files are typically text and are processed by Csound; treat them like code/data from other people—render them only if you trust the source.