Encoding audio and removing file extensions from files

tariq — Fri, 24 Jul 2009 06:41:28 +0000

Earlier today I got a massive SCORM object that contained lots of mp3 files. They were all high quality files, so I wanted to cut them down in size for web use. For this purpose I am using ffmpeg which you can easily get for Windows, Linux or Mac. I tried the following on a Mac, but it should also work on Linux (paths permitting) and on Windows if you are using something like cygwin.

I highly recommend you get familiar with ffmpeg as it is amazingly useful. Just check out the man pages; swf to avi, avi to something that works on ipods, all a breeze!

So lets start and end with entering the directory which contains all our audio files on the command line. Once inside this directory we can use:

find . -type f -name *.mp3 -exec ffmpeg -i {} -ac 1 -ab 32k {}32kb_m.mp3 \;

Now, as you can see, I have created a new file for each original file. Each new file’s name is appended with 32kb_m.mp3 which tells me information about how the new mp3 file is encoded and gives hints to ffmpeg as to the files format (mp3 and encoder). Let me explain a little about the command. With find we are saying find stuff in the current directory which are files and end in “.mp3″ and when you find them execute ffmpeg. The {} bit is expanded with whatever file findfound. With the ffmpeg bit we are saying our lord of ffmpeg please take as input this file fromfind‘s output and set the number of audio channels to 1 and the bitrate to 32kbp/s and then output the file using the settings to a file whose filename is the same as our input file but has 32kb_m.mp3 added to end.

Now we have created our new files and checked everything is ok (you should have those audios backed up somewhere too) we want to move all these new files to the locations of the originals. Our command moves/renames the files, removing part of the filename, recursively. Here it is:

find . -type f -name *32kb_m.mp3 | sed 's/\(.*\)32kb_m.mp3/mv "\132kb_m.mp3" "\1"/' | sh

So, again we use find! Here we are saying find, in the current directory, all files with file names ending in “32kb_m.mp3″ . Here we are only, hopefully, pulling out our newly created files. Next we pipe all this data to sed. We tell sed: hey Mr. Sed, look for any set of characters that are followed with “32kb_m.mp3″ and replace the entire string (including 32kb_m.mp3) with “mv [the bit matched before 32kb_m.mp3]32kb_m.mp3 [the bit matched before 32kb_m.mp3]“. Very simple, I hope! We are taking the big list from the output of find and using sed to transform the output into lots of mv commands. If we pipe these commands to sh then all those commands get executed. Hey presto, we’re done!

How much space did you save?

All my mp3s were in ‘audio’ which I copied to ‘audio_32kb_m’. I then entered audio_32kb_m by cding into it and executing the commands above. Below is the output from du which tells me the total size of my audio directories. Size reduction is around 75%.

snapple:/tmp tariq$ du -hs audio*
 33M	audio
8.5M	audio_32kb_m

The post Encoding audio and removing file extensions from files appeared first on GL.IB.LY.

Searching compressed Apache logs

tariq — Tue, 23 Jun 2009 06:27:23 +0000

From time to time things tend to go wrong and systems tend to go crazy. Sometimes these errors are more of nuisance than anything else, an intermittent annoyance you’d prefer not to investigate — trawling through logs is a pain in the backside. Now you need to take a peak at those compressed Apache error log files, ugh! Well before you look for suitable places to hang some rope try running some expressions across a certain number of files. Normally you’d only want to look at logs for the last 7 days, so lets give that a go.

The error messages I am interested in all contain the text Healthcheck so I will use trusty grepfind matching lines in the logs. I will use find to get me all the files modified in the last seven days. A program called xargs will then be used to call cat which will pipe to a compression program which finally pipes to grep. Put this all together and you get something like this:

find /var/log/apache2 -type f -name "error_*.bz2" -mtime -7 | sort | xargs cat | bunzip2 | grep"Healthcheck"

If your files are tar.gz then you’ll need to replace bunzip2 with gzip -dc. So that would look like:

find /var/log/apache2 -type f -name "error_*.tar.gz" -mtime -7 | sort | xargs cat | gzip -dc |grep "Healthcheck"

Have fun!

The post Searching compressed Apache logs appeared first on GL.IB.LY.

GL.IB.LY » find

Encoding audio and removing file extensions from files

How much space did you save?

Searching compressed Apache logs