<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ievgenii Larin on Medium]]></title>
        <description><![CDATA[Stories by Ievgenii Larin on Medium]]></description>
        <link>https://medium.com/@ievgeniilarin?source=rss-6e9debf4afe9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mPcPdPvG1Dxnemh-.jpg</url>
            <title>Stories by Ievgenii Larin on Medium</title>
            <link>https://medium.com/@ievgeniilarin?source=rss-6e9debf4afe9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:20:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ievgeniilarin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NDI 5 Release Notes]]></title>
            <link>https://ievgeniilarin.medium.com/ndi-5-release-notes-efcac9a479e4?source=rss-6e9debf4afe9------2</link>
            <guid isPermaLink="false">https://medium.com/p/efcac9a479e4</guid>
            <dc:creator><![CDATA[Ievgenii Larin]]></dc:creator>
            <pubDate>Thu, 29 Jul 2021 07:21:05 GMT</pubDate>
            <atom:updated>2021-11-23T08:27:12.068Z</atom:updated>
            <content:encoded><![CDATA[<p>The copy of the NDI Changes PDF document bundelled with the NDI 5 SDK installer.</p><h3>NDI 5.0.11.1</h3><p>Bug fix for the NDI Transmit plug-in for Adobe CC applications.</p><h3>NDI 5.0.10.1</h3><p>Version number update to match public launch of NDI Tools that includes NDI Bridge.</p><p>MOV files recorded by the NDI SDK or Tools where technically limited to about 14 hours long because the indexes for this file format have a size limitation of 32bits in “number of clock samples”. By using the extended version of these headers there is no longer any reasonable restriction on the length of recordings.</p><h3>NDI 5.0.10</h3><p>First version that includes full NDI Bridge. The NDI Bridge executable supports three command line options, the first is “/join” which will start the application in the Join mode. “/local” and “/host” start the application in Local and Host mode respectively.</p><p>Support for hardware rendering of the mouse cursor in Screen Capture without “trails” and without any performance overhead.</p><p>KVM support for applications has been added to the Advanced SDK.</p><p>Support for the latest version of the Adobe CC applications that have been updated.</p><p>Reliable UDP sending is likely to use lower CPU usage than previous versions. NDI will take advantage of computer systems with NICs that support hardware accelerated UDP segmentation offload. This can be used to offload much of the CPU burden of high bandwidth UDP sending. Better reliable UDP spreading of sending and receiving across multiple CPU cores.</p><p>If you are connected to an NDI discovery server and the network connection is physically lost (i.e. the application or device on one side does not gracefully close the connection), this will now be detected and handled much more quickly than previous versions.</p><p>Lower CPU usage in many situations through more efficient use of queues without CPU locking.</p><p>The NDI installer on Windows will check whether “Media Foundation” is available on your operating system and notify you if it needs to be installed. There are some local versions of Windows (e.g. Windows 10 Pro N) that might not include this as a default option.</p><p>The NDI installer will backup your NDI configuration when it is being installed so that each update to Tools does not wipe out your configuration. When you uninstall NDI Tools completely, the configuration should be completely removed.</p><p>ix on Apple SDKs for cases in which extra data was incorrect in HX2 streams, we now handle this condition gracefully.</p><p>Apple SDKs with Free NDI SDK now bring back all of the Apple platforms into a single installer which unfortunately significantly increases the install size. It does mean one SDK covers Mac, iPad, iOS, tvOS however.</p><p>Android SDK is available for free for use in mobile applications.</p><h3>NDI 5.0.9</h3><p>Launching an NDI application no longer will try to configure the firewall for you unless you have administration privileges. This avoids the potential for the annoying user-access-control dialog to come up each time you launch an NDI application — you are likely still then to see a firewall warning which you will have to click on “Allow” access for, or NDI will not be able to access you network correctly.</p><p>The NDI screensaver is now aware of multi-DPI settings when you have multiple monitors on the system with different DPI settings.</p><p>The NDI Webcam tool will no longer show an NDI logo when connecting to sources. This makes the tool better for people who are using it in production.</p><p>When auto-focus is switched off for a PTZ Monitor in Studio Monitor, we do not resend the previous focus distance which makes the operation “feel better” because the focus stays set on the last value it was seen when auto-focus was used.</p><p>Reliable UDP sending is likely to use lower CPU usage than previous versions. NDI will take advantage of computer systems with NICs that support hardware accelerated UDP segmentation offload. This can be used to offload much of the CPU burden of high bandwidth UDP sending.</p><h3>NDI 5.0.8</h3><p>Very significant changes have been made to RUDP sending to allow for much better network utilization on network with high round-trip time or packet loss. In addition, RUDP support has significant updates with much improved performance on WAN and MTU discovery. Significant improvements on macOS, iOS and Android have been made. Some important notes have been added to the Advanced SDK documentation regarding how to efficiently send compressed frames to the network under poor conditions with the SDK.</p><p>NDI SDK documentation has been updated with comments on performance, particularly related to some ARM platforms.</p><h3>NDI 5.0.7</h3><p>The NDI redistributable that was included with the SDK was not digitally signed, this has been corrected.</p><p>Fix for NDI Screen Capture HX in which a lockup was possible if a device (e.g. blue-tooth keyboard) was removed at almost the same time that an NDI connection was closed.</p><p>Fix for a problem with Screen Capture in which we might not send the first frame if the current screen was not changing at the time the NDI connection was made.</p><p>A condition was fixed in which Panasonic NDI cameras might not be detected on the network if they had been added after NDI started and had not yet been running for more than a few minutes.</p><h3>NDI 5.0.6</h3><p>Change to the RUDP receiver (and somewhat the sender) to have higher performance on multi-core machines that are under load or running many threads. When possible, we now keep a thread in a wake-able state on each CPU core so that upon receiving data we always know that it can be processed if there is any CPU time on the machine.</p><p>In Screen Capture it was possible that if a screen was not currently being updated that new NDI connections that occur do not receive a frame. The primary problem occurred when there was more than one connection at a time.</p><p>The NDI Launcher application will notify you when there is a newer version available, so you do not always need to track our web site for changes!</p><p>The NDI launcher will give you access to the NDI changes list so you can quickly see what has been updated in this version of NDI.</p><p>A crash that could occur based on timing when applications connected and disconnected from the “Web Cam input” on Windows has been fixed.</p><p>The discovery server allows you to specify a port number using the flag “-port 5959”. You can now choose any port you want and in Access Manager or the configuration files you can specify a discovery server address that includes a port number. This allows you for instance to run multiple discovery servers on a single machine that control different sets of NDI sources.</p><h3>NDI 5.0.5</h3><p>Using NDI | HX v1 cameras with the Bridge Local mode (our transcoder) could cause video artifacts under certain network conditions due to the potential for compressed frames to be missed. This is now no longer possible.</p><p>There was an issue where if a configuration file had a NIC filter set up that specified adapter that did not exist on your machine then we would bind to a NIC that does not exist which would fail but might slow down the creation of connections or other possibly symptoms. We now validate the configuration files against the NICs that are on the machine and check that the IP addresses are truly valid before attempting to bind to them.</p><p>The NDI Launcher application will notify you when there is a newer version available, so you do not always need to track our web site for changes!</p><p>The NDI launcher will give you access to the NDI changes list so you can quickly see what has been updated in this version of NDI.</p><p>SDK sample code that shows how to display the average frame time and jitter in the advanced SDK</p><h3>NDI 5.0.4</h3><p>NDI Remote had an issue with some cameras when moving between the high quality and proxy streams. This has been resolved.</p><p>Reliable UDP sending was always asynchronous in all sending, however it still needed to use a single thread per sending destination to ensure that individual connections could not interfere with other ones (which might have stalled). This is no longer the case and RUDP can now send across all destinations with all buffers in flight without needing any additional threads to service the sending.</p><h3>NDI 5.0.3</h3><p>Improvement to Windows based Audio and Video drivers that will make them much more robust to applications that are less tolerant of “strange clocking”. In general, this makes things far more robust and should result in much better results. A placeholder image is shown when you are not connected to a source so that the application receives video instead of simply receiving no data.</p><p>In the NDI Tools on Windows, clicking on the “Balloon help popups” in Screen Capture and Webcam input no longer opens the help, but instead opens the context menu for that tool. This is very convenient and much less annoying! (Help is still available on the context menus).</p><p>The Webcam tool on Windows will connect to audio much faster. It was previously a problem that when you started a call (e.g. with Skype, Teams or Zoom) that it took about half a second for the audio to even start which meant that communication was hard. This should no longer happen.</p><p>Importantly, if you are using the Webcam plugins with applications like Skype, Teams or Zoom and you are using audio content that is not just speech, it is important to disable noise suppression and echo cancellation. These effects are designed to make speech more audible against background sounds however can also create significant audio artifacts on music or other non-speech content.</p><p>Audio support on some much older NDI HX v1 converter devices was not working, this has now been solved.</p><h3>NDI 5.0.2</h3><p>NDI discovery server has an optional parameter that allows you to bind it to a single NIC on your machine for improved security.</p><p>NDI discovery server displays output that is designed to be read by another application that might want to provide a UI on top of it.</p><h3>NDI 5.0.1</h3><p>Example code for showing how to connect to a device (as a receiver) and recover the tally state. This makes the implementation of external tally devices very simple. This uses the <em>tally_echo</em> functionality.</p><p>New example code included in NDI Advanced SDK.</p><p>RUDP is available as a specific connection type setting on macOS, previously “auto” selected it because it is now the default but there should be a specific setting that enables it.</p><p>The “preferred NIC” is not a guarantee that a NIC will be used on all protocols since there are some cases where it might not be possible; this is particularly true for the older transfer protocols. We have extended the support for NIC selection to include more modes and increasing both sides of the connection (both sending and receiving).</p><p>Bug fix for a case in which connection sharing might not have always worked, particularly when using loop-back on the local machine. This did not actually cause any visible problem but caused NDI to work a little less efficiently than it should have.</p><p>Studio Monitor PTZ keyboard shortcuts handled “left” at a slightly different speed from “right”. These now match exactly.</p><p>Changes to HX drivers on iOS that make them more compliant with app store rules.</p><p>Bug fix for crash using NDI Audio Direct with Adobe Audition.</p><h3>NDI 5.0.0</h3><p>The first launch of NDI 5!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efcac9a479e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NDI 5 Overview]]></title>
            <link>https://ievgeniilarin.medium.com/ndi-5-overview-ac5f255fa5e4?source=rss-6e9debf4afe9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac5f255fa5e4</guid>
            <category><![CDATA[ndis]]></category>
            <dc:creator><![CDATA[Ievgenii Larin]]></dc:creator>
            <pubDate>Sat, 17 Jul 2021 17:12:56 GMT</pubDate>
            <atom:updated>2021-07-17T17:15:14.585Z</atom:updated>
            <content:encoded><![CDATA[<p>A rundown of NDI 5 headline features. The overview is focused primarily on NDI Tools for Windows.</p><h3>NDI Launcher</h3><p>The new app called NDI is launcher for the NDI Tools applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1ZIrVh07yyJ42BNZo95lQ.png" /><figcaption>Quick access for the NDI Tools applications</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HsWf9dfWbybOohEUxWpcQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DwPUlNBYFaXlwZYXkCWSBA.png" /><figcaption>Shortcuts for each application contain a brief explanation of functionality in a couple of slides</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhgAnu4l81lkRX2WmweSdw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCxbeG3OXiF3U-tapnfg-Q.png" /><figcaption>An easy way to check NDI version and change Recieve and Send groups</figcaption></figure><h3>The New White Paper on Networking Best Practices</h3><p>The new <a href="https://go.ndi.tv/NDI_NetworkingBestPractices">White Paper on Networking Best Practices</a> contains more technical details and it is much more specific on certain use cases.</p><h3><strong>Redundant NDI Discovery Servers</strong></h3><p>From the NDI Networking Best Practices document:</p><blockquote>Within NDI version 5 there is full support for redundant NDI discovery servers. When one configures a discovery server it is possible to specify a comma delimited list of servers and then they will all be used simultaneously.</blockquote><blockquote>If one of these servers then goes down, then as long as one remains active then all sources will always remain visible if at least one server remains active then no matter what the others do then all sources can be seen.</blockquote><h3>Reliable UDP</h3><p>From the NDI Networking Best Practices document:</p><blockquote>The new NDI protocol uses a highly optimized UDP sender that supports very high latency connections, with congestion control and loss recovery, full inter-stream bandwidth management and connection sharing, no front of line queue blocking, reduced number of open ports and fully asynchronous sending and receiving.</blockquote><p>Reliable UDP is based on <a href="https://en.wikipedia.org/wiki/QUIC">QUIC</a> designed by Google.</p><p>From NDI 5 SDK Documentation:</p><blockquote>We generally discourage the use of Multicast since configuration and ensuring that high performance is achieved is very difficult at a network level in most cases the default protocols (particularly reliable UDP) perform much better.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FkG8nn-BiGYE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DkG8nn-BiGYE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkG8nn-BiGYE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe1a100eb2c80a28e6c823594bf0962c/href">https://medium.com/media/fe1a100eb2c80a28e6c823594bf0962c/href</a></iframe><h3>NIC Selection</h3><p>From the NDI Networking Best Practices document:</p><blockquote>It is generally preferred that you let NDI select the network adapters automatically which can smartly select which to use and how to choose the ones that result in the best bandwidth.</blockquote><blockquote>While in some modes NDI can automatically balance bandwidth across multiple NICs, it is normally better for you to use NIC teaming at a machine configuration level which can result in much better performance than what is possible in software.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cRNBljb3HqdLW24_vwiT9A.png" /><figcaption>NIC Selection configuration is part of NDI Access Manager</figcaption></figure><p><strong>Enzo Quaglia in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>So … KVM is not working great anymore (some software doesn’t want to move or be closed with KVM), NIC selection doesn’t work, R UDP is QUIC … nice Alpha version !</blockquote><p><strong>Kane Peterson in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>It’s permissions. Try running NDI Screen Capture as Admin and it will let you interact with high privilege applications.</blockquote><blockquote>Same thing could happen before. I have my auto start NDI Screen Captured set to run with high privilege so I can interact with Task Manager is needed. You might want to turn down the UAC setting in Windows as well.</blockquote><blockquote><strong>For NIC selection. What is the other end? They both have to be NDI 5 and it doesn’t control all transmission modes. Lastly best option if you want to set the network for NDI to use, setup a Discovery Server.</strong></blockquote><h3>NDI Device Alias</h3><p>Now it is possible to use custom host name (not a computer name) for NDI feeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Puj7XpD3lghVHENYYUE61Q.png" /><figcaption>Custom name for a host of NDI feeds in Access Manager</figcaption></figure><h3>NDI Bridge (Beta)</h3><p>Secure sharing NDI sources between remote sites. NDI Bridge works with alpha channel, KVM, PTZs, tally, metadata.</p><p><strong>Currently it is possible to transcode or redistribute NDI feeds in the Local mode only.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPHq5wAf6Oy0&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPHq5wAf6Oy0&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FPHq5wAf6Oy0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0f0d4aa6fa27f6548b13d5b5f3ef9f23/href">https://medium.com/media/0f0d4aa6fa27f6548b13d5b5f3ef9f23/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G6inTZTs9nB7B7kbCkjMKg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMiZGk6d8vbPFq3FaRAtaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uxk6tfV4F2WXFtm_gc-99w.png" /><figcaption>NDI Bridge offers three modes: Local, Host, Join</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eTTZ40bmc2Z3kPvmM4yd_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtSdoAoEFZJpHcmsjNBNtw.png" /><figcaption>Compatibility check for encoding and decoding H.264 and H.265 (H.265 software decoder is a paid option on Microsoft Store)</figcaption></figure><p>Once it was clear that NDI Bridge is still in beta and and the Host and Join modes are not released users complained heavily.</p><p><strong>Chris McCann in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>All that wait and the main feature still isn’t ready? Sigh.</blockquote><p><strong>Russ Smrtt in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>Yea i’m quite pissed of right now…</blockquote><blockquote>Was waiting NDI 5 only for this!</blockquote><p><strong>John Benton in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>BETA on the most important parts. Have to agree that part was pretty awful. Just say that it will be BETA up front. People had really high expectations.</blockquote><p><strong>Andrea Angeli in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>It is quite upsetting to get something you’re waiting for so long and to realize that it’s just a beta version that we cannot use in serious productions. The communication was really bad. It seemed you were releasing something cool and now half of the video world’s professionals are simply upset about what we’ve seen today.</blockquote><p><a href="https://uk.linkedin.com/in/winmoz"><strong>Stephen Wind-Mozley</strong></a><strong>, CMO at Vizrt Group in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote><strong>We wanted to get you the biggest release we could. Literally millions of lines of code, across multiple operating systems, doing some things that we had to take a deep breath to even contemplate. Yes we could have waited until all the ducks where in a row, but we think there is so much in NDI 5 it was better to share what we are able as soon as possible, rather than hold back longer.</strong></blockquote><blockquote><strong>You know we will keep going and we will not stop. We remain on a mission to make video better for everyone and you, the community, make that possible. Thank you.</strong></blockquote><h3>NDI Remote (Beta)</h3><p>From the <a href="https://www.ndi.tv/">NDI.tv</a>:</p><blockquote>Securely connect with multiple remote contributors to receive their video and audio over the internet by sharing a link.</blockquote><p><strong>NDI Remote is not a two-way communication application with automatic mix-minus.</strong></p><p>NDI Remote is a tool to add a remote NDI source via WebRTC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2VAsOnpz1oMHjWEZDWxHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6OSgv167o92WgWfhsSTQw.png" /><figcaption>Managing Connections within NDI Remote</figcaption></figure><p>Many users were confused and asked about features typical for a conference app.</p><p><strong>Tim O’Brien in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>Soooo…. Downloaded and like it, but how do you handle 2 way feeds? For example a panel discussion with live remote? Do you need a seperate computer or browser for the return ndi feed?</blockquote><p><strong>Penn Tangu in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>Looks like you need to send a feed to your remote guests. I think NDI remote is only meant to bring in remote cameras for now.</blockquote><p><strong>Andrew Abrams in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>As far as remote I was trying to figure that out as well. Kinda of defeats the purpose until they figure out how to get the return feed. I thought that’s why they made it, their own version of zoom.</blockquote><h3>NDI Audio Direct (Beta)</h3><p>From the <a href="https://www.ndi.tv/">NDI.tv</a>:</p><blockquote>Audio Direct is a set of audio plugins that allows virtually any audio software application to take advantage of NDI.</blockquote><blockquote>Users select, receive, and generate multichannel audio with extremely high quality and near zero latency.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8m5P9b4sJ9tab54EwFuKxA.png" /><figcaption>NDI Input and NDI Output VST3 plugins</figcaption></figure><p><a href="https://harrisonconsoles.com/product/mixbus/">Harrison Mixbus</a> and <a href="https://ardour.org/">Ardour</a> are two compatible application suggested by NewTek. Some users have successfully tried the NDI Output plugin with <a href="https://www.reaper.fm/">Reaper</a>.</p><p>NDI Audio Direct is not a Dante competitor or replacement.</p><h3>NDI Benchmark</h3><p>The new utility is bundled with NDI 5 SDK. NDI Benchmark is a syntethic test showing how many 1080p60 NDI feeds a particular system can handle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bX-LFjZQ9sc6D1cuCsqYbw.png" /><figcaption>NDI Benchmark</figcaption></figure><p><strong>Kane Peterson in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>I think it can be useful to get a benchmark how many streams of NDI the system can handle. Real world usage will be lower than this, because you need CPU cycles left over for running the applications and other tasks, but at least it can give you and idea of how well a system can perform once you get the data into the system.</blockquote><p><strong>Jurgen Bauwens in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>On my home video editing workstation this tool doesn’t seem to work. It starts but closes before I get any result.</blockquote><p><strong>Carl Mills in the </strong><a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></p><blockquote>Run in inside command prompt, if you just double click it in windows it’ll close when finished, thus not giving you a chance to view the result.</blockquote><h3>NDI iOS Test Patterns App</h3><p>From the <a href="https://www.ndi.tv/">NDI.tv</a>:</p><blockquote>Available free from the App Store, <a href="https://apps.apple.com/us/app/ndi-test-patterns/id1571995248">NDI iOS Test Patterns</a> app allows users to test NDI signals and NDI enabled devices for color and sound, independent of other hardware.</blockquote><h3>Useful Links</h3><ul><li><a href="https://www.keycodemedia.com/2021/06/23/the-state-of-ndi-in-2021/">The State of NDI® in 2021 + NDI® Version 5</a></li><li><a href="https://www.ndi.tv/nditv/odv/ndi-tv-21-005-ndi-5-sdk-developers-conference/">NDI 5 SDK Developers Conference</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac5f255fa5e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Stop NDI Traffic Going Over Dante Network]]></title>
            <link>https://ievgeniilarin.medium.com/how-to-stop-ndi-traffic-going-over-dante-network-b43c8af2c00c?source=rss-6e9debf4afe9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b43c8af2c00c</guid>
            <category><![CDATA[live-streaming]]></category>
            <category><![CDATA[ndis]]></category>
            <category><![CDATA[dante]]></category>
            <category><![CDATA[vmix]]></category>
            <dc:creator><![CDATA[Ievgenii Larin]]></dc:creator>
            <pubDate>Mon, 03 May 2021 14:59:28 GMT</pubDate>
            <atom:updated>2021-05-07T17:15:08.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pe2UMJFMcKU3-pIvDlGcug.png" /></figure><h3>Disclaimer</h3><p>I’m not a network engineer and I don’t pretend to understand why things work like they do. I’ve been trying to find out how to use computers with multiple NICs connected to multiple physical networks or VLANs with NDI and Dante for quite a while.</p><h3>Credits</h3><p>The solution came from <a href="https://www.linkedin.com/in/tom-van-den-heuvel-5a518964/">Tom van den Heuvel</a>, who commented the <a href="https://youtu.be/eNVm4Q5GjGA">tutorial</a> from <a href="https://www.youtube.com/c/Streamingtech">Jon Pratchett</a>.</p><h3>Setup</h3><p>You want to run two different networks handling two different types of sources: NDI (video) and Dante (audio).</p><p>You have NDI devices that access only the NDI network and you have Dante devices that access only the Dante network. And you have computers with multiple dedicated NICs for accessing each network.</p><p>A typical setup might involve multiple vMix stations sharing NDI sources and accessing Dante-enabled audio gear. Each vMix station has two network adapters: one for NDI and one for Dante.</p><h3>Problem</h3><p>Everything is great until you monitor network traffic on vMix PCs. For some reason NDI traffic is polluting the Dante network. In such a situation Dante might work unreliably.</p><p>Dante uses standard Voice over IP Quality of Service switch features to prioritize clock sync and audio traffic over other network traffic, but for NDI Quality of Service should be disabled all together. Mixing NDI and Dante multicast traffic in one network is not recommended.</p><p>Dante Virtual Soundcard has an explicit option for choosing what NIC is used for Dante traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmXgTqGaqyy3anzQldhJCQ.png" /><figcaption>Dante Virtual Soundcard on macOS</figcaption></figure><p>NDI Access Manager has nothing similar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtwvDw74SspsEKUABHKzmA.png" /><figcaption>NDI Access Manager on macOS</figcaption></figure><h3>Solution</h3><p><strong>If multiple NICs configured to different networks are present in a system, NDI prefers to send traffic to a network adapter with the lowest address.</strong></p><ul><li><em>192.168.0.*</em> is preferred over <em>192.168.1.*</em></li><li><em>172.16.0.*</em> is preferred over <em>192.168.0.*</em></li><li><em>10.0.0.*</em> is preferred over <em>172.16.0.*</em></li></ul><p><em>Testing was conducted using two Windows 10 computers and NDI 4.6.2.</em></p><p>I posted this hack on multiple social media platforms and people responded.</p><h4><a href="https://www.facebook.com/toby.mills1">Toby Mills</a> in the <a href="https://www.facebook.com/groups/ndiusers/"><strong>NDI Video Users</strong></a><strong> Facebook Group</strong></h4><blockquote>no no no no no no no no.. NO</blockquote><blockquote>Just don’t do this.</blockquote><blockquote>Dante and NDI should both be on the same network if you set it up properly.</blockquote><blockquote>This breaks the standard security model across all networks (never multi home a machine that isn’t a router) and it makes it harder to integrate audio and video.</blockquote><blockquote>If you don’t have capacity, the solution is to add a bigger nic (10Gb or 40Gb or 100Gb) not to try and split the traffic.</blockquote><h4><a href="https://www.facebook.com/toby.mills1">Toby Mills</a> in the <a href="https://www.facebook.com/groups/ndiusers/">NDI Video Users</a> Facebook Group</h4><blockquote>Hackers LOVE dual homes machines as they bypass routers and you only need to compromise one machine to get full access to two networks.</blockquote><blockquote>There might be some valid edge case reasons for splitting the traffic but if you have one or more machines that need to receive both NDI and dante, there is no good reason to split the traffic and lots of bad reasons.</blockquote><blockquote>The video fails to address all those bad reasons.</blockquote><h4><a href="https://www.facebook.com/tom.vandenheuvel.121">Tom van den Heuvel</a> in the <a href="https://www.facebook.com/groups/ndiusers/">NDI Video Users</a> Facebook Group</h4><blockquote>I wrote the comment on the YouTube video. Multi homing is definitely not the way to go in regular networks but in “our” AV industry it’s a choice that works well. There are so many sound/light/comms/… devices that have seperate ports for seperate protocol that it’s, in some cases, even more difficult to put everything on the same network. So it just depends on what the user wants en what it’s used for. In our infrastructure, everything can work on the same network, but there’s also multiple reasons why you don’t want to have it that way in mobile kits where you need to connect to “foreign” devices.</blockquote><blockquote>That said: in both cases you should set it up properly and know what you’re doing.</blockquote><blockquote>BIG sidenote on this: never multihome just the internet connection. That’s connected into your NDI network using a router. Otherwise you will get in trouble or make it way too complicated.</blockquote><h4><a href="https://www.facebook.com/LeeDickinson">Lee Dickinson</a> in the <a href="https://www.facebook.com/groups/ndiusers/">NDI Video Users</a> Facebook Group</h4><blockquote>The main concern with dual homing is connecting to a public network and a private network simultaneously. For example, a PC connected to both a corporate network and that corporations public lobby network could potentially grant hackers access to the corporate network.</blockquote><blockquote>It is very umlikely to be a security concern in a studio setting with a closed Dante network and a closed NDI network. In a studio setting, both networks are likely accessing the internet through the same firewall.</blockquote><h4><strong>Ben Keller</strong> in the <a href="https://www.facebook.com/groups/ndiusers/">NDI Video Users</a> Facebook Group</h4><blockquote>NDI starts with the lowest numbered adapter. You may be able to use NDI access manager to restrict it to an IP range. Using Avio’s will separate the dante network from the computer.</blockquote><h4><a href="https://www.reddit.com/user/MaxSpecs/">MaxSpecs</a> in the <a href="https://www.reddit.com/r/VIDEOENGINEERING/">r/VideoEngineering!</a> Subreddit</h4><blockquote>To avoid Dante and NDi problem, differencing IP class adresse is one solution.</blockquote><blockquote>You can also add</blockquote><blockquote>• a RME Digiface Dante to you vMix system, so no NIC / ethernet problem</blockquote><blockquote>• Netgear AV Line m4250 Switch</blockquote><blockquote>… and if you’re working with Yamaha Dante equipment, be sure you’re at least 255.255.0.0 and not 255.255.255.0</blockquote><blockquote>disable IGMP on the port where Yamaha and the computer with R-Remote software is connected to … or use the Primary Ethernet connect to unmanaged LAN (and R-Remote too) and Secondary Ethernet connect to Dante newtork</blockquote><h4><a href="https://forums.newtek.com/members/tcomerma.119105/">tcomerma</a> in the NewTek Forums <a href="https://forums.newtek.com/threads/how-to-stop-ndi-traffic-going-over-dante-network.164499/">Thread</a></h4><blockquote>We tried another aproach to solve the same issue. We use <a href="https://r1ch.net/projects/forcebindip">ForceBindIP</a> to start vMix bound only to the IP of the NIC we want it to use. This forces vmix to send/receive just for this NIC without affecting the rest of the system. Has some pros/cons…</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b43c8af2c00c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>