AIR

[Rufus McDufus]

There is lots of very clever stuff posted around this forum by people able to interrogate what AIR is actually doing, in terms of rates of data packets and similar. One thing I wondered is that is it possible to go direct, and actually look at the AIR programme itself. Presumably anyone who could understand the programme would then be able to ascertain exactly what AIR is doing. I am not an expert on this subject, maybe it is just unintelligible machine code or something? However, it would be nice no know, it would help solve some of the debates over asynchronous clocking, if dedicated steamers can out perform PC's and so on.

Any ideas anyone?

If we had the source code, it would be easy! It's compiled down and humanly unreadable, though it is possible to search for character strings using a command like "strings" but this really doesn't help.
I submitted a bug report for a particular bug a few days ago actually and ran AIR through a debugger to figure the hex address of the access violation It would've been easier if I had the symbol table for AIR but even this is of course protected proeprty of Devialet.