<div class="readme">
<h2>Performance Instructions:</h2>
<p>Each group/musician should point their browsers to:<br/></p>
<a href="http://nodescore.kiben.net:8889/1.html">http://nodescore.kiben.net:8889/1.html</a> <br/>
<a href="http://nodescore.kiben.net:8889/2.html">http://nodescore.kiben.net:8889/2.html</a> <br/>
<a href="http://nodescore.kiben.net:8889/3.html">http://nodescore.kiben.net:8889/3.html</a> <br/>
<a href="http://nodescore.kiben.net:8889/4.html">http://nodescore.kiben.net:8889/4.html</a> <br/>
<a href="http://nodescore.kiben.net:8889/5.html">http://nodescore.kiben.net:8889/5.html</a> <br/>
<p>where they can login into the server by entering their name and pressing enter at the "Login:" prompt </p>
<p>The conductor/director should load this page:<br/>
<a href="http://nodescore.kiben.net:8889/admin.html">http://nodescore.kiben.net:8889/admin.html</a> <br/>
where she is automatically logged in as "admin" <br/></p>
<p>The login status of musicans can be monitored in the header of the embedded chat client.</p>
<p> Once everyone has logged in the director can begin the timer and commence sending instructions to the musicians using the button panel above.</p>
<p>
There is a networked client server stopwatch system here which is optimised for mobile devices, might be a usefull generic tool for networked performances.
<br/>
Server : <a href="http://nodescore.kiben.net:8889/nsws.html">http://nodescore.kiben.net:8889/nsws.html</a> <br/>
Client : <a href="http://nodescore.kiben.net:8889/nswc.html">http://nodescore.kiben.net:8889/nswc.html</a> <br/>
There is one control stopwatch (server) and can be as many client you
please, the clients will all lock on to the time broadcast from the
central server instance and there will be no drift between them all.
</p>
</div>
e22c5abe6a