Now, as display resolutions go up and people are pumping more pixels through the video stream, there's going to be an upper limit on how well the existing codecs work in software as well. The vast majority of those problems are resolved with some basic advice ( ), but if you're a content provider that doesn't want that support headache, the software-only approach is understandably attractive. Because leveraging hardware inherently depends on more things going correctly (like the user applying updates to the machine after they unboxed it back in 2003), there's always going to be a small, but non-zero baseline of GPU-related headache. #Adobe flash player 64 bits wimdows 10 driversIn that instance, we hand everything off to the hardware, at which point we're totally dependent on the drivers and silicon to do the processing.Īt Flash Player scale (current rough estimates are ~2.5 billion desktops, or 98% of internet connected computers), you're dealing with the messiness of the real world. Universal compatibility, where everything is in our sphere of control and done in software ( at the expense of battery life and/or performance), or we can go for speed. So content providers ultimately have a choice. It's been a few years, and now both Flash and the browser are both leveraging hardware acceleration, and more and more, decisions about blacklisting hardware are happening at the browser level. You *have* to have hardware acceleration on those devices. The big initial motivation for hardware acceleration was the netbook market, which at the time, was targeting really low-end CPUs (for price point and power consumption) that couldn't do native H.264 video decoding in software with any reasonable kind of performance. #Adobe flash player 64 bits wimdows 10 driverWhether people pick up the driver updates (particularly on trailing-edge systems) is a whole other problem, so there's always this baseline of problem hardware in the mix. We worked closely with most of the major manufacturers to report issues over the years, and by and large, they've issued updates to resolve them. Since Flash rolls out to 98% of the internet, including machines from the 90's running WinXP SP2, we exposed a large number of latent issues in existing hardware. The issue isn't StageVideo itself, it's the state of drivers and hardware in the market. #Adobe flash player 64 bits wimdows 10 fullEven when the full HTML 5 player is released, a number of older browsers will still have to use the Flash due to a lack of HTML 5 support, and supporting that group of viewers will remain important." We understand that both the Adobe and Chrome teams have made substantial improvements since that time, and are interested in trying to move toward StageVideo again. Communication with other organizations that had tried (and then avoided) StageVideo made it clear these issues were not isolated, and a followup discussion with the Chrome team reinforced that position. The flash/driver incompatibility issues uncovered were extensive, and we had to roll it back due to a non-negligible percentage of viewers in the test group who could no longer watch video due to frame flickering. "We pushed out a A/B test with StageVideo around a year and a half ago. What Twitch staff member had to say on this topic
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |