After settling upon this design nearly two years ago, I was sure there would be some bugs to crop up – and I found them. Being CSS based, not only text based browsers dislike it, but Konq 3.3.x seems to dislike my css divs due to a bug in it’s handling of border code. It will render the full div as inherited if you specify a border to inherit.

I will be toying with the CSS live at times, so pay no heed if it looks strange.

I must say I was shocked this afternoon to find an email asking me when My Music would be fixed. I noticed that the bandwidth use had gone downhill – but it never did more than a few hundred megs a month, anyhow. After looking at my base64 encoded URLs, I realized that I still had the references in place for my old test domain, the now defunct ‘esrc.us’. Oops!

This has since been rectified. Dave, I feel sorry for your ears. Why anyone would want to hear my horrible remake of modfiles (on ten dollar headphones, none the less) is beyond me, but you’re welcome to ‘em!

I’m starting to appreciate the abilities of DCOP:

%./amaroktunewatcher > Notification: New Song (Streaming): Tom Wax – Maximal ssl > Notification: New Song (Streaming): Absolum – Push | Album: Sub Science > Notification: New Song (Streaming): Mili Sefic – 04 > Song has not changed. > Song has not changed.

Yeah, so all I’ve done so far is interface amaroK, so I can keep a small list of the last few songs I’ve listened to. It’s amazingly trivial. I have it take the current song and stuff it into a variable. If that variable doesn’t match the last-known song, then update the list, checksum, and ping my backend database here on my website. Practical upshot? I’ve got that tiny little ‘Last song’ blurb on the front page. An exercise in futility? Perhaps. It’s still fun, though!

amarok is a media player for the KDE desktop environment.

The ‘configure’ script is a bit broken under FreeBSD. Thankfully, we know what the root of the problem is, being, that parameters are not being properly passed, and it’s not making the files it needs for the program to function.

I wrote a quick little shell script, which, if dropped into the source tree for amarok, will do all of the proper patching to make amarok buildable.

I posted my simple little hack on the KDE board, and will hopefully be cleaned up and added to the amarok port, if the configuration is not patched. However, since most folks who find this will be through Google, here’s the code:

#!/bin/sh MYDIR=`pwd` if [ -d amarok/src ]; then cd amarok/src echo ”>>> Compiling configurations…” kconfig_compiler ./engine/gst/config/gstconfig.kcfg /engine/gst/config/gstconfi g.kcfgc kconfig_compiler ./amarokcore/amarok.kcfg /amarokcore/amarokconfig.kcfgc cd ../.. ./configure LDFLAGS=-pthread $* MYFILES=`find . -name \*.ui -print` for n in $MYFILES; do THISDIR=`dirname $n` THISFILE=`basename $n` CPPFILE=`echo $THISFILE | sed s,ui,cpp,` HEADERFILE=`echo $THISFILE | sed s,ui,h,` cd $THISDIR echo ”>>> Processing $THISFILE…” uic -o $HEADERFILE $THISFILE uic -o $CPPFILE -impl $HEADERFILE $THISFILE cd $MYDIR done sed s,”KWizard”,”QWizard”, < amarok/src/firstrunwizard.cpp > amarok/src/firstrunwizard.cpp1 mv amarok/src/firstrunwizard.cpp amarok/src/firstrunwizard.cpp.bak mv amarok/src/firstrunwizard.cpp1 amarok/src/firstrunwizard.cpp echo ”>>> Ready to build amarok!” else echo ”>>> Error: You must place this file in the amarok source directory!” echo ”>>> You are in: $MYDIR” exit 1 fi

For the terminally lazy (pun not intended), I’ve created a tarball of a modified /usr/ports/audio/amarok tree for amarok 1.2.2.

%gzip -dc amarok-1.2.2-FreeBSD-port.tar.gz | (cd /usr/ports/audio; tar xvf -); cd /usr/ports/audio/amarok; make install clean

Good luck!

Mosu has released MKVToolNix 1.4.1, primarily a bugfix version. Here’s a partial bugfix log:

* mkvmerge: bug fix: AC3 detection was broken in rare cases. * mmg: bug fix: If the TEMP environment variable contains spaces then the calls to mkvmerge when adding files failed. * mkvmerge: bug fix: Extracting the FPS from some AVC MP4 files did not work. * mkvmerge: bug fix: Appending + splitting was segfaulting if used together and at least one split occured after a track has been appended. * mkvmerge: Added more descriptive error messages if two tracks cannot be concatenated because “their parameters do not match”. * mkvmerge: bug fix: A failing call to posix_fadvise will only turn its usage off for that one file and not abort mkvmerge completely.

... and many, many more. You can get the goods here.