This will walk you through how to install and troubleshoot WiFi Speakers.
Setup:
First,
download the server. Install the server on your Windows media PC.
After installation, download and install the Android client from
Google Play on your android device.
Start the WiFi speakers app on your android device. Start the server application on your Windows media PC.
Connecting:
Within the WiFi Speaker Android application there should be a search button. Click this button to auto-find servers
on your local network. If none are listed at first, try again after about 10 seconds. A list should display your
server's IP address. Select the server in this list, then press the connect button. The Android device is now connected
to the server.
Decreasing Latency:
4 things affect latency; server buffering, client buffering, audio format, and audio compression.
Try adjusting the app's buffer time first. This will increase the likely hood of breaks in audio, but will reduce latency. If you are running locally you will probably
be able to set this to zero.
Next adjust the server's buffer time. You'll find this option in the server's settings under the Audio section. Lastly, select a smaller audio format.
This will reduce the size of the audio being sent.
If you have the pay version of the WiFi Speaker app, enabling audio compression will further reduce audio size.
Crashing or bugs? Other questions?
Please
contact the developer. Bugs will be fixed quickly, and all feedback is welcome!
Can't connect?
If the Android device fails to connect to the server, please ensure the server's firewall allows TCP connections on the server's
port. The server's default port is 57005, but this can be changed in the server's settings.
No Audio?
If there is no audio playing from the Android device, please check the Android device's media volume. Next,
check your server's volume. Lastly, check that the device you wish to capture from is selected, and that the
server's graphic equalizer is displaying activity. If all these options check out, try shutting down the app and server,
and starting again. If this continues to be an issue, please contact the developer.