View Single Post
Old 04-14-2016, 01:01 AM   #37
TBProAudio
Human being with feelings
 
TBProAudio's Avatar
 
Join Date: May 2014
Location: Germany
Posts: 643
Default

Quote:
Originally Posted by Castanuelas View Post
Since your dpMeter VST is based on this JS, does this mean that the dpMeter VST also doesn't support 88k and 96k for true peak?

DAW users who work for the movie industry need 96k to support Dolby TrueHD on Blu-ray discs. DAW users who work for the Hi-Res music industry need to support 88k, 96k, 176k and 192k.

What I saw in the BS1770 specification is that 176k and 192k don't require any upsampling filter to measure true peak -- just measure on the raw samples. BS1770 only requires upsample by 2 for 88k and 96k. Upsampling all sample rates by 4 will comply with BS1770, but CPU is reduced for rates above 48k by upsampling by a lower factor.

Please also confirm whether your JS and VST implementations support 88k, 96k, 176k and 192k sample rates properly for integrated loudness (LUFS).
TP measurement of dpMeter supports all 44/48K "times factor" sample-rates.The signal is always 4 times up-sampled, even if this may not be necessary for 88K and higher according BS1770.
IL, ML and SL measurement works for all sample-rates.

For the JS implementation I have to check, if TP measurement above 48k complies to BS1770. If not i will fix it :-)
__________________
www.tbproaudio.de
TBProAudio is offline   Reply With Quote