Blogs

I'm sure there are others working through the same saga (or is it s-ogg-a?) with regards to prepping video to play natively in HTML 5. This post contains some additional thoughts that some readers (and googlers) may find useful in developing a workflow around OGG Theora video for Macs. For any readers of mine that have no interest in technical video issues, (most of you) I'll have to ask you to bear with me and ignore this post, as I promise more interesting reading in the future.

Each week, I need to be able to convert two parts of a church worship service into Ogg theora. Each part is about 30-45 minutes long. I'd like a higher quality audio encode for the portion of the service that contains music. For the sermon portion, which is mostly speaking, I am willing to sacrifice some visual quality and sound encoding for smaller files and better use of bandwidth. I'm used to these files in Quicktime H.264, and file sizes typically range from 120 meg to about 180 meg. Encoding time is a consideration, since the computer we use has a lot to do between Sunday and Tuesday, which is when I try to have the files ready online.

I didn't mention in my last post one other option that I was almost happy with - if I encoded my files using compressor into basic MPEG1s set to the highest quality I could set, then ran those through Simple Theora Encoder, it created decent-looking video through batch processing very quickly. Unfortunately, I wanted the ultimate quality a little better and the filesize to be about half of its final result. Still, it would work in a pinch.
.
Since my last post, I've toyed with two additional workflow possibilities - I found the options in compressor to create custom settings using quicktime extensions, which allows you to encode OGG theora in a batch if you have the Xiph.org quicktime components. Unfortunately, this method insists on a quicktime container format, which won't work for HTML5 playback in firefox. I'm told there's a command line trick using FFMpeg, but reading about it makes my eyes glaze over, so I had to find another solution.

I also found a plugin for firefox called Firefogg which looks extremely promising. If you go to the firefogg website , it'll give you options to choose a file, choose some settings, and encode the file locally on your computer using the plugin. This has the added bonus of not tying up my video editing software while it encodes. Unfortunately it does not allow me to choose a file on my Mac, so I can't get my foot in the door to test it out. I guess I'll have to save that one for my PC videos.

So that brought me back to exporting using Quicktime conversion in Final Cut. I started with the default settings (Keyframe every 64 frames and "best" on frames per second) and scaled back the quality to "low", kicked on optimize, and sharpen on low. While the final video wasn't bad, it was about twice the file size I expected and took 30 minutes to encode a 3-minute video. This 10:1 ratio on encoding times was not going to work on my schedule.

Over my series of tests, I discovered that the "Optimize" checkbox seemed to do little for the quality other than increase encode time significantly. Meanwhile the "lowest" quality was far too pixelated, although the file size was well under what I'd hoped. Meanwhile, if I set more keyframes, it didn't add much to the file size, and lower frames per second helped keep it small as well.

I hit the sweet spot at 20 frames per second, keyframing every 15 with the quality slider set to "low" and optimize off. File sizes where what I expected from my H.264 encoding, and my encoding time ratio was closer to 2:1 (about an hour to encode a 30 minute video). For the size and the processing time, the quality was far better than I'd expected. I adjusted the settings to 15 fps for the sermon, started it encoding, and called it a day. I'd been looking at this too long, and my problem was solved.

Later, I checked my twitter stream and found out that Google had announced a new video format called WebM, which is unencumbered by licenses and backed by Mozilla and Opera. The goal is that it could work for HTML5, which could potentially make encoding in Ogg a moot point. *sigh* Why is it that just when I figure out the best way to do something, it changes? I guess that's what I get for aiming at a moving target. ;)

I've begun to take the plunge into HTML5 for the sake of video. On Hillvue.tv, we've been using flash for several years for video playback, but the benefits of HTML5 are worth a little extra effort, so I've been doing more research.

I'm particularly interested in achieving playback of the videos on iphones and allowing for people to jump ahead without having to buffer the 30 minute video to watch something near the end. It should also be more future-proof as browsers and devices improve. Ultimately it's a more efficient system than flash for displaying video.

The Video for Everybody code at http://camendesign.com/code/video_for_everybody looked like a good way to implement it. If you have a compatible browser, it'll start with the mp4 version for the sake of Safari and maybe Chrome, then fallback to the ogg version for Opera and Firefox users (and some Chrome), then to flash for anyone unfortunate enough to be using internet explorer. It requires two encodes -- one in mp4 (which I already do each week) and one in ogg theora.

I've learned a lot about the Ogg theora format. In the HTML5 debate, it has a lot going for it, including the 30ish percent market share of Firefox and its forever royalty free status. As an encoder, I'm told that it can look as good or better than H.264 at very small filesizes, if you encode it properly. The "Big Buck Bunny" video on the Video for Everybody page had me convinced.

