Jump to content
Yrosma

different behaviour in hardware transcoding between emby 4.2.1.0 and 4.4.2.0

Recommended Posts

Yrosma

Not sure if this is in the right location so if it's not just move it.

 

We are trying all kinds of different hardware with xponology and running emby server via docker.

We had some issues before with the intel with hd605 graphics boards. This was fixed for xponology so we could use them for hardware transcoding. At least we tough that was the case.

We were running emby server 4.4.2.0 and transoding kinda worked but was mostly scrambled blocks and stuff so even though emby said vaapi was being used the eventual result was kinda crappy and therefor not usefull.

Just for reference and testing purpose we reversed emby server to the 4.2.1.0 release. And a bit too our surprise everything worked fine with emby server 4.2.1.0.

 

Now we are wondering what could be causing this difference in a messed up transcoding output in 4.4.2.0 and a correctly working transcoding output in 4.2.1.0?

 

Just guessing here, driver difference in the emby docker image? or different build of ffmpeg that is used for the transcoding? I assume the emby docker images contain their own ffmpeg build?

 

For now we can just use the 4.2.1.0 emby server. But would be nice if at one point we could upgrade to the latest one without problems and we also would just like to understand what is happening here.

Share this post


Link to post
Share on other sites
Luke

Hi there, can we please look at an example?

Share this post


Link to post
Share on other sites
Yrosma

Hi there, can we please look at an example?

Hi Luke, what exactly do you need. Friday I'm at my friend again and we can look into this again.

For now I was thinking about getting logs for the emby 4.2.1.0 release. Then upgrade the emby server to emby 4.4.2.0 again and try and collect the log files again.

Is this enough for you as an example? Or should we do also try some other things?

Share this post


Link to post
Share on other sites
Luke

Hi Luke, what exactly do you need. Friday I'm at my friend again and we can look into this again.

For now I was thinking about getting logs for the emby 4.2.1.0 release. Then upgrade the emby server to emby 4.4.2.0 again and try and collect the log files again.

Is this enough for you as an example? Or should we do also try some other things?

 

I would check out softworkz suggestion and see if that helps. Thanks.

Share this post


Link to post
Share on other sites
Yrosma

I couldn't exactly do what was suggested in the other topic. Things like the /opt folder which I don't have in my docker image on my xpenology nas and I also couldn't find anything like the emby server config file to set the export.

But I did manage to try some other things.

I checked the ffdetect on the docker container for emby 4.2.1.0 which is working for us and that one is using DEVICEINFO:Driver=Intel i965 driver for Intel® Gemini Lake - 2.3.0.

We also checked the emby server 4.4.2.0 and latest beta version. Both have newer versions. 2.4.0 for the Intel i965 driver. This one we can't get to work. It does use hardware transcoding but the output is scrambled. We also tried the iHD_drv_video.so driver for the newer versions but they all give the same result.

We also did copy the Intel i965 2.3.0 driver to the 4.4.2.0 emby server and then the transcoding is working correctly again.

 

So somehow things go wrong with the newer drivers for us as the old driver is working.

 

Not sure what to do to get it working with the newer drivers?

Share this post


Link to post
Share on other sites
Luke

That's interesting, thanks for the investigation. We'll try to chase it down.

Share this post


Link to post
Share on other sites

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...