Yes, that seem to be two different issues.View attachment 84005
That's what I had on the video capture device settings (OBS is set to 60 FPS and so is the cam).
I am sure now that I am fighting with two separate issues here.
Issue 1: related to the Color Range setting
Issue 2: initial connection for the filter teleport only works every 2nd time
- If I set Color Range to "Partial" instead, then the green transmission problem is fixed and I will always see the cam feed in the cases where the connection works at all (i.e. I don't have issue 2).
- But that only seems to be a problem with initialization, not with "Full" not being supported in general, because as stated above I can get "Full" to work if I switch to "Partial" and back - and I can see the difference in color, so the "Full" setting is actually effective.
In my test setup I have one sender OBS on the gaming PC and two receiver OBS instances on the streaming PC. The sender is transmitting a full Teleport stream as configured from Tools -> Teleport (called "Base") and another separate stream only for the cam capture device (called "Face Cam") by using the Audio/Video Teleport filter on this device. The two receivers receive both the "Base" and "Face Cam" streams as separate sources each. I leave the cam setting set to "Partial" for the sake of these tests so that I don't additionally run into issue 1.
In my earlier post I misinterpreted this issue to be related to the starting order of sender and receiver, but that was only a coincidence because I switched between both tests. After doing more tests I am sure the real problem is that it works on the sender side only after every 2nd OBS start.
The "Base" feed always works for both receiver instances every single time. But the "Face Cam" feed doesn't transmit anything to both receivers. Then I restart the sender and I also get the "Face Cam" feed on both receivers. Restart again, no "Face Cam" feed, restart again, feed is back, you get it, I tried 10 times to be really sure and it's consistent.
If I do the test with only receiver 1 I get the same behavior. And the part why I am sure that it's coming from the sender: if I only test with receiver 1 and e.g. it's working this time, then if I additionally start receiver 2 it will also get the feed. If I only test with receiver 1 and it's not working this time, then if I additionally start receiver 2 it will also not get the feed.
It's weird, maybe some clean-up is not performed by the filter at the end, then the next startup fails but some kind of error handler at least does the clean-up, so that the next start then succeeds again? All I can say is that it's not related to the network port. I set a fixed port for the filter and in both cases where the feed is transmitted and where it's not send I can see with netstat that OBS is indeed listening on that port (and stops listening as soon as OBS is shutdown).
For 1. You have selected "any" for the format. Does the log say which one is chosen? Can you try to set them manually and check which ones do fail?
For 2. it sounds weird.. I guess it needs some investigation. Sounds like you have given a good reproduction scenario. I will look at it by chance, but may take some time as I have other things on my plate currently.