This process mitigation flag is inherited by child processes and applies
to load-time DLL resolution, pushing the application's own directory
below the system directories. If there are system-installed copies of
dependent DLLs such as FFmpeg, those get loaded when OBS is updated as
the updater and subsequent relaunch of OBS inherit the mitigation.
As we use SetDefaultDllDirectories, this mitigation is less important,
the proper fix would be to use /DEPENDENTLOADFLAG to protect load-time
import resolution.
Qt 6.11 only supports macOS 13+. It does not support macOS 12, and OBS
Studio will fail to launch on macOS 12 as a result. We should reflect
that with our deployment target.
https://doc.qt.io/qt-6.11/supported-platforms.html
We suspect users hit errors updating the system-wide hook files even if
the file is not in use, but without logging we have no way to know for
sure. This commit adds additional logs. Not logging source paths
anywhere is intentional to avoid wide char to utf-8 issues making this
more complicated than it needs to be - the source will always be the OBS
install dir regardless.
The previous increase from 1 to 3 deltas has an acceptable time cost on
CI. Further increase it from 3 to 5.
This should somewhat improve the update experience on macOS for users
not on the most recent previous version of OBS Studio.
Notable Changes:
* deps.qt: Backport fix for QTBUG-146665
Fix a bug that causes right-click to not work for disabled items in the
source list. This is fixed on the Qt 6.11 branch and in 6.12.0-beta1,
but we've backported the patch for now.
More useless "security" software to try to prevent screenshots that
installs global hooks and kernel drivers. Crash reports indicate that
their hook attaches to and subsequently crashes OBS.
Previously, the appcast generation happened in the same workflow that
the artifacts were generated, so they could be fetched without issue.
Since they are no longer in the same workflow, we have to account for
that.
The CUDA calls in AUDIO FX were added initially to big a bug on the SDK
side where the SDK functions where not checking the CUDA context.
This led to interference with the VIDEO FX, potentially breaking it.
These bugs have been fixed by the SDK so we don't need anymore these
CUDA calls.
Signed-off-by: pkv <pkv@obsproject.com>
Penwywern