This article contains technical information that may help support personnel and advanced users diagnose problems with the loopcloud plugin connection. If you are not familiar with the terms and tools discussed in this article and have problems getting the loopcloud application to connect to the plugin please contact support. Or find someone you know who is familiar with using the command line to help you.
Problems with this connection are rare but have included:
Loopcloud connects to the loopcloud plugin using a TCP connection to localhost on port 19282*
- The hostname localhost not being properly defined (possibly because of risky modifications to the hosts file)
- Security software (firewalls) blocking the connection
- The plugin is not loaded
- Loopcloud App will need to make connections to localhost on port 19282
- The Loopcloud plugin (which runs inside your DAW) will need to allow inbound connections from localhost on port 19282.
If you are reporting a problem with the Loopcloud Connect button operation to support it would be useful to have information and screenshot sfrom all your internet security software and firewall settings. This includes the OS firewall as well as products such as ZoneAlarm, Little Snitch and other network security utilities.
You can check that the plugin is running using netstat -na. On OSX and Windows you can run netstat -na from the command line. The output should include this line starting tcp4.
tcp4 0 0 *.19282 *.* LISTEN
Testing with Telnet - MacOS
Furthermore on MacOS you can use telnet localhost 19282 from the Terminal command line to check that a connection can be made to the plugin.
The output should look like this:
$ telnet localhost 19282
telnet: connect to address ::1: Connection refused
Connected to localhost.
Escape character is '^]'.
,���serverStatecomputerNamsnoopypluginHostDescriptionAbleton Livetempo `@sampleRate���@canPlayNow,���serverStatecomputerNamsnoopypluginHostDescriptionAbleton Livetempo `@sampleRate ���@canPlayNow^]
Testing with Telnet - Windows
Windows does not include the telnet client in a default installation.
To add the telnet client:
- Click Start > Control Panel.
- Click Programs and Features.
- Click Turn Windows features on or off.
- In the Windows Features dialog box, check the Telnet Client check box.
- Click OK. The system installs the appropriate files. This will take a few seconds to a minute.
Then proceed to use telnet localhost 19282 from the command line*. The output should look similar to the MacOS example above.
* Open the command line by pressing Windows-R and in the Run... dialog that appears enter CMD and press enter. Then type telnet localhost 19282 into the command line.
Understanding the resultsIf netstat does not show port 19282 in LISTEN mode then the plugin may not be running or has had a serious problem starting up.
If netstat does show the port is in LISTEN state but telnet does not work the problem lies with security software or (rarely) the hosts file.
* NB. In beta versions 1.5.x and later Loopcloud plugin connects back to the application on tcp port 19280, and in these version the plugin will automatically connect when both it and the Loopcloud app are opened.