General

On Sawfish, Metacity and Linus

11 Comments

Managed to get myself embroiled in a little email exchange with Linus about configurability options and GNOME. Seesm that little exchange even managed to hit Slashdot.
The misconception that I feel Linus have and a lot of the people posting on Slashdot is that patches that adds configuration options to GNOME would automatically get rejected. This is simply false.

At best this is an extrapolation of the quite strict policy of Metacity in particular and the general GNOME policy of ‘no GUI options before thinking’. This policy did come into effect with GNOME 2.x and it came about both due to UI design usability discussions, but also as a result of seeing our config menu’s get clogged with options which mostly where there due to bugs, missing features and a heterogen deployment environment below GNOME. It was decided to focus on actually trying to solve these lower level issues instead of offering config options to work around them. A talk by Jim Getty’s at GUADEC called ‘Draining the swamp’ being considered the call to arms on that issue. Projects such as HAL, the rejuvenated X.org effort and many other freedesktop projects came about almost as a direct consequence of this.

There was also some misconceptions on the Sawfish to Metacity switch that happened in this time period. It is not correct to say that Sawfish got replaced by Metacity due to it being deciding its high degree of configurability was bad, far from it. Sure there
where people who felt Sawfish went a bit overboard in that regard, but that was not the reason it got ditched as the default GNOME window manager. The reason for that was simply that after Eazel went backrupt and Sawfish maintainer John Harper had to find a new job, he ended up at Apple. And thus due to Apple corporate policy, and probably long hours at work, he couldn’t maintain Sawfish anymore. The troublesome thing about Sawfish was that it was written in its own Lisp dialect so as part of Sawfish you got both an extra lisp interpreter and GTK+ bindings for it. This meant that the C/C++ skills in the GNOME community didn’t lend themselves well to fixing bugs in Sawfish.
The two libraries and Sawsfish itself thus went unmaintained as John went away and nobody where interested/felt qualified to take it over. Thus the GNOME developers had to look around for a new window manager and it was decided that one should aim for one written in C like the rest of the desktop libraries to lessen the chance of future maintenance prolems. To answer this call Havoc Pennington stepped up with Metacity and it was quickly adopted by a lot of GNOME developers and users and subsequently chosen as the standard.

Metacity was philosophically very different from Sawfish and Havoc
was very strict about what he let into Metacity, due to an idea that requests for config options was usually a result of broken behaviour in the window manager and thus feeling the behaviour should be fixed instead of a config option added to work around the problem.
This was in line with the policy that do govern GNOME as mentioned above, but in the case of Metacity this was applied in a much sterner/hardcore fashion that for most other modules.
But due to Havoc’s high profile in the community and beyond it I think the policy he kept for metacity colored how people outside the project perceivedthe project as a whole which is the main reason I see for this hard killed perception to live on.

Anyway, back to Linus and his irritation with Metacity. I can’t not say if his patches will go in or not, its not my call. But I did at least add them properly to bugzilla for Linus to ensure they get reviewed and commented on at least.

GStreamer

More on GStreamer Windows and Mac support

3 Comments

Thought I should follow up on yesterdays post about Windows and MacOS X with some more information. The work is done in collaboration with the great guys behind the SongBird
music player. Those who don’t know Songbird its a very cool cross platform Music player built using XUL, the same GUI toolkit used to make Firefox. The idea is that by making sure GStreamer runs perfectly on Windows and MacOSX in addition to Linux/Unix they can use GStreamer as their backend across all platforms. The Songbird guys are doing some very cool things around web integration of their music player so I recommend everyone to take a look at their onsite demo.

Anyway to show of where we are at here is a screenshot. The screenshot shows our small proof of concept Windows mediaplayer playing a video under Windows. For a more full featured experience look to future versions of Songbird.

You can download binaries for Windows including the little sample player here on this site maintained by Sebastian Moutte who is our resident Windows porting expert.

We are a little shorter along on the Mac side of things as the Mac videosink is currently leaking memory like crazy and screenshots of audio playback tend to be a bit less interesting :). We expect squish those leaks and polish it up further in the next few weeks so I can provide a nice screenshot of GStreamer on MacOS X too.

