lcalder
Member
Mac Mini Apple M2 Pro Chip, 32gb memory, Sequoia 15.2, OBS 31.0.0
Immediately upon installing Sequoia 15 and all later updates, MacOS screen captures become unresponsive (they fail to update) after 20-30 minutes of run time. In order to recover, each screen capture must be modified by going to properties, and change the window / application / physical screen to something else, save it, then return to properties and set it back to the original window / application / physical screen, in order to have obs update the window/application/screen on the output. It doesn't matter what type of capture is being used.
This problem occurs whether I am using a usb-c thunderbolt connection to my monitor or through an external hub connected via thunderbolt 4, (using the synaptic display link manager). Interestingly, with the displaylink connected monitor, and using synaptic's latest (1.11) version of the software, the entire monitor output would freeze and become inaccessible to the mouse after the 20-30 minutes until I restarted displaylink, then quit obs and restarted obs - which would then grant me another 20-30 minutes of operation. I contacted displaylink and they recommended I use the 1.9 version, which doesn't freeze the entire screen, just the obs-macos-screencaptures similar to the "default" operation for direct connection to the tb ports on the back of the mac mini...
When using the displaylink 1.9 version (which freezes the entire screen after 20-30 minutes, please note that the screen never freezes except when I am using obs... which I think must be related to the macos->screencaptures and the way apple's new sequoia is (mis-)handling it. It seems that every time Apple dumps a new "release" some new, secret or non-disclosed change ambushes me and breaks something in my system.
Immediately upon installing Sequoia 15 and all later updates, MacOS screen captures become unresponsive (they fail to update) after 20-30 minutes of run time. In order to recover, each screen capture must be modified by going to properties, and change the window / application / physical screen to something else, save it, then return to properties and set it back to the original window / application / physical screen, in order to have obs update the window/application/screen on the output. It doesn't matter what type of capture is being used.
This problem occurs whether I am using a usb-c thunderbolt connection to my monitor or through an external hub connected via thunderbolt 4, (using the synaptic display link manager). Interestingly, with the displaylink connected monitor, and using synaptic's latest (1.11) version of the software, the entire monitor output would freeze and become inaccessible to the mouse after the 20-30 minutes until I restarted displaylink, then quit obs and restarted obs - which would then grant me another 20-30 minutes of operation. I contacted displaylink and they recommended I use the 1.9 version, which doesn't freeze the entire screen, just the obs-macos-screencaptures similar to the "default" operation for direct connection to the tb ports on the back of the mac mini...
When using the displaylink 1.9 version (which freezes the entire screen after 20-30 minutes, please note that the screen never freezes except when I am using obs... which I think must be related to the macos->screencaptures and the way apple's new sequoia is (mis-)handling it. It seems that every time Apple dumps a new "release" some new, secret or non-disclosed change ambushes me and breaks something in my system.