Archive for March, 2007

Treesex

It’s that time of the year again. The time where I invest heavily in the pharmasutical industry; specifically the producers of Alavert. It makes the itching go away, melts in your mouth, and it tastes good! Unfortunatley, its eight flippin dollars a box–and you only get twelve.

It’s never fun when you are rudely awakened by the feeling of asphyxiating on your own mucus. I feel sorry for Jimi Hendrix, because choking on bodily fluids while you sleep would be an incredibly sucky way to die. Fortunately the TSRB has a great ventilation system, so if I camp out here I’m unaffected. Well, that’s where I spend all my time anyway. I’m good.

Comments

Profound words

Question: What is the chief end of man?
Answer: Man’s chief end is to glorify God, and to enjoy him for ever.

These words were written in a sermon by Thomas Watson, an early puritan pastor. How simple, yet resonant can two sentences be? Recently I have ejoyed reading some puritan and other older works. I am considering a copy of Body of Practical Divinity. If anyone has any other suggestions, feel free to post!

Comments

I cried

I still like funny cat pictures. My friend josh sent me a link a little while ago with some classic material that made me cry. I would add commentary, but most of these are best served dry.

TechCat

Christkitty

Wheelz

Legoz

Snow

Danger

AZNcat

Ewok Kitty

Comments (5)

Quotage

Eric sent me a couple of really good /. quotes that I should share:

It took me one day to get online. The detail is tedious and highly technical: reinstalling drivers and router firmware didn’t work, but after many trial and error tweaks to Vista’s TCP/IP settings, I had internet access.

I had to post that one based on my recent anti-vista diatribes.

So, what you’re saying it’s kind of like installing an oddball wi-fi card on Linux. Except without the option of reading hundreds of pages of obscure documentation until you’ve transformed yourself into a mutant linux hotplugging guru.

D10 has been having troubles installing his wifi card on SuSE, so I’m sure he can relate to that one. And finally, my favorite:

In a nutshell, the difference between getting things working in Linux and Windows seems to be this. Linux is like being parachuted into the wilderness with a hammer, forge, and load of pig iron. Windows is like being parachuted into the wilderness with an impressive looking knife that snaps in two if you don’t use it very, very carefully.

I booted up XP earlier today to do some webdev for a side project that I am involved with. After becoming accustomed to XGL/Compiz and Gnome: XP seemed lifeless. Two dimensional. Dead. Also, I have started noticing how slow XP is on certain functions; especially inside Visual Studio 2005. Granted, opening a terminal and using sed/grep to search and replace an entire group of .c files for an obscure function call is not for the weak at heart, but it is definately more satisfying for the inner hardcore geek in me. Yes fanboys, I know that visual studio has find/replace.

Visual Studio 2005 is quite possibly the best IDE that I have ever used. However, part of me has yearned toward a purest approach to coding. Turns out, if you give me EMACS with some customized LISP plugins for syntax highlighting and windows style cut/copy/paste then I am perfectly happy. VS2005 seems to be taking all the thinking out of coding; which after all, is Microsofts goal for the product anyway. That’s not a bad thing, necessarily. I don’t like setting up all the extra library includes inside VS2005. The last time I tried to us a standard distribution of openGL it took me 30 minutes to fix all the linker problems. It’s much simpler for me to simply add -l or -L and simply tell the makefile where the library lives.

I’m ranting because I’m feeling novel. It’ll probably wear off later. =)

Comments (1)

Mp3ize

I recently won a black 30GB video iPod for second place in Georgia Tech’s campus iMovie fest. It’s really sexy. I can understand now why all the Apple fanboys are drooling all over themselves. It has a slick interface, sounds much better than my little 512MB rio, and it works as removable storage.

After I got it I brought it to my office, unpacked it, and hooked it up to my system. Amarok and SuSE found it, initialized it, and it was automagically ready to transfer music/files/videos. No annoying restarts because of driver installs, or waiting on the OS to find my device. Were I on Windows I would have to go through the pain of downloading and installing[sic] iTunes, waiting for Windows to figure out that something new has been connected, wait for the driver installs, and then begin transfers.

Something most unfortunate for consumers is the restriction of file formats for certain branded mobile audo devices. I am not about to convert my entire 6000+ song archive from .wma to .aac. First off, aac is DRM, and second off, they all sound nearly the same.

Depressing? Fret not ye who ripped all your cd’s to wma. Linux to the rescue.

I wrote two small shell scripts that search a directory structure for wma’s and convert them to 250kbps VBR LAME encoded mp3. I won’t go into the details of CBR vs. VBR, but trust me when I say it’s better. Also, word is from Lorenzo the compression expert that conversion from high bit rate wmas to VBR mp3s should not result in too much signal degradation. W00t.

mp3ize

#!/bin/bash
 
# look for wma's and run convert on them
find . -name "*wma" -exec convert {} ;

convert

#!/bin/bash
 
set -e
old_name="$1"
cat_name=`basename "$1"`
path=`dirname "$1"`
nospaces=`echo $cat_name | sed -e 's/  */_/g' -e 's/_-_/-/g'`
new_name="${path}/${nospaces}"
 
#echo ---------
echo $old_name
#echo $path
#echo $cat_name
echo $new_name
 
if [ "${path}/${old_name}" != "$new_name" ];
then
   mv "$old_name" "$new_name"
fi
 
mplayer -ao pcm:file="${new_name%.wma}.wav" "$new_name"
lame -V 0 --vbr-new "${new_name%.wma}.wav" "${old_name%.wma}.mp3"
rm -f "${new_name%.wma}.wav"
 
mv "${new_name}" ~/.Trash/

Copy the source into two files named mp3ize and convert respectively, and toss them in your usr/bin/ directory. Then cd into the top directory where the files you wish to convert live, and type mp3ize. Watch for commas in path names because it will cause the script to skip those files or misname them. It will often cut off everything after the comma. This is a limitation of bash scripting, so we will have to live with it.

One thing that I would like everyone to note is my CPU usage graph:

System resource graph

Notice that it’s pretty much pegged at around 100%. As of right now I am typing this blog, running eclipse, seeding a DVD on bittorrent, and running around 9 other terminal tasks all while the mp3ize script is running. When’s the last time you could actually use your Windows system when CPU usage was near 100%? Never. Ever. It should also be noted that I do not have a dual core CPU.

Comments (2)

« Previous entries