[BUG] Line 6 products (various models) work with UMP-aware tools, but not with MIDI 1 tools
@Psychlist1972 is already working on this.
Since Aug 25, 2026.
- Dominant language
- C++
- Stars
- 679
- Forks
- 72
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 59
Description
Thank you Pete. On my system the Spider V is shown in the device manager under "Sound, video and game controllers". And even the audio drivers work.
The Spider V midi ports are shown in the new midi tools and I can monitor them with the new cli tool. When I start the Line 6 Spider Remote application, the monitor shows a sysex-message that is sent to the amp repeatedly, and the application hangs about 1 minute, then opens and says no amp connected.
Switching to legacy API-Mode (1) fixed this for me, the amp gets detected by the application immediately.
Discord
https://ptb.discord.com/channels/980245825202552942/1539035628111528017
It's not clear where the error is, or what the error is. The data flows through the service just fine, and the client-side callback events fire showing that the message data is transferred. It's exceedingly strange that only these devices are affected.
Devices include
- Line 6 Helix
- Line 6 Spider
Issues include
- MIDI 1.0 data not received by client apps
- Line 6 management apps do not detect the devices
Reverting to legacy mode fixes the issue for customers.
These devices use their own combined audio/midi driver.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.