search

CESNET / UltraGrid

UltraGrid low-latency audio and video network transmission system
http://www.ultragrid.cz
Other
492 stars 53 forks source link

Spout not working #402

Closed zbynekdrlik closed 1 week ago

zbynekdrlik commented 1 month ago

Hi, spout input device is not working in 1.9.4 and also in nightly build.

MartinPulec commented 1 month ago

Do you have any further details how to reproduce the problem? It doesn't seem to be generic - I've downloaded Spout build, run DEMO/SpoutSender.exe from it and UltraGrid was able to capture it without problems (both versions), using:

.\uv.exe -t spout -d gl
zbynekdrlik commented 1 month ago

I am using it with obs as sender.

image

I have also test this on my laptop and there it is correctly working. What else could I do to debug it?

zbynekdrlik commented 1 month ago

And this is list of spout displays on related not working computer image

MartinPulec commented 3 weeks ago

Sorry for the delayed response - I've missed your response somehow.

Unfortunately, I still cannot reproduce the problem - as indicated above, the sample Spout sender worked flawlessly for me. Also the signal generated by UltraGrid itself - uv -t testcard -d spout can be normally captured.

Would it be possible to try these 2 senders to check if there is some general problem with Spout or is it specific to some sender(s) only? If the second is true, what is the actual program(s) that acts as the Spout sender that is UltraGrid incapable to capture?

UPDATE 1: I've just noticed that you've written that you use OBS as a sender - which plugin do you use for that? I've tried with obs-spout2-plugin and it worked for me (tested with OBS 30.2.0 and the plugin latest release on GitHub). Do you use this plugin or an another?

UPDATE 2: Not strictly necessary, but if possible, prefer the continuous version for testing, I've added some additional checks there.

zbynekdrlik commented 1 week ago

I have retest it again over newly released version 1.9.6 and now it is working correctly. Believe that somehow it has been fixed meanwhile. Thanks for support