YAMAHA DM7 · .DM7F

Your DM7 scene, with the supported strip state visible.

Import a native .dm7f, review the supported channel settings in the Strip, and export a patched copy. The preview names every field load·in writes and every field it preserves.

Open load·in See what it won't touch

01 — The format

The full DM7's native scene

.dm7f is the scene file the DM7 Editor and the console save. load·in works against the native container, preserving unedited data while applying only the bounded fields the export preview lists. The DM7 Compact is a separate, unproven record and stays a CSV workflow for now.

File Format

.dm7f

DM7 Editor's native scene file

Input Channels

120

The full DM7's channel array

02 — What load·in reads

Channel identity and the supported Strip

Import a .dm7f and load·in pulls channel names, colours and the supported filter, EQ, gate and comp state into the project, plus each mix bus's own name and output processing where the file carries them. Layouts it has not proven are preserved rather than rewritten.

03 — What load·in writes

A bounded standard-strip write path

✓Channel names you edit in the app, shortened to fit the file where they must, with every cut named in the preview

✓HPF and LPF, the standard EQ bands, gate and comp values you set in the Strip, where the imported channel uses the standard processing model

—Not written: 48V, mute, fader level, pan, aux send levels, DCA membership and stereo links. They are preserved from the imported scene, never authored, and the preview says so.

—Moving a channel to another strip of the same console is not carried into the file yet; the preview names the channels it applies to.

04 — What load·in leaves alone

Unedited scene data stays with the scene

load·in patches supported channel-owned fields and preserves the rest of the imported scene. When a scene has no spare room for a longer name, names are shortened before anything else is given up, and each step down that ladder is disclosed by channel.

05 — What load·in won't claim

The honest edges

—Unfamiliar processing models are preserved, not converted into standard controls.

—Exports opened successfully in Yamaha DM7 Editor 1.7.5. Physical-console and every-firmware acceptance are not claimed.

06 — Before the show

Verify it before it's the desk's problem

Yamaha DM7 Editor 1.7.5 opened load·in's exports without a format or load error. Three cases were run on 2026-08-09 — a fresh export, a real DM7-authored scene re-saved with a renamed channel, and an imported scene with edited names — and the exact output files are kept on record alongside the result. That is editor acceptance for those cases. It is not console-firmware certification. Check yours on the desk you're using.

Open the exported .dm7f in the matching DM7 Editor release and confirm channel names and changed Strip values.
Load into a spare scene and compare 48V, mutes, faders, pans, sends, DCAs and stereo links against the source; load·in never writes them.
Read the export preview before every download; it is the exact contract for the selected workflow.

Other Yamaha workflows: CL/QL · DM3 · TF · RIVAGE PM · the full list is on the console support page.

Bring the plot and the supported strip state together.

Import your DM7 scene. Build the plot. Review the Strip. Export a patched copy.

Try load·in free →

No signup required for local planning. DM7 console-file import and export require Pro and an internet connection.