1 / 6

Reference distribution

Reference distribution. SMPTE proposal. (View the Notes pane to see comments by Rob Silfvast and Willem-Jan Dirks). Introduction. For background on the approach supported within SMPTE: Google search [“Paul Briscoe” and “the new genlock”].

kylie-garza
Download Presentation

Reference distribution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reference distribution SMPTE proposal (View the Notes pane to see comments by Rob Silfvast and Willem-Jan Dirks)

  2. Introduction For background on the approach supported within SMPTE: Google search [“Paul Briscoe” and “the new genlock”] • First years there will be a mixed environment. Feedback of customers is to keep a long transition period in mind. • Traditional gen-lock sources will source the reference in this mixed environment. • Receiving signals that some “Big players” in the broadcast domain are aiming for the SMPTE 33TS reference solution. • We don’t want to inherit the current situation where references need to be tuned for different sources.

  3. Mixed environment

  4. Pro: • Doesn’t increase bandwidth usage. Calculations are made in each endpoint using the timestamps already distributed by the clock master. Only a single control packet to tell the endpoint which reference to take. • SMPTE defined standard which is respected in the Video Broadcast (VB) domain. • Ready for future reference standards. • Multiple reference standards distribution in a single network (not used today in VB).

  5. Cons: • Calculations are not straight forward. • No backup master as when using streams, this could result in a “reference jump” when switching from Master to a new Master. • A relation to TAI (via GPS) is needed for synchronizing “Traditional” infrastructures to an AVB network.

  6. To Do before deciding: • Investigating the “cost” of a SMPTE implementation • Most complex implementation is for the 59,94 reference, since this has a 1,001 relation to a second. Each 1001 second there is an aligned frame. • Find solution for “ref jump” when master changes • Automatic master switching is under discussion for broadcast, since customers are afraid of this principle.

More Related