OBS Studio 28.0 and you: What you need to know as a StreamFX user #879
Replies: 4 comments 9 replies
-
How long is the AMF FFmpeg encoder going to be kept around? I use AMF on Linux because it has better performance and quality compared to VAAPI in OBS. The new AMF integration in 28.0 isn't available on Linux, so removing the StreamFX option leaves Linux users without any AMF support until #861 is resolved. |
Beta Was this translation helpful? Give feedback.
-
So far no matter what i have done i haven't been able to get StreamFX to work with OBS 28. |
Beta Was this translation helpful? Give feedback.
-
OBS Studio 28.0 seems to have just dropped - any ETA on when StreamFX is going to be available ? |
Beta Was this translation helpful? Give feedback.
-
Is there a list of what needs to be completed before v0.12 is considered done? |
Beta Was this translation helpful? Give feedback.
-
As the release of OBS Studio 28.0(.0) is looming on the horizon, StreamFX has a lot of catching up to do. 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. Let's go over what exactly will change
For End-Users
OBS Studio 28.0 is now the minimum OBS version
Due 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. Therefore in order to make it easier on myself, the minimum OBS Studio version is now 28.0.
MacOS: ARM64 support on MacOS
As OBS Studio is also heading in this direction, StreamFX is following suit and opting to support ARM64 natively. The support for ARM64 requires a MacOS version of at least 11.0 or higher, so no 10.15 for the ARM64 crowd. 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.
System Requirements are now on each Release
With the requirements changing from version to version, it really doesn't make sense to put these in the documentation. Instead from now on they'll be at the bottom of the Release Notes, formatted to be easily readable by anyone. This change is not retroactive, and was only applied to the latest stable and current alpha/beta versions.
Deprecation of the AMD AMF (via FFmpeg) Encoder
With OBS Studio 28.0 the old obs-amd-encoder project is finally laid to rest, and a new AMD AMF integration is provided. This AMD AMF integration is technically and functionally superior, especially due to the FFmpeg AMD AMF encoder practically being unmaintained. Therefore users should prepare to migrate to the new OBS Studio integrated Encoder when OBS Studio 28.0 is released.
Deprecation of the AV1 (via AOM) Encoder
Same story as above, the encoder is no longer necessary. The integrated encoder solves most if not all situations, and for the remaining situations you have the other integrated encoders. And if those aren't enough, there's also ProRES and DNxHR.
For Developers/Contributors
No more Auto-Dependency system
Originally this system was extremely helpful, working in every situation, easily able to handle most if not all problems thrown at it. 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. 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.
Formatting validation is now functional on all Platforms
Mainly affects people writing PRs, as without passing this test your PR can't be merged. Run clang-format before pushing!
Beta Was this translation helpful? Give feedback.
All reactions