On Wed, Mar 4, 2009 at 6:03 PM, Kassen <signal.automatique_at_gmail.com> wrote:
> Alex;
>
>>
>> If other projects are interested in applying is
>> it worthwhile pooling resources and applying as the toplap mothership?
>> It'd be good to add netclock (inter-app network time sync for live
>> (coding) performance) as a possible application idea, which would run
>> across supercollider, chuck, fluxus and pd.
>
> Regardless of Google, Universities and demanding formats this sounds like a
> good idea to me.
>
> A simple, non-fidgety network clock that could be used across these and that
> wouldn't require that performances start by forming a committee dedicated to
> the design of a appropriate standard for message format, time stamping and
> heaven knows what else in a multi-page document to be implemented over the
> course of the first three days of the performance would be a great idea in
> general.
a suggestion: clocks should announce themselves over mDNS service
discovery, so softwares would find them more easily.
in fact any software supporting well-known network interfaces should
probably do that, so that interconnecting on LAN would become a matter
of browse-and-click (like selecting a DAAP share in a music player or
a network printer in a print dialog).
--
cheers,
artm
http://lab.v2.nl/
Received on Wed Mar 04 2009 - 20:09:50 GMT