You can find the latest Production-ready release here. These releases should never be used in Production workflows, and you take all responsibility for what happens if you do! We can not guarantee functionality, performance or even stability in Testing releases, which is why they should only be used in Test environments. So as I (and probably others) got extremely tired of this system doing its best to be the worst in the world, it was carefully removed from reality, never to bother developers again.įormatting validation is now functional on all PlatformsMainly affects people writing PRs, as without passing this test your PR can't be merged.
As time went on, more and more problems occured for which solutions were non-existent - if you ran into the problem(s) you were just screwed. And if those aren't enough, there's also ProRES and DNxHR.įor Developers/Contributors No more Auto-Dependency systemOriginally this system was extremely helpful, working in every situation, easily able to handle most if not all problems thrown at it. The integrated encoder solves most if not all situations, and for the remaining situations you have the other integrated encoders. Therefore users should prepare to migrate to the new OBS Studio integrated Encoder when OBS Studio 28.0 is released.ĭeprecation of the AV1 (via AOM) EncoderSame story as above, the encoder is no longer necessary. This AMD AMF integration is technically and functionally superior, especially due to the FFmpeg AMD AMF encoder practically being unmaintained. This change is not retroactive, and was only applied to the latest stable and current alpha/beta versions.ĭeprecation of the AMD AMF (via FFmpeg) EncoderWith OBS Studio 28.0 the old obs-amd-encoder project is finally laid to rest, and a new AMD AMF integration is provided. Instead from now on they'll be at the bottom of the Release Notes, formatted to be easily readable by anyone. System Requirements are now on each ReleaseWith the requirements changing from version to version, it really doesn't make sense to put these in the documentation. As we're currently running into a bug with this support, these binaries will be available either with the full release of v0.12 or when the bug is fixed. The support for ARM64 requires a MacOS version of at least 11.0 or higher, so no 10.15 for the ARM64 crowd. MacOS: ARM64 support on MacOSAs OBS Studio is also heading in this direction, StreamFX is following suit and opting to support ARM64 natively. Therefore in order to make it easier on myself, the minimum OBS Studio version is now 28.0.
Let's go over what exactly will changeįor End-Users OBS Studio 28.0 is now the minimum OBS versionDue to massive build system, API and dependency changes, it is not possible to support both 27.2 and 28.0 and beyond in a single binary. A lot of work happened over the last weeks to make sure that StreamFX can be used and built with the latest OBS Studio version, despite it not being out yet. As the release of OBS Studio 28.0(.0) is looming on the horizon, StreamFX has a lot of catching up to do.
0 kommentar(er)
