What if they took a 16 bit file and put it in a 24 bit container while
adding 8 LSB of dither? A bitscope wouldn't help you there, would it?
If the noise floor sometimes drops below the 16th bit, I could maybe see
that the noise floor hovering right at 16 bits would be a clue. But if the
noise floor never drops below the 16th bit, then how would you know whether
the bottom 8 bits is program or dither?
I suppose that, if there is a fade-out, if the dither remains at 16 bits,
that would also be a clue, unless they added the dither before the fade.
On Mon, May 5, 2014 at 10:32 AM, [log in to unmask] <[log in to unmask]>wrote:
> Henry Borchers:
> > I have some doubts about a file being digitized at true 24-bit.
> > The file says 24-bit but I?m not sure how to verify it. Is there
> > a way of verifying a file to see if it?s truly 24-bit and not 16-bit
> > conversion in a 24-bit file?
> Yes, you need to use a bitscope to see which bits toogle or are
> stuck with no activity in them.
> I use an ADT, England, Digital line tester where you can see the
> status of the AES/EBU user bits and you can also manipulate
> those bits any way you wish.
> I have modified it so I can also use it as a bitscope which can be
> very useful as in the past there were many pieces of didgital
> equipment that claimed to be 24 bits but could be anywhere from
> true 24 bits down to 16 bits.
> The Valley Audio 730 Comp/limiter stated 24 bis but was in fact
> a 16 bit device only.
> There are many more devices that you can use as a bitscope from
> Prism and many manufacturers that sell you software has a bitcope
> If you are handy you can even build your own as is shown here:
> Best regards,
> Goran Finnberg
> The Mastering Room AB
> E-mail: [log in to unmask]
> Learn from the mistakes of others, you can never live long enough to
> make them all yourself. - John Luther
> (")_(") Smurfen:RIP
[log in to unmask]