<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/time-code-summits" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Time-code-summits ]]></title>
                <link>https://www.tvtechnology.com/tag/time-code-summits</link>
        <description><![CDATA[ All the latest time-code-summits content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Tue, 27 Sep 2016 10:56:00 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ SMPTE Plans Series of Time Code Summits ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/show-news/smpte-plans-series-of-time-code-summits</link>
                                                                            <description>
                            <![CDATA[ The Society of Motion Picture and Television Engineers is turning to the broadcast community to provide feedback on what the next “Time Label” standard should be with a series of Time Code Summits. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">nf5xbrp4HtvsnPUmhBpWue</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/5Ut85ZCmogzwbauCkEEKB5-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 27 Sep 2016 10:56:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Events]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/5Ut85ZCmogzwbauCkEEKB5-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/5Ut85ZCmogzwbauCkEEKB5-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WHITE PLAINS, N.Y.—</strong>The Society of Motion Picture and Television Engineers is turning to the broadcast community to provide feedback on what the next “Time Label” standard should be with a series of Time Code Summits. SMPTE is looking to address the requirements of handling media across cinema, broadcast, theatrical, music recording, concert, live entertainment and theme park markets with the creation of the new Time Label standard.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="cEtUVthqqwFNNfUkwq5h9S" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/cEtUVthqqwFNNfUkwq5h9S.jpg" mos="https://cdn.mos.cms.futurecdn.net/cEtUVthqqwFNNfUkwq5h9S.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Howard Lukk</em></p><p>There are currently three summits planned—with more potentially on the way—and each will provide an overview of what the current standards offer, collect answers from attendees on questions about their requirements for the new standard, and a free-form discussion about additional requirements and considerations. All results will be integrated into a report for the SMPTE Working Group on Time Labeling and Synchronization, with an aggregate support also planned for the industry at large.</p><p>The first Time Code Summit is scheduled for Oct. 10 at the Linwood Dunn Theatre in Hollywood, Calif. The second will take place Nov. 1 at the BT Tower in London. The third is planned for New York in November.</p><p>The Summits are hosted by Howard Lukk, SMPTE director of engineering and standards, with support from the local SMPTE Sections.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>