StreamFX 0.12.0 Alpha 117 #913
Replies: 3 comments 6 replies
-
|
I did not find the exe installer file to 0.12.0 alpha 117 :-( |
Beta Was this translation helpful? Give feedback.
-
|
It is in the Assets, below the release. This is the discussion thread, which for obvious reason does not contain the actual release - but it does link to it, as you can see above. |
Beta Was this translation helpful? Give feedback.
-
|
worked to me ... thank Xaymar ! |
Beta Was this translation helpful? Give feedback.
-
|
I followed the uninstaller for macOS (M1) prior to installing this, however, the plugin still doesn't appear to be available. I noticed that it's installing in |
Beta Was this translation helpful? Give feedback.
-
|
Please follow the Installation guide. Additionally, as already explained on the release itself, Alpha, Beta, and Candidate versions do not recieve any support. |
Beta Was this translation helpful? Give feedback.
-
|
Windows installer assumes OBS is installed to c:\program files\obs-studio. A simple kludge is to copy the files into the correct directory, but it would be nice if the installer did not hardcode the destination. |
Beta Was this translation helpful? Give feedback.
-
|
The windows installer checks the registry for the correct location, and only prevents choosing a new directory if it detects that StreamFX has already been installed. If you want to move StreamFX to another location, first uninstall the previous static install, then install a new version. Eventually StreamFX will install into ProgramData, or use the new environment based per-user installation method. |
Beta Was this translation helpful? Give feedback.
-
|
The the uninstall process found in the guide did not function as intended, as I'd previously run that before running the installer. Also, I've just checked my registry and it shows the installed location as the "correct" location. (if it matters, it's on my E drive, while the usual "program files" directory is on the expected C drive.) (There wasn't a key structured the way it is in the installer file you linked... It was the only value in the key and it was named "(Default)". Maybe my OBS install is screwy.) |
Beta Was this translation helpful? Give feedback.
-
|
In the Windows registry, an empty string in a "Key" is the same as NULL, which is treated as "(Default)" by RegEdit and similar. The uninstall process will work for Static installs, as Portable installations leave no hints or information about files behind - they extract their content and that's all they do. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
⚠ Preview Release not for Production! ⚠
This release is meant for testing in isolated conditions and early adopters only, and should never be used in production. If you use one of these releases, all promises of support, warranty, functionality, and similar are immediately void and if things break you are on your own. The latest production ready release can be found here.
Please read the Installation Guide and System Requirements!
The installation of StreamFX requires that you follow certain instructions, as well as fulfill a minimum hardware and software requirement. Please ensure that you have read and verified both before asking for help, as many issues can be fixed by reading both of them in their entirety.
Support StreamFX on Github Sponsors or Patreon!
Overview of Changes
New Release process: Alpha -> Beta -> Candidate -> Release!
The old two stage system didn't work out quite as I'd have hoped: It didn't communicate the dangers of Testing well, and did not differentiate between different stability levels. To solve this I've adopted a new release process now available in StreamFX, which follows the usual development cycle of Software itself: Alpha -> Beta -> Candidate -> Release. The further right you go in that graph, the more stable software is supposed to be, at the cost of new features and changes. The further left you go, the more up-to-date things will be, but you sacrifice stability and safety.
Avid DNxHR Encoder (via FFmpeg) by @IceStormNG
A new contender for the visually lossless intermediate codec arrives: Avid DNxHR! Thanks to work done by @IceStormNG, it is now possible to use this encoder without configuration trickery and directly configure it with a proper user interface. As this encoder is based on the real codec specification, it may perform better than the Apple ProRes encoder while being way more compatible with video editing software.
Loadable Bundles on MacOS
With OBS Studio 28.0 came the introduction of Loadable Bundles, a variation of MacOS's Bundle format. This format offers a lot of advantages for almost no drawbacks, and it StreamFX from now on uses this packaging format on MacOS. As a bonus, FFmpeg Encoders should now be available on MacOS too.
⚠ This change requires that you cleanly remove old versions of StreamFX first!
As the packaging and installation method has changed, please follow the Uninstallation guide to clean up any left over old files. Failure to do so will result in undefined behavior and may render OBS Studio entirely unusable. You have been warned.
Universal Binaries for x86 & ARM64 support on MacOS
Users on ARM64 devices can now enjoy native ARM64 binaries for less CPU usage, and as such more overall performance on CPU focused tasks. While StreamFX is mostly GPU workloads, some of the internal code does actually do very heavy lifting that benefits from this.
Deprecation of the AMD AMF (via FFmpeg) encoders
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 to both the old obs-amd-encoder and FFmpegs AMD AMF integration. All users are urged to migrate as soon as possible, as no guarantees are made for how long this deprecated encoder will remain. Additionally, users on Linux should put their focus on the open Pull Requests for Linux support (1, 2.
Deprecation of the AV1 (via AOM) Encoder
With OBS Studio 27.2.4, the SVT-AV1 and AOM-AV1 encoders were integrated into OBS Studio directly. This integration is functionally identical, and as such replaces the StreamFX provided AOM-AV1 encoder. All users are urged to migrate as soon as possible, as no guaratees are made for how long this deprecated encoder will remain.
Shader Texture Inputs no longer corrupt Scene Collections
For quite some time, Shader Texture Inputs were haunted by ghosts from the past, also known as work-arounds and deprecated code. This resulted in Shader Texture Inputs keeping stale references around and requiring an OBS Studio restart to actually update. Several code modernization cycles later, this is now fixed and Shader Texture Inputs immediately update as expected - while also no longer keeping stale references around, so your Scene Collections are safe again.
Detailed Changelog
0.12.0a117
0.12.0a106
0.12.0a77
0.12.0a45
0.12.0a1
System Requirements
Windows
Ubuntu, Debian, ...
MacOS
Required Instruction Sets: x86-64-v2, AVX, BMI1, BMI2, F16C, FMA, MOVBE
Required Instruction Sets: x86-64-v2, AVX, BMI1, BMI2, F16C, FMA, MOVBE
FFmpeg for obs-studio
This discussion was created from the release StreamFX 0.12.0 Alpha 117.
Beta Was this translation helpful? Give feedback.
All reactions