My thoughts on Slackware, life and everything

Month: June 2010 (Page 2 of 2)

KDE SC 4.4.4 available for Slackware 13.1

I asked Pat if he was planning on an early start of slackware-current now that the sources for KDE SC 4.4.4 are available. But he said, go ahead, build your own set.

So here they are, my packages (32-bit and 64-bit) for Slackware 13.1 that give you KDE SC 4.4.4!

The routine has not changed, and the README explains the simple upgrade process as always. This time, it is even easier because I did not have to update or add any dependencies. The KDE and KDEI packages are all that’s new.

There will be a source release of KDE 4.4.5 too, somewhere near the end of june, and then it’s waiting for a stable 4.5 release. I have no idea if there are going to be Slackware packages for 4.4.5 in slackware-current, but I am going to invest some time in checking out the build process for KDE SC 4.5.

Have fun! Eric

Edit (07-jun-2010):

And oh, there is an easy way to mirror my KDE packages… using rsync! The rsync URI is rsync://alien.slackbook.org/alien-kde/ and these are the commands to either download 32-bit packages (will create a local “x86” directory) or 64-bit packages (will create a local “x86_64” directory):

$ rsync -av –progress rsync://alien.slackbook.org/alien-kde/4.4.4/x86 .

$ rsync -av –progress rsync://alien.slackbook.org/alien-kde/4.4.4/x86_64 .

Note the dot at the end of the command!


Re-encoding video for Android

So I bought myself a nice Android phone in april. It’s a HTC Desire, a real “tweakers’ phone”. It runs Android 2.1 – and before the end of the year, HTC should have an update to Android 2.2 available.

It is an impressive piece of work, and when I compare it to the iPhone or Windows Mobile based phones some of my friends/collegues carry with them, it clearly gives me a lot of freedom – I do not have any desire to “root” or “jailbreak” my phone in order to make it do what I want. I dream of putting Slackware on it, sometimes, but then I usually wake up fast… It’s a real Linux phone (with a SSH and a VNC client installed from the Android Market!), and the HTC Sense interface makes it just perfect and enjoyable as it is.

It goes without saying that I took a flat-fee Internet subscription; this kind of phone is not fully functional unless it is always online. I have been running a bandwidth metering app which told me that I transfered 440 MB in my first month. That would result in a pretty heavy bill if I did not have unlimited traffic.

I may write some more about my experiences with the Desire in future posts (so may exciting things to tell!), but for this one I want to talk about video playback on Android. Android has decent multimedia support out of the box, and audio as well as video players can make use of the standard codec libraries that the Android platform offers.

The “native format” I think you may call it that, for the Android seems to be H.264 video and AAC audio in a MP4 container. There are some limitations however, as people found out when trying unsuccessfully to play MP4  video files on their Android device that would not have had playback issues on a normal PC or mediabox.

Android only supports the H.264 baseline profile, meaning that some of the fancy encoding tricks that give you great video quality at lower bitrates (but require more processing power on playback) can not be used for videos you want to play on your Android device.

And rest assured, you do want to watch videos on the 800 x 480 pixel WVGA screen of the Desire! The AMOLED display has fantastic vibrant colours.

So, in order to create a video file that fits the display dimensions perfectly (without the scaling/resizing which would result in an ugly picture) and contains fully compatible MP4 video, I once again turned to my faithful companion… ffmpeg.

Here is a ffmpeg command line for you. This will take a video file (any supported format will work as input) and produce an Android-compliant MP4 file with WVGA dimensions (800 by 480 pixels). The input file will be transcoded in a two-pass process in order to achieve the best possible results. The transcoding will take a long time, so find something else to do in the meantime.

$ ffmpeg -i [inputfile] -threads 0 -vcodec libx264 \
    -vpre slow_firstpass -vpre baseline -b 480k -r 13 \
    -acodec aac -ab 128k -sameq \
    -pass 1 -f rawvideo -an -y /dev/null && \
    ffmpeg -i [inputfile] -threads 0 -vcodec libx264 \
    -vpre slow -vpre baseline -b 480k -r 13 \
    -acodec aac -ab 128k -ac 2 -sameq -pass 2 [outputfile].mp4

If you are on Slackware, then you get lucky. My ffmpeg packages (the variant that supports AAC audio encoding) are right here: http://slackware.org.uk/people/alien/restricted_slackbuilds/ffmpeg/

Have fun experimenting!

Eric

ffmpeg fully supports webm video

Today, the ffmpeg developers have completed the integration of the Google-sponsored VP8 codec and associated new WebM video container format.

The WebM video container format as well as VP8 decoding were added a little while ago, and the last part – VP8 video encoding – has entered the repository now. External patches are no longer required.

The ffmpeg package which I had built for Slackware 13.1 a couple of days ago, can encode VP8 too but I had to apply the patches made available by the WebM project (and which have now been more or less completely absorbed by ffmpeg). I’ll rebuild my ffmpeg package soon, getting rid of the patches, thus having a less complex build.

The only thing that seems to be missing compared to the patches from the WebM project, are the preset files specific to the VP8 encoder. As an example, ffmpeg has several preset files for x264 – they greatly simplify the ffmpeg commandline by gathering a lot of encoder settings into one configuration file. I’ll look at how I can add those presets to my package, in case the ffmpeg folk don’t do it first.

Eric

Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