We are implementing the GStreamer XOverlay interface accross all these video sinks. That means that you should be able to write a video player without any kind of special casing across platforms for video and audio output, GStreamer’s output autodetection should take care of it for you. So for Songbird it will let them write the code embedding the video window once and it will work using native video output on both Windows and MacOSX in addition to under X Windows of course. When these elements are 100% finished and polished up I think porting things like Totem or Pitivi to Windows and MacOSX should be quite trivial in theory with both GTK+ and GStreamer running natively on these platforms. That said practice tend to prove that there would be some work involved :)

It should also be mentioned that thanks to Songbird we are not only able to provide these elements to the community, but they will be fully documented and polished up. This means the Windows and MacOS X output support will be 100% solid and not just ‘checkbox’ level.

GStreamer

gst-phonon code now public

8 Comments

Some time ago I announced that we would be working on a GStreamer backend for Phonon. This work is still ongoing, but we have now put the code into the GStreamer CVS repository. The code is still early stage, but at least those interested can now follow the code as it progresses. One thing people will notice is that the current code is still all C which I guess most people would find strange for something meant to be used with Phonon. Well the idea is to provide the Phonon components with both a C and a C++ API. So the current code is meant to both be usable from C and also be easily used to power the GStreamer backend for Phonon. We decided on this approach as we found that since a lot of the work on implementing a GStreamer backend for Phonon was actually about writing some high-level GStreamer components and at that point we came to the conclusion that offering people to use them with a C API in addition to the official Phonon C++ API made quite a lot of sense. The code and design so far have been done by Wim Taymans, but in order to get more focus on the development from here on we will have David Gerber take over from here and work exclusivly on this for a the next months.

GStreamer for Mac OSX and Windows

Those following GStreamer CVS will have noticed that there has been quite a few commits recently for audio and video output plugins for Windows and Mac OSX. This is not a coincidence as we are currently working on a project to ensure that GStreamer works perfectly on these operating systems. The Windows audiosink and videosink should already be in working order and the MacOS X audio sink also works fine. We still have some work needed on the MacOS X video sink, but we hope to have that done by the end of the Month. With these plugins in place writing a cross platform application with GStreamer should be very easy so I suggest anyone working on crossplatform development take a look at the plugins and try them out on their own systems.

Elisa priorities

I know a lot of you are waiting for us to add PVR support into Elisa. This task is making its way quickly up our todo list, but one thing we are going to try to tackle first is how we handle large media collections. Anyone who has ever run Elisa will notice that while it looks very nice the current GUI concepts are not very practical when you want to find/play one specific song in a collection of many thousand. We consider this the top issue atm in order to make Elisa not only look nice but be really nice :)

In Elisa related news the first official release of Coherence happened today. Coherence is a Python Upnp framework developed by Frank Scholz and is the framework we use for all the upnp goodness in Elisa.

ffmpeg pains

Back in the day we tried relaying on ‘released’ versions of ffmpeg in GStreamer. The problem was that there never really was any releases of ffmpeg and the versions that floated around all tended to have different API’s. So what we discovered was that when distributions packaged GStreamer and a other multimedia systems using ffmpeg one or the other always tended to end up broken. So in the end we gave up on relying on ffmpeg as an external dependency and instead set up a system to ‘suck in’ snapshots of ffmpeg into the GStreamer ffmpeg plugin and thus avoid the problem of different applications conflicting due to relaying on different versions of ffmpeg.

Well it seems some of the major distro’s have decided that they want a return to the painful old days. The problem is that even to this day ffmpeg change its API’s more often than Linus Torvalds change his socks and they still don’t do proper releases, thus relaying on it as a shared library is a pain. Yet distributions in the name of security and not wanting duplicate copies of the code installed are now trying to get all their ffmpeg using systems to share one install. So if you get tons of weird error messages on your console when running a GStreamer application, please dont blame us, but instead email the package maintainer for your distribution with your frustrations.

Oddball entries

Morocco trip

2 Comments

So I managed to get the Marocco photo’s
online tonight so I thought I document the trip for posterity.

Marrakesh

