If Newtek can make an app on a phone that can encode NDI, does that mean that theoretically something like this: https://www.aliexpress.c...a2g0s.9042311.0.0.PASg1P

could have an app on it that would receive and output an NDI stream?

Currently around 60USD for 11.11 sales if someone knows how to make it happen :)

The NDI SDK doesn't have decode support for ARM based devices at this time. Right now you need a x86 based CPU to decode.

Kane Peterson
NewTek

The app is for cameras, so an NDI transmitter (encode) app, not an NDI receiver (decode). The NDI SDK doesn't support NDI receive (decode) on ARM devices yet. Not sure why they only added transmit support for ARM and not receive, because NDI receive on ARM would be incredibly useful.

I appreciate that but I think what the OP was suggesting is that if the mobile app can encode and send the camera then a similar spec system running Android could potentially do the same thing with an internal source.

And for anyone reading the title of this thread - there are options for cheap 'receivers' - but note the caveat that the latest version of the NewTek Studio Monitor has increased system requirements compared to the earlier NDI Video Monitor - so for low end PCs - keep a copy of the NDI Video Monitor. Another option in the pipeline is FFPLAY which now supports NDI and will very likely run on these older PCs

You can read about one low cost PC tested as an NDI Receiver as part of a this blog: Testing very low end hardware and rapid setup

From what I read he was asking for output.

Android (and iOS) devices have restrictions which do not allow an application to 'scrape' the screen, it isn't possible to write an app that will be accepted in the stores for these operating systems. If you want the screen turned into NDI, you need to use AirPlay/GoogleCast/MiraCast software receiver and convert that into NDI.

Kane Peterson
NewTek

NDI is really not the good protocol for doing things like this. NDI is for production, not delivery, hence the issue you're facing...

Use Multicast or HDMI over IP for example.

Guillaume

I was just thinking about this solution. The NDI® webserver in NewTek Connect Pro will allow you to view NDI channels using a web browser, however it is video only, there is no audio.

Kane Peterson
NewTek

What would be the advantages of multicast or HDMI over IP?

If I understand correctly - NDI uses mDNS to find the stream, but only sends the necessary packets which reduces network traffic over the network compared to multicast. ok - so the issue with distributing via NDI is that each receiver adds another stream reducing bandwidth? If we were to use multicast - what video codec / format would you be likely to use, and how would you receive it?

HDMI over IP - so you mean output to an HDMI splitter and from there to ethernet baluns? eg: http://www.altronics.com...n-extension-transmitter/ ? The last time I tried a different product / same idea there was around 1.5 seconds latency. Have you had better success with them?

One of the advantages I like about NDI is that we could run multiple video streams on each screen - eg: video on one half and a match schedule on the other half - in two studio monitor windows.

Actually it turned out that the performance issue with the Sienna.Cloud decoding was actually due to a Windows 10 performance issue, not this hardware.
So this little box with Windows 7 or 8 (or with Ubuntu) would probably be find for Sienna.Cloud decoding - although that needs further testing to confirm.

For basic NDI Monitoring, we tested using the older NewTek Video Monitor and Full HD sources, playing fullscreen via HDMI out, and the results were pretty good. Note that the newer NewTek Studio Monitor does *not* work on this hardware since its using some CPU instructions not supported by this processor. However, any other more standard NDI Monitor should work fine - the NewTek special commands are nothing specific to NDI - just optional functions they chose to use for accelerated decode or composition of overlays which are not available on lower end CPUs, and they havent kept any failback functionality for simpler processors. Note that we did not test HX