Symptom: The audio engine service is started and appears to be running, but client applications are unable to communicate with the audio engine.
Reviewing the application client event log indicates that the audio engine service is running. The client communications software, aeRemote.dll, loads OK according to the XStudio Voice Tracker event log, but when a connection attempt is made, the attempt times out after trying 10 or more times.
Solution 1 - TCP/IP Port Check
XStudio Voice Tracker communicates with the audio engine using TCP/IP on port 12042. Another application may have control of this port or a firewall may be preventing communications on the port. You may have to consult with your LAN administrator to determine if either of these possibilities are the case.
Solution 2 - apt-X Encoder Check
Check to see if the apt-X encoder is installed with the audio engine. If apt-X is installed, check to see if the apt-X temporary time period has expired. It can be checked one of two ways:
1.Use the apt-X Registration Utility included in audio engine installations - the file name is aptX_RegDlg.exe.
2.Stop the audio engine service and launch the audio engine from a command window. See the topic on running the audio engine in console mode for instructions.
If an expired apt-X trial license is the issue, the apt-X registration dialog will appear using either of the two methods. Correct the problem by registering the software or removing it.
Solution 3 - Host PC Name Check
Check the client application's host PC name. If the computer name is longer than 15 characters, it is unlikely a connection can be made. To test, shorten the computer name to 15 characters or less. This problem occurs because of Microsoft's maximum computer name length of 15 characters for NetBios naming compatibility. It is why users are warned when they try to create a computer name longer than this limitation.
