Firmware
The firmware for most of the inMusic devices is packaged the same, so we're able to extract, recompress, and update most device firmwares.
One Image, Many Devices
inMusic publishes a separate per-product download for every device, but those downloads aren't always separate firmwares. From Engine OS 5.0.0 onward, several of them are byte-identical - same MD5, served out of the same release directory, differing only in filename. All Engine OS devices on 5.0.4 are covered by six distinct images:
Devices | Hardware IDs | Vendor Filenames (all identical within a row) |
|---|---|---|
Mixstream Pro, Prime 2, Prime 4 |
|
|
Prime 4 Plus, Prime GO Plus, SC Live 2, SC Live 4 |
|
|
Prime GO, SC5000 Prime, SC5000M Prime |
|
|
SC6000 Prime, SC6000M Prime |
|
|
Mixstream Pro Go, Mixstream Pro Plus |
|
|
System One |
|
|
The same six-way grouping holds for 5.0.0 through 5.0.4. The System One (Rane, RMZ2) stays on its own image throughout, which is expected - it's the only RK3588/AZ04 device.
It Isn't Consistent Across Versions
Image sharing comes and goes, so it can't be assumed from the version number alone. SC Live 2 and SC Live 4 shipped a shared image at 2.3.3 and 2.4.0, then diverged into separate per-product images for every release from 3.0.0 through 4.3.4, then converged again at 5.0.0 - this time into the four-device image alongside Prime 4 Plus and Prime GO Plus.
Akai MPC
The MPC line does something different again. Rather than publishing duplicates, a single download covers eight hardware IDs outright: MPC-3.9.1-Gen1-update.img serves ACV5, ACV5S, ACV8, ACVA, ACVA2, ACVB, ACVM, and ACVR (see Akai), with MPC-3.9.1-Gen2-update.img as the Gen 2 counterpart.
Additional References
Denon Prime Go Console Access - Information to unpack the firmware, add in remote access, and re-pack the firmware.