Jump to content

Strange issue with HW transcode


Recommended Posts

Posted

OK, this is may even not be an issue, just a really strange thing I have no idea it would be a problem or not.

I just build a new unraid NAS with intel i3 10100T for my parents, I install emby with docker, enable HW transcode, but it shows two options:

image.png.a765a9726e3661e3b1d2adad86eaede1.png

Before this I build 2 NAS with similar setup, I only see VAAPI option, where did this quicksync option come from, is this some sort of new upgrade and how this different from VAAPI?

I know quicksync is intel gpu transcode tech, I just never see it in emby before.                                                                                                                                                                                                  

Posted

HI, is something wrong?

Posted
3 hours ago, Luke said:

HI, is something wrong?

Nothing is wrong, both option works( tho quicksync option has slightly higher CPU useage than VAAPI).

I am just confused cuz I never see this option before, don't know where did it come from..........

Posted

Because you have an Intel chip and we support hardware acceleration via quicksync (and vaapi).

Posted
9 hours ago, xyzeratul said:

Nothing is wrong, both option works( tho quicksync option has slightly higher CPU useage than VAAPI).

I am just confused cuz I never see this option before, don't know where did it come from..........

In earlier versions, users needed to install the Intel Media SDK themselves to be able to use QuickSync on Linux. Only few had done this.

Recently we have added QuickSync support for Linux to the Emby installation, so it is supported right out of the box.

 

Understanding performance in those scenarios can be tricky: QuickSync generally provides better performance than VAAPI while the difference varies between cases and hw platforms.

Most likely, QuickSync does video processing faster which causes the CPU to do its tasks (audio transcoding, copying memory) faster as well => higher CPU load

Posted
3 minutes ago, softworkz said:

In earlier versions, users needed to install the Intel Media SDK themselves to be able to use QuickSync on Linux. Only few had done this.

Recently we have added QuickSync support for Linux to the Emby installation, so it is supported right out of the box.

 

Understanding performance in those scenarios can be tricky: QuickSync generally provides better performance than VAAPI while the difference varies between cases and hw platforms.

Most likely, QuickSync does video processing faster which causes the CPU to do its tasks (audio transcoding, copying memory) faster as well => higher CPU load

Thank you, that clears my confusion.

You mention it's support right out of box now, but still need to map the gpu device in its docker deployment right?

Posted
11 hours ago, xyzeratul said:

Thank you, that clears my confusion.

You mention it's support right out of box now, but still need to map the gpu device in its docker deployment right?

Virtualized environments such as docker may require additional work on your part, yes.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...