J5’s Blog

The Open Video Conference just ended yesterday. I attended the first two days and just stopped in briefly during the hack-fests yesterday before having brunch with some old highschool friends and heading back to my parents house where my dog and car were stashed.

I can say without a doubt the turnout was amazing and even though not everything I heard all weekend was positive it was a giant leap forward in then understanding of the importance of Open Video and culture. I won’t put a figure on how many people attended but some of the upstairs talks were standing room only and after the first day some of the organizers were lamenting that then needed to get bigger rooms (consequently some of the talks were swapped the next day). Speaking about the organizers, they ran an incredibly smooth ship and should be thanked and praised for their efforts.

The Good

Apps

I was mainly there looking to see what video producers wanted from FOSS application developers and to support the PiTiVi/GStreamer teams on behalf of the GNOME Foundation. It is amazing to see the PiTiVi non-linear video editing app at such a usable state. While Edward Hervey (bilboed on irc) gave his mini presentation on PiTiVi I was busy hacking up a “How To Make Chocolate Truffles” video from pictures and clips I had laying around.

Afterwards I showed him some of the bugs I encountered in the 0.13.1 release and he just rattled off, fixed in git, fixed in git, fixed in git…etc. Sadly the releases are tied to GStreamer releases (which is a good thing from a development/bugs standpoint but not so good from a user standpoint given the early stages of PiTiVi) so we won’t see an official release soon. I plan on trying to automate a Fedora Repository at some point just to be able to view the progress without breaking my system.

The point is PiTiVi is about 90% there (and perhaps 100% in git) to be able to support my needs for basic video editing in terms of stability and basic tools. That should be pretty reflective of those who need to do things like screen casting and interview style video blogs. Some advanced features like effects (look at Cheese for some examples of this already working in an app) already exist in GStreamer and just need to be integrated in PiTiVi’s UI and rendering pipeline.

There was also a show of Cinelarra but more interesting is the GTK+ fork Lumiera which unfortunately is not usable yet but the direction they are going in (GTK+ interface and some GStreamer integration) looks like a great re-start in the case of pro level editing tools.

Also of interest in the pro level space was Blender which seems to be the pro project with the most momentum and features for pro’s. At least that was the initial reaction from some on the Red Hat media team. The dev’s did admit that the functionality is limited to what they needed during production of Big Buck Bunny (and other productions currently in the queue) but that in those areas it is rock solid. It is interesting to see a UI designed with different usability profiles. For instance one of Blender’s usability criteria is the avoidance of repetitive strain injury. To combat RSI mouse clicks are evenly divided between left and right mouse clicks.

Bassam Kurdali, one of the Blender developers and animators, came up to me later in the conference and said he had noticed me using PiTiVi to edit my video. He was impressed at the simplicity and slickness of the interface and how far along it is. There is plenty of room for different approaches and a real potential for cross pollination between the pro tools and the every day end user tools.

What Content Producers Want

Speaking of end users we got to hear from a bunch of them who let us know how we could support them. One of the biggest themes was that Windows tools suck and those who taught others couldn’t just tell them to go out and buy a mac (praises were heaped on iMovie and Final Cut Pro). They really want an easy to use tool, with the unfortunate note that it would have to run on Windows. One really good thing is that a lot of the non-tech content producers understood the need for free codecs. However in the end they just want a simple way to render down to DVD, You Tube, Daily Motion, iPhone, etc. and don’t want to deal with formats.

I ended up collecting a bunch of buisness cards and am toying with the idea of starting a feedback group with content producers which would get them involved in improving GNOME App usability from the perspective of those who are not yet familiar with the GNOME workflow. If we are serious about expanding our reach we need to go beyond our current self selecting internal feedback loops. The goal wouldn’t be to get these people using GNOME (though giving them a way through the apps wouldn’t be a bad thing). It would be more about getting groups outside of GNOME/Linux to be part of the process of improving GNOME. Will it be fruitful? I don’t know but it is an interesting experiment with a potential huge payoff for a little bit of effort.

Sita Sings the Blues

This good section wouldn’t be complete without the mention of Sita Sings the Blues by Nina Paley which is a feature length (82 minutes) animated film released under the Creative Commons Attribution-Share Alike 3.0 United States License. You have complete rights to watch, screen, remix and redistribute the film as long as you abide by the license. I do suggest you watch it and if you like it buy the DVD or simply donate to encourage more works like this (I bought the DVD for $20). Not only is Nina a content producer but she is heavily involved in advocating her distribution methods, going as far as documenting the process that went into releasing Sita under a creative commons license and in her work with QuestionCopyright.org.

Mozilla and the Open Video Contest

I was very impressed with Mozilla’s involvement and their push for Ogg Theora to become a base line codec for the HTML 5 video tag. They are also helping launch the upcoming Open Video Contest which would see the winner flown to the 2010 South by Southwest conference. We should probably run some sort of sister contest to encourage GNOME users to submit entries.

The Bad

It wasn’t all roses. While I feel we are reaching independent content producers way more than I would have though at this point, some of the big companies still don’t get it or are afraid of Open Video implications.

Adobe

It must be said that Adobe has been somewhat good at working with the community over long periods of time but that they just never get around to resolving key issues. What really surprised me was when on one of the industry round tables the Adobe representative pointed to their release of the Flash documentation as a shining example of this relationship. After checking with a developer of an alternative flash implementation I was told those documents are pretty much useless. Due to bugs, some of the spec just doesn’t work as written and other issues makes it impossible to write a third party Flash player.

YouTube/Google

While reportedly Chrome will ship with Ogg Theora support their flagship video site YouTube seems afraid to do so. Their rep at the round table stated some pretty audacious things such as continuing the myth that Theora wasn’t good enough when clearly that argument was directly debunked (the side by side comparisons were even playing on HDTV’s at the conference).

Even more of an issue was the representative’s idea on what Open Video meant. He declared that they would love to support Open Video but that it meant letting anybody do whatever they wanted and that doesn’t work from a buisness perspective.

Open Video isn’t about wild west, trample on rights. If anything it is about balancing the rights of content producers, end users and fair use. From what I read, YouTube’s position is that they are the 1000 pound gorilla in video distribution and at the end of the day they only believe in a user’s and content producer’s freedoms if it is walled behind their own servers. “All the world’s video” indeed.

The solution there is to drive traffic to sites like Daily Motion and Blip.tv which understand the issues involved.

Conclusion

Nothing is perfect, but we are off to a really good start. In the end it is up to us to keep the momentum going and eventually produce a better experience within the complete Open Video stack, from content production to delivery. The web was built and exploded around the concept of open technology. Let’s continue to make sure this is the case going forward. The last thing we want is the web to become the domain of a few, with creativity being stifled by restrictions in the non-open parts of the stack.

As a culmination of all the positive momentum that has been going on the past few years all the important Open Video players will be gathering at NYU’s law center for the first of hopefully many Open Video Conferences on June 19th.

The interesting part of this conference is it isn’t exclusively a tech conference. According to their website:

Open Video is a broad-based movement of video creators, technologists, academics, filmmakers, entrepreneurs, activists, remixers, and many others. When most folks think of “open,” they think of open source and open codecs. They’re right—but there’s much more to Open Video. Open Video is the growing movement for transparency, interoperability, and further decentralization in online video. These qualities provide more fertile ground for independent producers, bottom-up innovation, and greater protection for free speech online.

If we have any hopes of success in bringing the general public an understanding of our views on the importance of openness and freedom, forming a larger community with like minded content creators is the next logical step and another piece of the puzzle.

I will be attending the conference as a representative for GNOME. Others should consider registering and attending to represent their own media minded project. I hope to see you there.

Edward Hervey recently announced the 0.11.2 release of the PiTiVi video editor.  Even though it is rough around the edges it is feeling really nice and a couple of major features away from being baseline usable for every day simple video editing.  The features I would personally like to see are:

• Splitting of audio and video channels
• At least one more video channel which makes it easier to line up cuts
• Being able to split a video into segments (with gnonlin this should be as easy as setting the time properties on the video timeline object, cloning the video timeline object to the end of the cloned object and adjusting the time properties on the clone)

The only other thing I would want is a compositor so adding titles and credits would be easy.  Things like having a text tool, transition effects, being able to undock controls for dual screen use and other nice but not needed features would simply be gravy after that, the majority of which could be implemented as plugins.

Thankfully Collabora Multimedia has started to put muscle behind the development of PiTiVi and hired Brandon Lewis who’s summer of code work significantly contributed to the latest release.  Edward, it seems, will also have a limited amount of time to work on PiTiVi.

We can’t forget  Sarath Lakshman who was my Fedora Summer of Code student.  Although he had done very little pygtk work (he had done some projects in pyQt previously) his eagerness to learn and willingness to take criticism had him make significant contributions in the form of the webcam and network capture code.  He also started on a D-Bus API for doing direct desktop recording in PiTiVi in conjunction with the Istanbul desktop recorder.  That did not get in this release because the API was deemed to be too PiTiVi specific.  This is basically blocking on me finding time to review the code and make comments on how the D-Bus API should look.

All in all I’m looking forward to what comes out of this renued interest in PiTiVi.

Havoc,

I totally agree that embeddable languages is the way to go.  I’ve been using JavaScript heavily lately, along with the excellent Firebug for debugging (decent debuggers are something some very big languages are missing btw).  The biggest issue I have with JavaScript  is it’s lack of structure and horrendous scoping rules (this certainly doesn’t mean you are calling the containing object, especially when running a “method” from a callback).

What would really make JavaScript even more useful is the proposal for JavaScript 2. Unfortunately that presentation was made in 2006 but some, if not all of those features are part of the ECMA Script 4 proposal.  They even have a reference implementation up which is under a liberal license (I haven’t looked into it much but it links to a GPLv3 library).  As anything in committee, it is slow moving.  Hopefully we will see a finished spec sometime soon but I couldn’t find a timeline.

In the meantime there is an ECMAScript 4.0 to JavaScript converter call Mascara.  Unfortunately it is under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 license which means the code can not be distributed on many distributions because of the Noncommercial clause.  It isn’t always clear what constitutes commercial and most distributions I know of want to allow the possibility of for pay distribution or use in a commercial product by 3rd parties.  It also isn’t clear if that license extends to the generated code.  Does anyone want to write a GPL version?