One thing I know for sure is that Macs make it tougher to use ogg as a part of a Final Cut Studio workflow. It appears that I've attacked the problem backwards the whole way. A twitter follower suggested I use handbrake to convert the file, but handbrake can only encode with an MKV extension, not an .ogg. I tried the miro video encoder, and frankly don't remember why it couldn't work for my needs, but I had to give up on it. Then I tried the simple theora encoder, and was really excited about the speedy encode and its output quality, although in its simplicity it failed to encode my audio. Fail.

I finally found the Xiph.org quicktime components that allow you to export out of FCP directly to Ogg. It's predicting a two-hour encode on a 30-minute video, so the jury's still out. I also read in one forum that it caused Compressor to have some broken ogg files, but as they say, you can't make an omelette without breaking some oggs.

If anyone reading this has found a workflow they're happy with, I'd love to hear about it. In fact, that would be downright ogg-citing! I'd be ogg-static! Sorry, I'll stop now.

The dreamer in me feels a little trapped by the high-speed-internet status quo. I have two providers to choose from, and the competition isn't exactly driving prices down or increasing innovation. Truly high-speed internet, like the gigabit/second access Google's experimenting with, seems way too far off, and my bills aren't any getting smaller.

In fact, since AT&T is providing "high speed" access at about 6.0 mpbs, and Insight's at 20.0, there's not a lot of competition. Insight's pricing structure limits the competition by bundling phone, internet and cable for a cost that's much lower compared with the services individually. I suppose I should be happy about that, but if I want to reduce my costs by dropping cable or by using the Magic Jack for my home phone, I can't.

The internet, at its essence, is a bunch of people hooking their computers together in a network. No one owns it, and no one owns access to it, although companies like AT&T and Insight have developed infrastructure that allows people to have quicker and more reliable access that they can charge for. People sacrifice that all the time by logging on through a neighbor's wireless router. So long as their access doesn't use enough data to trigger the Internet Service Provider (ISP) to look into it, this is considered acceptable by everyone involved, including the ISP.

I wonder what it would take for people to take back control over their own internet access through an public, ad-hoc, peer-to-peer network. A neighborhood do-gooder could set up a wireless router in a high location, and anyone in range could access it. Then, someone at the edge of the radius could do the same, and so on. Eventually, this would create a chain of internet access that would snake through suburban areas. Ideally, if there were multiple paths to the information a user needed online, the routers could choose the path that was least burdened by traffic and low signals. As long as someone, somewhere along the chain had internet access, the public has it as well, along with a side of choice.

Clearly there are technical hurdles to something like this in our current IP based system. There are security concerns and even moral ones, since it would potentially deprive those who have invested in the current network of the benefits and profit of their investment. Still, imagine the benefits that could result in such a network. The public could benefit greatly and directly from each improvement and price competition either comes back into play or becomes moot because the access is free.

Ironically, I'd say that ISPs are actually pushing people towards this eventuality by their current pricing structure. Look at any other utility - If I wanted to avoid an electric bill, I could run an extension cable to another house. Naturally, that homeowner would object to this because he has to pay more to cover my access. Same with water, sewer, and natural gas, and that's why it doesn't happen. Not so with communications - one fee gives users access to an unlimited stream, facilitating exactly the kind of network that I've described. If cable and internet companies could build out a pricing structure based on the amount of data used by the end user, such an ad-hoc network would be nipped in the bud. Users would suddenly have an incentive to lock down their wireless security, and internet power users would pay a fairer share of the costs.

Thoughts?

There seem to be multiple ways to learn a language, but when it comes down to it, the best approach is to be in an immersion environment, where just about everything you use is in the new language.

On the other hand, if you're teaching yourself a new language, and you can't exactly fly off to Shanghai or live at the local Casa de Burritos, immersion isn't practical.

One way for the bravest of the brave to learn a new language would be to use Google's open translation tools to translate everything you read on the internet to the new language. Unfortunately, this isn't practical either unless you know enough of the language to work out the context and/or enough time to translate everything back word-by-word.

So here's my brainstorm - what about a browser plug in that translates words into the new language in small increments?

Part of the beauty of this is that words that are the most useful to learn are typically the most common, and they're also easiest to pick up in the context of the rest of the conversation.

For example, you might read a paragraph like this one, posted by a friend of mine as a facebook status:

Just saw Avatar, and was pleased by it's celebration
of strong Republican values. Family, lifelong monogamous
relationships, community and reference for God. How could
atheistic illegal immigrants hope to prevail? >=)"

As a student of a new language, you may know a few words like "and" and "was" from the paragraph above, but how often will you encounter "illegal" in an introductory language course?

This tool would offer a compromise through a sliding setting between 1-100, designating roughly the percentage of the new language you're ready for. It would also have its own database of sorts behind it to know which words in the language are the most common. Also, you could set it to replace or go side-by-side with the translation. Assuming slider at 5ish and "replace" on, translating to Spanish, it becomes:

