Changelog / Product updates

Miditor Changelog

A public record of what changed in Miditor: shipped MIDI tools, user-facing bug fixes and the next improvements planned for local browser conversion.

Last updated:

01 — Shipped

The working MIDI path is now in the browser

2026-08 · PLAYER

MIDI Player became a first-screen workspace

The player now joins the site Header and its tool surface as one interface. It includes local MIDI playback, a visual piano roll, practice controls, curated playlists and filters for trending tracks, easy pieces, random mixes, instruments, styles and composers. Open the MIDI Player.

2026-08 · CONVERTER

MIDI conversion starts above the fold

The general MIDI Converter, MIDI to MP3 and MIDI to WAV pages now open directly to an upload workspace. Users can parse a local MIDI file, preview the browser SoundFont render, set output options and download audio without uploading the MIDI file.

2026-08 · EDITOR

MIDI Editor now starts with the tool

The editor now lives at /midi-editor as a first-screen workspace. New sessions begin with a local upload/drop zone or a blank MIDI option, then open the piano roll after a file is chosen. The former application route redirects here.

2026-08 · EXPORT

Audio output controls are available before export

The converter supports MP3 bitrate selection, 44.1 or 48 kHz sample rate, output volume, normalization, configurable fades and release tail, local preview, render progress, cancellation and MP3/WAV download.

2026-08 · P0

Conversion now covers the core production workflow

The P0 pass adds two bundled, licensed SoundFonts with local caching, batch MIDI queues, per-track mute/solo/volume/pan/instrument controls, individual stems, second-based range export, tempo-map duration handling, and WAV 16-bit/24-bit PCM with optional dither. Use the MIDI Converter or read the license records.

02 — Fixed

Small navigation details now match the tool

FIX_01 · ROUTING

Converter CTA no longer opens the editor

The shared landing component previously sent every live tool's “Open in Miditor” action to the editor application. Converter pages now use a dedicated “Use this converter” action that returns to their first-screen conversion workspace.

FIX_02 · CONSISTENCY

Player and converter pages share one visual entry point

The tool Header, brand treatment and workspace title are aligned so the player and converter do not appear to contain duplicate Headers. The converter's SEO content remains below the working tool rather than replacing it.

FIX_03 · SOURCES

MIDI source and license information stays discoverable

The player now preserves the live catalog's license and source URL fields, falls back to a small local demo set when needed, and lists bundled SoundFont notices separately in the public MIDI licenses directory.

03 — Next

The converter roadmap

NEXT_01 · QUEUE

Queue packaging and recovery

Add ZIP packaging for completed batch outputs, plus pause and resume for long browser conversion queues.

NEXT_02 · RANGE

Measure-based range selection and metadata

Extend the current second-based range controls with measure markers, then add editable title, artist, album, composer and comment metadata to exported audio.

NEXT_03 · FIDELITY

Complex MIDI fixtures and fidelity edge cases

Add deterministic fixtures for time signatures, sustain, bank-select events, malformed input and long-tail effects, then verify exported files with an independent PCM parser.

04 — Principles

What counts as an update

Miditor separates shipped work from planned work. A feature appears under Shipped only after it can be used in the public browser workflow. Bug fixes describe the user-visible problem and the route or tool that changed. Next items are priorities, not promises or release dates.

The long-form implementation checklist lives in the repository's open-source project history, while this page stays focused on changes that matter to people using the public MIDI player, editor and converter.

Quick answers

Frequently asked questions

What does the Miditor changelog include?

It records user-facing MIDI tool improvements, bug fixes, shipped workflow changes and clearly marked next steps. Planned work is never presented as a released feature.

How often is this page updated?

The page is updated when a meaningful feature, compatibility improvement or user-visible fix is released. Small internal refactors may not appear here unless they change the user experience.

Where can I report a MIDI tool bug?

Use the Contact page with the affected route, browser, operating system, steps to reproduce, expected behavior and actual behavior. Do not send private or copyrighted MIDI files without permission.