GUADEC 2014

July 28th, 2014 by Edward Hervey

Well hello there, dear Internet.

So yes, it’s been quite some time since the last blogpost. A lot has been going on, but that will be for future blogposts.

Currently at GUADEC 2014 in Strasbourg, France. Lots of interesting talks and people around.

Quite a few discussions with several people regarding future GStreamer improvements (1.4.0 is freshly out, we need to prepare 1.6 already). I’ll most likely be concentrating on the whole QA and CI side of things (more builds, make them clearer, make them do more), plan how to do nightly/weekly releases (yes, finally, I kid you not !). We also have a plan to make it faster/easier/possible for end-users (non-technical ones) to get GStreamer in their hands. More on that soon (unless Sebastian blogs about it first).

If you want to come hack on GStreamer and Pitivi, or discuss with the various contributors, there’s a Hackfest taking place at GUADEC from Wednesday to Friday. More info at https://wiki.gnome.org/GUADEC/2014/BOFs/Pitivi

PiTiVi hackfest/meetup at GUADEC (updated)

July 22nd, 2010 by Edward Hervey

Hi all,

Since most of the PiTiVi hackers are going to be present in The Hague next week for GUADEC and the Collabora Multimedia annual meetup, we decided to organize a hackfest/meetup on Tuesday 27th July in the afternoon just before GUADEC. I’m still trying to figure out a venue to hold this, I’ll keep you informed via blog/mail/twitter.

If you want to learn more about PiTiVi, chat with the hackers, get face-to-face assistance/discussion, learn what’s planned next, etc… you’re welcome to join. And yes, if you want to complain, you can also come by :)

UPDATE: It will take place in the area below the Paris Room (stairs going down in the middle of the open space).

3 days left to prepare your summer

April 6th, 2010 by Edward Hervey

Hi folks,

The Google Summer of Code deadline for student application is nearing and thought it would be good to highlight some projects that are dear to me:

  • PiTiVi : The inclusion of PiTiVi in Ubuntu Lucid has brought about a lot more interest, and while the reception is overall positive for what it can do right now, we know there’s still a lot more work to make it the swiss-army-penknife of editing. A student has already proposed adding the support for effects, but other items that would be great to have are:
    • Collaborative editing : Allowing several people across a network/internet to work on a common project, using the telepathy project.
    • Improving the Media Asset Management support of PiTiVi (i.e. solving the problem of having hours and hours of footage, how to search/sort/tag them efficiently). Leveraging existing technologies instead of reinventing the wheel is a must here
    • Auto-cleanup of editing: Average consumers don’t know how to shoot, the camera moves, there’s some hissing in the audio, the color-balance is always changing,  …  This would be an excellent project for somebody with lots of video editing experience who has got an eye to making an editing project look professional (i.e. anti-youtube) and wants to help automatize all the tedious little tasks one has to take care of. The goal would be to come up with a system to cleanup footage on import, help define proper transitions,.. This would go hand in hand with effects support.
  • Wine DirectShow GStreamer backend. I mentored Trevor Davenport last year who proved that using GStreamer as a back-end for DirectShow on Wine is possible, but quite a bit of work is required to finish up this task to have it merged in wine trunk.
  • GStreamer: Supporting VA-API in GStreamer would be a must, especially considering the awesome work Gwenole Beauchesne has done to make it support VDPAU as a backend. VLC has already switched to supporting only VAAPI for hardware-accelerated and it’s time GStreamer catches it up :)

The PiTiVi proposals can be proposed both in the GStreamer and GNOME organization, the Wine/DirectShow project with the Wine organization and the GStreamer projects… with GStreamer.

You can also hop into the IRC channels of the various projects to discuss your proposals. On the freenode network: #gstreamer, #pitivi, #winehq

The best proposals are always the ones where students have got an itch they want to scratch as opposed to being told what to do, so if you’ve got something in particular you’d like to hack on in the projects above, don’t hesitate to contact the maintainers/developers of those projects and propose your ideas… but hurry up… tic tic tic

PiTiVi 0.13.4 “Cabernet d’Anjou”

