REV Installer Tools

Musway DSP Converter

Provide your source file and a blank template from the target unit. The converter handles format detection, channel mapping, and firmware encoding differences.

1

Source
File

2

Target
Template

3

Review &
Convert

4

Download

Upload the tune file you want to convert — the preset saved from the existing DSP unit.

🎛

Source Tune File

.ini.txt

Drop file or click to browse

Legacy binary .ini or 512k JSON .txt / .ini

What is this? The preset exported from the old Musway app (pre-512k binary) or saved from a 512k unit. Single preset ~24 KB · All presets ~180 KB+.

→

Target loads
in Step 2

Load a source file to continue

Upload a blank export from the target unit — the DSP you're loading this tune into. Export it while connected to the hardware in the Musway app.

Source Loaded

—

→

📄

Blank Template

.txt.ini

Drop file or click to browse

Fresh blank export from the 512k target unit

Critical: Must be exported from the exact unit you're loading into — not a tune from a different unit. Wrong file = hardware mismatch error on load.

Load a blank template to continue

What This Tool Does

Capabilities & Limitations

✓ Converts Automatically

✓Converts legacy Musway binary presets into 512k JSON format
✓Transfers tunes between 512k DSP models (M8 → M10, etc.)
✓All 31 EQ bands per channel — gain, Q, and frequency
✓HPF/LPF crossover frequencies (single-preset legacy files)
✓Auto-detects format, channel count, and preset structure
✓Normalizes filter encoding differences between firmware versions

⚠ Manual Entry After Loading

↳Enable HPF/LPF per channel — frequencies load, toggle ON manually
↳Crossover slope types — set per channel in app
↳Crossover frequencies when using all-presets legacy files
↳Channel delays — not stored in legacy per-channel data
↳Output levels, master level, phase and polarity
↳Channel mapping when moving between different DSP models

Always verify the tune by ear after loading a converted file. The blank template must be a fresh export from the specific target unit — a saved tune from a different unit will cause a hardware mismatch or scene file model mismatch error on load.

Step-by-Step Reference

Guide

Expand any section for detailed instructions. Use "Expand All" within a section to open every step at once.

Reference

File Formats

Understanding what format your files are in before you start a conversion.

LEGACYBinary Preset — Pre-512k.ini

Encoding

UTF-16 LE
Decimal text, one value/line

File size

Single preset ~24 KB
All 6 presets ~180 KB

Q values

Single: float (4.320000)
All presets: integer (432)

EQ bands

31 bands/channel
1/3-octave 20Hz–20kHz

Crossover

Single preset: readable
All presets: not decoded

App

Pre-512k Musway app

512k512k JSON — Single Preset.txt

Encoding

UTF-8 JSON
Human-readable

EQ fields

lx (type) · pl (freq)
qz (Q) · zy (gain)

Crossover

gq/gq_pl = HPF
dq/dq_pl = LPF
Enable flag: 0=off, 2=on

Filter bypass

HPF bypass: gq_pl = 20
LPF bypass: dq_pl = 20000

Device ID

deviceNo = unit serial
ProductModel = model string

App

Musway 512k app
Current firmware

Hardware mismatch / Scene file model mismatch: Both errors mean the file's device identity fields don't match the connected unit. Always use a blank exported from the exact target unit as your template.

512k512k JSON — All Presets.ini

Encoding

UTF-8 JSON
Human-readable

Structure

prefs: [ array of
6 preset objects ]

Filter flags

dq=0 (off), dq=2 (on)
NOT dq=1 (legacy value)

EQ fields

Same per-channel structure
as single preset

Crossover

Not decoded from
legacy all-presets format

App

Musway 512k app
Current firmware

Conversion Compatibility Matrix

From	To	Mode	EQ	Xover Hz	Delays	Notes
Legacy binary (single preset)	512k same model	Legacy→512k	✓	✓	Manual	Enable filters after load
Legacy binary (all presets)	512k same model	Legacy→512k	✓	Manual	Manual	All 6 presets transferred
512k M8	512k M10	512k→512k	✓	✓	Manual	Channel map required
512k any model	512k same model	512k→512k	✓	✓	✓	Direct copy