Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: OBS QuickSync encoding issues with drivers 32.0.101.6127/32.0.101.6044 - 32.0.101.6130/32.0.101.6048 #1871

Open
maginhart opened this issue Oct 30, 2024 · 4 comments
Assignees

Comments

@maginhart
Copy link

Which component impacted?

Encode

Is it regression? Good in old configuration?

Yes, it's good in old version

What happened?

I'm using Intel Arc A380 in a separate pc for encoding purposes.
After installing 32.0.101.6127/32.0.101.6044 drivers the obs qsv encoding performance regresses.
Average time to render frame jumped from usual 2.5-3.0 ms to 10 ms with one local recording session. (QuickSync h264/hevc/av1)
The last three drivers have this issue.
Rolling back to at least 32.0.101.6083/32.0.101.5736 resolves this issue.

What's the usage scenario when you are seeing the problem?

Transcode for media delivery, Content Creation, Game Streaming

What impacted?

No response

Debug Information

No response

Do you want to contribute a patch to fix the issue?

None

@bai-isaac
Copy link
Contributor

hi maginhart, which OS do you use?
This issue is for all codec(AV1/HEVC/AVC)?

@maginhart
Copy link
Author

Windows 11 23H2 yes all codecs.

@maginhart
Copy link
Author

maginhart commented Oct 31, 2024

I've launched fresh obs OBS 30.2.3 with only one scene element video capture device and started recording.
Bellow you can see the difference between drivers 32.0.101.6083/32.0.101.5736 and 32.0.101.6127/32.0.101.6044

obs_old_driver_2024-10-31 11-33-43.txt
old driver_32 0 101 608332 0 101 5736

obs_new_driver_2024-10-31 11-19-24.txt
new driver_32 0 101 6130_32 0 101 6048

@maginhart
Copy link
Author

maginhart commented Nov 13, 2024

I've tried the latest driver 32.0.101.6297 still the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants