rc-web@42:
rc-web@42:

Performance Instructions:

rc-web@42: rc-web@42:

Each group/musician should point their browsers to:

rc-web@42: rc-web@42: http://nodescore.kiben.net:8889/1.html
rc-web@42: http://nodescore.kiben.net:8889/2.html
rc-web@42: http://nodescore.kiben.net:8889/3.html
rc-web@42: http://nodescore.kiben.net:8889/4.html
rc-web@42: http://nodescore.kiben.net:8889/5.html
rc-web@42: rc-web@42:

where they can login into the server by entering their name and pressing enter at the "Login:" prompt

rc-web@42: rc-web@42:

The conductor/director should load this page:
rc-web@42: http://nodescore.kiben.net:8889/admin.html
rc-web@42: where she is automatically logged in as "admin"

rc-web@42: rc-web@42:

The login status of musicans can be monitored in the header of the embedded chat client.

rc-web@42:

Once everyone has logged in the director can begin the timer and commence sending instructions to the musicians using the button panel above.

rc-web@42: rc-web@42:

rc-web@42: There is a networked client server stopwatch system here which is optimised for mobile devices, might be a usefull generic tool for networked performances. rc-web@42:
rc-web@42: rc-web@42: Server : http://nodescore.kiben.net:8889/nsws.html
rc-web@42: Client : http://nodescore.kiben.net:8889/nswc.html
rc-web@42: rc-web@42: There is one control stopwatch (server) and can be as many client you rc-web@42: please, the clients will all lock on to the time broadcast from the rc-web@42: central server instance and there will be no drift between them all. rc-web@42:

rc-web@42: rc-web@42: