Repository navigation
Releases: TicT4x/MX-Edit-Testing
Releases · TicT4x/MX-Edit-Testing
Release list
v0.2 – Diagnosis 2
Diagnosis 2 – one tool that collects everything we need to support the Pedalboard and Gigboard in MX-Edit.
Thanks to the first Pedalboard report: the bridge runs on a real Pedalboard!
What is new in HeadRush_Bridge_Diagnose.exe:
- It reads much more by itself: setlists and songs, the rig list (names and order only), the layout of a rig (which settings exist, not their values), the scenes of all footswitches.
- A short guided round (about 2 minutes) in which it only watches what you do on the device:
- Rig view – confirm the rig names, page one bank down and up.
- Stomp view – it shows your switches with their display texts and tells you exactly which ones to press.
- Setlists (optional) – open a setlist the way you normally do; the program notices every screen by itself.
- It still changes nothing on the device. The log is saved after every part, also if something goes wrong.
If you already sent a log, please run the new version once more – it collects a lot more.
The testing patcher is unchanged in function (rebuilt from the current sources).
v0.1 – Pedalboard & Gigboard testing
First testing release of the HeadRush Bridge for the HeadRush Pedalboard and Gigboard. It is the MX5 Bridge from MX-Edit, built for all three devices. Untested on real Pedalboard and Gigboard hardware – please read the README first, especially the risks. The Gigboard has no recovery mode.
Downloads
HeadRush_Bridge_Testing_Patcher.exe– builds the HeadRush Bridge 0.7 updater for the MX5, Pedalboard or Gigboard from the official HeadRush 2.7 updater (downloaded from inMusic on your PC; optional NAM mod).HeadRush_Bridge_Diagnose.exe– reads the device through the bridge (changes nothing), asks a few questions, records the footswitches and writes a log file. Please attach it to an issue with the Diagnosis log form.
Checked so far (without a Pedalboard or Gigboard)
- Firmware comparison: the start scripts, the kernel (USB-MIDI built in), the QML interfaces the bridge uses and the factory database are identical to the MX5. Only the USB product name and ID differ.
- The built Pedalboard and Gigboard updaters differ from the official ones only in the 12 bridge files. The file system check is clean.
- The diagnosis tool was checked on an MX5, including the footswitch test.