Stayed at the Atlas Asni
hotel. Not a backpacker place for sure, but not horribly expensive either. My impression of Marrakesh and most of the towns we found in Marocco was that they where effectivly two towns. You had the old city which was still within their original medival city walls and next to it a new modern city. Marrakesh featured a lot of beautiful architecture, especially the Bahia Palace stood out. While there Wim and I visited/got lured into the taneries, was an interesting visit both visually and smell wise :). We also got hijacked into a local leather and carpet shop and which both Wim and I was each a carpet richer and a bit of money poorer. Also signed up for an evening at Chez Ali which is a gigantic resturant and folklore show. The show was definetly interesting, but I couldn’t help but feel that it felt a little short due to little things like for instance giving you some insight into who the dancers and groups represented in terms of Moroccan society and maybe a bit more choreography to the horse show. But still definetly worth it. We also figured we couldn’t visit Marocco without riding a camel so we signed up for a trip with local trip organizers Sahara Expeditions. We signed up for their 2 day trip which included one night in a berber tent in the dessert. Turned out we ended up traveling with a fun group of people, including two crazy Canadians called Oryan and Jeff. While the camel trip and the desert stay was fun I did regret not signing up for the longer trip though, the trip we took did end up being mostly two days in the car back and forth with only hour or two of camel riding at each end. Also we noticed that there where a lot of cute backpacker girls signed up for the longer trip :). That said both Wim and I ended up quite cripled for a few days just from the little camel riding we did so maybe we did ok as it was :)

Back from the desert we rented a car and set of for Fes, deciding for a little detour past the d’Ouzoud waterfal on the way.

Trip to Cascade d’Ouzoud and Fes

We decided to go by the d’Ouzoud waterfall on our way to Fes. As it turned out we never found the actual waterfall, but we drove through some beautiful mountain terrain. We also ended up staying in the town of Khenifre instead of reaching Fes. Khenifre was maybe not a terribly interesting town from a sightseeing perspective, but it was a pleasant change in the context of people giving us non-inflated prices for things like the hotel room. I guess not being a tourist town had spared them from slipping into the mindset that every foreigner is a walking cash dispenser.

Fes and Rabat

Next day we drove into Fes to look around the old city. Fes being the old city of learning and religion I have to admit I where a bit disapointed in the town. Had expected more in terms of architecture for instance. Of course having caused a chain collision on the way into town I guess we might have been a little bit to edgy to really enjoy the town :). Drove down to Rabat in the afternoon and spent the morning after sightseeing around. Rabat is the administrative capital of Marocco and used to be the adminstration town of the french. It shows with one of the major landmarks in the town being the church built by the french.

Casablanca

Casablanca had three major events/sights. We did a guided tour of the Hassan II Mosque. It was a very beautiful building, but walking through the slums on the way to the mosque you couldn’t help but wonder if it really was money well spent in light of the problems of the country.

The second fun stop was Rick’s Cafe which was an attempt to recreate Rick’s Cafe from the classic movie Casablanca. Such things tend to easily end up cheesy, but I have to say that in this case it had been pulled of beautifully. Part of the reason for that is that it was clearly done as a labour of love and not primarily as a business venture.

The last don’t miss waypoint in Casablanca I have to recommend is the Bodega de Casablanca. Its a Spanish bar/resturant with a great menu and a great athmosphere. I ended up seeing more bullfighting and listening to more spanish music during the hours I was there than I has for all my years in Spain :). To top if off they have a nightclub in the cellar which seems to be the place to go for the young and beautiful of Casablanca. It comes with a great DJ and crew. Stay away from the places called nightclubs in Casablanca though, they are generally horrible places.

Marocco and free software

As a sidenote, what struck me in Casablanca was that it could be a great place to host GUADEC. So any local enthusiasts interested should definetly think about it and get maybe send a proposal to the GUADEC comitee :)

Oddball entries

Off to Marakesh

1 Comment

So Wim and I are going on a vacation/hiking trip to Morocco this evening. We are flying into Marrakesh and will be staying there for a few days. Apart from that we don’t have any concrete plans apart from our return flight Sunday in a week :). At this point even the hotel reservation we thought we did seems a bit flaky, but hopefully we at least avoid sleeping in the gutter. Wish us good luck!

GNOME

The endless Linux ready for the desktop discussion

3 Comments

