<?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/switch" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Switch ]]></title>
                <link>https://www.tvtechnology.com/tag/switch</link>
        <description><![CDATA[ All the latest switch content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Mon, 02 Nov 2020 13:26:24 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Best Switch Topology for AoIP Redundancy ]]></title>
                                                                                                <dc:content><![CDATA[ <p>If you’re new to AoIP topologies, you have probably heard it’s best to set up a central core stack of switches in the TOC with edge switches at each studio or group of studios. There are two good reasons to do this: </p><p><strong>1. Should a studio lose connectivity with the central stack for any reason—fire in the TOC, flood, power outage—individual studios can continue to operate independently via their local switches.</strong></p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:2398px;"><p class="vanilla-image-block" style="padding-top:47.29%;"><img id="k9s3AY8RRWxC6FMP5V8EjQ" name="StackwiseDWG.jpg" alt="Stackwise" src="https://cdn.mos.cms.futurecdn.net/k9s3AY8RRWxC6FMP5V8EjQ.jpg" mos="" align="middle" fullscreen="1" width="2398" height="1134" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/k9s3AY8RRWxC6FMP5V8EjQ.jpg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="credit" itemprop="copyrightHolder">(Image credit: Cisco)</span></figcaption></figure><p>Cisco has a topology called Stackwise, where the back planes of multiple switches in a TOC, for example, can be joined at very high bandwidth (somewhere on the order of 160 gigabits-per-second links) in a daisy chain configuration, as shown above. If any one of the switches should drop out of the stack, the other stack members can still communicate with each other. </p><p><strong>2. All local I/O is handled by the edge switches, which provides a more efficient networking and traffic control by cutting down the number of “home runs” from the studio to the central core stack.</strong></p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:2560px;"><p class="vanilla-image-block" style="padding-top:58.36%;"><img id="HkEPicm9UqDKBXLCBnEPHR" name="SystemDWG.jpg" alt="12-port edge switch" src="https://cdn.mos.cms.futurecdn.net/HkEPicm9UqDKBXLCBnEPHR.jpg" mos="" align="middle" fullscreen="1" width="2560" height="1494" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/HkEPicm9UqDKBXLCBnEPHR.jpg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="credit" itemprop="copyrightHolder">(Image credit: Phil Owens)</span></figcaption></figure><p>Shown above are smaller, 12-port edge switches that handle the local I/O for the studio and have a trunk connection back to the central stack. For additional redundancy, you can take a baseband connection out of one of the local I/O nodes (or BLADEs, in the case of Wheatstone) in the studio and run it into the rack room. This gives you a baseband audio connection directly from the studio to the TOC in case you need to quickly patch programming into the RF chain. </p><p><em>As a sales engineer for Wheatstone, Phil Owens has a working knowledge of AoIP topologies and best practices for designing an effective IP audio networked studio.</em></p> ]]></dc:content>
                                                                                                                                            <link>https://www.tvtechnology.com/opinion/best-switch-topology-for-aoip-redundancy</link>
                                                                            <description>
                            <![CDATA[ Wheatstone's Phil Owens details why you should set up a central core stack of switches ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">FxqZD3E6ePMtmV4wtPcrjZ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/2HUkeUMUqqiWa9e9m3E4YR-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 02 Nov 2020 13:26:24 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Phil Owens ]]></dc:creator>                                                                                                        <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/2HUkeUMUqqiWa9e9m3E4YR-1280-80.jpg">
                                                            <media:credit><![CDATA[Wheatstone]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Strata 32]]></media:description>                                                            <media:text><![CDATA[Strata 32]]></media:text>
                                <media:title type="plain"><![CDATA[Strata 32]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/2HUkeUMUqqiWa9e9m3E4YR-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>If you’re new to AoIP topologies, you have probably heard it’s best to set up a central core stack of switches in the TOC with edge switches at each studio or group of studios. There are two good reasons to do this: </p><p><strong>1. Should a studio lose connectivity with the central stack for any reason—fire in the TOC, flood, power outage—individual studios can continue to operate independently via their local switches.</strong></p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:2398px;"><p class="vanilla-image-block" style="padding-top:47.29%;"><img id="k9s3AY8RRWxC6FMP5V8EjQ" name="StackwiseDWG.jpg" alt="Stackwise" src="https://cdn.mos.cms.futurecdn.net/k9s3AY8RRWxC6FMP5V8EjQ.jpg" mos="" align="middle" fullscreen="1" width="2398" height="1134" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/k9s3AY8RRWxC6FMP5V8EjQ.jpg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="credit" itemprop="copyrightHolder">(Image credit: Cisco)</span></figcaption></figure><p>Cisco has a topology called Stackwise, where the back planes of multiple switches in a TOC, for example, can be joined at very high bandwidth (somewhere on the order of 160 gigabits-per-second links) in a daisy chain configuration, as shown above. If any one of the switches should drop out of the stack, the other stack members can still communicate with each other. </p><p><strong>2. All local I/O is handled by the edge switches, which provides a more efficient networking and traffic control by cutting down the number of “home runs” from the studio to the central core stack.</strong></p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:2560px;"><p class="vanilla-image-block" style="padding-top:58.36%;"><img id="HkEPicm9UqDKBXLCBnEPHR" name="SystemDWG.jpg" alt="12-port edge switch" src="https://cdn.mos.cms.futurecdn.net/HkEPicm9UqDKBXLCBnEPHR.jpg" mos="" align="middle" fullscreen="1" width="2560" height="1494" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/HkEPicm9UqDKBXLCBnEPHR.jpg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="credit" itemprop="copyrightHolder">(Image credit: Phil Owens)</span></figcaption></figure><p>Shown above are smaller, 12-port edge switches that handle the local I/O for the studio and have a trunk connection back to the central stack. For additional redundancy, you can take a baseband connection out of one of the local I/O nodes (or BLADEs, in the case of Wheatstone) in the studio and run it into the rack room. This gives you a baseband audio connection directly from the studio to the TOC in case you need to quickly patch programming into the RF chain. </p><p><em>As a sales engineer for Wheatstone, Phil Owens has a working knowledge of AoIP topologies and best practices for designing an effective IP audio networked studio.</em></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Telestream Releases Switch Version 3.0 ]]></title>
                                                                                                <dc:content><![CDATA[ <p><strong>NEVADA CITY, CALIF.—</strong>An updated version of the Switch cross-platform media player and inspection tool has been announced by Telestream. Switch 3.0 offers new features for comparing multiple files, previewing output through Blackmagic Design devices, and one-step publishing destinations for Vimeo, YouTube and Facebook.</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="Y6GNKYDsg4BFDnapzBPL27" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/Y6GNKYDsg4BFDnapzBPL27.jpg" mos="https://cdn.mos.cms.futurecdn.net/Y6GNKYDsg4BFDnapzBPL27.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>Exports to Vimeo, YouTube and Facebook are supporting from within the Switch user interface. The platform also supports HDMI/SDI output through Blackmagic devices in addition to the previously supported AJA output devices. Switch 3.0 Pro allows for the loading of multiple video files in a single window for frame-by-frame comparisons. In addition, the system supports MXF OP1a and OP-Atom containers export in Switch Pro/Plus models to convert an MPEG2 file into an MXF file; it also features playback and indexing of files for spot-checking of large video files.</p><p>Switch 3.0 is available in three versions, Switch Player, Switch Plus and Switch Pro. All three versions are available on the Telestream website.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.tvtechnology.com/equipment/telestream-releases-switch-version-30</link>
                                                                            <description>
                            <![CDATA[ An updated version of the Switch cross-platform media player and inspection tool has been announced by Telestream. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">7f5q8e32hMvvppeAykXcJV</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/PhrwjGRmjWgBAoqZfKZnYU-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 17 May 2016 10:27:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <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/PhrwjGRmjWgBAoqZfKZnYU-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/PhrwjGRmjWgBAoqZfKZnYU-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>NEVADA CITY, CALIF.—</strong>An updated version of the Switch cross-platform media player and inspection tool has been announced by Telestream. Switch 3.0 offers new features for comparing multiple files, previewing output through Blackmagic Design devices, and one-step publishing destinations for Vimeo, YouTube and Facebook.</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="Y6GNKYDsg4BFDnapzBPL27" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/Y6GNKYDsg4BFDnapzBPL27.jpg" mos="https://cdn.mos.cms.futurecdn.net/Y6GNKYDsg4BFDnapzBPL27.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>Exports to Vimeo, YouTube and Facebook are supporting from within the Switch user interface. The platform also supports HDMI/SDI output through Blackmagic devices in addition to the previously supported AJA output devices. Switch 3.0 Pro allows for the loading of multiple video files in a single window for frame-by-frame comparisons. In addition, the system supports MXF OP1a and OP-Atom containers export in Switch Pro/Plus models to convert an MPEG2 file into an MXF file; it also features playback and indexing of files for spot-checking of large video files.</p><p>Switch 3.0 is available in three versions, Switch Player, Switch Plus and Switch Pro. All three versions are available on the Telestream website.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>