After the mediamtx stream was up for ~16 hours, OBS started doing the thing on the right. Disconnecting and reconnecting fixed it, but my check-volume.pl script did not detect it and so could not auto-reset it. Any ideas on either how to make it never do this, or how to detect it?
What does this mean and how do I make it go away? "WAR [HLS] [muxer live/live] segment duration changed from 1s to 2s - this will cause an error in iOS clients".
Is there any reason to try to get hlsVariant "lowLatency" working instead of "mpegts"? What are the downsides? (Besides that check-volume.pl doesn't understand that format.)
After the mediamtx stream was up for ~16 hours, OBS started doing the thing on the right. Disconnecting and reconnecting fixed it, but my check-volume.pl script did not detect it and so could not auto-reset it. Any ideas on either how to make it never do this, or how to detect it?
What does this mean and how do I make it go away? "WAR [HLS] [muxer live/live] segment duration changed from 1s to 2s - this will cause an error in iOS clients".
Is there any reason to try to get hlsVariant "lowLatency" working instead of "mpegts"? What are the downsides? (Besides that check-volume.pl doesn't understand that format.)