Global MIDI Destination Remapping for Actions
under review
Z
Zulu
Description:
Enable users to globally reassign the MIDI destination for all MIDI-triggering actions within a project. This would allow for seamless redirection of output when switching to a different MIDI device or host.
Problem:
Currently, each action that sends MIDI is hard-linked to a specific MIDI device. When a project contains 100+ MIDI actions, replacing the destination device one-by-one becomes extremely time-consuming and error-prone. If the originally used MIDI device is unavailable or replaced (e.g. when using a different host or sharing a project), the project becomes effectively unusable.
Proposed Solution:
- Introduce a centralized MIDI routing table or alias system.
- Allow users to reassign all MIDI actions linked to a given device to a new one in a single step.
- Optionally prompt for reassignment when a project is opened and the original MIDI device is not found.
Benefits:
- Dramatically improves project portability across different setups.
- Saves time when replacing MIDI devices or migrating to new hardware.
- Makes project sharing between users or systems far more reliable.
- Avoids project breakage when devices are renamed, disconnected, or replaced.
Examples:
- A user creates a full project using an external MIDI device. Later they switch to a MIDI host, and the destination names no longer match, rendering the entire project non-functional.
- During collaboration, another user imports the project but doesn’t have the same hardware; with global remapping, they can instantly reroute all MIDI outputs.
This summary was automatically generated by ChatGPT-4 on July 24, 2025.
Original Post:
Possibility to replace MIDI destination for all actions
All actions triggering MIDI are bound to 1 MIDI device.
When +100 MIDI actions are created it's tedious to replace the destination one by one.
Example:
I made a whole project controling a MIDI device,
But the day I choose to use a MIDI host, the device isn't the same in Loopy so my whole project is unusable.
Also, it will be very useful in case of project sharing
ultracello
under review