More about the Chrome HTML Video Codec Change (The Chromium Blog)
Posted Jan 17, 2011 11:36 UTC (Mon) by krake
In reply to: More about the Chrome HTML Video Codec Change (The Chromium Blog)
Parent article: More about the Chrome HTML Video Codec Change (The Chromium Blog)
Not for my purposes, no. The higher it stays in the stack the better it is for all of us.
My line of thinking is that decryption in the output hardware does not require any special kind of software in the operating system or higher up, making content accessible even by users of alternative operating systems, media players and browsers.
If done higher up we end up with crap like Microsoft's "secure media path".
...trying then to convince people that they should drop 300 dollars on non-existent hardware...
I didn't get that part.
My understanding is that very specific data processing, e.g. media decoding, is first implemented in software to be easily deployable to the mass market even if it more efficient to be implemented in hardware.
So after a pure software base period there is a transitional period where hardware implementation become common. Some customers might even prefer a hardware based solution and buy devices offering such in favor over ones with host software based solutions.
But I could be mistaken and deployment of host software based solution is always delayed until a significant portion of the market has hardware based solutions available as well.
My personal impression was that it doesn't work that way though.
to post comments)