Troubleshooting; Software Won't Start Up; Can't Connect To The Opsix - Korg opsix Owner's Manual

Troubleshooting

Software won't start up

Make sure that your computer meets the operating requirements
See "Operating requirements" on page 1.
Check whether other applications might be running
If other applications are running, it is possible that they might somehow interfere with the opsix Sound Librarian. As
a troubleshooting step, quit the other applications.

Can't connect to the opsix

Make sure that the opsix is connected via USB
The Sound Librarian requires USB and cannot communicate with the opsix over 5-pin DIN MIDI.
If you are using a USB Hub, try connecting the opsix directly to your computer
A usb hub might interfere with the connection.
Try a different USB cable
A faulty cable might interfere with the connection.
Confirm that the opsix is running software version 1.0.1 or later
To check the software version number, restart the opsix.
Make sure that the opsix has been detected by the connected computer
Windows 7/8.1/10: open the Device Manager (see the instructions for
page 3) and check the "Other Devices" tab. If the opsix does not appear, repeat the RNDIS configuration procedure.
Mac OS: open the System Preferences application, in the Applications folder. Go to the Network panel and check the
list of networks and network devices on the left of the window.
Make sure that the required network ports are not blocked by a software firewall
When communicating with the opsix over USB, the Sound Librarian uses TCP ports 50000 and 50001, and Bonjour
uses UDP port 5353. These won't be affected by an external firewall in a separate server or router, but can be
blocked by a software firewall running on the same computer.
Disable VPN software
In some cases, VPN software may interfere with communication to the opsix.
Confirm that you have the latest version of the Sound Librarian
You can download the latest version from the Korg website (http://www.korg.com/ ).
Try restarting your computer
In some cases, the opsix may not be immediately recognized after installation. If this occurs, simply restart your
computer.
Troubleshooting
12
RNDIS configuration under "Windows" on