Reddit
https://www.reddit.com/r/line6/comments/1vixssl/comment/p5rri0y/?context=1&screen_view_count=2&ext-referrer=DIRECT
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.
Reddit
https://www.reddit.com/r/line6/comments/1vixssl/comment/p5rri0y/?context=1&screen_view_count=2&ext-referrer=DIRECT
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
Issues include
Reverting to legacy mode fixes the issue for customers.
These devices use their own combined audio/midi driver.