Changes between Initial Version and Version 1 of OscProtocol


Ignore:
Timestamp:
08/02/2010 03:23:09 PM (10 years ago)
Author:
shahn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OscProtocol

    v1 v1  
     1There is a version of the protocol here: [http://fourierscratching.open-projects.net/code/Loops/protokoll.txt], but I suggest, we work on it on this page. So I'll start by writing down what works (or should work). This table should be updated, once Loops supports the respective messages. Proposals for future enhancements are further below. 
     2 
     3|| '''OSC-path'''    || '''signature''' || '''argument description'''           || '''description''' || 
     4|| '''SC -> Loops''' || || || || 
     5|| /fsloops/register || s{s}*           || (!ClientName, Sonifikationsmethoden) ||     Handshake     || 
     6|| /fsloops/reconnect || s     ||    (!ClientName)  || Handshake ohne resetting || 
     7|| /fsloops/gamecontroller/scalar/selectNext || || || selects the next scalar || 
     8|| /fsloops/gamecontroller/scalar/selectPrevious || || || selects the previous scalar || 
     9|| /fsloops/gamecontroller/scalar/manipulateX || f || value || sets the real part of the selected scalar || 
     10|| /fsloops/gamecontroller/scalar/manipulateY || f || value || sets the imaginary part of the selected scalar || 
     11|| /fsloops/gamecontroller/loop/selectNext || || || selects the next loop || 
     12|| /fsloops/gamecontroller/loop/selectPrevious || || || selects the previous scalar || 
     13|| '''Loops -> SC (deprecated)''' || || || || 
     14|| /fsloops/reset || || || Loescht alle Loops und mutet instantan || 
     15|| /fsloops/updateLoop || s{ff}* || (!LoopName, abwechselnd magnitude und phase) || Legt eine neue Loop an || 
     16|| /fsloops/muteOn     || ss || (!LoopName, Sonifikationsmethode) || || 
     17|| /fsloops/muteOff    || ss || (!LoopName, Sonifikationsmethode) || || 
     18|| /fsloops/onSet      || si || (!LoopName, !SkalarIndex ab 0) || || 
     19|| /fsloops/offSet     || si || (!LoopName, !SkalarIndex ab 0) || || 
     20 
     21The messages that are sent from Loops to !SuperCollider are all deprecated, because Loops is going to be a perfect slave. We don't even need a message to acknoledge receiving, because we are using tcp. 
     22 
     23== Future Changes == 
     24 
     25=== Remove name of sonifications === 
     26 
     27Loops doesn't need to know these. 
     28 
     29|| '''OSC-path'''    || '''signature''' || '''argument description'''           || '''description''' || 
     30|| /fsloops/register || s               || (!ClientName)                        || Handshake         || 
     31 
     32=== Remove deprecated messages from Loops to SC === 
     33 
     34Yes. Loops should be totally silent. 
     35 
     36=== Allow creation of Loops from SC === 
     37 
     38Well, yeah, that's probably the most basic thing we need. Here's a proposal: 
     39 
     40|| /fsloops/loops/add   || s   || !LoopName || Adds a new empty Loop || 
     41|| /fsloops/scalars/add || sff || (!LoopName, magnitude, phase) || Adds a scalar || 
     42 
     43Another option is this: 
     44 
     45|| /fsloops/loops/update || s{ff}* || (!LoopName, magnitude and phase, alternating) || If a Loop by that name does not exist, a new one will be created. The scalars will be reset. If a pre-existing Loop contained more Scalars than are transmitted during an update, they will be removed from the Loop. || 
     46 
     47I would prefer the second option. Martin? 
     48 
     49=== Look at this ticket === 
     50 
     51http://fourierscratching.open-projects.net/ticket/1 
     52 
     53=== Tidy up gamecontroller messages === 
     54 
     55The protocol does not need to reflect that a modification is triggered by a gamecontroller (this is probably misused already anyway ;). So we need similar messages to manipulate single scalars that are a bit cleaner. 
     56 
     57 
     58 
     59