YAMAHA RIVAGE PM · .RIVAGEPM

Names, scoped to what's actually been tested.

RIVAGE PM3 through PM10 share the .RIVAGEPM container. load·in writes channel names into it — and is upfront that the round trip has only been exercised on the PM3/DSP-R10 144-channel shape.

Open load·in Read the RX-EX caveat

01 — The format

One container, four surfaces

.RIVAGEPM is the scene file for Yamaha's RIVAGE PM line — PM3, PM5, PM7, PM10 — built and read by the RIVAGE PM Editor (offline) or the console itself. The surfaces differ wildly in scale: PM10 can run a 288-channel show across expansion DSP racks, while PM3 tops out closer to a self-contained 144-channel engine.

File Format

.RIVAGEPM

RIVAGE PM Editor's native scene file

Models

PM3 · PM5 · PM7 · PM10

Same container, very different channel scale

02 — What load·in reads

Channel names, for the plot and list

Import a .RIVAGEPM and load·in pulls channel names into your input list. The export preview reports the currently supported fields before a file is written.

03 — What load·in writes

Names. That's the whole claim.

✓Channel names — proven on the PM3/DSP-R10 144-channel container: export, re-import, size-preserving round trip

—Colors, icons, stereo links, mix labels: not written.

—48V, gain, EQ, dynamics: untouched.

04 — What load·in leaves alone

Almost the whole file, and that's the point

Outside the name field, a RIVAGE scene comes back the way it went in — gain, EQ, dynamics, routing, everything the desk's own DSP is carrying. On a console this deep, that's not a hedge — it's the only responsible scope for a first pass.

05 — What load·in won't claim

Read this one before a PM5 or PM10 show

RX-EX Risk

The verified round trip covers the PM3 / DSP-R10 144-channel container only. If your PM5 or PM10 rig is running RX-EX expansion racks, that configuration has not been exercised — the file container may not represent your show the way it represents a PM3's. Treat any RX-EX export as unverified until you've confirmed it yourself on a spare scene.

—Names only, full stop — no color, icon, stereo link, mix label, or processing writeback for this format.

—Round-trip verification does not extend past the PM3/DSP-R10 shape today.

06 — Before the show

Verify it before it's the desk's problem

Open the exported .RIVAGEPM in RIVAGE PM Editor and confirm names before touching a live console.
If you're running PM5 or PM10 with RX-EX, load into a spare scene and do a full manual read-back — this shape hasn't been through the corpus.
Compare every other field against the source scene — it should be byte-for-byte identical.

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

Names travel. Verify the rest yourself.

Import your RIVAGE PM scene. Build the plot. Export the names back in.

Try load·in free →

No signup required to plan. Console-file export and account features need a connection.