March 10th, 2010 by Edward Hervey

Hi all,

The PiTiVi development team is thrilled to announce a new release of the PiTiVi video editor.

Amongst the new features:

  • video mixing/transparency support
  • icon view in source list
  • smoother scrolling
  • modeless splitting
  • seek on click
  • faster waveforms
  • zoom slider
  • UI beautifications
  • Speed optimisations
  • dbus/hal dependency now optional
  • translated in 30 languages

More info in the release notes , tarballs available on ftp.gnome.org and should be available on your distros any time soon (will be included in Lucid Lynx).

Update : The gstreamer-developers PPA has been updated for Ubuntu Karmik with 0.13.4 and all required dependencies : https://launchpad.net/~gstreamer-developers/+archive/ppa

The result of the past few months of hacking

November 30th, 2009 by Edward Hervey

As some people noticed in the PiTiVi community, I haven’t been working that much on PiTiVi over the past few months. I did mention the work I was doing was somewhat related to PiTiVi and that hopefully I’d be able to talk about it openly.

That day has now arrived.

GStreamer editing services

The “GStreamer Editing Services” is a library to simplify the creation of multimedia editing applications. Based on the GStreamer multimedia framework and the GNonLin set of plugins, its goals are to suit all types of editing-related applications.

The GStreamer Editing Services are cross-platform and work on most UNIX-like platform as well as Windows. It is released under the GNU Library General Public License (GNU LGPL).

Why ?

Because writing audio/video-editors is a lot of work, and we should make it as easy as possible for people to write such applications while being able to leverage the power of GStreamer and not requiring a PhD in nuclear engineering.

The GStreamer Editing Services (GES) introduces 3 concepts:

  • GESTimeline : This is your central container corresponding to a TimeLine, you can add Tracks and Layers to it. It is also a GStreamer Element, so you can use it in any GStreamer pipeline.
  • GESLayer : This corresponds to the User-visible part of the Timeline. This is where the user lays out the various LayerObjects (files, transitions) he wishes to use. The LayerObjects can be as simple or advanced as required (ex : a FileSource can have a mute property, an ‘overlay’ property, a rotate video property, …) and those objects will take care of properly filing up the Tracks. Applications can create their own subclasses of LayerObjects for their custom usage, implementing the logic of what TrackObjects to create in the background and not have to worry about anything else).
  • GESTrack : This corresponds to the media part of the Timeline. An audio editor will only require one audio Track, a video editor will require one Audio and one Video Track, etc … These parts don’t have to be visible to the user… nor the application developer :)

Why another library in addition to GNonLin?

The answer to that is that GNonLin will remain a media-agnostic set of elements whose goals are to be able to easily use parts of streams (i.e. from GStreamer elements) and arrange them through time. While this makes GNonLin very flexible… it also means there is quite a bit of extra code to write before getting to the ‘video-editing’ concepts.

Can I write a slideshow/audio/video/cutter/<crack-editor-idea> with it ?

Short answer : yes. Longer version : yes, but you might have to write your own LayerObject subclasses if you have some really specific use-cases in mind.

Where can I find it ?

The git repository is located here . Documentation can be generated in docs/libs/ if you have gtk-doc , and you can find some minimalistic examples in tests/examples/ . I will be gradually adding more documentation and examples.

GstDiscoverer, Profile System and EncodeBin

GES alone isn’t enough to end up with a functional editor. There are a couple of peripheral multimedia-related tasks that need to be done, and to solve that I’ve also been working on some other items. All of the following can be found in the gst-convenience repository.

GstDiscoverer

Those of you familiar with PiTiVi/Jokosher/Transmageddon/gst-python development might already be using the python variant of this code. The goal is to be able to get as much information (what’s the duration, what tags does it have, how many streams, of what type, using what codecs, …) from a given URI (file, network stream ,…) as fast as possible. While the code already existed, it was only python-based. So I rewrote one in C, with several improvements over it. It can be used synchronously or asynchronously, and comes with a command-line test application in tests/examples/

EncodeBin

