Hi everyone, and thanks to anybody.
I have decent IT-Background. Sorry, I didn’t say before.
Fortunatly I just found the solution to my issue and wanted to document it here in case someone else encounters the same problem.
The Issue:
If you’re using a Remote Desktop Protocol (RDP) session to connect to a Windows 10 system running Gig Performer 5, the application might not detect any MIDI devices—even though they appear correctly in the Device Manager and work fine in other applications.
The Fix (in my case):
- Adjust RDP Audio Settings
In your RDP connection settings, set the audio playback option to either:
- “Play sound on this computer” (host), or
- "Do not play sound."Any other setting (e.g., “Play on remote computer”) causes Gig Performer 5 to fail to detect MIDI devices.
- Restart the Host Machine
- After making this change, restart the host system.
- Without a restart, I experienced persistent artifacts from previous RDP sessions (e.g., using the iPadOS Microsoft RDP app) that continued to block MIDI detection on the host system even after making the required changes to the configuration.
Additional Notes:
This behavior seems unique to Gig Performer 5. In may case I had the chance to check differnt applications (like Cantabile) which worked fine with any RDP audio playback settings. Gig Performer 5 likely handles interface access differently, which (in my case) leads to this issue.
If you previously relied on remote audio playback (e.g., to hear system sounds (host) on your remote Apple iPad), you’ll properbly need an alternative workaround for this, as the above changes disable this functionality.
I hope this helps anyone facing similar challenges!
Cheers