Pidgin to Replace Skype

A while back I wrote about the need for a Skype-competator. We discussed this at work and decided to try to transition to XMPP and libjingle a.k.a. Google Talk. Many thanks for all commenters leading me this way.

The decision that we decided to go for was Pidgin (largely because some colleagues prefer OS X). On (k)ubuntu, Pidgin works with video + voice out of the box. It even detected the Mac Book Pro web camera right away – very nice! As Pelagcore is an all-geek-company, the internal transition has been smooth.

Basically, what the solution relies on is XMPP and libjingle. Jingle being an extension to XMPP for voice and audio.

So, what do I miss?

  • The ability to fix spelling errors by going back through the chat history
  • The ability to call land lines from within the application

There is also something that I have to look into – I just need to find the time (and colleagues to bother).

  • Is it possible to make group calls (group chat does work, but with voice and (optionally) video?

Apart from this, all that is left is convincing everyone that I interact with to make the transition.

Distributed MythTV Support Script

It has been a long time since I had time to play with my MythTV setup, but now it finally works. It turns out that the biggest hurdle was not to split the functionality, nor to configure the channels (one just has to get one’s head around the way that MythTV looks at receivers, channels and providers…). The big hurdle was that one of my frontends are connected over WiFi.

The issue was that the frontend application was launched before the WiFi connection was established. This resulted in the frontend running some sort of configuration guide each time the system was booted. Having realized the source of the issue, disabled the autostarting of the frontend and added my own autostart script:


#!/bin/bash

TRIES=0

ping 192.168.1.201 -c 1
RES=$?

while [ "$RES" -ne "0" ]
do
sleep 1
ping 192.168.1.201 -c 1
RES=$?

let "TRIES+=1"
if [ "$TRIES" -gt "100" ]
then
exit -1
fi
done

mythfrontend --service

Here, 192.168.1.201 is the IP of the backend. The script ensures that the backend can be pinged before the frontend process is launched. The end result is a stable boot every time.

MythTV getting TV

For the last few months I’ve run a MythTV frontend/backend combination as our upstairs entertainment center. I use it for SVT Play using Tommy Persson’s excellent plugin, but also to play some music and act as a DVD player.

Yesterday a box arrived with my brand new Hauppauge WinTV-NOVA-TD stick (from a sale on netonnet). Last time I fought with receiving TV through a Linux system, it was a proper struggle. This time, it was just a matter of plugging in the stick, setting up the MythTV backend and watch TV (I admit – I did spend a bit of time sorting and filtering channels, but nothing advanced).

Checking the system this morning, it had recorded all three shows I asked it to – on time. Even the ones colliding in time, i.e. requiring the dual tuners to be used. Very nice!

Now, all I have to do is to setup my dedicated backend machine and get the connection between it and the frontend working. If that goes smoothly,  a card reader and soft CAM would be the next step, but boxer is charging 89+21 SEK per month for a twin card, so I guess that would mean setting up a new frontend downstairs…