There is a new flavor of NDI that is being implemented in some devices, especially PTZ cameras, called NDI-HX. I tested it the other day with a Panasonic camera, but it can only be received by TriCaster using the new NDI-HX driver and updated versions of NDI tools like Studio Monitor. The problem I ran into was that the NDI for OBS plug-in works great with the original NDI, but when the HX driver is installed the NDI source option in OBS disappears. This must be an issue with the plug-in. Does anyone know if the plug-in is in the process of being updated to include HX? I believe it is just an additional compression scheme for the video coming from the camera.
hello i got a problem with my obs and my NDI plugin they where working before but they just stopped!
my streaming PC specks
CPU Name: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz
CPU Speed: 3373MHz
Physical Cores: 4, Logical Cores: 8
Physical Memory: 24573MB Total, 22124MB Free
Windows Version 10 64 bit
Windows 10 Gaming Features:
AMD R200
gaming PC Specks
CPU Name: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz
CPU Speed: 3.104MHz
Physical Cores: 4, Logical Cores: 8
Physical Memory: 38910MB Total, 35865MB Free
Windows Version: 10.0 Build 16299 (revision: 309; 64-bit)
GPU AMD Rx580
Network Device Interface: http://newtek.com/ndi
Think of it like SDI, but over ethernet/IP, thus not requiring expensive capture cards and simplifying cabling/routing. It actually works surprisingly well, with indiscernable latency. NDI support would involve being able to add input from NDI video "devices", and possibly output over NDI as well, though a lower priority than supporting NDI inputs.
All I can really say about it is that it will probably be thrown onto the pile of feature requests with everything else, but don't hold your breath for a release with NDI support soon unless someone takes the time to implement it of their own volition and submit a PR.
It's possible there are licensing issues with Newtek that would prevent it from being compatible with the GPL2, in which case it's an impossibility. I haven't looked into it enough to know for sure.
This might be the same issue as other users had: https://github.com/Palakis/obs-ndi/issues/59Im new to NDI/RTMP/etc outside regular use of OBS/Xsplit, so I'm not sure if perhaps I'm missing something that NDI is changing that I don't see mentioned or that "should be" common knowledge and I'm just frustrated with my ISP and skipped it..
I got NDI to work and all that, currently dealing with some ISP packetloss issues that I can't seem to work around as well. However, installing the NDI installer seems to completely cause my Down and Up speeds to go to complete crap. Capping out at 60-90 down, from 450+down. At first I thought perhaps all the stuff I've been working on was the cause, but both PC's with NDI installed did this, even after uninstalling. However my 3rd PC was fine with speeds which is what tipped me off. I could not figure out what was the actual cause but as a shot in the dark I ran the good ol Speedguide TCP optimizer which apparently reverted and cleared up w/e changed and was causing that. For some reason even windows recovery wouldn't even let me go that route.
Basically just wondering what or if I did indeed miss something with NDI so I'm aware in the future.
This might be the same issue as other users had: https://github.com/Palakis/obs-ndi/issues/59
Im new to NDI/RTMP/etc outside regular use of OBS/Xsplit, so I'm not sure if perhaps I'm missing something that NDI is changing that I don't see mentioned or that "should be" common knowledge and I'm just frustrated with my ISP and skipped it..
I got NDI to work and all that, currently dealing with some ISP packetloss issues that I can't seem to work around as well. However, installing the NDI installer seems to completely cause my Down and Up speeds to go to complete crap. Capping out at 60-90 down, from 450+down. At first I thought perhaps all the stuff I've been working on was the cause, but both PC's with NDI installed did this, even after uninstalling. However my 3rd PC was fine with speeds which is what tipped me off. I could not figure out what was the actual cause but as a shot in the dark I ran the good ol Speedguide TCP optimizer which apparently reverted and cleared up w/e changed and was causing that. For some reason even windows recovery wouldn't even let me go that route.
Basically just wondering what or if I did indeed miss something with NDI so I'm aware in the future.