where does jitter matter?

[Rickie]

i think i found an answer:

Jitter - Benchmark

The people at Benchmark calls the (forever "printed" errors in the A/D-process)
"conversion clock jitter" and they are the result of the clock that is used during A/D.

The jitter that occurs during transport and interfacing is called "interface jitter" and matters when your going to D/A-convert. The "anti-jitter" functions in the D/A ("jet pll" for example) that takes place before actual conversion decides the purity of the final listenable analogue signal.

So in my example with the "bit-bucket-computer" it does nor matter at all if that signal becomes "jittery" on the way to the computer (interface jitter) since that is not "permanent", but rather "temporary".

Unless Benchmark is full of s... i think i got it now, but if anyone cares to comment, feel free!


found another link:

http://www.digido.com/articles-and-d...15-jitter.html

[S21]

Only your a/d conversions should need to be clocked by the same oscillator.

The receiving computer doesn't care. It just writes the data to disk at any old time.

[Rickie]

Yes, thank you!

and that opens up a whole lot of possibilities to use the macbook with stand-alone a/d & d/a´s without any further "interfacing" then the built-in digital i/o (mini-toslink) as long as you only process 2 channels at the time..
exciting times!
no more firewire-chipset-issues, driver-upgrades och firmware-conflicts on products thats needs constant attention just to pass ad/da in/out of a computer..
i will just have a nice digital format converter & plenty of digital cables and then i have many configurations to choose from wherever i go with my macbook.

[skillz335]

im glad that worked out for you man.