Choose PDF, MusicXML, or MEI¶
Choose PDF to keep the appearance you prepared in the score editor, or MusicXML to choose parts, transpose, and use musical information. MEI is supported too, with different notation limits and part handling.
Choose for your purpose¶
| Format | Best for | What happens after import |
|---|---|---|
| Playing from the pages and placement you finished in the score editor | Keeps the exported layout. Supports annotations and automatic page turns you set up manually. The XML workflows for musical auto settings, transposition, adding parts, and source-file updates do not apply. | |
MusicXML (.musicxml / .xml / .mxl) |
Choosing parts, changing key, and using tempo and measure structure for preparation | PagePilot rebuilds fixed pages. Choose a full score or part when multiple candidates exist; add another part or update from a source file later. |
MEI (.mei) |
Displaying supported MEI notation and using its musical information | Supports a single-movement full score. Transposition and source-file updates are available, but part extraction is not. Notation that cannot be converted stops the import with an explanation. |
Choose all these formats through the same Score File option. MusicXML and MEI build fixed pages, then save alongside PDFs in Scores in your library and open as ordinary scores. Source files is an auxiliary screen for managing the saved MusicXML and MEI sources.
Bring scores from MuseScore or Dorico¶
MuseScore .mscz / .mscx and Dorico .dorico files are the score editors' native projects. Export PDF or MusicXML in the score editor, then import that export into PagePilot.
- MuseScore desktop: Use File → Export to choose PDF or MusicXML and the parts to export. See the official export guide.
- Dorico desktop: For MusicXML, use File → Export → MusicXML and choose flows or layouts. For PDF, select the layout in Print mode, choose Graphics and PDF, and export. See MusicXML export and exporting PDF and other graphics.
Menus and available options differ by version and platform. For an iPad version or another environment, check its own official instructions. Complete reproduction of every version and export from these editors is not guaranteed.
MusicXML and MEI can look different from the original¶
MusicXML and MEI do not carry finished pages. PagePilot builds pages with its own fonts and rendering, so symbol placement, text placement, and page counts can differ from the score editor.
- Original page breaks are ignored.
- Original MusicXML system breaks are kept when displaying all parts supplied by the input, such as a full score. A part extracted from a full score is laid out into new systems by PagePilot.
- Pages are fixed after import and do not reflow during ordinary viewing.
- Information omitted by the exporter and notation unsupported by rendering or MEI conversion cannot be used. Check the detailed import and notation limits.
If appearance matters, try MusicXML with a short score first or choose PDF. See also languages and scripts covered by the bundled fonts.
Using auto settings, updates, and transposition¶
When you create a new song using a score built from MusicXML or MEI, safely readable tempo, meter, page turns, and related information are applied automatically as initial settings. Unreadable values and ambiguous repeats or jumps are not guessed. Timing is not fitted to an audio recording automatically: play it through and check or adjust it.
For source-file updates, review and apply changes for each song that will use them. Annotations and adjusted cues keep their saved page numbers and positions, so check for misalignment with the new pages. After transposing, check the notation too, including transposing instruments, tablature, and percussion.
PagePilot does not edit notes or synthesize playback from the notation. Edit notes in your score editor, export again, and update from that source file.