Gstreamer

We’re happy to have released gst-dots-viewer, a new development tool that makes it easier to visualize and debug GStreamer pipelines. This tool, included in GStreamer 1.26, provides a web-based interface for viewing pipeline graphs in real-time as your application runs and allows to easily request all pipelines to be dumped at any time. What is gst-dots-viewer? gst-dots-viewer is a server application that monitors a directory for .dot files generated by GStreamer’s pipeline visualization system and displays them in your web browser. It automatically updates the visualization whenever new .dot files are created, making it simpler to debug complex applications and understand the evolution of the pipelines at runtime. ...

For the last years, the GStreamer community has been analysing and discussing the idea of merging all the modules into one single repository. Since all the official modules are released in sync and the code evolves simultaneously between those repositories, having the code split was a burden and several core GStreamer developers believed that it was worth making the effort to consolidate them into a single repository. As announced a while back this is now effective and this post is about explaining the technical choices and implications of that change. ...

GStreamer Editing Services OpenTimelineIO support OpenTimelineIO is an Open Source API and interchange format for editorial timeline information, it basically allows some form of interoperability between the different post production Video Editing tools. It is being developed by Pixar and several other studios are contributing to the project allowing it to evolve quickly. We, at Igalia, recently landed support for the GStreamer Editing Services (GES) serialization format in OpenTimelineIO, making it possible to convert GES timelines to any format supported by the library. This is extremely useful to integrate GES into existing Post production workflow as it allows projects in any format supported by OpentTimelineIO to be used in the GStreamer Editing Services and vice versa. ...

WebRTC is a w3c draft protocol that “enables rich, high-quality RTP applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols”. The protocol is mainly used to provide video conferencing systems from within web browsers. https://appr.tc running in WebKitGTK A brief history At the very beginning of the WebRTC protocol, before 2013, Google was still using WebKit in chrome and they started to implement support using LibWebRTC but when they started the blink fork the implementation stopped in WebKit. ...

Collabora ltd. has been developing a tool that allows GStreamer developers to check that the GstElements they write behave the way they are supposed to: GstValidate. The tool was started first to provide plug-ins developers with a tool to check that they use the framework the proper way. Since the beginning, it has been available in gst-devtools, a gst module where we collect a set of tools to facilitate GStreamer development and usage. ...

So as suggested by the title, the work I did during the Google Summer Of Code has been Merged! It means that the next Pitivi release which should arrive quite soon will gain effects. I haven’t been blogging for a long while so sorry about not telling you what was happening but I did it in order to make a surprise :P Now that it is merged, you are very welcome to test it and report all the bugs you will find so we have a great release soon to propose the world…. with effects! ...

Sorry for not blogging in such a long time! Now that I am back in chile afer the GUADEC, I have finally been able to hack again on Pitivi. So has I said during my presentation of my project during the GUADEC, I implemented everything I wanted to. So I am now working on debugging everything, cleaning code, and even if I have a few remaining critical bugs (which could probably be bugs in gnonlin), you can use it for testing purposes. ...

I didn’t blog for almost 3 weeks but it doesn’t mean I didn’t progress with this project. I thing it actually means more that I prefer to spend my time on coding than on blogging! Last week was pretty full because of the end of the semester but tomorrow I have my last examen for university. Next week I am planning to go skiing so it may not be the week I will be hacking the most, but anyway, I will code! ...

I didn’t blog for almost 2 weeks now because I wanted to have something interesting to say before saying it! So the last 2 weeks I started an experimental branch to handle effects in the timeline and of course corrected all the bugs I found during this time. Then I rethought this design with nekohayo and got this pretty cool mockup from him: So as you can expect, I am now implementing that. I already rewrite the effect list and it looks the same as you can see in the mockup. And I am working on making effects being per clip or per track instead of being considered as clips themselves. This should actually be pushed by the end of the week. ...

This week I have been debugging everything and I final (Thanks to my mentor Edward Hervey) got effects working! So better show you how it works for now. It is still quite buggy, and not really ergonomic, but it is the beginning! Here is the video (of course edited in Pitivi and using effects). The original host (people.collabora.co.uk) is gone, so the video is no longer available: You need a modern browser to see this video (chromium, firefox, epiphnay, midori…) ...

Here is my second report about the implementation of effects in Pitivi. I am going quite well with this project, and I now have almost everything ready to be able to add effects to videos. The dragging of effects to the timeline is almost ready, but I need to work on it a bit more to be able to show you a screen-cast! I hope it can be done next week. ...

Here is the first report about my Google summer of code project. I have been working quite a lot on it for the last 2 weeks! So here is the summary of what have been done so far: Code reading, analyze of Pitivi architecture (Thanks to the pitivi wiki) Some reading about Gstreamer to understand better the way it works Creation of my git branch to start working on effects implementation Implementation of the core Pitivi modifications to be able to create effects (With unit tests) See how I can implement effect files as described in my Gsoc application, and discussions about it in the Pitivi community. We actually didn’t take a fixed decision about this for now. Creation of the UI to show the list of effects detected thanks to the gstreamer registry (the list was already retrieved in Pitivi) Some talking to know how this UI should be done. I will need to talk more about that to the Pitivi community to take a good decision about how it should look like. For now, it looks like: ...