![]() |
Add a DAC to a cheap CD player?
In article , Ian Molton
wrote: On Thu, 11 Dec 2003 10:06:03 +0000 (GMT) Jim Lesurf wrote: This may be the case if there is no mechanism in the receiver to adjust its medium/long-term clock frequency towards that of the transmitter. However the S/PDIF stream has clock info encoded into it. Indeed. but we were discussing reclocking to a perfect clock, which means the spdif clock is being replaced by one that is not even locked to it, which will show the effects described (eventually) I need to distinguish between two situations: 1) Where the receiver/output clock rate is intended to be essentially the same as that which we expect to receive. In this case I would call this process 'reclocking' if a new clock is used at the receiver, rather than just taking a filtered version of what arrives. 2) Where the receiver deliberately processes the data to a somewhat different data rate (e.g. converting 44.1kHz data streams to 48kHz). I do not call this 'reclocking' although I have seen it described as such. In this thread I am primarily considering (1), not (2). On that basis reclocking may or may not include a subsystem to adjust the long- or medium-term frequency of the new clock to be in line with that being received. Hence reclocking may or may not mean using a receiver clock that "is not even locked". In practice, it may well be advisible when converting to also do some form of locking as well, so that in the example mentioned in (2) you might phase lock the new 48kHz to the old 44.1kHz. You always end up needing some amount of data buffering. However if you have no attempts to lock the clocks over the long term, these buffers may need to be very large. This may or may not be a 'good idea'. In the end, with each approach, it comes down to "how well did the designer/manufacturer impliment their solution as being appropriate for the intended use?" Indeed. of course, for the purposes of what I was explaining, its valid to consider the transmitter clock as perfect and the other running fast or slow (its the relative difference that matters :-) I would not view in that way if the practical problem was that the TX clock shows serious variations which - if allowed to affect the eventual DAC conversion rates - would cause the output signal patterns to become audibly phase-rate modulated. This would create a nasty form of intermodulation distortion with components anharmonic with the music. In this situation it may make sense to employ a smoother reciever clock, and treat that as being the one to follow by reclocking the data to it! I would not normally choose to conside *either* clock as "perfect", just look to see if they were adequate for their intended purpose. Slainte, Jim -- Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Audio Misc http://www.st-and.demon.co.uk/AudioMisc/index.html Armstrong Audio http://www.st-and.demon.co.uk/Audio/armstrong.html Barbirolli Soc. http://www.st-and.demon.co.uk/JBSoc/JBSoc.html |
Add a DAC to a cheap CD player?
In article , Ian Molton
wrote: On Thu, 11 Dec 2003 10:06:03 +0000 (GMT) Jim Lesurf wrote: This may be the case if there is no mechanism in the receiver to adjust its medium/long-term clock frequency towards that of the transmitter. However the S/PDIF stream has clock info encoded into it. Indeed. but we were discussing reclocking to a perfect clock, which means the spdif clock is being replaced by one that is not even locked to it, which will show the effects described (eventually) I need to distinguish between two situations: 1) Where the receiver/output clock rate is intended to be essentially the same as that which we expect to receive. In this case I would call this process 'reclocking' if a new clock is used at the receiver, rather than just taking a filtered version of what arrives. 2) Where the receiver deliberately processes the data to a somewhat different data rate (e.g. converting 44.1kHz data streams to 48kHz). I do not call this 'reclocking' although I have seen it described as such. In this thread I am primarily considering (1), not (2). On that basis reclocking may or may not include a subsystem to adjust the long- or medium-term frequency of the new clock to be in line with that being received. Hence reclocking may or may not mean using a receiver clock that "is not even locked". In practice, it may well be advisible when converting to also do some form of locking as well, so that in the example mentioned in (2) you might phase lock the new 48kHz to the old 44.1kHz. You always end up needing some amount of data buffering. However if you have no attempts to lock the clocks over the long term, these buffers may need to be very large. This may or may not be a 'good idea'. In the end, with each approach, it comes down to "how well did the designer/manufacturer impliment their solution as being appropriate for the intended use?" Indeed. of course, for the purposes of what I was explaining, its valid to consider the transmitter clock as perfect and the other running fast or slow (its the relative difference that matters :-) I would not view in that way if the practical problem was that the TX clock shows serious variations which - if allowed to affect the eventual DAC conversion rates - would cause the output signal patterns to become audibly phase-rate modulated. This would create a nasty form of intermodulation distortion with components anharmonic with the music. In this situation it may make sense to employ a smoother reciever clock, and treat that as being the one to follow by reclocking the data to it! I would not normally choose to conside *either* clock as "perfect", just look to see if they were adequate for their intended purpose. Slainte, Jim -- Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Audio Misc http://www.st-and.demon.co.uk/AudioMisc/index.html Armstrong Audio http://www.st-and.demon.co.uk/Audio/armstrong.html Barbirolli Soc. http://www.st-and.demon.co.uk/JBSoc/JBSoc.html |
Add a DAC to a cheap CD player?
In article , Stewart Pinkerton
wrote: On Thu, 11 Dec 2003 10:06:03 +0000 (GMT), Jim Lesurf I don't know if there is any official timescale defined in audio for the longest term that is 'jitter' beyond which it becomes 'drift' of 'static error'. Hence I'd be inclined to regard these as all facets of the same problem and treat them accordingly. Perhaps we could agree that 74 minutes would be a hard limit for jitter on a CD? :-) Make it a shade over 80 mins. I have some 80 min CDRs. :-) Slainte, Jim -- Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Audio Misc http://www.st-and.demon.co.uk/AudioMisc/index.html Armstrong Audio http://www.st-and.demon.co.uk/Audio/armstrong.html Barbirolli Soc. http://www.st-and.demon.co.uk/JBSoc/JBSoc.html |
Add a DAC to a cheap CD player?
In article , Stewart Pinkerton
wrote: On Thu, 11 Dec 2003 10:06:03 +0000 (GMT), Jim Lesurf I don't know if there is any official timescale defined in audio for the longest term that is 'jitter' beyond which it becomes 'drift' of 'static error'. Hence I'd be inclined to regard these as all facets of the same problem and treat them accordingly. Perhaps we could agree that 74 minutes would be a hard limit for jitter on a CD? :-) Make it a shade over 80 mins. I have some 80 min CDRs. :-) Slainte, Jim -- Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Audio Misc http://www.st-and.demon.co.uk/AudioMisc/index.html Armstrong Audio http://www.st-and.demon.co.uk/Audio/armstrong.html Barbirolli Soc. http://www.st-and.demon.co.uk/JBSoc/JBSoc.html |
All times are GMT. The time now is 10:09 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.0.0
Copyright ©2004-2006 AudioBanter.co.uk