DigitalVolcano Software Support

The program thinks files with Bit Rates of <100 (ie 2 digits only) are three digit numbers. It sees 56 bit files as 560 bit!

I too am suffering considerably at this moment from this serious bug. I've the latest (1.4.3) perhaps I'll try an old version yikes. When I click keep highest bitrate it is keeping the 96bit and checking to remove 192, 148 n other better quality, ugh! Please fix this asap.

Hmm, just investigating a bit further...
knowing MS WMP has no end of troubles correctly interpreting ID3v2.4 tag I wondered if that had something to do with it... nope, some of them are v2.4 but just as many are v2.3
I was doing this on Vista, and that always begs the question is that somehow the culprit.
In some examples, Duplicate Cleaner shows the bitrate as 98, and if I use mp3tag it also shows the bitrate as 98 and as VBR... however in Vista explorer if I right click and choose properties on the .mp3 the properties details tab says it is 160kbps... uh oh. So maybe one part of DupClean interprets and correctly shows the bitrate in the listings but another part is not? Or it could simply be what K writes that DupClean is not correctly doing a numeric comparison/leading zero for two-digit bitrates?
It'll take a little time but I'll try to get the same music on an external drive and then attach it to an XP machine with Duplicate Cleaner and test it under XP. I might have an old copy of DupClean I can try as well.

Anyway, this whole thing just reminds me of my rather elaborate request some months back in the forums that fixed CBR versus variable VBR bitrate music be weighted so as to better automatically and correctly choose to keep the better quality, because, a VBR with an avergae bitrate of 140k could very well be superior in quality and yet smaller in size to a constant 192k of the same song.

Oh dear, sorry about this - I'm guessing it's treating the bit rate column as a text field rather than numeric - which messes up the sorting, etc.

I'm working on DC 2.0 now, but this bug is probably serious enough to warrant an update to 1.4.3.

Thanks