In a thread on the ripping forum recently, mswlogo has sussed out how to
'up-bit-depth' his flacs from 16 to 24 bits. Filesize is similar, as it
just compresses out, so no downside. The file is padded out with
zeroes, so there is no change
Potential upsides he gives are reduced jitter and (if
I don't see how simply having more bits (with no information in them)
makes it any more likely that any of them will arrive at the right
time...I would have thought that it's even harder to control jitter at
higher bit rates, since everything is happen faster if you see what I
mean. What am I
Jitter will be exactly the same. The SPDIF spec transmits 32 bits of
data per sample anyway; up to 24 of these are available for the sample
word (with the bottom bits explicitly set to zero if unused!), and the
rest are overheads such as sync pulses, checksums and other stuff.
Apart from possibly
Cheers Andy, good reply. Saves me from agonising over whether to do
lots of converting and testing :)
Adam
--
adamslim
Those are my principles, and if you don't like them... well, I have
others
http://www.last.fm/user/AdamSlim/
Thanks Andy - that makes sense!
--
Phil Leigh
Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85
View this thread: http://forums.slimdevices.com/showthread.php?t=34892
If your going to upsample as well doing it in larger word length is more
accurate (some would say a better guessitmate). Upsampling doesn't make
a lot of sense with Slimdevices because SB3 only does 48khz and
Transporter doesn't do 88.2Khz. BUt my library is for other devices
beside the
But didn't you just say 16 vs 24 wouldn't make any difference in the
actual jitter of the 32bit word. Why would it matter which bits are
being used in the test?
So your saying each bit has it's own jitter measurement?
Or if he toggled Bit 8 of the 24bit word he'd get the same measurement
as bit
mswlogo;198595 Wrote:
But didn't you just say 16 vs 24 wouldn't make any difference in the
actual jitter of the 32bit word. Why would it matter which bits are
being used in the test?
So your saying each bit has it's own jitter measurement?
Or if he toggled Bit 8 of the 24bit word he'd
AndyC_772;198601 Wrote:
I must admit, I don't know for sure why the test results are different -
but I suspect it's much more to do with flaws in the test itself than
the behaviour of the Transporter.
For example, the AK4396 DAC is a 128x oversampling delta-sigma device,
so there will
What I was getting at, is that your DAC, or your processor, or whatever
else is connected over SPDIF, simply won't know whether it's getting 16
bit or 24 bit data. The SPDIF frame includes 24 bit positions for use
with audio data, and a source that only has 16 bits available simply
pads the
So you're saying I've effectively prepadded the low 8bits before it
would have already?
--
mswlogo
mswlogo's Profile: http://forums.slimdevices.com/member.php?userid=9090
View this thread:
mswlogo;198587 Wrote:
http://www.stereophile.com/mediaservers/207slim/index4.html
Stereophile's jitter measurement in this case is just nonsense. They
are using the Miller jitter analyzer, which implements the test
described in Julian Dunn's Jitter and Digital Audio Performance
mswlogo;198613 Wrote:
Also just a thought wouldn't replay gain (done digitally) or any
normalization now have lot headroom in 24bit?
No, the volume function is always 24 bit.
--
seanadams
seanadams's Profile:
seanadams;198655 Wrote:
No, the volume function is always 24 bit.
But if someone did normalization on a 16bit file you could lose data.
Where is if was done on 24bit data your unlikely to lose anything.
Are you saying that even digital volume done on the SPDIF output of a
SB3 is effectively
mswlogo;198663 Wrote:
But if someone did normalization on a 16bit file you could lose data.
Where is if was done on 24bit data your unlikely to lose anything.
I think I follow what you're trying to say there, but it does not
apply. The volume function is always 24 bits wide. It doesn't know
seanadams;198672 Wrote:
I think I follow what you're trying to say there, but it does not apply.
The volume function is always 24 bits wide. It doesn't know or care
whether the lower 8 bits are used, and all 24 bits of output are
meaningful regardless of the input word length.
That's
yes any static normalisation is a bad idea, regardless of how many bits
you have to play with. The engineers did their best to master your
bits...do not mess with them - you will not make them better - only
different :0)
--
Phil Leigh
mswlogo;198673 Wrote:
Ok, I understand the SPDIF part.
Actually I was talking about the volume function, but yes, this applies
to the s/pdif link also.
But if I have a 16bit wav file, and applied a normalization (not replay
gain, static normalization of the data). which may reduce it's
18 matches
Mail list logo
