Wonder if Linux video drivers have added the ability to retrieve the decoded video data in the two and a half years since this blog post was made.
Solving Different Problems
11–20 of 50 posts
Re: Solving Different Problems
#12> it has to convert YUV data to the RGB colorspace and combine the image with other Flash elements. The screen has red, green and blue pixels, either way a video is played, the colours have to be converted into RGB.
not every video frame is encoded in RGB. actually, very few transports use that. the in-memory layout of a YUV-encoded frame is different than the one of a RGB one. it needs conversion, which implies an intermediate copy, as well as traversing a buffer that can go up to 1080 rows. most video players (and Flash on Windows and MacOS), these days, use shaders and multi-texturing to do that conversion on the GPU; it remo…
Why don't they encode the elements to YUV once, and then flip to YUV (so not needing to convert each time), as opposed to converting the video to RGB?
Re: Solving Different Problems
#13Wow. A tip to anyone reading this: if you ever find yourself explaining away poor—nay, pathological—performance with anything other than ‘we made some mistakes in the past and we’re doing what we can to correct them’, please take a good hard look at yourself and consider exiting the software industry. That’s all I have to say. Edit: that wasn’t all I had to say. > What about Mac? I’m not sure but my Mac colleagues ha…
Doubly so if your product crashes even half as often as Flash. That they cannot seem to code for stability doesn't give me any confidence in their ability to code for speed.
I heard that they refused to work with Apple to improve its performance on Mac, and that was a core reason why they got excluded from the iOS platform -- searching for this I came up with an explanation directly from Apple:
"Symantec recently highlighted Flash for having one of the worst security records in 2009. We also know first hand that Flash is the number one reason Macs crash. We have been working with Adobe to fix these problems, but they have persisted for several years now. We don’t want to reduce the reliability and security of our iPhones, iPods and iPads by adding Flash."
Re: Solving Different Problems
#14While watching streams of Olympia in both HTML5 (on Chrome) and Flash i found HTML5 to take nearly twice as much CPU then Flash. Might be due to the implementation of the sites (german broadcasters ard & zdf) but flash works pretty awesome for me.
Besides that it's a shame that the option to just get the stream running in VLC is such a hassle (with VLC I get much lower CPU usage + the ability to freely move and resize the video and place it somewhere on my second screen, even fullscreen)
Re: Solving Different Problems
#15Wow. A tip to anyone reading this: if you ever find yourself explaining away poor—nay, pathological—performance with anything other than ‘we made some mistakes in the past and we’re doing what we can to correct them’, please take a good hard look at yourself and consider exiting the software industry. That’s all I have to say. Edit: that wasn’t all I had to say. > What about Mac? I’m not sure but my Mac colleagues ha…
> What about Mac?
This is a two and a half year old blog post. Mac hardware video decoding is supported now.
Re: Solving Different Problems
#16This is a blog post from January 2010. I think a lot of the details are out of date. (Mac hardware decoding support, for example.)
Re: Solving Different Problems
#17I don't know if the explanation is accurate or just their own product defense, however (long) after playing a video (and not something else in flash), I usually go into top and kill the Chrome flash process manually as it's a) taking an insane amount of memory b) taking a lot of CPU for no reason (I'm not watching the video anymore and closed the page). Seems there is a ton of leakage going on after playing a video. So even though the story might to explain the actual playing of the video, it doesn't explain the molestation of my i7/8gb/ssd machine AFTER I closed (the only) Flash window. Not to mention the crashes.
Re: Solving Different Problems
#18The message that I take is that some companies use Flash as the wrong tool to solve a problem which I'm not interested in. I want to see videos with minimum overhead. I don't want to be bothered with ads, poor performance, poor user interfaces, poor security, ... all which I get through Flash.
Re: Solving Different Problems
#19This is an extremely outdated article which was posted before they added "StageVideo", an API that fixes this problem 100%.
Re: Solving Different Problems
#20Wow. A tip to anyone reading this: if you ever find yourself explaining away poor—nay, pathological—performance with anything other than ‘we made some mistakes in the past and we’re doing what we can to correct them’, please take a good hard look at yourself and consider exiting the software industry. That’s all I have to say. Edit: that wasn’t all I had to say. > What about Mac? I’m not sure but my Mac colleagues ha…
Doubly so if your product crashes even half as often as Flash. That they cannot seem to code for stability doesn't give me any confidence in their ability to code for speed. I heard that they refused to work with Apple to improve its performance on Mac, and that was a core reason why they got excluded from the iOS platform -- searching for this I came up with an explanation directly from Apple: "Symantec recently hig…
You must have heard wrong, and it's the other way around.
Apple did not open their video acceleration APIs until they released OS X 10.6.3 circla mid-2010.
http://xbmc.org/davilla/2010/05/03/osx-gets-h-264-accellerat...