streamripper: Keeping local copies

It’s been a while since I’ve seen an audio stream ripper — in fact, I think the last one was fIcy, way back when this site was just starting up.😐

So here’s streamripper, which does something similar to what fIcy does, but seems a little better prepared for the task.

2014-10-28-6m47421-streamripper

What I remember most about fIcy is that without an -o flag, it would dump its output to the screen, and with an -o flag … it didn’t quite work right.

So seeing streamripper effortlessly pull down a stream, dissect the individual files at their correct start and stop points, nest them in a neat tree of folders, and set aside tracks that are incomplete … well, it’s very pleasant to watch.

streamripper is not new. In fact, it looks like it faded away (I need a better term than that for software that stalls) around 2008. That’s the bad news.

The good news is, I don’t imagine much has really changed in the past six years in the way streaming music is broadcast, or for that matter, how mp3s work. Both technologies are pretty much solid at this point.

So if you can deal with the awful public shame of using six-year-old software, streamripper appears to be a viable option for capturing your favorite online audio. And if you can’t deal with that big a lag in software development … well, you’ve come to the wrong place, bub.:\

Edit, 2014-11-02: I got a little coaching from wavexx (an fIcy maintainer) and fIcy seems to be working for me now. It’s been a while since I wrote the original post about fIcy so I’m not sure what my problem was the first time, but wavexx helped me iron it out.🙂