Creating encoding pipelines, despite what many people might think, is not a trivial business and requires constantly thinking about a lot of little details. In order to make this as smooth as possible, I have written a convenience element for encoding : encodebin. It only has one required property : a GstEncodingProfile. Once you have set that property, you can then add that element to your pipeline, connect the various streams you wish to encode, connect to your sink element… and put the pipeline to PLAY.

Encoding profiles are not a new idea, and there has been many discussions in the past on how to properly solve this problem. Instead of concentrating on how to best store the various profiles for encoding… I decided to tackle the beast the other way round and, after having sent a RFC to the GStreamer mailing-list and collected as many use-cases as possible, came up with a proposal for a C based encoding profile description (see gst-libs/gst/profile/gstprofile.h). I still have some more use-cases to test and a few extra things to implement in encodebin, but so far the current profile system seems to fit all scenarios.

The remaining problem to solve… is to figure out how to store those encoding profiles in a persistent way for all applications to benefit from them.

Next steps

Using all of the above in PiTiVi :) But also looking forward to seeing comments/feedback/requests from people who wish to use any of the above in their applications.

In addition to that, I will be at the Maemo Barcelona Long Weekend starting from Friday, where we will try to corner down the UI and code requirements for creating a video editor for Maemo. All of the above should make it much easier to do than anticipated :)

Answering questions…

November 20th, 2009 by Edward Hervey

(This was initially posted as a reply to a blogpost regarding PiTiVi being proposed as a default application in the upcoming Ubuntu Lucid. That comment was removed for an unknown reason, so I thought it best to put it here, and it would also be interesting for other people)

What a depressing post (in some aspects). I’ll answer the various questions/comments/rants all the same.

PiTiVi doesn’t support DV/mpeg4/whatever-format

Where did you get that idea from ? PiTiVi doesn’t come shipped with codecs, it relies on GStreamer to provide the needed plugins/decoders/etc… If you load a DV file in pitivi and you don’t have the plugins, the application missing-plugin system should appear proposing you to download the needed plugin.

Collabora pushed PiTiVi aggresively into ubuntu

That’s 100% totally wrong. I personally had chats with Jono and Rick Spencer about having PiTiVi shipped as a default application, and canonical were interested by the idea of having a video editor shipped by default. All of this was far from being enforced, or us (Collabora) going out of our way to have PiTiVi shipped by default. And nothing’s engraved in stone at this point. If we (pitivi development team) get feedback/help on improving what’s bothering people by the Lucid release date and people deem it good enough to be shipped by default, great ! If we get no help… well.. PiTiVi won’t die and people will still be able to use it via PPAs.

Why ship PiTiVi as default app and not another video editor ?

I’d say the main reason is that all the dependencies (except for goocanvas, which is pretty slim) are already shipped by default : GStreamer, GTK, python. All the other editors would require bringing in more dependencies. I’ll let Canonical/Ubuntu confirm that or not.

lack of features …

On this part we have always taken the stand of making sure features are as solid as possible before adding new features. In terms of video editing, that means you do need to have input/output format support rock solid, trimming/cutting rock solid. Check out how many clips/movies/documentaries/… out there and see how much of them make use of video effects, for how long, and how many don’t.
The two features we find critically missing are : video transitions and overlaying. I just merged yesterday the videomixing branch yesterday to master which enables setting transparency on every video streams (like Sony Vegas does). It still has some issues, but having it in master will force/speedup the bugfixing process.
Video effects are not a top-priority. Getting those… without being able to do the features above are pointless. We won’t diverge from that point of view. Helping us get the above rock solid as fast as possible … will mean you will see video effects faster.

To people throwing generic rants about <video-editor-name> sucking

Write a video editor (or any non-trivial multimedia applicatoin), then come back and rant about other people’s application sucking. Then we might have a proper discussion. In the meantime… you’re not improving the situation.

PiTiVi is dead or no longer maintained

