This message was deleted.
# clouds
steep-balloon-41261
07/08/2023, 10:41 PMThis message was deleted.
d
dry-elephant-14928
07/09/2023, 5:16 AMCloud is running Ingress 1.0 as well. that's rather unexpected. what's the Ingress ID?
h
handsome-guitar-37911
07/09/2023, 5:21 AMWe were running 3 different ingress inputs from OBS yesterday.
IN_4AE5aGfofBnUIN_nUdYbSQaxJb6IN_fCxLvN9twMYzhandsome-guitar-37911
07/09/2023, 5:22 AMI'm not 100% sure what caused it, but the one that was fine I was running myself and I have very good upstream. Whereas I can't say for the other two, but they were running the same settings as they normally use for a twitch stream and I've seen many of their streams and they don't glitch like that.
handsome-guitar-37911
07/09/2023, 5:23 AMThe symptom was that the stream would occasionally stall, and then need to catch up. I watched back an egress recording of this and can verify that it was happening on that version too.
d
dry-elephant-14928
07/09/2023, 5:25 AMdo you know where they were running from?
it's possible that the encoder settings was higher than the bandwidth available at those clients. RTMP does not handle bitrate adaptation.. so it could lead to choppy results if there's insufficient bandwidth
dry-elephant-14928
07/09/2023, 5:26 AMwhat are the encoder settings set as?
h
handsome-guitar-37911
07/09/2023, 5:26 AMSorry I don't have that, but I'll ask them and let you know.
handsome-guitar-37911
07/09/2023, 5:27 AMI just know it was the same settings they usually use on twitch without issues.
handsome-guitar-37911
07/09/2023, 5:35 AMFor the ingress that worked fine, I was running at 5850 Kbps video / 160 audio with auto keyframe interval
handsome-guitar-37911
07/09/2023, 6:07 AMIN_4AE5aGfofBnUd
dry-elephant-14928
07/09/2023, 6:37 AMyeah, those settings seem fine. we'll dig through a bit to see what might be happening with these instances
🙏 1