Truthfully, I have a dirty little secret - I like JavaScript with all of its warts and hackish workarounds.  I like it because I know non-programmers who can grok JavaScript but can’t wrap their heads around Python or C.  I attribute that more to the environment than the language itself because it allows for the instant gratification of hitting the reload button and seeing something happen.  But what I like even more is the idea of embeddable languages bringing that sort of development process to GNOME.  There are a few apps that already do this and though it isn’t as easy as it is with the web whenever I have jumped into one of those apps, such as experimenting with writing a quick Vi mode for gEdit, it is amazingly simple.

What would keep me working in those environments would be an embeddable debugger, object viewer and UI/extension point tree.  Whoever writes those components and makes it simple to add scripting to any GObject app will be a hero in the community.  Anyone willing to sign up?

For my Fedora friends who don’t read Planet GNOME (you should):

• Federico’s screencast of rpm2git tool - we should be using this or something similar

This really gives a kick in the pants to those who take short cuts and lose sight of software freedom.  Kudos to Mozilla who actually has the critical mass to effect real change by endorsing Vorbis and Theora on all of their OS platforms.  Soon it will be up to the content producers to make open formats ubiquitous.  Having a delivery channel which people use on a regular basis means we can finally work from start to finish without touching a closed format if we so choose.  That to me is freedom - not forcing everyone to encode in open codecs, but to allow for those who prefer open formats the ability to deliver their content without any barriers between them and their end users. There are those who don’t want to see this happen but I have to believe that momentum is starting to swing our way.

Last week I talked about Ogg and stirred up a bit of controversy when I suggested we take Linux.com to task for not providing open formats. While it was very effective in getting people to write in showing their displeasure with propriatary formats, it almost failed at achieving the goal of getting them to switch. The problem with language is it can be very imprecise, especially in written form where tone is often hard to assess. While there is a time and a place for strong words we must understand that words can hurt and push people into a defensive stance where even the most innocuous of statements are misconstrued.

The correct words I should have used with Linux.com was that we should engage them. Simply telling them that they had to switch to Ogg was putting them in a defensive stance because of various factors. From what I had found out, this was a small team of hard working individuals with families, a love for reporting and not enough time or resources to do everything they would like to do. What I needed to do was find an way over the wall so we could figure out a way forward. That way was through politeness and an offer to help.

I had e-mailed Robin “Roblimo” Miller, a senior editor at Linux.com, with my offer to help and he suggested I call him so we could speak as two humans. I spent an hour on Friday talking and more importantly listening to Robin, realizing that this was a man who was willing to help push forward the use as open formats where practical. He had talked to Monty during an interview for a piece on video formats and hashed out the quality issues to his satisfaction. But, he has also talked about the need for delivery systems which would make Ogg as ubiquitous as Flash video and make using Ogg as his primary format and easy choice as it would be able to reach the the wider audience which keeps his site going.

What I picked up out of the conversation that was important to me was that Linux.com was moving forward and had a keen interest in supporting open media. I didn’t expect things to happen overnight, I just wanted to know that they were happening. I was pleased to see their last weekly wire go out with a link to the Ogg Theora download which I promptly watched.

But now it is our turn to be “taken to task”. We need to help out by making it more economical for sites to post open media. To do this we need to help improve the quality of Theora and help complete Dirac. We must also help out writing easy to use software to edit video. Two promising contenders in this area is Kino and Pitivi with Kino being much further along though I personally like Pitivi’s interface better. Delivery systems as I have said are also important, whether it be working on Firefox’s video tag support, various plugin systems, video blogging software or simply setting up a “Got Ogg?” campaign to distribute plugins, content and advice on using open formats.

The ball is in our court and we need to keep running with it. If you really care about open media then find a way you can help out. Happy holidays everyone.

It seems Apple is not the entity fighting for a DRM-less world we thought they were and Nokia isn’t such a great patron for open source software either. For those who haven’t heard the news, lobbying by both companies have caused the W3C to strike a provision in a HTML5 draft which would make OGG Vorbis and Theora a standard media format on the web. What baffles me about this is having Vorbis and Theora media formats does not stop Apple or Nokia from distributing content using whatever proprietary format they wish. This just hobbles the web which had exploded thanks to open standards, open formats and open source. In recent years though the web has become more and more proprietary. Allowing companies to remove open formats from an open standard without nominating another equally open format to take its place allows special interests to control the development of the web. This effectively locks out a large portion of the small independent content providers from distributing next generation content such as video while moving us toward a world where a few entities control the distribution of all content.

There is a light at the end of the tunnel though. It is time for us to make the OGG family of codecs ubiquitous with or without the mandate of a standard. A large step in that direction is Firefox developing native OGG support. Easily installed IE plugins would go a long way also. It is also up to the community to post their content in an open format. The next time linux.com post a link to mp3 content that they produced and not have a Vorbis link associated with it I hope people take them to task. The same goes for people posting content on the various planets. Open formats are essential to a free and open web.