After hearing about all the hype around Rock Band for so long, I finally got around to trying it out with some friends the other night. Here’s a pic that Shawn took of us in between sets with me on the bass guitar.

The problem

About a month ago, while at work listening to music on my iPhone 3G, I noticed that certain songs weren’t playing.  The iPhone would pause for a brief moment at the start of the song and then skip to the next one.  It happens so quickly that if you weren’t looking at the screen you wouldn’t notice it.

At first, I thought it was an issue specific to the iPhone.  However, when I tried to play those same songs on iTunes 7.x, they would also refuse to play.   Since I am almost always playing music on “shuffle” (random) mode, it’s easy to see why I didn’t notice this earlier.  In fact, I had no idea how long this was occurring.

The odd thing was that these same songs would play in other media players like Windows Media Player, Winamp and Foobar2000.  It was just iTunes, and consequently the iPhone, that was giving me problems.

After researching the problem by scouring the web, I found that this was in fact a common problem hitting a lot of users.  I read a ton of suggestions, some dating back quite a few years.  Here are some of the suggestions that I found and tried in desperation:

• Deleted the ID3v2 tag and rebuilt it
• Disabled “Allow applications to take exclusive control of this device” from the advanced properties of my sound card
• Re-installed DirectX
• Removed song from iTunes Library and Re-added it
• Completely uninstall iTunes and re-install it

None of these worked and I was making no progress.   I even tried upgrading to iTunes 8 hoping that it would be one of the hidden bug fixes.  Unfortunately, the new version of iTunes didn’t help.

Finding a solution

After quite a few more days of troubleshooting and experimenting, I finally stumbled upon the solution.  It turns out that the MP3s that wouldn’t play had out of spec MPEG headers, which I verified and repaired using a freeware tool called MP3 Validator.

I scanned my entire library of music and turned out that about 60% of my music collection suffered from this problem.  Since only a subset of these songs wouldn’t play in iTunes (but would play fine in others), it seems that while iTunes is tolerant of some MPEG header errors it is not as forgiving as all other media players I tried.  Since I”m positive these songs played on older version of iTunes 7, something must have changed under the covers along the way in later iTunes update.

After scanning and repairing all the afflicted songs in my library, all my music happily plays in iTunes (and my iPhone).

Step-by-step guide on how to fix your music

Here’s a quick guide on how to fix this problem using free tools in case you’re suffering from the same problem.  I’ll show you how to fix one song, then you can use the same technique on your entire library if you need to.

1. Download MP3 Tag Validator and extract it to a folder on your PC.  It doesn’t require any installation.
2. To start the program, just run mp3val-frontend.exe. You’ll be shown a simple application window:
3. (Optional) First thing I did was to enable the option Keep file timestamps since I didn’t want all the timestamps to change from the repair.  Go to File | Preferences and make your configuration look like this:
   
4. Find one of the songs that won’t play in iTunes and add it to the MP3 Validator window.  You can either drag-and-drop it into the main program window, or you can go to File | Add File(s).  For me, one of the songs was Stealth by Way Out West.
5. We’ll now run a scan of the file first, to see if you are suffering from an MPEG header problem.  Click Actions | Scan all. The app is quite fast and you’ll get a modal confirmation dialog almost right away.  Dismiss it with OK.
6. In order to see the results of the scan, you have to select the song in the main window, and then you’ll see status messages from the scan in the status area.

   Here is a copy and paste of the output, from which I’ve bolded the specific MPEG errors that are present in the file:

   Analyzing file "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3"…
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3" (offset 0xa301a3): Garbage at the end of the file
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": Wrong number of MPEG frames specified in Xing header (13122 instead of 13056)
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": Wrong number of MPEG data bytes specified in Xing header (10711873 instead of 10658221)
   INFO: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": 13056 MPEG frames (MPEG 1 Layer III), +ID3v1+ID3v2, Xing header
   Done!

