You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep the Video Encoder settings I previously applied in my profile:
Current Behavior
When I save my video encoders for use, they behave as normal. The issue is when I close the app and then re-open it, then the video encoder settings specifically reset to x264:
Everything else seems to stay the same as intended.
Steps to Reproduce
Have either one or two (or more) profiles.
In one of them, change the Video Encoder setting on Settings > Output > Streaming and/or Recording > Video Encoder
Apply > OK
Close OBS.
Open OBS.
Check the settings being reset to x264 (doesn't seem to affect other profiles than the selected when the app closed).
If you have a second profile: then change the Video Encoder again.
Switch profiles.
Assuming the profile has a Video Encoder other than x264, Close OBS with the second profile active.
Open OBS.
Now the second profile's Encoders are set to x264.
If you switch back to your first profile, you see than it remains unaffected.
Anything else we should know?
Drivers up to date.
Hopefully everything you may need is already in the log information.
Never encountered something like that up to 30.2.3.
The text was updated successfully, but these errors were encountered:
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
31.0.0-beta2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/KnomraaKCj5YKPww
OBS Studio Crash Log URL
No response
Expected Behavior
Keep the Video Encoder settings I previously applied in my profile:
Current Behavior
When I save my video encoders for use, they behave as normal. The issue is when I close the app and then re-open it, then the video encoder settings specifically reset to x264:
Everything else seems to stay the same as intended.
Steps to Reproduce
Anything else we should know?
Drivers up to date.
Hopefully everything you may need is already in the log information.
Never encountered something like that up to 30.2.3.
The text was updated successfully, but these errors were encountered: