What’s HappeningAnother application is probably using the port that ControlRoom would typically use. Solution (Windows)Shut down all of your ControlRoom components and your DAW. Shut down Command Prompt and Task Manager if they are open as well. Reopen your ControlRoom components. Reopen your DAW and add a Channel Plugin to a track. Not sure how? See instructions for doing so with Ableton here and instructions for doing so with ProTools here. Open your Command Prompt and enter, “netstat -a -n -o”.
Info |
---|
Wondering what’s happening here? We are using the Command Prompt, which is a program that allows us to give our computer specific orders, to show us which programs are using which ports. | Image Added3. Look at the column, “Local Address,” within the Command Prompt window. Find the row that says, “0.0.0.0:7000,” the row that says, “0.0.0.0:7001,” and that row that says, “0.0.0.0:7002.” Find the PID column (it should be on the far right) and note the PID value given for each of the rows. Image Removed4. Open your Task Manager and find which Tasks correspond to which PIDs in the task manager. Note |
---|
Can’t find the PID within the task manager? Note how the user in GIF below opens the PID column by right-clicking on the label row within the Task Manager. |
5. Shut down those Tasks unless they are ControlRoom Hub, ControlRoom VR, or your DAW. 6. If you had to shut down non-ControlRoom tasks in step six, restart your ControlRoom apps and your DAW, and try connecting again. |