Acabo de ver "Avatar", y se pleased por que es celebration
de strong republican values. La familia, lifelong monogamous
relationships, community y reference a Dios. ¿Cómo could
atheistic illegal immigrants hope to prevail?

.... which is spanglish, I suppose, but even a not so well-versed Spanish student could understand the intent from the context, and be learning by partial immersion in the process.

A side-by-side version might look like this:

Acabo de ver (Just saw) Avatar, y se (and was) pleased
por que es (by it's) celebration de (of) strong republican
values. La familia (Family), lifelong monogamous
relationships, community y (and) reference for God.
¿Cómo (How) could atheistic illegal immigrants hope
to prevail? >=)"

At 5%, I'm figuring it would replace just about every conjunction, preposition, and pronoun. It would be on a curved scale, so a 1% improvement from 0-1 % may only replace the most common 20 words, but 10-11% may replace a hundred, and going from 90-91 may replace several thousand of the least commonly used words. The idea would be for the user to always adjust the slider to the point where he can still read through the context and be learning until he can deal with the completely translated page.

Naturally, any errors in the original or from Google's mistranslation would be unavoidable, and you can only hope that Google's translation tool would improve over time and make the results better.

Of course, there's also the "Como mucho" problem. It relates to how translation isn't always a word-for-word endeavor. My Spanish teacher in high school told me the story about a guy who went to a spanish-speaking country armed with only a English-to-Spanish dictionary. In the marketplace, he wanted to ask "How much?", so he found "how" (Como) and "much" (mucho). He went to shopkeeper after shopkeeper asking "Como Mucho?", only to receive nods and confused looks in response. This is because the Spanish meaning of "como mucho" is "I eat a lot", thanks to the verb "Comer" conjugating into "como". In cases like this, some mechanism would have to be built in to grab phrases where it's appropriate for the language and ignore the word-by-word translation.

As I was writing this post, I played with the Google translate extension for Chrome. With it, you can translate a page, then mouseover questionable text to see the original in English. This isn't all that useful for paragraphs, because it can be tough to know which words mean what. Still, it makes things such as the "comentario" and "gustar" buttons pretty obvious ("Comment" and "like"), and short sentences look instructive.

Unfortunately, I doubt that I can take the time to immerse myself in the programming languages of plugins to make this happen. Does anyone else wanna give it a shot and let me help?

I've spent the better part of this afternoon jumping through the necessary hoops to get my website (ChrisDillingham.com) to allow authentication using Facebook connect. For me, this is no small achievement on my journey towards Drupal CMS mastery, and it means that all my friends from the Beech High School Band of 90-93 can log in on my site and leave comments without creating a separate registration.

I find this rather ironic, in a way, since of all the things I took away from band in high school, the most enduring are the friends I've made through the process. In fact, if Facebook had existed back in the early 90's, marching band would have been a complete waste of time.

Sure, I learned how to play a euphonium with the tone quality of a moose. I learned how to read music, march out five yards pretty closely in eight steps, and retain an appreciation of the jazz work of Blood, Sweat and Tears. I learned how to kill a lot of time between classes hanging out at the band room. Unfortunately, most of those skills haven't translated into anything useful in the real world for me.

What did make the impact was the process of working together with my peers to a common goal. We spent time together marking our spots to stand on the field, cheering in the football stands at the games, and riding on the bus on our way to tournaments. Over the course of several years, that was a lot of time, and we got to know each other pretty well. We created friendships that have endured long after we graduated, had kids, and forgot all we knew about the life of spats and spit valves. I suspect that the same happened with non-band friends of ours who spent that much time together, say, poring over drama scripts or math equations or bus rides together on the way home.

So now we've found our way back to Facebook, and we've sought each other out to catch up. The more I use Facebook, the more I can't help but think that everything that the band did for me then, Facebook does for me now. It is an absolutely superb tool for virtually hanging out with your peers and getting to know people that you are acquainted with, but don't really know much about or don't have the opportunity to get to know for various reasons.

Through Facebook, I might have gotten to know that guy in the back of the government class that always seemed to have something up his sleeve. It would have helped me break the ice with that quiet girl I kept seeing in the hallway that didn't seem to know anyone. It would have allowed me to discover that other people all over my school shared my interests, even though I didn't know it.

It's easy to say "well, why didn't you just go up and talk to those people?". It's a fair question, since I've never been known for my ability to be social. I did where I could. Still, unless you sit near someone for weeks and have ample opportunity to talk, it's tough to get to know much about them, let alone to forge a friendship. Conversations on the way through the rush of the hallway are challenging, and the common ground of a class together or mutual project is a powerful catalyst. In fact, the friends I have kept up with through more than 15 years are the ones I spent many classes with over several years and met with regularly outside of class -- or spent a couple of seasons with in band.

Marching band forced that kind of proximity and ultimately great relationships because of all the time we had collectively to wait around and get to know each other.
Had Facebook been an option then, I might have known the rest of my classmates just as well.