History

Albi 2009¶

attendees:
Trond, Nils, Pascal, Jasch, Philippe, Tim

NOTES Tuesday: 20090120¶

test scenario albi_01:¶

device: lemur (multiball)
translator
lemur-spatDIF-creator:

device: iphone
translating layer
mrmr-spatdif-creator:

device monome:
model representingdatastrucures/sources/rooms etc.
monome to spatdif-creator:

holospat-trajectories
xml-parser/reformatter
holospat-to-spatdif-creator

|
v
spatDIF stream/file |
v
---------------------------

jamoma-SpatDIF-interpreter:
jamoma-rendering

ambiencode-spatdif-interpreter:
icst-ambitools rendering

....

spatdif interpreter
spatdif-rendering for visualisation

h.3 core descriptors: low-level

meta-discriptors:

state / stateless depending on implementation

implicit coordinate system and units

core descriptor are without extension tag

extensions are declared in header AND used in name-space

fallback policy ?

draft core descriptors:¶

position¶

definition:
Coordinate System - cartesian

/spatdif/source/1/position 0. 0. 0.

/spatdif/source/1/gain 0.

1 <spatdif>
2     <source>
3     <1>
4         <event>start 0.0</event>
5     </1>
6     </source>
7 </spatdif>

gain¶

 1 <source>
 2     <1>
 3         <position>0.0 0.0 0.0</position>
 4     </1>
 5 </source>
 6 <roommodel>
 7     !-- extension
 8 <source>
 9     <1>
10         <distance>
11             <decrease>
12                 <type>inverse proportional</type>
13             </decrease>
14         </distance>
15     </1>
16 </source>
17 <source>
18     <1>
19         <distance>
20             <decrease>
21                 <dbUnit>0.5</type>
22             </decrease>
23         </distance>
24     </1>
25 </source> 
26 </roommodel>

-> /spatdif/extension/event/source/1/start
or
-> spatdif/source/1/event/start -> spatdif/source/1/position 0.0 0.0 0.0 /source/1/media/type adc /source/1/media/inputChannel 1 /spatdif/media/source/1/inputChannel 1

encoding formula used (Furse-Malham, SN3D, N3D)

/source/1/ambi/type FMH

/source/1/type B-format

/source/1/type media

/source/1/path audiofile.wav

/spatdif/roommodel/source/1/distance/decrease/type "inverse proportional"

/spatdif/roommodel/source/1/distance/decrease/dBUnit 0.5

Flowcharts¶

NOTES Wednesday: 20090121¶

decision process: carefully calibrated

incremental steps:

don't imply standard status in the namespace

RFC - peer-review cycles:

Trond:
spatdif
object (array of objects)

alias system: higher level grouping and offering a different view of the data-set

TIME::::::
timestamp
duration
both are part of ANY data-item and if omitted are implied with the default or in a stream considered being NOW (timestamp)

thought models:

YAML

 1 spatdif:
 2 source:
 3 1:
 4 position: 0. 0. 0.
 5 duration: 1000.
 6 time: 23456
 7 2:
 8 position: 0. 0. 0.
 9 duration: 1000.
10 time: 23456
11 3:
12 position: 0. 0. 0.
13 duration: 1000.
14 time: 23456

OR:

1 spatdif:
2 source:
3 duration: 1000.
4 time: 23456
5 1:
6 position: 0. 0. 0.
7 2:
8 position: 1. 1. 1.

OSC issues;
packet contains timestamp: 23456.

osc variant 1: individual messages¶

/spatdif/source/1/position 0. 0. 0.

/spatdif/source/1/duration 1000.

osc variant 2¶

key value pairs at address

/spatdif/source/1/ position 0. 0. 0. duration 1000.

jamoma flavored OSC¶

/spatdif/source.1/position 0. 0. 0. ramp 1000.

SpatDIF

Wiki