A melody to harmonize or chords already chosen?
Use the melodic-sketch finder for scale-degree input and candidate diatonic triads; use the Roman numeral visualizer for an existing progression. Neither recognizes chords from a recording.
Elysia Tools
Navigation
Workflow Playbook
Develop a short piano idea, save editable MIDI, reopen it in music software and review an externally rendered audio demo with format, listening and file-integrity checks.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Chord Progression Finder from Melodic Sketch
Hubs
| Tool | What it does | Category |
|---|---|---|
| Chord Progression Finder from Melodic Sketch | Enter a melodic contour as scale degrees (1-7 or do-re-mi) plus a target key, and get candidate diatonic chord progressions ranked by voice-leading smoothness, with roman-numeral analysis and an audio demo. | Media |
| Chord Progression Roman Numeral Visualizer | Analyze a chord progression by key, Roman numerals, harmonic function, transposition, and cadence clues. | Media |
| 88-key Piano Studio | A full piano, a little room to play. Learn a phrase, connect a MIDI keyboard, or record your own. | Media |
| Audio Metadata Viewer | View all metadata tags of an audio file | Media |
Hubs
| Audio Cutter | Cut and extract audio clips from audio files with precise time selection | Media |
| Audio Waveform Generator | Generate a waveform image from an audio file | Media |
| Audio Loudness Report (LUFS) | Generate a report on the loudness (LUFS) and dynamic range | Media |
| File Hash Verifier | Calculate MD5/SHA1/SHA256 hash values for files and verify against expected hashes | Utilities |
This workflow is for beginning composers and piano learners sharing one short musical idea with a teacher, collaborator or arranger. The deliverable is an editable performance plus an audible reference, not a mastered release or an automatically generated arrangement. State the key, intended tempo, phrase boundaries and what feedback is needed. Keep an authorized original and distinguish each revision.
Choose the output contract before playing: MIDI for editing, audio for listening, and a note linking both to one revision. Browser piano processing stays on the device and uses no microphone. Supporting audio tools may upload files; check permission before sending an unreleased piece. A MIDI keyboard additionally needs a compatible browser on HTTPS or localhost.
For an unharmonized idea, enter scale degrees and a target key into the melodic-sketch chord finder. Compare a few diatonic candidates by ear. Its ranking describes model preferences, not the best artistic answer. If the chords already exist, use the Roman numeral visualizer to examine harmonic function and possible transposition instead.
Both aids use bounded major/natural-minor theory. Neither listens to your piano recording or reliably explains borrowed chords. Write down deliberate exceptions rather than forcing them into a diatonic label. Keep the chosen progression and key with the take; a candidate audition is not an automatic accompaniment track in the piano recorder.
Record a short manageable phrase in the 88-key piano. Check notes and pedal by listening, then save its MIDI with a take number before beginning again: a new recording replaces the previous take. The recorder allows up to 10 minutes or 20,000 events; do not use that limit as a storage strategy. Download accepted and alternate takes locally.
MIDI stores performance events, not the sampled sound. Reopen the actual downloaded file in external music software. Check note positions and lengths, velocity, tempo interpretation, note releases and sustain behavior. Do not assume an imported tempo setting proves that the performed rhythm is correct. Listen to the intended phrase and document corrections. Preserve the original MIDI if editing or quantizing a copy.
Select an instrument and render audio externally, recording the software, instrument, tempo and export settings. Browser timing and sound can vary, and piano samples last up to six seconds; sustain does not extend their natural sample end. The reference from another instrument need not reproduce the browser sound. If external rendering is unavailable, deliver MIDI only and label the audio reference as outstanding rather than claiming a complete pair.
Read the rendered audio's codec, duration, sample rate and channels with the metadata viewer. If unwanted lead-in or tail silence needs cutting, work on a copy and use the actual audible boundary. Preserve pickup notes, pedal release and reverb decay. Reinspect metadata and listen after any cut; the original render's measurements no longer describe the final artifact.
Use a waveform to locate suspected abrupt edges or long gaps, then confirm them by ear. It cannot prove correct pitches, correct pedal or absence of distortion. Measure integrated LUFS, true peak and loudness range as review context, not as a mandate to normalize every sketch. Very short or quiet material may produce unavailable or unhelpful integrated readings. Record the limitation and agree a listening level instead of inventing a pass mark.
Listen from beginning to end at a safe volume, including the last decay. If the wrong instrument, stuck sustain, missing pickup or distorted peak is found, fix the corresponding performance or render stage and repeat the final-file checks. A report alone is not musical acceptance.
Use matching revision names for MIDI and final audio. Include key, intended tempo, chosen chords, instrument/render settings, any MIDI edits, optional trim offsets, reviewer decision and unresolved issues. Keep the original take separate from the approved editable revision. Download all artifacts; a temporary processing URL is not durable delivery.
Calculate SHA-256 on the final local MIDI and audio after all changes. The recipient can compare those values to identify the same files; hashes do not prove musical quality or ownership. Mark external-software checks as pending if not performed. Continue with singing practice for vocal adaptation, multitrack mixing for arrangement, or mastering/loudness workflows for a later release requirement. This workflow ends at one reviewed sketch and its listening reference.
Workflow playbook
Record key, intended tempo and phrase boundaries. Explore diatonic chords from a scale-degree melody or analyze an existing progression, then choose by listening rather than rank alone.
Record notes and pedal with the browser piano, audition the take and download a named MIDI before replacing the recording. Keep the musical intention beside the take.
Manually import MIDI into music software, check the performance and instrument, then render audio. Inspect the rendered file's stream information; the metadata tool does not render or validate MIDI.
Trim a copy only if necessary, preserve musical decay and inspect the resulting waveform and LUFS/true-peak/LRA report. Listen to the complete final file and recheck metadata after edits.
Use the melodic-sketch finder for scale-degree input and candidate diatonic triads; use the Roman numeral visualizer for an existing progression. Neither recognizes chords from a recording.
Deliver MIDI for note editing and an externally rendered audio file for an agreed sound. MIDI does not contain the browser piano samples, and another instrument can sound different.
Cut only an identified unwanted region on a copy. Keep pickup notes, pedal releases and reverb decay; do not normalize or compress simply to reach an arbitrary loudness number.
Collect MIDI, final audio and revision/render notes, disclose untested cases and calculate SHA-256 after the last edit. The recipient checks the same files rather than relying on a temporary link.