Hi

I am experimenting with the Skype for Creators (Skype version 8.26.76.25) with built in NDI support.

The NDI feed from Skype into VMIX is just a pale blue screen, with a Skype Logo in the top right corner.

NDI is definitely switch on in Skype, and indeed if I switch it off the Skype NDI stream vanishes from the NDI selection in vMix. I have a good quality video stream arriving into Skype and can see it clearly in the Skype.

As the 'Skype' logo is present, its pretty obvious that vMix is working just fine, and Skype is just not generating the feed correctly.

Anybody else having issues?

Keith

Kane

That's an interesting one. I am going to re-install Skype on a clean 1803 build of Windows 10 on Monday morning, This PC has had every piece of NewTek software right back to the early days of AirPlay, along with a few different versions of Skype, so not exactly a virgin test environment.

I will report back.

Keith

It is currently NDI output from Skype. For input, you can use NDI Tools 3.5 which includes NDI Virtual Input as a standard feature.

I'm not sure when (if) NDI input will be included in this version of Skype. When I spoke to Microsoft about it at NAB, they told me that NDI output is what would be supported at first.

Kane Peterson
NewTek

Thanks Kane. Does the NDI output from Skype, when received back into vMix, exclude any audio coming into Skype from vMix (built-in mix minus)?

It can be created without having any content, which might be what is being requested here. For example, my NDI Router app creates the "Router out - A" NDI source as soon as the app is run, even through no inputs have been set up or selected. And I think NDI routing could be used to create a solution to some of these requests here.

NDI Routing allows the same actual source to be accessed via different (virtual) names. What I think some people are looking for is to have Skype generate static NDI names for the caller streams, like "Skype Caller 1", "Skype Caller 2", etc, rather than NDI names based on the names of the callers (which may be different each time). What could be done in Skype is to make use of NDI routing to create both logical names (eg Caller 1, 2, etc) alongside the personal names, and it could create the first (default) "Skype Caller 1" routed name at startup, adding additional "Caller n" names as more calls are received. That way, an app like vMix could have a permanent NDI input set to "Skype Caller 1" which would always receive the first/only caller connected, which I think is what people are looking for.

Meanwhile, if you want to achieve a similar solution externally, you could use the NDI Router to select NDI sources as they appear and send them to vMix as fixed name sources - "Router out - A", "Router out - B". Currently the router only has 2 outputs, but I'm working on a revised version at present (with more outputs). Another solution is to use the NDI RTx app, which re-transmits an NDI stream under a different (fixed) name, and also has the ability to add an overlay (caption).

I think that approach might be overthinking things.

Once an NDI input is added to vMix it can be changed through the right click menu.
So if you setup a test Skype call and add it to vMix, when the time comes for a new guest,
all you need to do is right click the input to change it to the new source, this will preserve all MultiView and
related settings as well.

I have downloaded skype desktop app for windows. Where is the button to enable NDI output. I can't find it in any setting.

Here is a video showing where to find it.



Kane Peterson
NewTek

Appears Skype has removed the NDI feature. Myself and several other Skype users who had the option last week, no longer have it showing up in the settings.

Its likely that any version of Skype available through any sort of "App Store" will NOT have the NDI feature.
Probably best to download direct from the Skype website.