Thanks, I already understand Leq, and have a tool that does that. I'm less concerned with the integration time aspect, more interested in what Adobe "thinks" is important for a single-figure weighted loudness analysis.
To that end.. here' s a quick/dirty comparison. Sorry, I hate Excel's graphing functions, so this is what you get.
Test conditions:
Source was pink noise at -13dBFS RMS for 10 seconds. 10 seconds was chosen arbitrarily to compensate for integration time functions included in most loudness measurement functions, though 10 seconds may not completely bring them into parity particularly if something like Leq was being done, it's probably close enough to get an idea of what's going on. A 1 octave filters for each frequency data point was applied, and Audition's Amplitude Statistics scanned, data copied to Excel. Then the filter was removed to revert to pink noise, and the next frequency filter applied. The result is a plot of individual octave-band response of each loudness measurement function.
Based on this very basic, and approximate comparison, I would say that Adobe Perceived Loudness is clearly radically different from ITU-1770, an industry standard. Adobe Loudness appears to be mostly flat in its spectral response, and also out of line with ITU-1770. Without at least a little explanation from Adobe on the how and why of each, there's really no point in using them at all, and they should, IMO, be eliminated if for no other reason than the confusion they cause. Can you imagine producing something for commercial use, basing some sort of decision on Perceived, then having your client apply 1770 and tell you your mix is no good?
It's curious that in CS6, ITU-1770 is shown outside of the data block, as if it were an afterthought. Leq would be a useful addition, being another well-established industry standard. A Zwicker meter would also be interesting.
I agree there are other tools, but including useful analysis tools is very worth while, and something Adobe does in other applications as well. Making them conform to industry standard seems like the only logical thing to do.