Hi,
Running OBS to stream church services, so running a triple monitor setup:
- OpenLP UI (a song words and other things to the big screens in church)
- OBS UI
- Feed to the big screens.
One of our OBS inputs is therefore a "macOS Screen Capture" configured to capture the relevant display.
This morning we had two instances where we advanced to the next slide on OpenLP, and the big screens updated, but the screen capture did not.
When we moved to the following slide we got a flash of the slide we'd "missed" on the stream, and the system continued correctly...
This doesn't seem to tally with https://github.com/obsproject/obs-studio/issues/7368 (partly because we're on Ventura 13.5.1, and partly because it self recovers the next time the screen content is updated).
Note that neither the program output, nor the source preview window updated - it's as if it said "I haven't seen a display update", until the following update at which point it went "Oops, here you go"
Anyone else observed similar behaviour, or suggest anything else I can do to isolate this rare event?
Running OBS to stream church services, so running a triple monitor setup:
- OpenLP UI (a song words and other things to the big screens in church)
- OBS UI
- Feed to the big screens.
One of our OBS inputs is therefore a "macOS Screen Capture" configured to capture the relevant display.
This morning we had two instances where we advanced to the next slide on OpenLP, and the big screens updated, but the screen capture did not.
When we moved to the following slide we got a flash of the slide we'd "missed" on the stream, and the system continued correctly...
This doesn't seem to tally with https://github.com/obsproject/obs-studio/issues/7368 (partly because we're on Ventura 13.5.1, and partly because it self recovers the next time the screen content is updated).
Note that neither the program output, nor the source preview window updated - it's as if it said "I haven't seen a display update", until the following update at which point it went "Oops, here you go"
Anyone else observed similar behaviour, or suggest anything else I can do to isolate this rare event?