Slashdot has a story from a guy giving up on using Linux on the desktop. When looking into it what he is actually giving up on is having a ‘rogue’ linux system seamlessly integrate into a Microsoft environment. The community is getting better all the time at providing technologies that will emulate your Windows software of choice, but unfortunatly Microsoft is not standing still so its chasing a moving target. So unless you have an IT organisation which is interested in truly supporting Linux you will proably always have some pains. On the other hand I do believe that for a lot of corporate environments Linux is ready for their desktop as long as they want Linux on their desktops. Meaning they tune their purchasing strategies and software choices to doing this.

That said I have myself been thinking about the state of the desktop. As I to have been part of this community for a long time now and there do always seem to be a new big hurdle to cross before we reach Desktop nirvana. Sometimes it can be a bit disencouraging. But if I look back to when I started out with Linux and compare the problems then to the problems we face today I realize that we have gotten a lot closer to being where we want to be. A lot of applications simply didn’t not exist on Linux when I started out. In fact the only two advanced desktop applications I can remember being at a level where they fullfilled my needs where Netscape and Gimp. Today there are a host of applications in most major categories. Applications that come to mind are Inkscape, OpenOffice, Evolution, Gaim, Ekiga, Totem and Rhythmbox.
For instance I remember getting my friends to switch to use Yahoo messenger as it was the only IM service I managed to get working under Linux at the time.

Hardware support has gotten a lot better. When I first installed Linux on my laptop back then I spent a full weekend to get basic audio working on it by grabing CVS versions of ALSA and trying to figure out magic options in the alsarc file. It also seemed like the only time hardware got detected under Linux at that point was during install so when I changed hardware I tended to end up re-installing Linux on the machine. That problem could have been avoided had I understood more of how linux worked back then, but today its not an issue as installing new hardware seems rather automated. I also remember spending a lot of time trying to get Linux to be able to read the ‘Joliet’ CD’s I burned under Windows. Linux at the time only supported another standard at the time (which there was only 1 burning application I ever saw which supported under Windows and that one was silly expensive).

CD burning under linux only existed in the form of the command line cdrecord application, which it took my quite some time to figure out.
Today my burning needs are mostly taken care of by Nautilus.

Hardware support is today as back then still an issue. But it is much less of an issue and hardware that is supported tend to be so in a much more ‘real’ way. Back when I started ‘supported’ meant ‘you can get it to work if you spend a few days on it’, today ‘supported’ means it will plug and play.

We have succeeded in creating standarized abstractions or subsystems for most things today. So when someone writes a new driver you don’t need your application to specifically support it anymore. As long as it is written towards this shared interface it will just work. I am sure there are still some subsystems which are not perfect yet in this regard, but lets face it we are currently working on fixing usability issues more often than we are looking into the ‘how can we get this type of thing to work somewhat at all’ kind of issues.

Its like libgimme-codec. We are not trying to solve the problem of ‘how do we get any kind of support for media playback’ anymore, instead we are trying to solve the problem of ‘how can we do this in the most userfriendly way possible, given the constraints we are facing’.

We might not be there 100% yet, but looking a few years back in time do make it clear we are moving forward rapidly. And I don’t think we need that many more major announcement like the recent Novell Peugeot Citroën deal before the hardware makers all realize that the Linux desktop is here to stay and needs to be supported properly.

Article with some quotes from me

Nathan Willis recently interviewed me about the codec shop launch Fluendo did.
The result is on
linux.com now. The result was less of an interview and more an article than I expected, but I guess it still explains a few things around our shop launch.

General

A cool video blogging idea

2 Comments

A bunch of us from Fluendo where out yesterday at a local bar with Internet access. As such things go we started playing a bit with our Nokia 800’s and the video conferencing feature. What suddenly struck me is that it would be great to have a small application which connects to a googletalk account and just listens for incoming talks. You should then be able to call this account and the application will just accept the inncoming talk and then record it to disk, by muxing it into a container format and maybe transcoding it to Theora/Vorbis. That way you have a easy way to record little video blogs as you travel around and store these on your home computer. The next step then of course would be some kind of youtube extension that let you upload the video clips automatically to youtube or something like that :)

Just proposed the application to the Make it with Mono competition that Miguel blogged about recently. Hopefully it will make it through the moderation so I can try plugging it when the voting starts in April. Should be fairly easy to build this on top of GStreamer and Telepathy (which are also used in the Nokia 800)

