<?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"
     xmlns:cf="https://www.futureplc.com/rss/content-flags"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/interopability" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Interopability ]]></title>
                <link>https://www.tvtechnology.com/tag/interopability</link>
        <description><![CDATA[ All the latest interopability content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Tue, 21 Oct 2025 15:38:25 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ BBright, GlobalM Successfully Trial End-to-End UHD Interoperability ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/bbright-globalm-successfully-trial-end-to-end-uhd-interoperability</link>
                                                                            <description>
                            <![CDATA[ Trial demonstrates Ultra HD interoperability across the entire contribution chain in the cloud ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">aKJvDgUSwUJDhNWvMYE2ZA</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/TEy4RK9kMj45GL8F7qkp2d-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 21 Oct 2025 15:38:25 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Infrastructure]]></category>
                                                                                                                    <dc:creator><![CDATA[ Phil Kurz ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/fioQsUoHKYn3b835FzG7nP.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/TEy4RK9kMj45GL8F7qkp2d-1280-80.jpg">
                                                            <media:credit><![CDATA[GlobalM]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[BBright and GlobalM interop test]]></media:description>                                                            <media:text><![CDATA[BBright and GlobalM interop test]]></media:text>
                                <media:title type="plain"><![CDATA[BBright and GlobalM interop test]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/TEy4RK9kMj45GL8F7qkp2d-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>RENNES, France</strong>—BBright and <a href="https://www.tvtechnology.com/news/globalm-to-showcase-next-gen-live-ip-video-transport-at-ibc2025">GlobalM</a> have conducted a technical trial validating <a href="https://www.tvtechnology.com/news/ultra-hd-defined">Ultra HD</a> interoperability across the entire contribution chain in the cloud, achieving transmission bit rates above 100 Megabits per second—a rate that’s higher than typical satellite contribution paths.</p><p>In the joint trial, BBright’s Ultra HD ST 2110 encoder converted an uncompressed IP input into HEVC 4:2:2 10-bit with the highest quality profile. The stream was transmitted using the <a href="https://www.tvtechnology.com/opinion/srt-in-practice-enabling-smarter-scalable-live-broadcast-infrastructure">Secure Reliable Transport (SRT)</a> protocol to the AWS cloud. There, GlobalM’s cloud transport platform provided secure routing, contribution monitoring and signal integrity across the end-to-end workflow, BBright said.</p><p>At the output, GlobalM restreamed the Ultra HD signal using SRT to a BBright decoder, which reconstructed the feed as an ST 2110 output. The result confirms the ability of both systems to operate seamlessly in an IP-native, cloud-based Ultra HD environment, the companies said.</p><p>“This end-to-end interoperability with GlobalM demonstrates the strength of ST 2110 and HEVC 4:2:2 workflows for high-bitrate Ultra HD contribution,” Guillaume Arthuis, managing director of BBright, said. “It shows that IP-based encoding and cloud transport can now match, and even exceed, traditional satellite links in terms of visual quality, latency and flexibility.”</p><p>This interoperability is opening new opportunities for customers seeking to deliver premium Ultra HD live sports coverage over IP and cloud networks. The combined solution enables rights holders and service providers to scale contribution workflows flexibly, ensuring broadcast-grade performance while reducing operational complexity and costs compared to traditional satellite or dedicated fiber infrastructures, the companies said.</p><p>“Partnering with BBright illustrates how broadcast-quality encoding and professional cloud contribution can converge,” GlobalM Global Sales Manager George Bery said. “This collaboration validates a new generation of interoperable, IP-based workflows capable of transporting Ultra HD content securely and efficiently in the cloud.”</p><p>More information is available on the <a href="https://www.bbright.com/product/encoder/">BBright</a> and <a href="https://globalm.media/">GlobalM</a> websites.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Interoperability: No Media Solution is an Island ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinion/interoperability-no-media-solution-is-an-island</link>
                                                                            <description>
                            <![CDATA[ Many organizations are choosing to move away from end-to-end solutions, in favor of customizable workflows ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">4zdEy6ULPxacc6WMmyUPzJ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/wkdRfRnkdyFkQzySWwHEHA-1280-80.jpeg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 26 Jan 2023 13:28:53 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Jane Sung ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/vnxRMCUu2csuH4aenpLzoT.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/wkdRfRnkdyFkQzySWwHEHA-1280-80.jpeg">
                                                            <media:credit><![CDATA[Adobe Stock Photo]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cinedeck]]></media:description>                                                            <media:text><![CDATA[Cinedeck]]></media:text>
                                <media:title type="plain"><![CDATA[Cinedeck]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/wkdRfRnkdyFkQzySWwHEHA-1280-80.jpeg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Media production is currently undergoing an enormous transformation. Technology is advancing, and cables and connectors are rapidly being replaced by cloud-based solutions. While some media organizations prefer an end-to-end approach, many are instead choosing to use separate vendor solutions for each segment of the workflow. </p><p>Increasingly, companies need flexibility, rather than solutions or services that are proprietary or place rigid definitions on how assets are processed. The availability of solutions that focus on very specific parts of the content supply chain, offer more choice and control over how companies operate. However, if media workflows are compartmentalized in this way, it is critical that solutions do not move into silos, and that all component parts of the workflow interconnect seamlessly. </p><p><strong>Many Parts Make a Whole<br></strong>We’re living in an age of optimization. So, it is incredibly important that each stage of the media workflow, from production, to ingest, to post-production, and right through to distribution, all operate effectively. This is why many organizations are now choosing to move away from end-to-end solutions, in favor of customizable workflows made up of component parts that are best suited to a specific task. </p><p>Alongside the crucial requirement for each link in the chain to be operating as well as it can be, there is also an overriding need for integration. It is great to take an à la carte approach, but that cannot be at the expense of interoperability – no part of the workflow should be isolated. </p><p>The ingest process is a prime example of how an individual workflow segment significantly impacts the subsequent stages. Ingest is a core component of the media workflow, without it, content does not get from camera to consumer. An effective ingest process makes it quick and easy to ingest raw footage, ready for editing and distribution. It is critical that the quality of the content is preserved and that the content is ingested in full, with no gaps. </p><div><blockquote><p>"A good ingest process can help the rest of the workflow run smoothly and efficiently.</p></blockquote></div><p>The role of ingest does not end there. A good ingest process can help the rest of the workflow run smoothly and efficiently. For example, if during production the footage can be recorded directly to shared storage, editors can gain access immediately. This prevents subsequent delays to the post-production schedule, as each workflow follows on seamlessly from the next. This way of working enables both master camera record and proxy record, to be undertaken concurrently, so users can access whichever file suits their requirements.</p><p>When best practice for content ingest is followed, all of the required media is captured and stored with the appropriate metadata. If the proxies are created at the same time as the master camera record, the files can be tagged with consistent metadata, which avoids confusion. </p><p>This makes it easier for media companies to manage and quickly locate assets later on. A good ingest process will also ensure that assets are organized well from the start. Doing this prevents media businesses from having to structure assets retrospectively, which is time consuming and inefficient. </p><p><strong>API is the Language of Interoperability<br></strong>When taking an à la carte approach, all components of a media workflow need to connect together seamlessly, through an Application Programming Interface (API). The API enables interaction between solutions, so they can communicate and understand specific requests. </p><p>An API also enables resources and information to be shared, without compromising security, control, and authentication. However, not all APIs are the same. Some may seem comprehensive on the surface, but actually, when you look closer, they are incomplete or incompatible. Other APIs may be complete but not have the required documentation. The difference in quality between APIs can be significant.</p><p>For a solution to be fully interoperable and easy to integrate, the API needs to be high-quality, customizable, fully comprehensive, and come with all the right documentation. A flexible API will allow media organizations to deploy a solution in a way that suits them. </p><p>So, how can media organizations ensure they implement a solution with a great API? For effective integration, solutions need a well-constructed RESTful API.  For an API to qualify as a RESTful, it must meet specific architectural requirements. This makes RESTful APIs scalable, faster, more lightweight, and easier to use than a prescribed protocol with restrictive requirements.   </p><p>With media organizations increasingly moving operations to the cloud, interoperability is only going to become more important. An issue with API quality has the potential to make or break a workflow. We’re now at the point where companies need to be able to drop a product into their ecosystem, knowing that it will meet their requirements, with minimum effort. </p><p>To achieve this, solutions need to excel at the job they are designed for, and at the same time, offer a fully customizable RESTful API for simple integration. No media solution is an island, so we need interoperability across production and post-production workflows to future-proof our industry.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ The Importance of Multi-Vendor Interoperability for Broadcast ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinion/the-importance-of-multi-vendor-interoperability-for-broadcast</link>
                                                                            <description>
                            <![CDATA[ RIST recently surveyed of media and broadcast professionals worldwide to understand how the protocol is being used in practice across the industry ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">tt4SbZrbhjvapYgDvW67wm</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/erCz98tmcmDZfbQRa4KVfK-1280-80.jpeg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 05 Oct 2022 17:27:21 +0000</pubDate>                                                                                                                                <updated>Wed, 05 Oct 2022 18:13:00 +0000</updated>
                                                                                                                                            <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Ciro A. Noronha, PhD ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/2xDY7YvH8LYUn3wCnfSTik.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/erCz98tmcmDZfbQRa4KVfK-1280-80.jpeg">
                                                            <media:credit><![CDATA[Adobe]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Adobe]]></media:description>                                                            <media:text><![CDATA[Adobe]]></media:text>
                                <media:title type="plain"><![CDATA[Adobe]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/erCz98tmcmDZfbQRa4KVfK-1280-80.jpeg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>As more and more broadcasters and video content providers adopt or consider adopting IP for transporting content, the need for a reliable, interoperable transport solution is becoming ever more clear. Broadcast workflows have become increasingly complex over time in part because of the many media businesses vendors involved in the entire media supply chain, and also because not all products and workflows are capable of operating together. </p><p>While the issue of interoperability can be problematic at all stages of the broadcast workflow, the problem is particularly apparent when it comes to transporting content. The actual physical process of sending content from content provider to broadcaster or affiliate is often not straightforward. Different encoders and decoders operating with incompatible transport protocols cause real problems in the industry. </p><p><strong>Industry response<br></strong>A group of industry experts developed the <a href="https://www.tvtechnology.com/the-wire-blog/rist-forum-established-with-21-members-promotes-interoperable-internet-video-transport-solution-at-nab-2019">Reliable Internet Stream Transport (RIST) </a>protocol in 2018, in response to this problem. RIST is an open-source, open-specification transport protocol designed for transporting broadcast grade video over the Internet, while ensuring reliability and security. With the intention of developing a cross industry interoperable standard, any organization can download the protocol information and develop compliant solutions that can be incorporated into their own products at no cost and very few restrictions. </p><figure class="van-image-figure pull-right inline-layout" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:1000px;"><p class="vanilla-image-block" style="padding-top:40.00%;"><img id="tBg3uSsYq2EkY5WUgVXwyN" name="unnamed (1).png" alt="RIST Forum" src="https://cdn.mos.cms.futurecdn.net/tBg3uSsYq2EkY5WUgVXwyN.png" mos="" align="right" fullscreen="" width="1000" height="400" attribution="" endorsement="" class="pull-right"></p></div></div><figcaption itemprop="caption description" class="pull-right inline-layout"><span class="credit" itemprop="copyrightHolder">(Image credit: RIST Forum)</span></figcaption></figure><p>RIST has been on the scene for several years now, so it seems timely that the RIST Forum, created to drive the adoption of RIST, has recently carried out a survey of media and broadcast professionals across the globe to understand how RIST is being used in practice across the industry.</p><p><strong>RIST uses in the real world<br></strong>Of the media and broadcast professionals surveyed, approximately half confirmed that they were currently using RIST at the time of the survey. Perhaps unsurprisingly, the main users of RIST were fibre and IP network operators, and television broadcasters. The survey highlighted that the protocol is also being used, albeit to a lesser extent, by sports rights owners, teleport owners, by systems integrators and during the video and TV production process.  </p><a target="_blank"><figure class="van-image-figure  inline-layout" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:1920px;"><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="KdvE77boEmx7NYtY6zhQTM" name="RIST Chart.jpeg" alt="RIST" src="https://cdn.mos.cms.futurecdn.net/KdvE77boEmx7NYtY6zhQTM.jpeg" mos="" align="middle" fullscreen="1" width="1920" height="1080" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/KdvE77boEmx7NYtY6zhQTM.jpeg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=" inline-layout"><span class="credit" itemprop="copyrightHolder">(Image credit: RIST)</span></figcaption></figure></a><p>The protocol is not being used in isolation; more often than not, it is being used alongside multiple transport protocols such as SRT, RTP, UDP and RTMP. This highlights the fact that RIST can, and is being, combined with other protocols to address the limitations of said protocols. </p><p>According to the survey responses, RIST is being used in a wide range of use cases, from streaming a 24/7 news channel, for content contribution and distribution, as part of cloud-based workflows, and as a backup for contribution delivered by other means. </p><p><strong>Interoperability is critical<br></strong>With so many different solutions on the market for each stage in the broadcast workflow, all with different price points and functionality, content owners and media companies want to be able to choose the product that best fits the type and value of the content, as well as their operation and business needs.</p><p>This preference for an a-la-carte approach to technology puts interoperability right at the top of the list in terms of priority. This is evident in the findings of the survey with 91% of broadcasters surveyed citing multi-vendor interoperability as a key factor when choosing which protocol to use.  </p><p><strong>Other considerations when choosing which protocol<br></strong>As broadcasters operate in an increasingly competitive market, the ability to deliver a reliable and efficient service is paramount. It is no surprise then that alongside interoperability being a key factor when choosing which protocol to use, the broadcasters surveyed stated that seamless redundancy and availability was the next most important consideration, followed by ease of use, then ability of the protocol to operate in degraded networks. </p><p><strong>Increased demand for content<br></strong>Consumer demand for content, in various formats, appears to be increasing exponentially and supplying this demand is in itself a challenge for the industry. The Internet is an economically viable and flexible medium for transporting content and this makes it sometimes preferable over traditional methods of transfer. </p><p>The Internet as a transport method has proven that it has an important role to play in today’s diverse broadcast industry. Media organizations and broadcasters need interoperability between vendor solutions in order to work efficiently so that they can meet the seemingly insatiable demand for content. </p><p><strong>The (bumpy) road to interoperability<br></strong>Since the industry started transitioning to using the Internet as a contribution mechanism, much has been penned about the importance of interoperability. While it would be hard to find someone in the industry that didn’t think it was vital, it is harder still to create the perfect conditions for interoperability to exist. Interoperability, by its very nature, requires a level of partnership working and, that can be difficult to achieve in a competitive commercial environment. </p><p>Technology companies naturally want to recoup maximum return on their R&D investments and that can mean making a solution proprietary. The industry-wide journey towards IP in general is set to continue so the importance of interoperability is only going to grow. In order to get the right level of cooperation and open communication to have full interoperability, we need to have a more partnership-led approach involving industry experts working together towards a common goal.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Calrec Passes JT-NM Interop Test ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/equipment/calrec-passes-jt-nm-interop-test</link>
                                                                            <description>
                            <![CDATA[ The test exams how technologies work together and adhere to SMPTE standards. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">u6dZBTvPfbRScxqkAMw3Ar</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/JniXdxVfPyfkfR5ccuvQLn-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 01 Oct 2019 14:10:47 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Phil Kurz ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/sNtEgpne6F9EezmB5uHeVM.png ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/JniXdxVfPyfkfR5ccuvQLn-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                        <media:description><![CDATA[Calrec’s ImPulse audio processing and routing engine supports AES67 and SMPTE 2110 connectivity.]]></media:description>                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/JniXdxVfPyfkfR5ccuvQLn-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>HEBDEN BRIDGE, U.K.—</strong>The Joint Task Force on Networked Media (JT-NM) has given Calrec passing marks on its IP interoperability testing and is including the company in its JT-NM Tested Catalog, published last month at IBC 2019 in Amsterdam.</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="JniXdxVfPyfkfR5ccuvQLn" name="" alt="Calrec’s ImPulse audio processing and routing engine supports AES67 and SMPTE 2110 connectivity." src="https://cdn.mos.cms.futurecdn.net/JniXdxVfPyfkfR5ccuvQLn.jpg" mos="https://cdn.mos.cms.futurecdn.net/JniXdxVfPyfkfR5ccuvQLn.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div><figcaption itemprop="caption description" class="pull-"><span class="caption-text">Calrec’s ImPulse audio processing and routing engine supports AES67 and SMPTE 2110 connectivity. </span></figcaption></figure><p>“What the JT-NM is doing—backed by VSF, SMPTE, AMWA and the EBU—is tremendously important in terms of continuing the push to true IP interoperability,” says Pete Walker, senior product manager at Calrec.</p><p>“It includes NMOS, which we believe is vital as a standardized mechanism for not only discovery/advertisement of IP technologies connected to a network alongside IP streams, but also connection management from a centralized point.”</p><p>The JT-NM’s interoperability testing exams how technologies work together and adhere to SMPTE standards.</p><p>Calrec participated in JT-NM testing in August. The company’s products were tested for SMPTE ST2110 and ST2022-7 interoperability.</p><p>More information is available on the Calrec <a href="https://calrec.com/news/calrec-continues-push-for-true-ip-interoperability-passing-the-recent-jt-nm-interop-test/">website</a>. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ A Future of Interoperability? ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinions/a-future-of-interoperability</link>
                                                                            <description>
                            <![CDATA[ The transition to IP-based media production and transport in our industry is the most transformative development since the move to digital. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">a8CpqujNdLQFgd4mjv64CF</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/6A38GxE8wZjfuoLDPwxAgY-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 24 Oct 2016 13:00:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                <author><![CDATA[ tom.butts@futurenet.com (Tom Butts) ]]></author>                    <dc:creator><![CDATA[ Tom Butts ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/Ym75XZxKuaGiZGj7nMGeGM.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/6A38GxE8wZjfuoLDPwxAgY-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/6A38GxE8wZjfuoLDPwxAgY-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The transition to IP-based media production and transport in our industry is the most transformative development since the move to digital. Internet protocol will lay the foundation for a revolutionary process that will enable faster, more flexible production and a much wider and more diverse array of services and programming.</p><p>But in the fast pace world of high-tech, the transition for IP-based video transport within the broadcast community has been slow and, for better or worse, some vendors are moving forward with their own networking protocols. Our industry looks to SMPTE (and related groups, such as AES and VSF) for the standards to guide this transition forward, and while the group is making great progress towards a standard, organizations such as the Alliance for IP Media Solutions (AIMS) are helping to corral manufacturers, media companies and the various alphabet soup of standards bodies towards a future where interoperability will break down the proprietary barriers that have characterized so much of our industry’s history. Less than a year old, AIMS has already attracted more than 50 members, including its founding members Imagine Communications and Grass Valley. (Check out our story, “The Ground Level View of IP-Based Media Transport”)</p><p>At the 2016 IBC Show, we saw the latest developments in these efforts with the IBC IP Interoperability Zone, sponsored by AIMS and the IABM and showcasing the work of the JT-NM (the Joint Task Force on Networked Media, a combined initiative of AMWA, EBU, SMPTE and VSF), and the AES on a common roadmap for IP interoperability. The zone included a live production studio, based on the technologies of the JT-NM roadmap that Belgian broadcaster VRT has been using daily on-air since last summer as part of the LiveIP project, a collaboration between VRT, the European Broadcasting Union (EBU) and LiveIP’s 12 technology partners.</p><p>After the show, I spoke with Mike Cronk, vice president of core technology for Grass Valley and the chairman of the board for AIMS about reaction to the zone. “People were saying, ‘wow, this stuff works,” he said. “There was the live IP demonstration people were doing real television with it. People said, ‘OK, now I see things coming together. I’m going to think more about IP.’”</p><p>Cronk said that, in addition to promoting interoperability in the IP world, the main goal for AIMS now is to support the adoption and completion of the SMPTE-2110 transport protocol which will provide the foundation for that interoperability. But he added that AIMS is also helping to fill in the some of the gaps during the standards process.</p><p>“I think AIMS has helped bring some unity,” he said. “The good people at SMPTE would’ve still been working probably on the same thing. AIMS can’t claim credit for that at all. We’re just one other piece of the puzzle.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>