Importers and exporters
Importer and exporter registration is (WIP).
An importer converts a source file into Amadeus tracks. An exporter converts Amadeus track data into a target format. Declare the file extensions and endpoint through the package builder; when the target release accepts the definition, an enabled package appears in the corresponding file dialog.
Capability state
Section titled “Capability state”| Surface | State | Limit |
|---|---|---|
| Import registration | Unavailable | The host does not accept the endpoint yet. |
| Input access | Available | Importers may read text, bytes, or an ArrayBuffer. |
| Import result | Available | Return one track, several tracks, or diagnostics with the result. |
| Export registration | Unavailable | The host does not accept the endpoint yet. |
| Export result | Partial | Text output is declared; binary output is unavailable. |
| File-dialog discovery | Unavailable | Formats are not added to the file dialog. |
Import
Section titled “Import”An importer receives file metadata and access to its content. Read binary formats as bytes and text formats with an explicit text decoder. Create tracks with their notes, written pitch, rhythmic position, duration, and lyric data. Return diagnostics when the source contains information the adapter cannot preserve, because the user must review the imported result before baking.
Export
Section titled “Export”An exporter receives the selected score data and returns text. Document which notation, lyric, tempo, and voice-assignment information the text format can preserve.
Use representative source files from the target notation application. Verify the imported score before rendering, and compare an exported file in a second application where practical. File formats vary in their support for vocal lyrics, articulations, and application-specific extensions.
Package specification
Section titled “Package specification”Published package documentation should identify:
- supported format names and versions;
- tested source or target applications;
- score data preserved, transformed, or omitted;
- text encoding and binary-data requirements;
- implementation state for every declared capability.
See the Plugin API for the declared operations.