Folks, I just put up this new site. It is WordPress and chosen because it is responsive design, accessible from anywhere and simply mega easy to style, modify and maintain. Expect to see more details as I add all sorts of techno babble, skills and projects on the site.
For the moment I am a consultant who works remotely. I have strong expertise in audio signal processing, compression standards, in particular ISO/IEC MPEG, as well as ITU G.7xx speech codecs. I also am an optimization expert and live to write cryptic assembly that I actually comment so one can follow along at home. C is my best language with my Kernighan and Ritchie still with me in tatters. I do have many other languages, including the antiquated Fortran and the obligatory C++.
I have a strong hardware background and have implemented projects on all sorts of embedded architectures. Yes, I do run a popular economics site, based in Drupal 7.x, where I did all of the coding modifications. The site currently resides on a CentOS 6.x, unmanaged VPS that I configured and maintain.
I build my own systems too. They will have to pry my Wiha T4 Torx from my cold dead hands, I am that geeky.
Other skills will be added to the site and overall I’m out to be more chatty. I am a notorious lurker who posts little, yet knows a lot. We’re out to change that.
Cisco just did a solid and released H.264 into open source for use in WebRTC. Cisco is absorbing the estimated $13 million in licensing fees from MPEG-LA. The reason Cisco did this was to avoid transcoding of H.264 streams from other video clients, a wise choice. The IETF is determining which video compression algorithm will be the baseline for webRTC this week.
Mozilla will incorporate webRTC, including H.264, into the Firefox browser and Chrome already has it. Google is sticking with VP8 and is a major developer and contributor to webRTC. The IETF vote is in Atlanta this week and we’ll update this post with who won out in the video codec selection. We hope both are supported, yet Cisco is right, the last thing one wants to be doing in a real time stream is transcoding H.264 to VP8. It does seem that stand alone proprietary video conferencing and streaming solutions are going the way of the dinosaur, although webRTC as the meteor which killed the beast is yet to be determined.
It appears at the IETF meeting there was no consensus on which video compression algorithm to make mandatory for webRTC. It also appears both is not an option, so far and Nexus has hardware implementations of VP8 while hardware acceleration for H.264 is available in many chipsets.
On a technical note, I am downloading the source for webRTC, focus on Opus, (Xiph), since supposedly it is not ported, never mind optimized, on many embedded platforms. I’ll write up what I find in another post.