|
Post by steffen on Apr 5, 2019 14:14:54 GMT
I just read the Milan-FunctionalSpec-Mediaclocking-2.1.pdf and was wondering how the CRF parameters for 96kHz / 192kHz looks like.
48kHz sample rate with timestamp_interval of 96 results in a packet transmission interval of 2ms.
Now at 96kHz, is the packet transmission interval still 2ms and therefore the timestamp_inteval 192, or 1ms packet transmission interval and timestamp_interval fix on 96?
Would be great if anyone could clarify that.
Thanks in advance, Steffen
|
|
fabra
New Member
Posts: 4
|
Post by fabra on Apr 10, 2019 15:35:18 GMT
Hi Steffen,
CRF parameters are equal across all sampling rates. It's the same CRF format used for 48kHz, 96kHz and 192kHz.
If you want to sychronize two devices @96khz the packet transmission interval is still 2ms and the timestamp_interval is still 96, too.
There is no need to have separate CRF formats for different sampling rates, because it doesn't make any difference for the recovered clock. You can look at it as if the CRF stream transports a downsampled signal of the original clock.
Thanks, Fabian
|
|
|
Post by steffen on Apr 11, 2019 15:08:02 GMT
Hi Fabian,
thanks for your reply.
That means, MILAN only synchronises the 1FS (48kHz) Domain, and everything else is AUDIO_UNIT dependent.
Regards, Steffen
|
|