Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
From
rjacquez
There’s no other Industry in the world that was more affected by Apple refusing to embrace Adobe Flash in their iOS devices like the eLearning Industry. I don’t have the ... Via k3hamilton 
No comment yet.
Sign up to comment
Scoop.it!
What Did We Do? We performed live streaming delivery tests, using RTMP and RTSP streaming protocols from a streaming server. We chose to use Flash Player for RTMP playback and the native Video app (an underlying player on most Android devices, not to be confused with the YouTube app) for RTSP streaming playback.
So What Did we Find? In our tests, several patterns emerged. First, on the performance front, content delivered in RTMP (the Flash Player "native" protocol) was consistently delivered at a higher frame rate than content delivered by RTSP to the native Video app, even when both were served from the same Wowza Media Server. None of the delivery solutions were perfect, by any means. Content played back as RTMP, RTSP and even HTTP dropped some number of frames for every clip played. That's to be expected in a mobile environment, and as mentioned above, our test clips were intentionally robust enough to tax the devices. Yet we were surprised to find that-although the content was streaming out from the server at full frame rates and resolutions-several devices just couldn't muster the performance necessary to play back content with the native video app and RTSP protocol. Via Nicolas Weil
|
Scoop.it!
[...] The support for HW accelerated 2D, 3D and video playback on mobile, plus an improvement in performance for Flex applications, plus the possibility to integrate HTML5 contents with StageWebView, plus the DRM, plus native extentions, **finally**, makes AIR (for Mobile) an interesting, efficient, effective and valuable solution for cross platform application development. Via Nicolas Weil
|
