Desktop Linux isn’t necessarily the first platform you’d think of going to for video editing. Despite that, there are several great projects that offer video editing functionality; things like PiTiVi, Cinelerra and Kino to name just a few.

Jonathan Thomas wasn’t satisfied with the existing video editing solutions on Linux, however. They weren’t easy enough to use, powerful or stable enough. Enter OpenShot, Jonathan’s solution.

Let me say right up front — the project is in a relatively early stage of development. There are plenty of things not yet completed or that don’t work quite right just yet. But I’ve had a brief play with OpenShot, and I am really quite impressed.

The interface will look familiar if you’ve used any other timeline-based video editing package before. You have a project bin on the left, a preview monitor on the right and the timeline at the bottom, where you arrange the clips in sequence to make your movie.

You can’t capture clips directly from a video camera at the moment, but if you are able to get video captured via another source, you then just import the video into OpenShot. I had some old PAL DV footage lying around. I just went to File > Import Files and selected the files.

Right away the clips just appeared in the Project Files area. It just, sort of, worked — I didn’t have to wait any time for the clips to be processed or for any conversion to take place. Now I did only import three clips of fairly short length, but it really was an easy, slick process.

You can then drag the clips to the timeline and arrange them. You can use the Razor tool to slice the in and out points of a clip or split a clip into two and rearrange it. It all really works in a very friendly, familiar way if you’ve ever done anything like this anywhere else.

The only thing that did throw me off with the timeline is the fact that the clips don’t seem to ‘snap’ to the edges of other clips, for example, so at times it feels quite difficult to line clips up one after another without having black space in the video between them. Having a satisfying ‘snap’ feel to the timeline where appropriate would really enhance it.

When you’re done, you can export the finished sequence into an array of formats.

Again, I’m going to admit to being lazy. I just accepted the default settings and exported — and it just worked, again. It is somewhat of a complicated dialogue box if you’re not into video codecs and standards and all of that, but you don’t necessarily need to spend time fiddling with it — the default settings will produce something useful (provided you can play back the codecs in your favourite media player).

There are issues with this project. I found the interface a bit — blue — and not really to my tastes. Also, the icons feel a little bit indistinct and unclear. It’s quite difficult to see quickly what each icon does and I did find myself taking a few minutes to get to grips with which button was which because of that.

Some keyboard shortcuts I’d expect to work, such as the Delete key to delete a highlighted clip in the timeline, spacebar to toggle pause/play in both the timeline and the clip preview in Project Files, to not yet be functional.

I want to stress again that this is an early in-development project. Despite that, it’s the most user friendly, simple video editing program I’ve used on the Linux platform. It just seems to have the attitude of a program that follows conventions, is really simple and just plain makes sense.

There are a lot of features more demanding users may expect before it can be accepted perhaps by a more seasoned video editing audience, but OpenShot shows promise and real potential to be the best home-orientated video editing solution on Linux.

You can download some pre-built packages for Ubuntu as well as source code from the OpenShot Downloads page. If you’re into video editing with Linux, give this a try.

A quick tip today for all Debian (and derivative) users:

Have a file on in your system that you just can’t figure out where it came from? Searching for the name in Synaptic doesn’t help? About ready to heave your weary keyboard out the window in an administrative rage? Fear not, dpkg to the rescue!

Let’s say you are trying to find out where in the world /usr/share/epiphany-browser/glade/epiphany.glade came into existence. You’ve checked epiphany-browser, but it’s not there. Let’s ask dpkg-query:

$ dpkg-query -S /usr/share/epiphany-browser/glade/epiphany.glade
epiphany-browser-data: /usr/share/epiphany-browser/glade/epiphany.glade

Okay, so it was in epiphany-browser-data. Let’s ask dpkg-query to do the reverse this time, and find all files included in that package:

$ dpkg-query -L epiphany-browser-data
/usr/share/epiphany-browser
/usr/share/epiphany-browser/components
/usr/share/epiphany-browser/components/epiphany.xpt
/usr/share/epiphany-browser/art
/usr/share/epiphany-browser/chrome
# ...

A good trick I use instead of remembering dpkg-query switches is to simply add aliases to my .bashrc:

alias dpkgs="dpkg-query -S"
alias dpkgl="dpkg-query -L"

The above example could then be shortened to dpkgl epiphany-browser-data.

Not all files are managed by packages, and so this may not always get you the results you wanted. Obviously, user-created files in /home will not be from any packages, nor will most files in /etc. But it’s still a handy way to figure out where a file came from.

In one last example, you can take advantage of shell command nesting to figure out which package contains a binary:

$ dpkg-query -S `which firefox`
firefox-3.0: /usr/bin/firefox

(Those are backticks, by the way, not regular quotes.)

If you followed my recent video tutorial on enabling Ubuntu/GNOME’s Tracker search tool, you should now be enjoying the ability to search the files on your system.

During a recent upgrade to Ubuntu 9.04, which was recently released, I found that the Tracker search tool index had become corrupted. I tried to tell Tracker to rebuild the index, but experienced some weird issues.

In this quick tip, I’ll show you how to avoid this and other issues by deleting Tracker’s index and cache manually, so that it can start ‘from scratch’. Note that if you are having issues with tracker, it is worth trying to rebuild the index from the graphical interface first. This tip is a last resort if you need to clear everything out from scratch and start it again.

Tracker’s Files

According to the documentation, Tracker stores its files in the following locations:

• Configuration Files – ~/.config/tracker/tracker.cfg
• Data Files – ~/.local/share/tracker
• Index Cache – ~/.cache/tracker

If you’re happy with the settings you have, you may want to leave the configuration file intact, and just wipe out the data files and index cache.

Quit Tracker and Delete the Files

First of all, you need to go ahead and quit the Tracker application in the system tray.

Next, you must quit all processes of both trackerd and tracker-indexer, so open up a terminal and run these commands:

And finally, carefully delete the files listed above (excluding the config file, if you don’t think you need to clear that out as well).

So to recap, go ahead and delete the folders:

• ~/.local/share/tracker
• ~/.cache/tracker

and if you wish, the config files:

• ~/.config/tracker/tracker.cfg
• ~/.config/tracker/tracker-applet.cfg

To restart Tracker, I recommend that you log out and log back in so that trackerd and the system tray applet both restart properly. You should then be able to reconfigure it from the beginning as detailed in the original tutorial.

And that should be it – Tracker should rebuild itself from scratch. Useful to know for if things go wrong!