Skip to main content

ActionScript: Dynamic Streaming

There's an article here about dynamic streaming in Flash Media Server 3.5 using Flash 10's new QoS features. It's a three-part series, and I just spent several hours reading it.

It talks about a class that Adobe provides called "DynamicStream". It doesn't come with ActionScript 3.0--it's a separate download. I was hoping to integrate this class into JW Player in order to do more intelligent bitrate switching using Adobe's new QoS features.

Let me explain why I'm frustrated.

First of all, this article was a three-part series, each with several pages. Hence, it was very long--much longer than I think was necessary. Part 3 covered "Integrating dynamic streaming with existing video players". Since it was the final page in the entire series, I expected it to be very exciting and useful. Instead, it was very mediocre. I can summarize, "Hey, this stuff doesn't work in Flash 9, so you'll have to do something else to support older players. Here, read this long code sample to learn how to parse the Flash player version number." There's a lot of code like:
private function _verifyServerVersion( p_version:String ):void
{
var fmsVersion:Number = Number( p_version.split(",", 2).join(".") );

trace("fmsVersion: " + fmsVersion);

if ( fmsVersion >= _targetFMSVersion )
{
_isServerCapable = true;
}
else
{
_isServerCapable = false;
}
}
At the very least, that if/else could have been written:
_isServerCapable = (fmsVersion >= _targetFMSVersion);
However, I think it's a flaw in ActionScript that you have to parse the version numbers manually at all.

Next up, I looked at the DynamicStream class, and it had multiple different coding styles:
if(...) 
{
...
if(...){
...
if (...) {
...
if(...) { ... }
When I see stuff like that, I lose my confidence in the code. The file is 1049 lines long, by the way.

Having said all that, what really frustrates me is that the code doesn't take into consideration the widths for the various encodings. Currently, JW Player will pick the best encoding based on width and bitrate. That way, you can have different encodings for different size players. This is important for several reasons. First of all, there's no use pulling down an HD video for a 480x320 player until the user goes full-screen. It eats up bits that could be going to quality instead of size. Furthermore, it's better to avoid scaling on the client since it looks better to scale only once during encoding.

Hence, I'm more than a little disappointed by the DynamicStream class, and I'm stuck wondering how the heck I'm going to pull the useful bits out of this 1049 line file in order to integrate them into JW Player. Ugh, painful.

Oh, did I mention Silverlight takes care of bitrate switching entirely automatically? Double ugh.

Comments

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…