Dr. Jocko's recipe........
Hi Jocko,
I know Zobels only from loudspeaker crossovers, sorry.... Could you please elaborate a bit in this digital context?
We are talking about the "Simplest TTL to S/PDIF coax interface" in the ePanorama listing, right? That one is identical to the one I stumbled across spending hours reading numorous S/PDIF threads on this forum. That's the one i implemented in my Philips transport and later in the Studer...... How does this look like with Zobel?
BTW your postings were the main reason to keep on reading. Funny, and very educating for an amateur like me.
Lourens
Jocko Homo said:
Hi Jocko,
I know Zobels only from loudspeaker crossovers, sorry.... Could you please elaborate a bit in this digital context?
We are talking about the "Simplest TTL to S/PDIF coax interface" in the ePanorama listing, right? That one is identical to the one I stumbled across spending hours reading numorous S/PDIF threads on this forum. That's the one i implemented in my Philips transport and later in the Studer...... How does this look like with Zobel?
BTW your postings were the main reason to keep on reading. Funny, and very educating for an amateur like me.
Lourens
flip-flopping
At the risk drifting off topic: What do you think I should do to minimize jitter in the Studer S/PDIF variation (see attachment in # 39, above)?
Don't tell me the line driver is a D flip-flop too
It's one of those puzzles I encounter studying different versions of S/PDIF circuits. The CDD882 transport uses 74LS08 as a buffer. The nearly identical CD880 (CDP-version) 74HC74....
The logic diagrams in the datasheets of those D flip-flops look quite different in my (laymans) eyes, compared to the one I found of the AM26LS31C. As i wrote before, I intend to feed it with some nice shunt food; will that do any good? But I can pull it out or replace it easily (IC's are not soldered in the Studer) if that cures the patient
Lourens
Jocko Homo said:
At the risk drifting off topic: What do you think I should do to minimize jitter in the Studer S/PDIF variation (see attachment in # 39, above)?
Don't tell me the line driver is a D flip-flop too
It's one of those puzzles I encounter studying different versions of S/PDIF circuits. The CDD882 transport uses 74LS08 as a buffer. The nearly identical CD880 (CDP-version) 74HC74....
The logic diagrams in the datasheets of those D flip-flops look quite different in my (laymans) eyes, compared to the one I found of the AM26LS31C. As i wrote before, I intend to feed it with some nice shunt food; will that do any good? But I can pull it out or replace it easily (IC's are not soldered in the Studer) if that cures the patient
Lourens
One thing at a time............
Zobel networks.........
They work the same way here. It cancels out the leakage inductance of the transformer, to make the source look resistive.
On that subject........do not use the 2:1 (or 1:2) versions. Yeah, I know Scientific Conversions tells us how good theirs are.............
Ask them how low their leakage inductance is. Guess what: they won't tell you. Hard to make a zobel without knowing that. So, you have to improvise ways of measuring it.
Jocko
Zobel networks.........
They work the same way here. It cancels out the leakage inductance of the transformer, to make the source look resistive.
On that subject........do not use the 2:1 (or 1:2) versions. Yeah, I know Scientific Conversions tells us how good theirs are.............
Ask them how low their leakage inductance is. Guess what: they won't tell you. Hard to make a zobel without knowing that. So, you have to improvise ways of measuring it.
Jocko
My DAC is a DS Pro Basic II, PCM57 or 67 DAC chips (18 bit, 2, running balanced line) CS8412 input reciver and a clock crystal around 28 Mhz.
The Transport the Theta Data Basic II, Philips CDM9 pro on a little Philips PCB to do motor and swing arm servo functions but everything else is done on a Theta designed/made PCB but full of Philips chips.
The 28.xxx Mhz clock inside the DAC is not a full multiple of the 11.2896 Mhz clock inside my drive so I am not sure how to go about this..... It actually works out to about 2.5 x 11.2896......
My friend would be very grateful. The jitter reduction spec for toslink, does it refer to overall improvement on best from the CDP or toslink vs output of the TLC? Ie no point in improving on something that is inferior to what you already have.....
From how? to: why.....?
Well, I was aware of the fact this route is no sinecure (hence the smiley -- left out in your quote...). Time to get back to the question you started this thread with. Why should we add an AES3 output in the first place?
In some cases I preferred AES3 (for instance between Levinson’s 390S -- 360S) in other cases S/PDIF (Studer A727 -- Weiss Medea). Both top of the bill combinations, up till now only outdone when the transport could be slaved (like my A727 -- dCS
) in which case the interface (=format+cable quality) really becomes secondary, IMHO.
Controlling the transport word clock from the DAC means you tackle one of the key problems with S/PDIF (and AES3, which is essentially the same format) in a much more fundamental way. Read this interesting TNT crash course and you know what I mean.
Synchronising word clocks has a far greater impact than switching from S/PDIF to AES3, in my experience.....
Lourens
tubenut said:
Well, I was aware of the fact this route is no sinecure (hence the smiley -- left out in your quote...). Time to get back to the question you started this thread with. Why should we add an AES3 output in the first place?
In some cases I preferred AES3 (for instance between Levinson’s 390S -- 360S) in other cases S/PDIF (Studer A727 -- Weiss Medea). Both top of the bill combinations, up till now only outdone when the transport could be slaved (like my A727 -- dCS
) in which case the interface (=format+cable quality) really becomes secondary, IMHO.Controlling the transport word clock from the DAC means you tackle one of the key problems with S/PDIF (and AES3, which is essentially the same format) in a much more fundamental way. Read this interesting TNT crash course and you know what I mean.
Synchronising word clocks has a far greater impact than switching from S/PDIF to AES3, in my experience.....
Lourens
Re: From how? to: why.....?
I can believe this quite easily. The difference between AES vs Co Ax are not that huge when using same brand / quality (but correct type for each) cable. For now I prefer my AES3. implementation and am glad I went through the trouble. I have heard the benefit of slave clocking on Deltec and Arcam products. Last night I lead taped the crystal and then covered it in amalgamating tape as well as earthed the can, that made a nice difference. Now I need to look at slave clocking or a better clock but I think the Theta uses something more then the standard Pierce circuit already.... 68nf and 22nf on the crystal and they do not seem to go to earth.... Where can I read some good info on slave clocking and how people have done it DIY?
Anyway this is off topic now......
The discussions have been good and informative.
Lourens said:
Well, I was aware of the fact this route is no sinecure (hence the smiley -- left out in your quote...). Time to get back to the question you started this thread with. Why should we add an AES3 output in the first place?
In some cases I preferred AES3 (for instance between Levinson’s 390S -- 360S) in other cases S/PDIF (Studer A727 -- Weiss Medea). Both top of the bill combinations, up till now only outdone when the transport could be slaved (like my A727 -- dCS
Synchronising word clocks has a far greater impact than switching from S/PDIF to AES3, in my experience.....
Lourens
I can believe this quite easily. The difference between AES vs Co Ax are not that huge when using same brand / quality (but correct type for each) cable. For now I prefer my AES3. implementation and am glad I went through the trouble. I have heard the benefit of slave clocking on Deltec and Arcam products. Last night I lead taped the crystal and then covered it in amalgamating tape as well as earthed the can, that made a nice difference. Now I need to look at slave clocking or a better clock but I think the Theta uses something more then the standard Pierce circuit already.... 68nf and 22nf on the crystal and they do not seem to go to earth.... Where can I read some good info on slave clocking and how people have done it DIY?
Anyway this is off topic now......
The discussions have been good and informative.
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.