I just installed the new release of [url=http://ubuntu.com/"]Ubuntu[/url] last night. This release was highly anticipated (by me, anyway) and is known as [url=http://ubuntu.com/dapper]Dapper Drake[/url]. There are many things different about this release from the previous one, and I won't list them because you can find the ChangeLog. Overall, it is very polished and very nice, but that's for another entry.
Right now, I'm working on compiling [url=http://diva-project.org]Diva[/url], an open-source video-editing system. Though it is very new and unreleased (it's still at version 0.0.2!), it looks (from the [url=http://diva-project.org/wiki/Screenshots]screenshots[/url]) very well done. We'll see if the compile is worth the trouble.
EDIT: I'm still not done with it. Diva requires all these dependencies that need to be fulfilled before it can be built. I have them all installed, but they are not being seen for some reason. Roar.
EDIT #2: Diva is installed and ready to go. However, there is a slight problem in that I can not import NTSC video files. This, however, is not on the fault of Diva; more on the fault of the gstreamer backend and the NTSC standard as a whole.
NTSC is 29.97 frames per second. Roughly. The problem here is that little word "roughly." While it is often rounded 29.97 frames per second, the actual rate is 1001/30000. Almost all video capture programs round the meta data to 29.97 frames per second, but Diva/gstreamer relies on it being 1001/30000 and so the frame rates do not match up, and thusly, the file is not imported.
I asked the lead developer (MDK on [url=irc://irc.freenode.net/diva]#diva[/url]) why Diva does not just change to 29.97 and was told that doing so would cause a time difference of about 12 nanoseconds per frame of timeline. While 12 nanoseconds may seem trivial, if you have a 5 minute timeline (300 seconds), that is [i]roughly[/i] 3000 frames. This means a difference of [i]about[/i] 36,000 nanoseconds. As you can see, this error is unacceptable and is being worked on.