Thursday, May 24, 2007
Squeezebox update: iTunes support redux
Well, the vbrfix program didn't work quite as advertised, and borked the mp3s I ran it on. Fortunately, they had all been converted from FLAC, so restoring was simply a matter of re-running the flac-to-mp3 script (which does take a while to chew on 300G of music.) But the "Fix MP3 Header" option in "foobar2000" does the trick, and now iTunes is happy with my MP3s. But since fb2k is a Windows app, it means that the incremental conversion process when new FLAC files are added has a manual step, rather than one I can script.
Thursday, May 17, 2007
JCiP best seller at JavaOne 2007
For the second year in a row, Java Concurrency in Practice was the best selling book at the JavaOne bookstore...thanks everyone!
Monday, April 23, 2007
At JAX in Wiesbaden this week
I'm at the JAX conference, in Wiesbaden, Germany this week (www.jax.de.) I'll be speaking on Wednesday evening on (what else) concurrency and performance.
Sunday, April 15, 2007
Squeezebox update: iTunes support
There are lots of tools for dealing with audio files of various formats (MP3, FLAC, AAC, Ogg, WMA, etc), but most of them fall down when it comes to letting you deal with an entire library of music files. (I suppose some of them must be good, but there are so many, you get tired of trying them.)
I've mostly fallen back on scripting-based approaches. When I rip using EAC (which rips to WAV, which has no tagging features), I instruct EAC to create a file that has all the relevant tags (title, artist, genre, etc) embedded in the file name, and I've got a script that feeds these into the flac encoder, creates files using a directory hierachy of the form /artist/album/track.flac, and sets the appropriate flac tags.
I downloaded another script (http://robinbowes.com/projects/flac2mp3) that takes this directory and creates a parallel directory of MP3 files, transcoded from the flac. It uses LAME to do the encoding, using the "--alt-preset standard" settings, and I point iTunes at that directory. So far, so good.
Well, iTunes seems confused by VBR (variable bit rate) MP3s that it didn't encode itself. The symptom is that iTunes thinks the tracks are way longer than they are.
After much searching, the best alternative I came up with was to use a program called 'vbrfix' (http://www.willwap.co.uk/Programs/vbrfix.php), which rewrites the mp3 headers in a way that iTunes is happy with. (It claims to fix other problems too. The documentation sucks, and I had to download the source and build it (with no make file, just guessed, but it wasn't hard), and it does appear to render the MP3s compatible with iTunes.
I've mostly fallen back on scripting-based approaches. When I rip using EAC (which rips to WAV, which has no tagging features), I instruct EAC to create a file that has all the relevant tags (title, artist, genre, etc) embedded in the file name, and I've got a script that feeds these into the flac encoder, creates files using a directory hierachy of the form /artist/album/track.flac, and sets the appropriate flac tags.
I downloaded another script (http://robinbowes.com/projects/flac2mp3) that takes this directory and creates a parallel directory of MP3 files, transcoded from the flac. It uses LAME to do the encoding, using the "--alt-preset standard" settings, and I point iTunes at that directory. So far, so good.
Well, iTunes seems confused by VBR (variable bit rate) MP3s that it didn't encode itself. The symptom is that iTunes thinks the tracks are way longer than they are.
After much searching, the best alternative I came up with was to use a program called 'vbrfix' (http://www.willwap.co.uk/Programs/vbrfix.php), which rewrites the mp3 headers in a way that iTunes is happy with. (It claims to fix other problems too. The documentation sucks, and I had to download the source and build it (with no make file, just guessed, but it wasn't hard), and it does appear to render the MP3s compatible with iTunes.
Sunday, January 28, 2007
Interview on Software Engineering Radio
Tune in to Software Engineering Radio to hear the interview Marcus Voelter did with David Holmes and I at OOPSLA 2006.
Tuesday, January 16, 2007
JCiP named Jolt Award Finalist
2006 Winners and Finalists
JCiP was named a finalist in the 2006 Jolt Awards in the technical books category.
JCiP was named a finalist in the 2006 Jolt Awards in the technical books category.
Friday, January 12, 2007
Mama's got a squeezebox...
A number of friends have asked about my Squeezebox home audio setup, so rather than repeat myself, I'll write it up here.
Squeezebox is a device that you attach to your home network and your stereo, streaming digital music to your stereo system. There are lots of such devices on the market; Roku's Soundbridge, Apple's AirTunes, and offerings from networking companies like Netgear and Linksys. I chose Squeezebox because it has a digital (optical) audio out, meaning that what gets piped into my expensive stereo is not going through the analog stage of a $20 sound card. The model I have has a wireless (802.11g) interface and a wired ethernet port as well; I paid about $250 each, and we have them in multiple rooms so you can listen to any music from any room without fussing with physical CDs. (You can even sync them so you can have the same music throughout the house, say for parties.)
My primary motivation for this transition was that I hate CD furniture; it's mostly ugly, and takes up an obscene amount of room in your living room if you have any reasonable size music collection. Even transferring from jewel cases to sleeves, which gives about a 2.5:1 space compression, CDs can overwhelm your living room.
The first challenge: ripping the CDs. This is the most time consuming step, so I did not want to have to do this again because I had chosen the wrong audio format. There are three components to ripping: the audio extraction, the association of metadata (artist, title, genre) with albums and tracks, and conversion to the format of choice (mp3, wma, etc.) As with many other situations, you can get all-in-one solutions like iTunes or Windows Media Player that will do all of these in a single step, or you can have more control over each step but have to deal with multiple programs.
It turns out that nearly all rippers do not take advantage of the error-correcting information present in CDs. So if you have a scratched CD, you'll get bad bits when you rip, and those bad bits will stay with your recording forever. The only Windows-based tool I know of that will use the error correction is EAC (Exact Audio Copy). It's not as slick as iTunes, but it will usually get you a perfect rip. For CDs in good condition, it can usually rip at 10x, ripping a whole CD in 6 minutes or so. If it detects bit errors, it will slow down and keep reading until it is satisfied; for one really badly scratched CD (one that wouldn't even play in my car), it chewed for 24 hours, and got all but ~1000 bits off!
EAC will rip to WAV, and has a mechanism to post-process to further launch an external converter (mp3, wma, etc), which I did not use. Instead, I saved the WAV files to disk and post-processed them separately. iTunes and WMP can access the commercial CDDB database that associates metadata (artist, album, track names) with albums and tracks; EAC uses the open-source freedb database, which is convenient but whose data quality is less than perfect. Expect to spend some time correcting titles and genres that don't match up (e.g., the first CD of a set is called Volume One, where the second is called Disc 2, or one volume lists Rock as the genre, where the other lists Pop). You can do this through EAC or using an ID3 tag editor, but in any case, expect to spend some time cleaning up the data.
For my storage format, I chose FLAC, the open-source lossless audio compression, which stores files in about 55% of the space of the WAV file. This about about three times bigger than a good VBR MP3 or AAC, but disk space is cheap -- real cheap. (As of this writing, 500G drives are going for less than $200.) And the time to re-rip is very expensive. I set up the ripper on Windows to write the output files to a drop folder on my Linux server (named using a convention that embeds the track, artist, album, and genre, since WAV doesn't support metadata tags), and have a home-grown perl-script (willing to share, just ask) that will find the files and feed them to the flac converter.
Squeezebox versions 2 and later support FLAC native, so it doesn't have to transcode to MP3 on the fly. This is nice because the transcoding interfers with fast forward / rewind functionality on the Squeezebox. So, following the chain, error-free RIP courtesy of EAC, lossless conversion to FLAC, digital transfer from server to squeezebox, lossless FLAC decompression to PCM on squeezebox, digital out to receiver -- meaning no end-to-end signal loss, and digital-to-analog conversion done by my receiver. Just as if I'd plugged the CD player's optical out into the receiver.
For the server software, the free SlimServer package is written in Perl so can run on Windows, Linux, or Mac. I chose Linux since I did not want to downgrade the reliability of my stereo to that of my Windows desktop. (I have a Linux server in the house anyway, but if you don't, you can build one fairly cheaply.)
If you want to transfer to your iPod or other device, you need to transcode from FLAC to MP3 or AAC or WMA or whatever your favorite portable format is. The best MP3 encoder is called LAME (open source); you then have to decompress from FLAC to WAV, and pipe that into LAME to get an MP3 out. (I believe iTunes for Mac has a LAME plugin, but not iTunes for Windows.) LAME encoding using VBR (variable bit rate) takes a while. Disk space is cheap enough you might consider an automated nightly script to encode all new FLAC files into a parallel tree of MP3 files for transfer to iPod, if iPod is a big enough part of your life.
Once you get all the ripping done, it's pretty nice. It took me about a week to rip ~400 CDs "in the background" while I was working. Thereafter, the only time you need to find the physical CDs is if you want to play them in the car. And the SlimServer software has a web interface that lets you create playlists and such, so you can set up playlists for parties so you don't have to be fussing with CDs.
Highly recommended. We've got two squeezeboxes now (living room and bedroom) and are considering adding more (kids room, family room). Plus there's a software player you can use on the computer.
Squeezebox is a device that you attach to your home network and your stereo, streaming digital music to your stereo system. There are lots of such devices on the market; Roku's Soundbridge, Apple's AirTunes, and offerings from networking companies like Netgear and Linksys. I chose Squeezebox because it has a digital (optical) audio out, meaning that what gets piped into my expensive stereo is not going through the analog stage of a $20 sound card. The model I have has a wireless (802.11g) interface and a wired ethernet port as well; I paid about $250 each, and we have them in multiple rooms so you can listen to any music from any room without fussing with physical CDs. (You can even sync them so you can have the same music throughout the house, say for parties.)
My primary motivation for this transition was that I hate CD furniture; it's mostly ugly, and takes up an obscene amount of room in your living room if you have any reasonable size music collection. Even transferring from jewel cases to sleeves, which gives about a 2.5:1 space compression, CDs can overwhelm your living room.
The first challenge: ripping the CDs. This is the most time consuming step, so I did not want to have to do this again because I had chosen the wrong audio format. There are three components to ripping: the audio extraction, the association of metadata (artist, title, genre) with albums and tracks, and conversion to the format of choice (mp3, wma, etc.) As with many other situations, you can get all-in-one solutions like iTunes or Windows Media Player that will do all of these in a single step, or you can have more control over each step but have to deal with multiple programs.
It turns out that nearly all rippers do not take advantage of the error-correcting information present in CDs. So if you have a scratched CD, you'll get bad bits when you rip, and those bad bits will stay with your recording forever. The only Windows-based tool I know of that will use the error correction is EAC (Exact Audio Copy). It's not as slick as iTunes, but it will usually get you a perfect rip. For CDs in good condition, it can usually rip at 10x, ripping a whole CD in 6 minutes or so. If it detects bit errors, it will slow down and keep reading until it is satisfied; for one really badly scratched CD (one that wouldn't even play in my car), it chewed for 24 hours, and got all but ~1000 bits off!
EAC will rip to WAV, and has a mechanism to post-process to further launch an external converter (mp3, wma, etc), which I did not use. Instead, I saved the WAV files to disk and post-processed them separately. iTunes and WMP can access the commercial CDDB database that associates metadata (artist, album, track names) with albums and tracks; EAC uses the open-source freedb database, which is convenient but whose data quality is less than perfect. Expect to spend some time correcting titles and genres that don't match up (e.g., the first CD of a set is called Volume One, where the second is called Disc 2, or one volume lists Rock as the genre, where the other lists Pop). You can do this through EAC or using an ID3 tag editor, but in any case, expect to spend some time cleaning up the data.
For my storage format, I chose FLAC, the open-source lossless audio compression, which stores files in about 55% of the space of the WAV file. This about about three times bigger than a good VBR MP3 or AAC, but disk space is cheap -- real cheap. (As of this writing, 500G drives are going for less than $200.) And the time to re-rip is very expensive. I set up the ripper on Windows to write the output files to a drop folder on my Linux server (named using a convention that embeds the track, artist, album, and genre, since WAV doesn't support metadata tags), and have a home-grown perl-script (willing to share, just ask) that will find the files and feed them to the flac converter.
Squeezebox versions 2 and later support FLAC native, so it doesn't have to transcode to MP3 on the fly. This is nice because the transcoding interfers with fast forward / rewind functionality on the Squeezebox. So, following the chain, error-free RIP courtesy of EAC, lossless conversion to FLAC, digital transfer from server to squeezebox, lossless FLAC decompression to PCM on squeezebox, digital out to receiver -- meaning no end-to-end signal loss, and digital-to-analog conversion done by my receiver. Just as if I'd plugged the CD player's optical out into the receiver.
For the server software, the free SlimServer package is written in Perl so can run on Windows, Linux, or Mac. I chose Linux since I did not want to downgrade the reliability of my stereo to that of my Windows desktop. (I have a Linux server in the house anyway, but if you don't, you can build one fairly cheaply.)
If you want to transfer to your iPod or other device, you need to transcode from FLAC to MP3 or AAC or WMA or whatever your favorite portable format is. The best MP3 encoder is called LAME (open source); you then have to decompress from FLAC to WAV, and pipe that into LAME to get an MP3 out. (I believe iTunes for Mac has a LAME plugin, but not iTunes for Windows.) LAME encoding using VBR (variable bit rate) takes a while. Disk space is cheap enough you might consider an automated nightly script to encode all new FLAC files into a parallel tree of MP3 files for transfer to iPod, if iPod is a big enough part of your life.
Once you get all the ripping done, it's pretty nice. It took me about a week to rip ~400 CDs "in the background" while I was working. Thereafter, the only time you need to find the physical CDs is if you want to play them in the car. And the SlimServer software has a web interface that lets you create playlists and such, so you can set up playlists for parties so you don't have to be fussing with CDs.
Highly recommended. We've got two squeezeboxes now (living room and bedroom) and are considering adding more (kids room, family room). Plus there's a software player you can use on the computer.
Subscribe to:
Posts (Atom)
