GNOME Asia 2015

I've just arrived back from GNOME Asia and it's time to blog about the experience there.

The trip to Jakarta was relatively uneventful. An early train to Sydney started the day followed by the trip to Singapore. A tight connection (1 hour) combined with switching terminals made life a little interesting. The fact that one of the Changi terminal connection AirTrain's was out of service meant we were bussed across the tarmac. Then to find the gate and the aeroplane, and the short trip to Jakarta.

After landing in Jakarta, I was meant to meet up with a local Indonesian, however different terminal exit points meant that we missed each other and a phone call was necessary on another local's mobile phone. After meeting there was a bus trip followed by a KRL (train) trip followed by a ride on a Ojek (motorcycle) which made for an interesting trip to my sleeping quarters. A local meal was followed swiftly by some horizontal time.

Some early breakfast consisting of an interesting mix of bread, cheese and condensed milk was followed by a short walk to the conference venue where the workshops were to take place. As can be seen from the schedule The workshops started out with the a talk about the GNOME Indonesian translation. The workshop was presented in Bahasa Indonesia unfortunately which I could not understand. He however had lots of pictures and gleaned some information from them. The following workshops by on contributing to GNOME and creating your first GNOME application were an interesting experience on how some people enter the GNOME contributor ecosystem. During the day, some fellow GStreamer hackers Arun and Nirbheek arrived and a mini reunion was held.

I attended a number of talks about using and promoting GNOME within the Indonesian shoe industry, the GNOME release cycle and a number of lightning talks. I also met a number of new people from Europe, David, Ekaterina, Alexandre and Andre. Originally I had planned on giving a rather technical talk on integrating GStreamer video and Gtk+ with respect to API use and best practices. However, after the first day, I felt a more general overview of the topic would fit better with the audience. So I adjusted the focus of my talk to include a more general overview of video handling within GStreamer

Overall, it was a time well spent catching up and meeting new people. I would like to thank the GNOME Foundation for sponsoring my travel.

Comments

Post a Comment

Popular posts from this blog

GStreamer RTP Session Handling in Rust

Recently we at Centricular had the opportunity to write some new GStreamer RTP elements in Rust as part of a grant from the Sovereign Tech Fund . We of course jumped at the chance. The existing RTP elements are all currently written in the C programming language and have been around for over a decade. The age is showing somewhat with some of the architecture decisions and user visible interfaces. There is also a general desire within the GStreamer community to write parsers and other elements handling potentially untrusted data in a much more memory safe language, like Rust. As a bonus, Rust comes with better tooling out of the box for developers than C/C++. In this blog post we will be looking into how RTP sessions are managed in GStreamer, independent of the specifics of a particular RTP payload format. The Prior Art: rtpbin In GStreamer, the pre-existing interface for handling RTP sessions is managed by the rtpbin element. The rtpbin element is over 15 years old and ha...
Read more

GStreamer 1.6 and OpenGL contexts

With the imminent release of GStreamer 1.6 there has been a change in the mechanism by which OpenGL contexts and Window System (X11, Wayland, Win32, OS X's Cocoa) specific resources are shared with a GStreamer pipeline for elements that need that information. Elements like sinks or any of the GL elements or any global application provided information that is shared between elements. Previously, in 1.4, there was a property, 'external-opengl-context' available on some(!) elements that one could set on the current set of filter and mixer elements (not sink or source elements though!). While it mostly worked well enough, it was a behaviour difference to how window system handles are shared between the application and the GStreamer pipeline. Internal GL context sharing between elements was occurring in the ALLOCATION query as a value in a GstStructure of the meta:GstVideoGLTextureUploadMeta parameters. The main problem with this is 1. the ALLOCATION query is handled diffe...
Read more

qmlglsink - GStreamer and Qt's QML

Windows Support - NEW!! Just recently, I added the missing piece for adding Windows support for qmlglsink for QtQuick 2 applications (tracked by this bug ) with this commit which means that qmlglsink is now usable on all major platforms 1 . With the list of supported platforms (Android, iOS, OS X, Windows, Linux) for qmlglsink growing, I thought I'd write a little bit about it and why you should use it. qmlglsink is a GStreamer element that will render a video stream into a QtQuick QML scene. As you can see from this example , qmlglsink does this by providing a GstGLVideoItem QML item that can be placed anywhere in the scene. The GstGLVideoItem is given a unique name to be able to link the element and the QML item. Without this link, the element cannot render the stream anywhere and will fail changing state. In the C++ code, we then retrieve the GstGLVideoItem by name like so . Then we set the pipeline to playing, start Qt's mainloop and watch the show. Why Use qml...
Read more