7. Now that we’ve verified there are indeed MPEG header errors, let’s fix them.  Click Actions | Repair all files.  Similar to the scan we did in step 6, you’ll see a modal confirmation dialog informing you the repair was completed.  After dismissing the dialog, select the song and you’lll see a more detailed confirmation of the repair in the status area:
   

   Analyzing file "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3"…
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3" (offset 0xa301a3): Garbage at the end of the file
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": Wrong number of MPEG frames specified in Xing header (13122 instead of 13056)
   WARNING: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": Wrong number of MPEG data bytes specified in Xing header (10711873 instead of 10658221)
   INFO: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": 13056 MPEG frames (MPEG 1 Layer III), +ID3v1+ID3v2, Xing header
   Rebuilding file "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3"…
   FIXED: "D:\Music\iTunes\iTunes Music\Way Out West\Intensify\06 Stealth.mp3": File was rebuilt
   Done!

8. You should now be able verify that the song now plays in iTunes.  Since MP3 Tag Validator doesn’t rename the file, you won’t even have to re-import the song into your iTunes library.

In the default configuration, MP3 Tag Validator keeps a backup of the original song in the same directory with the added file extension .bak. If your library was as big as mine and spread over countless sub-directories, you’ll want to clean this up to reclaim the disk space.  In Vista, this was really easy using the file search in Windows Explorer.  ALl you have to do is run a search in the root of your music folder for “ext:*.bak” (without the quotes) and you’ll get search results for all the backup files that were made  Just select them all and delete them and you’ll reclaim all the disk space.

Alternatively, you can configure MP3 Tag Validator to delete the backup files when it successfully finishes repairing the files, but I opted against this as I wanted to be absolutely certain the repaired files were OK before deleting the originals.

I really hopes this helps and saves time for at least one other person out there.  I problems wasted a total of 12 hours over the course of week trying to figure this out.

As soon as I upgraded to iTunes 8 I immediately noticed a problem where clicking the “Next track” button when shuffle was off would skip ahead 2 or 3 songs instead of going to the next track.  After consulting with a few friends that couldn’t reproduce the problem, I realized it was something specific with my setup.  I started up iTunes in safemode (hold CTRL+SHIFT as you start up iTunes) to disable all plugins:

After doing this, the problem was solved! This obviously meant it was one of the plugins I had installed was the culprit, which meant it was either the plugin from iLike or Last.fm.

I first uninstall Last.fm, but that didn’t fix it, so I then uninstalled iLike. Bingo!  Problem was immediately solved.  To make sure it was specifically the iLike plugin, I re-installed the Last.fm plugin to double check.  Yup, iTunes was working as expected still.

I’ll have to shoot a bug report over to Craig, who is now working at iLike to get them to fix this.  It’s good having “connections” sometimes!

We threw up a landing page today to help customers find our international stores we shipped more easily at http://store.microsoft.com:

After a rocking the Yaletown wordpress theme for a few years, I’ve decided to try out something different.  I wanted something a little simpler looking, and since I’m blogging mostly about photos these days, I wanted it to be based on a white background.

After digging around for awhile, I stumbled upon the Celeny theme which jumped out at me because it was 2 columns, ad-sense ready and supported widgets.

After installing it and mucking around with customizing it for my liking, I’ve got it in a state I’m reasonably happy with. The theme author didn’t do that great of a job allowing you to customize it through the Wordpress UI. Instead, I had to dive into the PHP code and make changes directly which I always hate doing since future upgrades of the theme will cause me to lose all my customizations.

There are some layout problems on the sidebar currently that I still need to fix, but I figure before I invest time in doing that, I’ll rock the theme for a few weeks to see how my loyal blog readers like it, and also how adsense performs with the theme.  I’ve reduced the overall ads on the site to a single 250×250 adblock in the sidebar, so it will be interesting to see if fewer ads that are less intrusive will outperform my previous attempt.

Let me know what you think!