iVolume

If it's really true that iVolume 2 will no longer work properly with iTunes 7.7.1 and newer, then that really stinks. Because quite frankly, $30 for this one-trick pony is a bloody insane ripoff, and I simply won't pay it. It was well worth the $7 it originally cost, and I was even willing to pay again when it doubled in v2, but the developer is getting awfully greedy now, and $30 is absolutely RIDICULOUS -- especially when you consider that the core "work" done by this app is done by an open source algorithm painstakingly written by SOMEBODY ELSE, given away for free, then taken by this schmuck and wrapped in a simple GUI that gets unnecessarily gunked up with CPU-wasting and pointless animations while the price -- for the exact same algorithm and results (which is all the work of someone ELSE) -- doubles every release. I no longer recommend this to anyone, and I will never support this guy ever again.

IVolume 3.7 crashes immediately on startup. I use a iMac27 and latest version of Mavericks. Anyone having the same issue? No problems however when returning to iVolume 3.6.6.

As of iTunes 11 (or maybe one of the later versions of iTunes 10.x), I've run into a lot of songs in my library that are no longer playing at the correct volume level. It used to be possible to "nudge" iTunes into re-reading the iTunNORM value from the file, but the old trick for this (editing some tag, then changing it back) no longer works. 1. Selecting multiple songs and changing one or more tag values no longer causes iTunes to refresh the SoundCheck value for those songs. Absolutely nothing will change when editing multiple songs. The *only* way to get iTunes to recognize the volume level in the file is to change a tag for one (and *only* one) song at a time, e.g. add "2" to the end of the album name. 2. Here's the worst part: as soon as you change that tag back, iTunes reverts to the wrong volume level, which means there's effectively no way to get it to recognize the SoundCheck level set by iVolume unless you're willing to have wrong info for the song. Even restarting iTunes between changes doesn't help. iTunes now seems to have the original SoundCheck level for each song (as measured by iTunes when the song was first imported) stored in its big unreadable binary database, and apparently there is no longer any way to get it to update that value. If a song plays too loud or too quiet, it's basically stuck that way. While iVolume itself still works quite well, this issue really defeats the entire purpose of using it. I've contacted the developer with a detailed report of this problem. Here's hoping he can figure out some way to work around this, because I've tried everything (and I've been coercing iTunes to do what I want it to do since v1.0, so I know my way around it).