If you're experiencing MIDI mapping issues in SoundSwitch while using a Windows operating system, you're not alone. Windows does not natively support multi-client MIDI connections as Mac OS does. Here are some essential points and solutions to clarify the situation and help you address your MIDI-related challenges:
1. Multi-Client MIDI Access:
- Windows lacks native support for multi-client MIDI connections, which can make MIDI setup more complex compared to Mac OS.
- Some older drivers may not support multi-client access, but newer driver updates from your DJ hardware might offer improved compatibility. Check for updated drivers to see if multi-client access is now supported.
2. Sharing MIDI Devices:
- It is possible to share the same MIDI device between different software applications if the device's driver supports it. However, this varies depending on the controller and its driver.
- For example, if you have a controller with MIDI functions mapped in Serato and you also want to map functions in SoundSwitch, the outcome depends on your controller's driver. You can check the driver specifications or experiment to see if it works as expected.
3. Using Separate MIDI Devices:
- If your DJ hardware's driver does not support multi-client access, an alternative solution is to acquire a separate MIDI device. You can map your SoundSwitch controls to this dedicated device.
- While this approach keeps your audio and lighting controls separate, it may limit some dynamic control options that you could achieve by mapping everything to the same MIDI device..
If you encounter any MIDI-related issues on Windows that aren't addressed here, don't hesitate to reach out to our support team at support@soundswitch.com