> This topic is likely to end in a flamewar in any
> hi-fi related newsgroup, because it tends to be
> based on a mixture of subjective perceptions along
> with hard physical facts. My (honest) question would
> be: Did you ever _hear_ the result of jitter?

Honestly, I would have to do double-blind testing to say
for sure whether my own ears can truly distinguish the
results of jitter.  Subjectively, I'm quite sure I can.

On the other hand, the specific effects (distortion) that
people blame on jitter do align with (at least my
understanding) of signal theory.  The most common reported
effect is high-frequency "graininess" or "harshness."  This
seems to make sense considering that a sudden dropped
sample in between two others could be seen as a
high-frequency component of the signal.  At CD sampling
rate, the Nyquist is low enough that most of these effects
would be within human hearing range and not rolled off by
the anti-aliasing filter.

A slave (asynchronous) DAC that does not try to re-clock
the samples before conversion would not lose samples, but
on the other hand, slight timing variations from the
source's master clock could easily skew the frequency by
effectively varying the sampling rate without re-sampling.

A DAC with it's own clock but no buffer would be subject to
clock drift between it and the source, thereby dropped and
duplicate samples would occur.  I don't think anybody is
dumb enough to do this.. (I hope)

A DAC with a buffer and it's own clock would eliminate the
timing variation of the source, but its clock would have to
intelligently sync to the average clock rate of the source
and employ a large enough buffer to handle the expected
variance of the source clock.  This would cost the most.

A system with a shared, low-jitter master clock would
fairly ideal, but most equipment isn't designed for this
and theoretically jitter could still be introduced by the
transmission lines (ie. digital interconnects and other
wiring or optical links).  Some buffering would still be
desired, albeit a smaller amount to minimize latency.

> after all, it's "just" digital data that's sent over
> S/PDIF. 16 bits make one sample, 44100 samples make one
> second of audio (with cd quality anyway), how can jitter
> degrade the sound if the D/A converter is aware of this?

see above possibilities

> If high-end manufacturers want to address any problems
> that might occur, why don't they just add a suitable
> buffer to the receiving side (the D/A converter) so that
> jitter is only a problem between this buffer and the DAC?
> Or they could introduce an alternative to S/PDIF (e.g.
> USB), which is not so "weak"
> when it comes to error correction.

I agree 100%.  Why try to time the signal at the source?
But of course, as you mentioned, this was done due to the
limited technology when digital audio began.  USB
'soundcards' are kinda interesting, though unfortunately

not supported by ALSA yet. ):
> > Well, the sb-live resamples everything internally
> > to 48 KHz, even stuff from the S/PDIF, even if it's
> > already at 48 KHz. So it's never a pure transmission.
> > I believe many other cards do this too, but I don't
> > know which ones.
>
> E.g. M-Audio's line of cards are said to be better in
> this respect, don't know how jitter-prone they
> are, though.

I will say that between the digital outs of the SB Live and
the C-media 8738, the C-media card is remarkably clearer
when playing at 44.1Khz. and I know for fact that it does
no internal re-sampling.

On the other hand, I did see something about a hack to send
raw stereo 44.1Khz. S/PDIF data out from the SB Live, much
in the same way you can send raw AC3 frames.  Can anyone,
ALSA developers or otherwise, comment on what kind of
clocking is used for the data in this situation?

Chris

_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to