Mar 08, 2008 9:29 AM
After discovering that unicode MP3 tags confuse my Alltel Hue cell phone's music player, I of course needed to fix the broken files. But I didn't want to figure out which they were by trial and error - we have a big music collection!
I cobbled together some code that I had sitting around, and created a little command-line utility that checks mp3 files to see if the tags are unicode.
If you found this post because you're looking for a solution to the same problem, you might find this useful. It requires .NET 2.0. Use the command-line argument -h for instuctions.
Mar 05, 2008 11:12 AM
One of the cool features of the Alltel Hue phone that Katrin and I have is the built-in music player. I recently started using this and found that some of my mp3 files show gibberish for the album and song information.
After a little research I figured out the source of the problem; the problem files have their tags stored in unicode. The phone can't understand this and shows the wrong characters.
There are a lot of tools out there for manipulating mp3 tags, but the one I've found that can fix this issue is Mp3tag. I don't have to reload the tag information; just set the appropriate options in the software, open a folder full of music files, and choose the save option from the file menu. The 16-bit tags are overwritten with 8-bit information and the phone can now understand them.
Update: I wrote a little console application to check which files have unicode tags.
Feb 18, 2008 7:07 PM
We've got three people working together on a specification, and a master document in Word seemed like the way to go. Once I figured out how to do it in Word 2007's newfangled menus it was easy enough to set that up. (Go to View/Outline, and check out the Master Document section on the Outlining Menu.)
But when the files are uploaded to Project Server, I can't open the master document. Bummer. Looks like this wasn't supported in the past, but I can't find any specifics on the current versions.
Jan 26, 2008 2:21 PM
I write about solutions to random computer problems here in the hopes that someone will run across them on Google and save some time. Here's one that would have saved me some time if I had written about it the first time I had to fix it.
I couldn't access folders with access restrictions on my Buffalo Linkstation from my new Vista machine. I had my user set up, and the multiple connections stuff didn't seem to apply.
I found this article that rang a bell for me. Vista has different ways of negotiating permissions over the network. Basically it doesn't use the old, less secure XP method, and the Linkstation doesn't support the new one. The steps in the above link (which didn't work for me, perhaps because I'm not logged in as administrator,) just change a registry setting.
Buffalo actually has a "patch" under the utility section of their downloads page (choose the linkstation option in the droplist.) This is just a registry key file which changes a single key:
Change the value from 3 to 2 and restart. Presto, explorer logs in with the current user and password, as expected. Assuming that this has previously been set up on the Linkstation.
Jan 22, 2008 10:17 AM
I just found out that the canvas page URL for a facebook application is case sensitive.
So if the application is at http://apps.facebook.com/myapp, then the URL http://apps.facebook.com/MyApp will not work. Be careful when sending out links to your application!