||4 months ago|
|COPYING.md||6 months ago|
|README.md||4 months ago|
|mioctl||5 months ago|
mioctl is an open-source command-line utility for configuring Mio X-series devices from Linux and other operating systems not supported by iConnectivity.
Being a command-line tool means the approach to configuration is very different from the official graphical tool, with emphasis on power rather than pretty. To me the device looks more like router-firewall on a MIDI network more than anything musical, so the command line interface is modelled with that in mind, and making it possible to do things with a single command things that would require dozens of mouse-clicks with current Auracle.
When this project was started, there was no documentation for the X-series configuration protocol, this is all reverse-engineered from analyzing network traffic between Auracle and MioXL. As such, it is inevitable that there will be errors and misunderstandings in the code.
As of March 2021, protocol documentation has silently been added to the iConnectivity manuals page: https://www.iconnectivity.com/s/Common-System-Exclusive-Commands-TNG.pdf
mioctl will naturally be updated to take advantage of the new knowledge, eventually.
Developed and tested on Fedora 33, but the above is what matters. On other OS'es, device port names will differ but that is command-line overridable.
I have only tested this with MioXL running firmware 1.2.0 - 1.3.1, but I would expect MioXM to work too, or at least be relatively easy to support.
The older Mio-devices use an entirely different protocol and I have no means to support them as I have no access to such a device. However there's another open-source project supporting them: https://codeberg.org/dehnhardt/IConnConfig
As of the initial public version, the following is implemented:
- List, load and save (including rename) presets
- List, add and remove routes
- List device ports by their names
- List and set active remaps and filters
- View device information (model, serial, firmware version)
- View and set network configuration
I hope to eventually implement everything Auracle supports on these devices, but this is a hobby project among many others so it might take time, and due to the reverse-engineering nature there cannot be any promises.
Keep in mind this is a very early version with little in the way of sanity and error checking, and is more likely to respond to errors with a Python traceback than a coherent error message. It should not harm your device in any way as it only uses commands that Auracle uses, but there cannot be any guarantees.
mioctl presetshows currently loaded preset, add
--listto list all preset by their names.
mioctl infoshows device model, serial and firmware version
mioctl netshows current network configuration,
--dynamicsets DHCP networking,
--static <ip> <network> <gateway>sets statip ip. A reboot is required for the setting to take effect.
mioctl load [n]loads a preset. If preset number is not specified, it reloads the current one.
mioctl save [n]saves the current preset. If number is not specified, it saves on the current slot.
--name <presetname>can be supplied to save with a different name.
mioctl portlists device port numbers and names,
--set <name>is used to rename ports. Multiple ports can be renamed at once, in which case an incrementing number is automatically used as a suffix.
mioctl route --add/--remove <source>:<target>adds and removes routes, plain
mioctl routelists current routing table. For example,
mioctl route --add 1,2:5to add routes from ports 1 and 2 to port 5. Multiple port numbers are permitted on both source and target ports.
mioctl filterlists currently active (input) filters,
--set [<val1>[,<val2>...]can be used to set filters. To filter channel messages, specify
mioctl remaplists currently active (input) channel remaps,
--set <val1>[,<val2>,...]:<channel>can be used to set new remaps,
--channel <range>is used to specify channels for which the remap is performed and port range can be specified as a positional argument.
All port-related commands accept ports as positional arguments.
Port and channel ranges can be specified as comma-separated combinations
of individual numbers and numeric ranges, such as:
By default it will look for a MIDI port name containing 'mioX' which
should find it when connected via USB but this can be overridden with
--midiport <name> for access through any OS MIDI port that is somehow
connected to the device (be it DIN or otherwise)
Firmware upgrade is not supported by
mioctl at this time, however you
can easily do this on Linux with the
aplaymidi utility. Connect your
computer to the USB DAW port on the Mio, boot up the
device into bootloader mode (hold button on powerup for 4-5s on powerup),
aplaymidi -l to discover the port of the Mio (only one port
is visible in bootloader mode, called "mioXL Loader" or so), and "play"
the firmware .mid file you've downloaded file into that port, eg.
MioXL 1.3.1 firmware upgrade is something like this:
aplaymidi -p "mioXL Loader" mioXL_DFU_131_20210120.mid
You should see a lot of traffic on the USB port, once it stops and
the command exits successfully, power cycle the Mio and it should now boot
into the new firmware.