Use this page to find the next safe step when a score, file, printout or practice tool does not behave as expected. Save a project backup before clearing data or changing browsers. There is no account to sign into and no cloud copy to restore automatically, so preserving the work on your device comes first.
Start with a short, supported melody
Open the main editor, choose the clef, key, meter and tempo, then enter one bar at a time. A simple 4/4 phrase is a useful first test because four quarter notes fill one bar. Count rests as well as notes. If a value will not fit, choose a shorter value or finish the current bar before continuing.
The editor is a single-melody workspace. It supports undotted whole through sixteenth values in the available 2/4, 3/4, 4/4 and 6/8 meters. Ties, tuplets, lyrics and multiple voices are not editing features here. A lesson may discuss those concepts for reading or paper practice without making them available in the editor.
Save a project you can reopen
Autosave is local to the same browser, profile and site address. It does not transfer a score to another device. Use the editable-project download to keep a .msm.json backup, especially before closing an important session. Reopen that file once and confirm the title, settings and notes.
A MusicXML export is for notation exchange, an SVG is a graphic, and a printed PDF is a reading copy. Keep the editable project as well. If the browser reports a storage problem, download a backup while the score is still open. Do not clear website data as the first troubleshooting step.
Check a project that will not open
Choose an actual project file previously downloaded from the editor. An .msm.json project is different from a MIDI, MusicXML, PDF or audio file. Renaming one of those files does not convert its contents. A JSON file edited elsewhere may also fail the project checks.
Try a known backup before changing your current score. If a file is rejected, keep the original and record the message. If it opens but appears different, compare the settings and note count with the source. Use the dedicated format tool for a file that was not created as an editable project here.
Fix clipping, small staves or unwanted print content
Use the score’s print control and inspect every page in preview. Match the paper size and portrait or landscape orientation in the tool, print dialog and printer. Staff-paper tools begin with A4 portrait; choose Letter when that matches your paper. The blank staff-paper generator lets you prepare a suitable layout first.
Check margins and scale if an edge is missing. Turn off unwanted browser headers or footers when they cover the music. Start with one test page. The printing guide explains these checks in more detail, including saving a PDF and inspecting it again before sharing.
Choose a suitable MIDI file and track
The MIDI tool accepts .mid or .midi files up to 5 MB. It reads symbolic note events, not an MP3, WAV or recorded song. Select a relevant melodic track and a rhythm grid, then review the draft rather than assuming that every performance detail has been preserved.
The conversion is simplified to a melodic voice. Dense chords, overlapping voices, drums, pedal effects and expressive timing can produce an unsuitable result. Test the original sample first when diagnosing a problem. If the sample works but another file does not, keep a small original example and note the selected track and grid.
Open MusicXML in the viewer and check the result
The MusicXML viewer accepts supported MusicXML/XML and compressed MXL files up to 8 MB. It is for reading and printing, not manually editing noteheads. A PDF, image or renamed MIDI file is not MusicXML. Keep the original score when trying a new export from another application.
Layout and specialised notation may differ after import. For the separate transposition tool, check the changed pitches, key and exported notation against a short known passage. A successful import or download does not remove the need to review the result, especially with transposing instruments or complex scores.
Get playback or a practice pulse to sound
Press the tool’s Play or Start control after opening the page; do not expect sound to begin automatically. Check device volume, tab muting, connected headphones and the selected audio output. A Bluetooth device may still be receiving sound even when the computer’s speakers appear silent.
Try a simple note or the metronome to separate a device-output issue from a score issue. Stop playback before trying again, and avoid running several sound tools together while testing. On a phone, return to the visible tab and start the sound again after switching apps or locking the screen.
Make a smaller screen or browser easier to use
Try a wider device orientation when a score or keyboard feels crowded. Keep browser zoom at a comfortable level and move through the page instead of expecting every control and a full sheet to fit in one small view.
If a control stops responding, save a project backup first, stop playback, and reload once. A current browser can help with notation, audio and download support. If you compare another browser or profile, bring the downloaded project with you; the original browser’s autosave will not automatically appear there.
Understand which progress stays on this device
The editor’s local project and note-reading practice progress belong to the browser that stored them. Other tool settings may reset during a new session. There is no account-based history that combines different devices or browser profiles.
Private browsing, blocked storage, cleared site data or storage pressure can affect what remains available. Download important projects before removing data. Reset practice progress only when you intend to start over; if a number seems unexpected, first check that you are in the same browser and profile as before.
Report the smallest example that shows the problem
If the relevant checks do not resolve the issue, use Contact. Include the page, a short sequence of actions, the expected result, the actual result and the browser or device context. Copy an error message accurately when one is shown.
Prefer a short original example over an entire private score. Do not send passwords, account details or sensitive files. Contact uses your email application; choosing a file in a music tool does not automatically send it with a report. Keep your own backup so that you can continue working or reproduce the same example later.