Hello,
I am jumping in to start some threads and contribute to issues. At present I am unable to contribute to the code repository directly until I receive appropriate clearance through my main employer. There should not be any issue, though it can take time. Until then, this note is on file to set scope of involvement and anticipated contributions.
In my role at Dolby I am responsible for scouting and assessing new possibilities of technology and business models. Over the last four years, a key theme has been on connected audio devices. I lead a technical team setting out some of the more longer term aspects, implications, designs, performance, possibilities and user experiences. This is within the Technology Incubation Group led by Mike Hollier.
There is a clear future where audio devices will be present and need to be co-ordinated at a scale beyond human intervention - imaging 60 billion microphones to choose from in routing audio with appropriate security and privacy. There are deep adjacent threads in my team on what this means for society, ethics, privacy and the implications of the post privacy audio world already upon us. My involvement with Ockam is exploratory around the possibility of a secure distributed approach that can scale and offer what is needed in addition to any audio processing in the realm of DUAD (distributed uncertain and asynchronous audio devices).
At this stage, some notes and scope limiting of my contribution
- Contribution to issues and comments only, with inline example code but no code contribution to the main repository
- Expressed opinions are personal and rising from personal technology experience and perspective
- The interest of Dolby is associative through myself, but not direct or indicative of any business relationship at this stage
Looking forward to the release and response to the great work and ideas in the API!
Glenn Dickins
Principal Architect of Convergence, Dolby
Honorary Professor, Australian National University
http:.//www.dickins.com