how to handle plugin error on different kernel/docker host

[Marc]

I was even starting to think that the spectre/meltdown bios updates were influencing this. 
Turned out that my vm settings[1] were not being used, because I did not add this schema
xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' to the top. pfffff

But still this ndi stuff could report errors better. Thanks for the quick help.


[1]
  <qemu:commandline>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='host,-hypervisor'/>
  </qemu:commandline>



> Ok I checked a bit more and it seems everything could be set up
> correctly but `NDIlib_initialize` just returns false. Did you just
> change the machine where you run the docker? People on forums talk about
> CPU incompatibility https://forums.newtek.com/threads/linux-ndi-sdk-
> examples-broken-on-amd-machine.164762/
> 
> You could google more about issues around that call and try to find some
> documentation around that call from newtek. What checks exactly do they
> do.
> 
> 
> If you really need to solve this and it seems that NDI is proprietary
> software you could try to reverse that function in library (Ghidra) and
> debug it to see where it fails.
> 
> 
> 
> 
> On 9/6/21 12:53 AM, Marc wrote:
> 
> 
> 
> 					this.