Improve time-to-first-synchronization (TTFS)

[schollz]

This is a test to see how long it takes to synchronize when the clients are attached and a new song is selected, after the song has been loaded. A TTFS of 0 seconds means that the synchronization with the browser and server occurred perfectly, and they both started playing at the same time.

Currently (12/18/2015):

Server	Raspberry Pi client	Desktop client
Raspberry Pi	~14 s	~6 s
Desktop	~10 s	0 s

Issues that may affect the TTFS:

• Whether an accurate half-latency is calculated. These are calculated by an initial 15 polls to the server to get the server-client fly time. These are always used to adjust the true seek time, so if they are off, it could be problematic. If your music file is huge, or if the computer has problems uploading, then it will take awhile to satisfy multiple clients. This could easily over-inflate the half-latencies as one client may see very long delays.

[schollz]

Improved using a running time difference:

Server	Raspberry Pi client	Desktop client
Raspberry Pi	4-10 s	0-6 s
Desktop	4-10 s	0-3 s