-
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NOALBS and Kiloview p2 with Nginx doesn't change the scene when disconnecting #120
Comments
What Noalbs-version are you using? |
I am currently using version 2.7.2 (the latest) and on Nginx I have 'idle_streams on;' because otherwise it gives me problems with the kilolink server to which I connected Nginx |
Just to be clear. The issue that you experience is that it stays on your live-scene, when you disconnect your kiloview right? |
yes, exactly, for example if the kiloview's battery die and It disconnect, the switcher doesn't change from live scene ti brb |
Hi @FkManu, You can set the offline trigger to a value greater than 0 to force it to change to the offline scene when the bitrate drops below that number. |
I have the same issue, tried to change trigger and to switch to an SRT signal but the problem remains. The script reads that the stream is active at 0kb/s and OBS is stuck to the IRL scene until the signals are manually turned off by the bonding server options. |
I tried putting 100 in the offline value it does not change because it does not seem to recognize a signal that arrives but which is exactly 0. |
Hi, I have a little problem with the switcher:
I connected a kiloview p2 (in bonding) to an Nginx server on a vps, it creates an always active channel with the Nginx server that constantly marks 0 bit/s. The switcher works well on drops, but when the encoder is turned off the scene change is blocked on the "live'' scene, without more switching to the "low'' scene, probably because the signal is always constantly active at 0 bit/s, I tried to raise the trigger threshold but nothing changes anyway, is it possible that it is a bug?
Usually in my classic RTMP-Nginx system when the signal is off the bot replies with '' No connection :( '' usually in my classic RTMP-Nginx system when the signal is off the bot replies with `` No connection :( '' instead with the encoder signal off it replies ''nginx: 0''
The text was updated successfully, but these errors were encountered: