Sweet. These will take a while to read through, but I'm sure they'll
be very helpful. Many thanks.
I've mirrored them on my server at [1], [2], [3]. I can't guarantee
they'll be up forever, but as long as they don't eat too much
bandwidth I'll leave them up.
> Would it be helpful if I calibrate the system (while saving the TDCs) then
> power cycle the xbox and dump the initialization sequence? It seems like
> that might be a first step towards understanding how you go from the 4 items
> above to the presumed CEMD data blob.
Yes, that would probably be good, although I suspect that the system
will upload the calibration blob at the end of the calibration
sequence. I won't know until I've looked through the logs, though.
Either way, it'd be good to see if it's there's some default blob
used, and whether that blob persists across device connections.
> All of the dumps linked above have a 700Hz tone in the background that's
> quiet enough to pass the background noise check. I threw that in there
> because I thought it might make it easier to make out patterns, but I'll
> take another set tomorrow without the tone. During the background noise
> check, you're expected to be as quiet as possible. During the volume check,
> the Xbox plays a sequence of stereo audio bursts. A similar set of audio
> bursts is also played during the microphone calibration. During the speech
> detection test you're asked to read a series of verbal prompts-
> "one,two,three",etc. I'll try to get a video recording of the whole process
> up sometime tomorrow, if I get the chance.
Thanks for the information!
> As you mentioned earlier, input from someone familiar with the usage of CEMD
> in the context of audio would be helpful. I can't even begin to guess what's
> in the CEMD blob. Would it be, for example, 100 complex points of the top 5
> IMFs for each channel? It'd also be helpful if an audio pro could comment
> on whether CEMD might be a red herring here- i.e. maybe CEMD stands for
> something else, maybe the blob is something like TDOA data computed from the
> audio bursts? Just a thought.
Made some small progress on interpreting the data (actually, Hector
did this himself some point back in November, but it wasn't written up
outside of IRC logs anywhere to my knowledge, so I didn't notice until
after I duplicated his work) - it's a long series of 32-bit floats
between -.5 and .5 . There are 200 blocks of size 2k bytes (512
samples) each. The second block, 22nd block, ... ( block = 2 mod 20
)th block ... all have much greater magnitude than the rest. I
converted the data to a WAV file [4] by multiplying each sample by
2**31 and flooring the integer value, then sticking a WAV header on
it. Maybe it'll help to visualize the waveforms with audacity.
Maybe I'll hear/see something similar in the logs.
> -S
-Drew
[1] - http://zarvox.org/kinect/acceptable_700hz_background_and_music_check.tdc
[2] - http://zarvox.org/kinect/microphone_calibration_700hz.tdc
[3] - http://zarvox.org/kinect/speech_detection_test.tdc
[4] - http://zarvox.org/kinect/filters.wav