GNOME

The lagging fortunes of XaraLX

7 Comments

About a year ago the source code and linux port of XaraLX was announced to much fanfare and excitement. Unfortunatly things haven’t developed that well as time has gone by. First of all Xara has had limited resources to devote to the project themselves and there has been little in the form of a developer community formed from the outside. What I learned to my suprise today is that part of the reason for this is because Xara depends on a binary blob called cdraw/gdraw which is similar to pixman in Cairo. This among other things keep most distro’s from shipping it. Not sure what will happen with XaraLX now, but one hope would be that someone sat down and ported the XaraLX code from cdraw/gdraw to Cairo. And through that make it a truly free software application. Xara is interesting and should have a chance to fullfill a need alongside Gimp and Inkscape.

Nokia 800

A little later than the rest of the herd I got my Nokia 800 today. It is a worthy upgrade to the 770. Especially with Tigert’s Plankton theme it looks and feel very snazy.

My main frustration though from the 770 is still there, and that is that when entering new streams to the internet radio I have to have the actual stream uri, the playlist uri which is the most easy/common to find is not supported. That said finding the place to enter such uri’s is much easier now compared to the 770.

One feature we look to get into Pitivi is a Nokia 770/800 output profiles. So if you want to prepare a video to take on a trip you just choose the Nokia 770/800 profile and it will get transcoded into a video using the optimal combination of codecs and imgae size/framerate to play back on your device. New release of Pitivi out today btw, so be sure to check it out.

Miguel on ODF vs OOXML

Miguel has a very interesting blog entry discussing the ongoing ODF vs OOXML ISO debacle. Since he linked to an email I sent not long ago regarding SVG I felt a bit compelled to comment on that part of his essay. I agree that it is weird to attack OOXML on its lack of use of SVG when OpenOffice don’t support it, but instead use its own OOD format. On the other side just because ODF fucked up in this area doesn’t mean OOXML need to repeat the stupidity. Of course if they do end up using SVG then it would be a bit funny as suddenly for graphics at least OOXML would be a better and freer standard than ODF is :)
Miguel also points out the size of SVG as a problem with SVG, to which I agree, but the solution I have advocated for a long while within the librsvg community is to aim to support the SVG Mobile profile as it is for the most part the sensible subset of SVG we are all looking for. Speaking of librsvg it is in maintenance mode currently. Caleb who pushed many of the major changes for a long while has gone AWOL unfortunatly and Carl Worth is naturally putting most of his energy into Cairo itself. Dom is still around maintaining and holding the fort, but lacks the possibility to take librsvg the last steps to match the SVG Tiny profile. So if anyone out there is interested joining the librsvg team to flesh out the remaining holes in librsvg to actually conform fully with one the W3c SVG specs then please drop by #librsvg on Gimpnet or join the mailing list.

General

Dirac encoder/decoder coming along nicely

6 Comments

So we have been working on the Schroedinger Dirac implementation for some time now and its starting to come together now.
The decoder is pretty fast and works well and the encoder is getting quite close too although its default settings needs to be moved away from developer settings. Not exactly sure where we stand in terms of being compliant with the latest Dirac specification, but we should be quite close as most of Dave’s commits recently have been about taking us the last few steps towards compliance. Anyway here is a screenshot I took today which is showing a video I created using this pipeline:


gst-launch-0.10 filesrc location=Dolphins_1080.wmv ! decodebin2 name="decode" decode. ! ffmpegcolorspace ! videoscale method=1 qos=false ! "video/x-raw-yuv, width=(int)640, height=(int)480" ! ffmpegcolorspace ! schroenc ! queue ! oggmux name=mux ! gnomevfssink location=file:///tmp/dolphins.ogg decode. ! audioconvert ! vorbisenc ! queue ! mux.

Two things stands out in this screenshot, one is that we need the Dirac plugins to report their codec and bitrate to the GUI :) The second is that the encoder needs tweaking so we don’t get the blur shadow at the ‘borders’ between different items in the image.

Blog talking about Fedora, GNOME, GStreamer and related topics

css.php

Bad Behavior has blocked 703 access attempts in the last 7 days.