Mercurial > hg > nodescore

comparison www/about/index.html @ 42:49c94f63b8b0

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
css for nexus 7 and associated files- archive m.a added - remove later
author tzara <rc-web@kiben.net>
date Tue, 04 Sep 2012 07:25:49 +0000
parents
children
comparison
equal deleted inserted replaced
41:56767c69b7c4 42:49c94f63b8b0
1
2 <!DOCTYPE html>
3 <html>
4 <head>
5 <link href="about/style.css" rel="stylesheet">
6 </head>
7
8 <body>
9 <div id="title"><h1>NodeScore</h1> </div><br/>
10
11 <img src="about/chromiumlogo.png" width="30" height="30"/>
12 <img src="about/nodejs-dark.png" height="30"/>
13 <img src="about/ECMAScript.png" height="30"/>
14
15 <br/><br/>
16
17 <div class="readme">
18
19 <h2>What is NodeScore?</h2> NodeScore is a framework to facilitate
20 networked telematic ensemble performance. As a framework it uses the
21 "screen score" as its paradigm. While it could be used to syncronise
22 any type of telematic event/performance in this context it is aimed at
23 the musical performance.
24
25 <p> The goal of the NodeScore framework is to allow performers
26 who are connected to a network via a computer/tablet/mobile device to
27 syncronise to a master clock and recieve instructions, in
28 realtime,from a central "conductor/director" as well as being able to
29 communicate with one another.
30 </p>
31 <p>As performers may be geographically dispersed the technical setup
32 needs to be trivial, this is why NodeScore uses the Internet browser
33 as it is a cross-platform, standards compliant
34 environment that will run on anycomputer without complex setup and
35 installation process. All that the performers involved in a NodeScore
36 performance need to do is open a browser such as Google's Chrome and
37 point it to the address of the NodeScore server, login and await
38 instructions that shall be displayed in the browsers window.
39 </p>
40 <p>The nature of these instuctions is the left to the composer, the
41 only prerequisite when composing for the NodeScore framework is that
42 the instructions are formatted in HTML5. This allows for the
43 incorporation of a wide range of rich media content such as images,
44 video, sound and animated SVG as well as simple plain text
45 instructions. Any medium that can be displayed in an internet web
46 browser maybe used in a NodeScore composition.
47
48 Other features include a shared, embedded network stopwatch and a
49 live-chat window to facilitate syncronisation and communication
50 between partisipants in the performance.</p>
51 <h2>How does NodeScore work?</h2> The control interface for
52 NodeScore is a webpage displayed in an internet web browser, from this
53 control page the "conductor/director" can issue the precomposed, HTML5
54 formated, compositional instructions. These instrutions can be
55 deployed to the ensemble as a whole or targeted at specific
56 perfomers. Once the instruction is deployed by the director it is
57 instantly presented in the web browser of the performer/s.
58
59 <p>In a NodeScore performance the conductor/director also becomes
60 active in the compositional process as he she decides who plays what
61 material when. In this way NodeScore can be seen as an evolution of
62 methods used by composers from Lutoslawski (Jeux vénitiens to Zorn
63 ("Cobra") amongst others, where musicians are given cues chosen by the
64 director indicating certian prearranged stratagies. NodeScore however
65 alows much more complex media to be incorporated in the instructions
66 as well as facilitating networked telematic performances in this
67 style.
68 </p>
69
70 <h2>How is this achived technically?</h2> NodeScore uses realtime web
71 technologies including the node.js server software allowing serverside
72 javascript as well as websockets. "Websockets" allows the server to
73 push content to the clients without them requesting it first as is
74 traditionally the case. <p>This has been possible in the past through a
75 technique called "longpolling", though this was quite inefficient
76 compatered to websockets which allow a persistant live connection
77 between server and client. Through this connection the server can push
78 content to the client in realtime for instant displayed in their
79 browser.</p>
80
81 <h2>Code</h2>
82
83 <a href="https://gitorious.org/nodescore">https://gitorious.org/nodescore</a>
84
85
86 <h2>Browser Compatability:</h2> This project uses some bleeding
87 edge network technologies his means it will not currently work in all
88 browsers, some versions of Firefox have disabled websockets for
89 security reasons, also different browsers deal with CSS scaling in
90 different ways for example. Recent versions of Chromium, Google Chrome or
91 Firefox are recomended.
92
93 </div>
94
95 <br/>
96
97
98 <br/>
99 <script type="text/javascript" src="about/footer.js"> </script>
100
101 </body>
102
103 </html>