If the user asks for a plugin that does come with their own binaries or other
files to be included in their OBS installation, it should include those files. A
good example is obs-vkcapture which /requires/ system-wide files to have any use
whatsoever.
Plugins' paths were removed from the wrapper in step with preventing OBS from
loading plugins twice but wasn't actually required because the env variables
already point at the one and only location for plugins. The plugins' share dirs
don't get put in the system-wide share by default on NixOS but I decided to
remove the directory anyways for clarity.
Partially reverts 593d64f975
Co-authored-by: Pedro Lara Campos <pedro.laracampos@gmail.com>
notable changes:
- improved handling for disc with mastering errors, structure protection
- minor bugfixes
full changelog: <https://www.makemkv.com/download/>
```
MakeMKV v1.17.1 (13.7.2022 )
Small improvements and bugfixes
Bug fixes:
Program could hang when scanning certain protected DVD discs using CellWallk method
Some titles were truncated on DVDs with structure protection, when using CellWallk method
Small bugfixes
1.17.0 regressions:
On some UHD HEVC streams program spitted thousands of invalid "Corrupt" messages, appearing to hang
Program crashed decoding certain AC3 (DD) streams, usually during transcoding
MakeMKV v1.17.0 (27.6.2022 )
Improved handling for discs with mastering errors
A new, rewritten DVD engine - much better handling for discs with structure protection
Many internal improvements and small bugfixes
Notable Bug fixes:
Program failed to recognize some exotic USB drives
Program failed on some DVD streams recorded from sattelite feed (TiVO DVD)
Program could hang if internet connection wasn't available
```
obs-ndi bundles the NDI SDK headers to avoid a more complicated build
setup, but this plays against us here because the soversion for the v5
NDI SDK is "5" even though as far as I know it's fully ABI compatible
with the v4 headers in use here.
Work around the v4/v5 incompatibility here by using the upstream SDK
headers instead.
The xdg-open utility is only ever a runtime dependency and its
dependents only expect that it accept a URI as a command line
argument and do something with it that the user would expect.
For such as a trivial relationship it should be possible for
users to override xdg-open with something else in their PATH.
