Comments by randygeorge

Thanks for the messages. I updated the device to 1.2.4 months back. I just posted it to this devices page. I'm not if it helps with jimbeam's issue at all. I am not yet on Live 12, so the device can't officially support it yet. I also still do not own an Osmose to be able fully support it. I'll investigate the crash as it relates to the description of the crash. Appreciate the detail. Thanks.

Mad Preset Launcher version 1.2.3 update posted. Automation of MIDI routing on the host track is no longer prone to MIDI Feedback in the short time when the configuration data is being fetched from the connected instrument. (previously this only occurred during "Preset Learn" function, but it also occurs when Manually setting the output routing using "External Instrument Device" placed after MPL device.

If anyone is using v1.2.1 with the "External Instrument Device" workaround because MPL is unable to trigger from MIDI or keystrokes, I strongly recommend to NOT use "Preset Learn" OR disable Track Input for your Osmose or Haken Instrument. This will eliminate any possibility for MIDI Feedback loop through Mad Preset Launcher. MIDI feedback loops are one possible cause for preset data corruption in the Osmose and Haken Instruments.

Mad Preset Launcher now also works in Max 8. With a Max 8 license (and the ability to Save patches) you can open and use MPL in the same way as in Max For Live, plus store MIDI / keystroke mapping assignments to the device file for later recall.
Apologies, Win11 is not supported yet because I don't have a system to test on. For any other windows users experiencing crashing with version 1.2.2, here is a link to download version 1.2.1. The External Device solution (described above) will need to be used for getting the messages to properly fire using MIDI or keystroke mapped triggers.

https://randygeorgemusic.com/media/software/Mad-Preset-Launcher-v1.2.1.zip
To be clear, the work around involving External Instrument device being placed after Mad Preset Launcher no longer works in version 1.2.2. Apply this solution only if you are using version 1.2.1 and if there is only a need for a single instance of the device.
Thanks for bringing that to my attention. I've applied a fix for this bug in version 1.2.2. Standard MIDI mappings and keystroke mapping should trigger presets now.

The device is designed in such a way that output settings for the Ableton MIDI track (selected Haken/EE device + midi channel 16) get automatically SET and CLEARED every time a preset is triggered. This makes it possible to have multiple instances of MPL on a single track. It also allows each instance to be set to a unique Haken device or Osmose.

In the version 1.2.2 it is more obvious when output and channel routing is being automated if you look at the track I/O. In the previous versions, the Live API calls were triggered so fast that it was not providing any visual feedback.

Placing the External Instrument device after MPL is a nice solution in case there are routing issues. Good find.