Albi 2009

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

NOTES Tuesday: 20090120

test scenario albi_01:

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

or

device: iphone
translating layer
mrmr-spatdif-creator:

or

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

or

ambiencode-spatdif-interpreter:
icst-ambitools rendering

or

....

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.
<spatdif>
    <source>
    <1>
        <event>start 0.0</event>
    </1>
    </source>
</spatdif>

gain

<source>
    <1>
        <position>0.0 0.0 0.0</position>
    </1>
</source>
<roommodel>
    !-- extension
<source>
    <1>
        <distance>
            <decrease>
                <type>inverse proportional</type>
            </decrease>
        </distance>
    </1>
</source>
<source>
    <1>
        <distance>
            <decrease>
                <dbUnit>0.5</type>
            </decrease>
        </distance>
    </1>
</source> 
</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

spatdif:
source:
1:
position: 0. 0. 0.
duration: 1000.
time: 23456
2:
position: 0. 0. 0.
duration: 1000.
time: 23456
3:
position: 0. 0. 0.
duration: 1000.
time: 23456

OR:
spatdif:
source:
duration: 1000.
time: 23456
1:
position: 0. 0. 0.
2:
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.

Flowcharts 2