The 3 main developers (who also happen to be hired by Collabora and that includes myself) have been working on some other company work in the meantime. Keeping Collabora hiring those 3 developers, means ensuring they have time to be paid to work on it also. (I’d personnaly love to have people working 100% of the time on PiTiVi … but you need to take into account the reality of running a business).
We’re progressively getting more company time for PiTiVi (Brandon has been back on it full time for the past frew weeks for example). It’s far from being abandoned/dead, just that we do it at our own pace. It’s freely available (LGPL, no copryight attributions required) and will always stay that way. We always welcome contributions and are pretty fast to review/commit patches.

Drop in on #pitivi on irc.freenode.net or send us a mail on pitivi-pitivi@lists.sourceforget.net and come and give your feedback, what can be improved, what’s good and should be kept and … who knows … be part of the pitivi team :)

Edward Hervey: PiTiVi creator/maintainer, GStreamer hacker, Collabora Multimedia co-director

PiTiVi 0.13.3 “… we shall never (sur)render”

September 12th, 2009 by Edward Hervey

Hi all,

The PiTiVi team is proud to announce a new release of the PiTiVi open-source video editor.

Features:

  • Fix rendering failures
  • UI beautifications
  • Switch to themeable ruler
  • Speed optimisations
  • Show the project name in the window title

More details can be found in the release notes. As usual, packages are available for debian/unstable as well as Ubuntu Jaunty in the gstreamer-developers PPA.

PiTiVI 0.13.2 “Jailbreak (out of Deadlock City)”

August 13th, 2009 by Edward Hervey

Hi all,

A quick post to announce the latest release of PiTiVi. You’ll be able to find more details here but here’s a short summary of what you can expect:

  • Undo/Redo support
  • Audio mixing
  • Ripple/Roll edit
  • And the usual truckload of misc improvements/bugfixes

Packages should be available really soon on the gstreamer-developers PPA for Ubuntu Jaunty here : https://launchpad.net/~gstreamer-developers/+archive/ppa

And I’m now off for two well deserved weeks of vacation back in France.

PiTiVi 0.13.1 : “L’Aquila Immota Manet : The eagle remains unmoved”

May 27th, 2009 by Edward Hervey

The PiTiVi team is very proud to announce the first release in the unstable 0.13 PiTiVi series.


This release is in memory of those who have lost their lives, friends, houses in the April 6th 2009 earthquake in l’Aquila, Italy.

You will find more info of the changes, bugfixes and so forth in the online release notes here .

To sum up this release :

  • 3 developers working mostly full time : Alessandro Decina, Brandon Lewis and myself
  • An insane QA/usability nazifreak who has overwhelmed the bugtracker with issues : Jean-Francois Fortin Tam
  • Over 700 commits !
  • Complete core rewrite, new multi-layered timeline, audio waveforms, video thumbnails
  • Speed improvements

This is not the end, far from it. We’re already working on the next 0.13.2 release which should be available just before the Gran Canaria Desktop Summit in July with exciting improvements like : transitions, mixing, effects, more speed/memory improvements…

People say an image is worth a thousand words… then I guess a video is worth a million words. Jean-Francois did a screencast showing off the latest features of PiTiVi… and of course edited it with PiTiVi. You can find it in ogg or on youtube. Thanks Jean-Francois !

Enjoy the Show !

PiTiVi video editor 0.13.0.2 pre-release !

May 21st, 2009 by Edward Hervey

We got a bit delayed, but it’s happened at last. The PiTiVi team is proud to announce the first 0.13 pre-release.

Tarball available here: http://ftp.gnome.org/pub/GNOME/sources/pitivi/0.13/pitivi-0.13.0.2.tar.bz2

For those using Jaunty, we’ve also made pitivi (and all required dependencies) available on the gstreamer-developers PPA:  https://launchpad.net/~gstreamer-developers/+archive/ppa

Testing, feedbacks, bug reports are welcome as usual on bugzilla:  http://bugzilla.gnome.org/enter_bug.cgi?product=pitivi

Unless blockers popup, expect the 0.13.1 release next monday (25th May).

Update : I didn’t put the details of the changes since summarizing 700+ commits is not trivial. The release will have more details, but to summarize : back-end rewritten, multi-layer editing, speed improvements and awesomeness :)