Skip to main content

Topic: (Not a) good explanation of jitter in TAS (Read 54864 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • andy o
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #50
surely the key difference is that image motion caused by hand holding powerful lenses is manifest on non-critical observation, causing obvious defects in normal use of the images.


I would certainly agree.

Yeah, I didn't say that there was gonna be more detail, I said that there wouldn't. It is a matter of not having to lug a tripod around. With photography, it even helps with a tripod and somewhat fast shutter speeds, since it can minimize the quick snappy shake of the mirror.

  • MichaelW
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #51
@andy o

I wasn't arguing with you--I've been there with camera shake, and wobbly binoculars. Just pointing out a gross difference between audio jitter and image wobbles. And I use image stabilization, because a good tripod will not fit in a pocket.

  • uart
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #52
Quote from: from linked article link=msg=0 date=
I've heard this most dramatically when I reviewed Esoteric's G-0Rb, a $16,000 rubidium-based external clock. That's right: The G-0Rb is an atomic clock in your equipment rack whose sole purpose is to provide a precise clock for the digital-to-analog conversion process. With the push of a button, I was able to compare the conventional clock in the Esoteric P-03/D-03 combination with the rubidium-generated clock. Engaging the G-0Rb brought the soundstage into sharp focus, revealed the size and character of the hall through better resolution of low-level spatial cues, made instrumental timbres sound more natural and “organic,” and resulted in a wholesale increase in involvement in the musical performance.


Phew it's a good thing that blind testing has been so thoroughly discredited by the author . Otherwise he might have been struggling a bit there.

  • andy o
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #53
@andy o

I wasn't arguing with you--I've been there with camera shake, and wobbly binoculars. Just pointing out a gross difference between audio jitter and image wobbles. And I use image stabilization, because a good tripod will not fit in a pocket.

Nah, I was agreeing with you. I thought Ed might have misunderstood my previous comment.

(Not a) good explanation of jitter in TAS
Reply #54
...because jitter is not a real problem...


Is this a common belief here at HA?

ATB,
-Elias
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
(Not a) good explanation of jitter in TAS
Reply #55
Why do you ask?

Can you demonstrate through a double-blind test that it is?

If so, please share.

13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

(Not a) good explanation of jitter in TAS
Reply #56
Why do you ask?

Can you demonstrate through a double-blind test that it is?

If so, please share.



Sort of...  We have an ABX box here (we are big believers in DBT testing, as well as the 'no B.S.' approach to audio technology that is embraced here at HA).  The real problem with jitter audibility tests is that it is hard to impose jitter on a digital music signal.  In other words, one can easily see the effects of jitter using an AP generator and an FFT.  However, setting up a test to compare Beethoven's 9th w/ and w/o jitter is much more difficult (logistically).

Would you care to see FFT's of a converter w/ and w/o jitter?

ATB,
e
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • pdq
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #57
I don't understand why it would be so difficult to perform an ABX test for jitter. Why not just upconvert the material to a higher sampling rate, apply jitter mathematically, and compare the before and after files?

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
(Not a) good explanation of jitter in TAS
Reply #58
Would you care to see FFT's of a converter w/ and w/o jitter?

If you mean "see" in a literal sense, then my answer is no.

Quote
8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objective support for their claims. Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings. Graphs, non-blind listening tests, waveform difference comparisons, and so on, are not acceptable means of providing support.

13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
(Not a) good explanation of jitter in TAS
Reply #59
Furthermore, tests for the audibility of jitter should be consistent with differences found in real-world hardware.

I doubt that you'll find anyone here who believes that there is no amount of jitter that can break the threshold of audibility in any given system.
  • Last Edit: 20 July, 2009, 01:22:07 PM by greynol
13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

  • Axon
  • [*][*][*][*][*]
  • Members (Donating)
(Not a) good explanation of jitter in TAS
Reply #60
I don't understand why it would be so difficult to perform an ABX test for jitter. Why not just upconvert the material to a higher sampling rate, apply jitter mathematically, and compare the before and after files?
Heh. And if Hawksford's simulator is insufficient, do tell.

(Personally I've had my doubt as to how accurately a bandlimited interpolation is capable of simulating a digital upsample + sigma delta modulator + zero order hold + antialias, but I can't really back that up.)
  • Last Edit: 20 July, 2009, 01:37:40 PM by Axon

  • krabapple
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #61
Would you care to see FFT's of a converter w/ and w/o jitter?

ATB,
e


Only if they're accompanied by controlled listening tests data to correlate them to audibility.

'Cos as you know, observable does not necessarily mean audible.

There's already too much audiophile hysteria and hand-waving about jitter; uncorrelated difference graphics wouldn't help the situation.
  • Last Edit: 20 July, 2009, 01:56:11 PM by krabapple

(Not a) good explanation of jitter in TAS
Reply #62
Furthermore, tests for the audibility of jitter should be consistent with differences found in real-world hardware.


Well, this is sort of a moving target, is it not?  Real-world hardware can be affected by several external factors... how can one quantify what is 'real-world' and what is not?

All the best,
Elias
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
(Not a) good explanation of jitter in TAS
Reply #63
Fine, then feel free to provide samples of audible jitter even if the effect has been exaggerated.  They will no doubt be more useful than the garbage article referenced in this discussion.
13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

(Not a) good explanation of jitter in TAS
Reply #64
Fine, then feel free to provide samples of audible jitter even if the effect has been exaggerated.  They will no doubt be more useful than the garbage article referenced in this discussion.


Ok, I'll try to pull something together.  As I mentioned, its hard to simulate jitter in a music file, and I'm sure no one wants to do a DBT with sine-waves.  But I'll see what I can do.

Would you all except the following premise: if the digital cable is the only variable, any differences can be attributed to jitter?

ATB,
-e
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • rpp3po
  • [*][*][*][*][*]
  • Developer
(Not a) good explanation of jitter in TAS
Reply #65
I don't understand why it would be so difficult to perform an ABX test for jitter. Why not just upconvert the material to a higher sampling rate, apply jitter mathematically, and compare the before and after files?


You would need very high sample rates to apply small amounts of jitter this way and the result would not necessarily sound comparable to what a specific DAC would output from a dirty clock. Good asynchronous DACs are immune to vast amounts of jitter, anyway.
  • Last Edit: 20 July, 2009, 02:21:10 PM by rpp3po

(Not a) good explanation of jitter in TAS
Reply #66
Good DACs are immune to jitter anyway.


True, but by this definition, there are very few 'good' DAC's.

An FFT may not be able to determine audibility, but it can determine susceptibility.  If we put a DAC on an AP machine and increase jitter, the FFT will show whether the DAC is immune to the change.  Most are not.

ATB,
-E
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • rpp3po
  • [*][*][*][*][*]
  • Developer
(Not a) good explanation of jitter in TAS
Reply #67
Most are not.


I own one whose circuit layout once filled your day, it sure is...

But I'm wondering why not more designs employ an ASRC by default. You don't need $1000 DACs just for jitter immunity. An AD1895, for example, is just $5.36 per piece.
  • Last Edit: 20 July, 2009, 02:33:43 PM by rpp3po

(Not a) good explanation of jitter in TAS
Reply #68
I own one whose circuit layout once filled your day, it sure is...


??  What is it?

But I'm wondering why not more designs employ an ASRC by default. You don't need $1000 DACs just for jitter immunity. An AD1895, for example, is just $5.36 per piece.


Well, you don't need $1000 to buy that chip, but you need $1000 to pay an engineer to design the infrastructure to execute it properly!    Not to mention all the other custom circuitry, components and board design.  EDIT: (and quality control, 5-yr warranty, etc)

Just because we share a disinterest in hokus pokus electronics doesn't mean we're talking about cook-book electronics either! 

All the best,
Elias
  • Last Edit: 20 July, 2009, 02:42:02 PM by EliasGwinn
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

  • Soap
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #69
Furthermore, tests for the audibility of jitter should be consistent with differences found in real-world hardware.


Well, this is sort of a moving target, is it not?  Real-world hardware can be affected by several external factors... how can one quantify what is 'real-world' and what is not?


Measurements of the amount of jitter on a production audio source would be easy enough to do, no?  I think that is clearly a reasonable definition of "real-world".

Is this not a case where If X amount is audible there is no point in testing X+1?  Or do different types of jitter exhibit different audio effects.
Creature of habit.

  • saratoga
  • [*][*][*][*][*]
(Not a) good explanation of jitter in TAS
Reply #70
I don't understand why it would be so difficult to perform an ABX test for jitter. Why not just upconvert the material to a higher sampling rate, apply jitter mathematically, and compare the before and after files?


You would need very high sample rates to apply small amounts of jitter this way and the result would not necessarily sound comparable to what a specific DAC would output from a dirty clock.


Couldn't you just upsample a 1000x, apply the jitter, and then downsample?  I don't see why thats so difficult, though it may use a couple seconds of your CPU time to compute.

Of course this is only as good as your model of real jitter, but I doubt a good model of clock noise is so difficult to come up with.  You pick any ok one and then just increase the std deviation until you hear something . . .

(Not a) good explanation of jitter in TAS
Reply #71
Is this not a case where If X amount is audible there is no point in testing X+1?  Or do different types of jitter exhibit different audio effects.


Different types of jitter DO sound different.  More importantly, different converters are susceptible to jitter at different frequencies.  Specifically, most are NOT immune at low frequencies (<1 kHz).  Well-designed PLL's can settle high-frequency jitter, but doesn't do anything to low-frequency jitter.  And, arguably, low-freq is the most detrimental jitter because it modulates the fundamentals to frequencies near-by (+/- the jitter frequency), which can cause things to sound out-of-tune (like one of a trio of piano strings is out of tune).

ATB,
e
Elias Gwinn

Engineer
Benchmark Media
www.BenchmarkMedia.com

(Not a) good explanation of jitter in TAS
Reply #72
The real problem with jitter audibility tests is that it is hard to impose jitter on a digital music signal.  In other words, one can easily see the effects of jitter using an AP generator and an FFT.  However, setting up a test to compare Beethoven's 9th w/ and w/o jitter is much more difficult (logistically).


Actually, its pretty easy to add jitter to a SP/DIF signal. I've done it with maybe $10 worth of parts on a protoboard plus an analog signal source for the signal that is to be the jitter.

Take a SP/DIF signal and use a high speed comparator or schmidt trigger chip to turn it into a square wave (Real world sp/dif signals are often band-limited and look a lot more like a sine wave than a square wave).  Feed that through a low pass filter to create a wave with a significant rise time. Then mix in variable amounts of the analog jitter signal. Finally, use another comparator or schmidt trigger input gate to create the signal with jitter. The analog signal will slide the trigger point of the digital signal back and forth along its rise time slope, and this will change the timiing of the SP/DIF signal.  The first comparator to square the input signal is optional, particularly if the SP/DIF signal coming in is very robust.

I made this work one morning and proved that it was working several ways. One of the DACs I had on hand (mid-90s era Denon DA-500)  had no jitter resistance at all, and I could add clearly audible vibrato to any audio signal. I could also measure the creation of the sidebands that are chraracteristic of FM distoriton (jitter).  The other DAC, a early Y2K Technics SHAC 500 surround processor (very similar to the circutis now found in just about every surround receiver) had utterly maximal jitter resistance.

With no added jitter applied, all spurious responses  from the SHAC-500 were 110 dB down or more, and they stayed that way until I jittered the signal so much that the both DACs would lose lock. In the extreme case, the Deneon DA 500 would make music sound like it was being sung between buzzing lips, and the Technics SHAC 500 would sound exactly the same as if nothing unusual was happening at all.

(Not a) good explanation of jitter in TAS
Reply #73
I don't understand why it would be so difficult to perform an ABX test for jitter. Why not just upconvert the material to a higher sampling rate, apply jitter mathematically, and compare the before and after files?


You would need very high sample rates to apply small amounts of jitter this way and the result would not necessarily sound comparable to what a specific DAC would output from a dirty clock.


Couldn't you just upsample a 1000x, apply the jitter, and then downsample?  I don't see why thats so difficult, though it may use a couple seconds of your CPU time to compute.


This is in essence how I prepared the variable jitter samples for the now-defunct PCABX web site.  I used CEP 2.1 to do the upsampling and downsampling (in steps because extreme ratios can break CEPs resampling algorithm), and also used the Flanger (if memory serves) to actually apply the desired FM modulation.  It was one of the time-sensitive EFX.

  • rpp3po
  • [*][*][*][*][*]
  • Developer
(Not a) good explanation of jitter in TAS
Reply #74
Very interesting comments.

The problem I generally see with externally generated jitter, either through up-/downsampling or electronically, is the applicability of those results. You can take it so far, that you can hear at least something, i. e. what jitter of model m at gain g does or does not sound like. After that you will have several pairs m, g that seem to be relevant. But those then have to be translated and tested against real world implementations.

Wouldn't it make more sense to route test signals into a common DAC known to be sensible against jitter, one from a low end onboard S/PDIF source and another of very high quality, make more sense? That's about the worst it can get in real life. If that already wasn't audible, testing could end. If it was, other common DACs could be fed with the same signal.
  • Last Edit: 20 July, 2009, 07:28:44 PM by rpp3po