In order to determine the official DR value, a song or entire album (16 bit, 44.1 kHz wave format) is scanned. A histogram (loudness distribution diagram) is created with a resolution of 0.01 dB. The RMS – an established loudness measurement standard – is determined by gathering approximately 10,000 pieces of loudness information within a time span of 3 seconds (dB/RMS). From this result, only the loudest 20% is used for determining the average loudness of the loud passages.
Wait, did I say that was bad news? Bad scores, yes, but very good news - since the tool has successfully identified a classic offender from a sea of excellence.
It also overestimates the loudness of low frequency content, which is a good move for being hard on modern hypercompressed masterings, but is harder to defend on psychoacoustic grounds.
Version 1.2 is up. The offline tool is still the same, though. And they have not fixed the English manual. They should release the source for the algorithm.Quote from: Axon on 25 February, 2009, 03:54:20 AMIt also overestimates the loudness of low frequency content, which is a good move for being hard on modern hypercompressed masterings, but is harder to defend on psychoacoustic grounds.Isn't the exact opposite the case? The current algorithm will assign a lower DR value to a recording with more bass. This is bad behaviour as bass is the first thing that suffers from hypercompression. An example: SND's first album (RG of -0.59 dB and very dynamic) is just a DR7!
Given the above commentary on TT's algorithm, if all you want is offline analysis, pfpf will probably tell you what you need to know. But it was never really meant for prime time and considerable care is necessary to interpret its results (although the same must be said for any dynamics estimator, really..)
They've really shot themselves in the foot by restricting access to their meter. They'd rather a donation, than get people to use their meter. Desperate administrators always act the same way (get the money in and then we can spread the message). The thing that was spreading the message is the thing they've just locked away.
I'm still hopeful that Chromatix and Axon will produce a meter that combines their different approaches and yields 3 results: 2 individual scores and one combined score.
Well, I've just tried pfpf, looks good, but it is a bit too... big for my laptop screen. I was rather thinking about something like command line tool? Sorry for being oldschool : )
They way of acting was since my first contact (about 2-3 Months away) like "give money, kk?" - i asked them, why their dr meter does not provide support for flac.The answer was: Many formats, many different problems - you could help by provide a amount of cash. The other question, why not spread the word in the "base" (us freaky little music lovers), instead of the "head" (music engineers, e.g.) was little "arrogant"; To reach the important people.
After a namecalling in a known german magazin (c`t - www.heise.de), they went probably totaly mad.It´s not like their board is about to collapse, they just earned some "fame" in places for their work (in fact most for the database at dr.loudness-war.info, who supports FLAC Sources).
I can't really blame them for this; I think the base has been pretty pumped up already. It's a much harder problem to make headway with the people actually producing the music. You essentially have to tell them how to do their own jobs.
OK, cough it up. You can't allude to a fight with c't without describing it in more detail
I'm sorry to bump this old topic after 4 years, but does anyone know what happen to the Foundation website? Are they gone? Since this morning I can't access their site anymore, there's a german message about the domain, which does not seem to be a temporary issue. Hope I am wrong.Also coincidentally the site hosting the Dynamic Range Meter plugin for Foobar is unreachable as well: http://www.jokhan.demon.nl/DynamicRange/
10b3be7c5dab4b055867588e731ddf79 foo_dynamic_range-1.1.1.zipc18a6eea356e80a7397f8431fc123cc5 foo_dynamic_range/foo_dynamic_range.chm65a5392ac0cb21a9bf820518bbead3ee foo_dynamic_range/foo_dynamic_range.dll