Jump to content

Recommended Posts

Posted

Hi there, please attach the emby server log as well. Thanks.

  • Solution
Posted

Hi Koolee,

I faced the same issue with my Synology DS224+, but I managed to resolve it with a few adjustments. Here's what worked for me:

  • Connect to your NAS via SSH and run the following command:

    sudo synogroup --get videodriver

     

This will display the GID for the videodriver group. Note down the GID.

  • Open the YAML configuration file for your Emby Server Docker container and update the GIDLIST value to include the videodriver GID you just retrieved.

Credits → https://joshmccarty.com/emby-with-hardware-transcoding-in-docker-on-synology-dsm-7-2/
 

I hope this helps!

image.png.ca47d731cd17974e9cd267d5cec64d68.png

image.png.59b0092705d943ec8e96d06e18b731aa.png

 

  • Like 1
Posted
1 hour ago, GroDoggo said:

Hi Koolee,

I faced the same issue with my Synology DS224+, but I managed to resolve it with a few adjustments. Here's what worked for me:

  • Connect to your NAS via SSH and run the following command:

    sudo synogroup --get videodriver

     

This will display the GID for the videodriver group. Note down the GID.

  • Open the YAML configuration file for your Emby Server Docker container and update the GIDLIST value to include the videodriver GID you just retrieved.

Credits → https://joshmccarty.com/emby-with-hardware-transcoding-in-docker-on-synology-dsm-7-2/
 

I hope this helps!

image.png.ca47d731cd17974e9cd267d5cec64d68.png

image.png.59b0092705d943ec8e96d06e18b731aa.png

 

It works! Thank you.

  • Thanks 1
Posted

Hi, 

Sorry for "hijacking" this thread but since it's almost the same, I thought that wasn't necessary to create a new one.

 

I installed (a couple of months ago) Emby on Container Manager (Synology DS920+) and like @KooleeI also followed a guide from Mariushosting.

In my case, the difference was that I've done it with Container Manager and (as you can see in the link I add) without HW Transcoding since I didn't have Premiere (which now I have).

 

So, now i can just change the settings on Container Manager to enable the feature, or do I have to delete it and start from the scratch using Portainer like o the guide from Mariushosting?

It would be EXTREMELY painful to set up everything again.

 

Thanks!

Posted

Why are you using container for emby and not install the native package from the App center?

  • Like 1
Posted (edited)
7 minutes ago, weyon668 said:

Why are you using container for emby and not install the native package from the App center?

I didn't know, so i followed the guide i mentioned. I think that when i read somewhere that was the best way to use it on the DS920+.

Anyway, the question here is not why i'm using these way instead of the native app.

Edited by Kurt13
Posted

Yes, but with the native app there are no problems with gpu acceleration. Just install and enjoy it.

Posted
4 minutes ago, weyon668 said:

Yes, but with the native app there are no problems with gpu acceleration. Just install and enjoy it.

I'm trying to avoid start everything from the scratch

Posted

No problem, never touch a running system 😉

  • Like 1
Posted

I changed the GIDLIST from 2 to 937 (that i got through SSH) but it still doesn't show nothing.

GIDLIST.jpg

Emby HWA.jpg

Posted

Hi, 

Is it possible for someone to help me? 

Thanks 

Posted
13 minutes ago, Luke said:

Hi, have you followed the examples in our Docker install guide?

https://hub.docker.com/r/emby/embyserver

When i decided to try Emby for the first time, and since i wasn't a Premiere member, i followed this guide so i don't have a properly yaml file to edit. On Container Manager Emby only shows on "Container" and "Image" tab.

Now, that i bought Premiere, i went to see his guide for having Emby with HW Transcoding but for that one, he used Portainer. 
I tried to ask him how to enable it without starting from the scratch, and, as expected, no help received.

Posted

Just try install the native app without docker and just look if hw works there (shurdown docker first). Then you can choose if you use the native app or loose time with the docker version.

Posted
3 hours ago, weyon668 said:

Just try install the native app without docker and just look if hw works there (shurdown docker first). Then you can choose if you use the native app or loose time with the docker version.

Yes this is a helpful test as well, to see if the native package recognizes it first.

Posted

Hi, 

I changed to a proper use of Emby on docker with YAML config, and now it seems to be working.

Everything was being shown but I had to point out the path to each library and do a re-scan again.

The only issue I'm having, is to set the backup & restore folder. I tried to add a line on YAML with the path to my previous backup folder (outside of the docker folder) with rw, but till now I'm not able to point to it on Emby.

 

Anyway, regarding transcoding, why "stats for nerds" only shows a green symbol for some movies? Both movies I tested are 4K Dolby Vision HEVC TrueHD 7.1. 

 

Thanks

 

Screenshot_20241207_120203_Emby.jpg

Posted

Hi,

The green box shown above would be the same you would see on the Dashboard.
image.png

Run your mouse over it and you'll see it means "Hardware Accelerated Encoding..."
If it's a transcode without the green box, it will be a CPU based transcode.
This will not apply to Direct Play or Direct Stream (Remux) as they don't require transcoding.

Carlo
 

Posted
6 hours ago, Carlo said:

Hi,

The green box shown above would be the same you would see on the Dashboard.
image.png

Run your mouse over it and you'll see it means "Hardware Accelerated Encoding..."
If it's a transcode without the green box, it will be a CPU based transcode.
This will not apply to Direct Play or Direct Stream (Remux) as they don't require transcoding.

Carlo
 

Watching on a cell phone, and outside the house, it would be a bit difficult to use a mouse.

But why the transcode can be on the cpu instead of the GPU (or both)? 

Posted

Blasphemy :)

I guess that's a good reason! LOL

Posted
31 minutes ago, Carlo said:

Blasphemy :)

I guess that's a good reason! LOL

I hate travelling on highways (and by airplane too), it's way too boring, so sometimes I like to watch something. That's one of the reasons why, sometimes, I use the smartphone/tablet to see something to not cut my wrists. 😁

So, do you know why the transcode can be on the cpu instead of the GPU (or both)?

 

Thanks 

  • Like 1
Happy2Play
Posted
23 minutes ago, Kurt13 said:

I hate travelling on highways (and by airplane too), it's way too boring, so sometimes I like to watch something. That's one of the reasons why, sometimes, I use the smartphone/tablet to see something to not cut my wrists. 😁

So, do you know why the transcode can be on the cpu instead of the GPU (or both)?

 

Thanks 

Would need to see the ffmpeg log as it should be gpu unless it fails for whatever reason and will fallback to cpu.

  • Like 1
Posted
12 minutes ago, Happy2Play said:

Would need to see the ffmpeg log as it should be gpu unless it fails for whatever reason and will fallback to cpu.

Tried now 2 times with 2 4K Dolby Vision HEVC TrueHD 7.1 movies (the same ones from my previous post), using my smartphone with 5G.

1st try: One movie didn't show the green symbol but the other did. Also, the 2nd video took some seconds (considerably more than the 1st one) to start playing.

2nd try: Both showed the green symbol. This time, the 2nd video started quickly

ffmpeg-transcode-75ba2829-4e88-4184-b579-4b4bc54c0205_1.txt ffmpeg-transcode-da456fd1-507d-4160-9d29-f7d470b17241_1.txt

Happy2Play
Posted
7 minutes ago, Kurt13 said:

Tried now 2 times with 2 4K Dolby Vision HEVC TrueHD 7.1 movies (the same ones from my previous post), using my smartphone with 5G.

1st try: One movie didn't show the green symbol but the other did. Also, the 2nd video took some seconds (considerably more than the 1st one) to start playing.

2nd try: Both showed the green symbol. This time, the 2nd video started quickly

ffmpeg-transcode-75ba2829-4e88-4184-b579-4b4bc54c0205_1.txt 42.84 kB · 0 downloads ffmpeg-transcode-da456fd1-507d-4160-9d29-f7d470b17241_1.txt 26.99 kB · 0 downloads

To me it would be your PGSSUB burn in as it is currently disable in hardware.  As the ffmpeg-transcode-da456fd1-507d-4160-9d29-f7d470b17241 log has graphical subs and the other does not.  And you see it is slow below 1x conversion speed.

Warning: Hardware-accelerated subtitle-overlay is disabled due to diagnostic option

>>>>>>  Subtitle Processing Steps for [0:3]: HDMV PGS subtitles
        Step                    Format             Target Size 
        HDMV_PGS_SUBTITLE    >> Subs: Bitmap       1920x1080   
        scale                >> Video: UNKNOWN     1920x-2     

>>>>>>  Processing Plan
        Name                                        CanDoInHW  WillDoInHW  Reason                                                 
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec                                          
        VideoInput                               >> True       True        Same adapter (/dev/dri/renderD128), same hardware co... 
        Scaling                                  >> True       True                                                                
        ToneMapping (when possible)              >> True       True                                                                
        SubtitleOverlay                          >> False      False                                                               
        VideoOutput                              >> True       True        Hardware encoder                                        
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec                                          

>>>>>>  Video Processing Steps for [0:0]: H.265 (HEVC)
        Step                    HW-Context   Format       SW-Format           Size   Next
        HEVC                 >> VAAPI        vaapi_vld    yuv420p10      3840x2160 >> scale_vaapi
        scale_vaapi          >> VAAPI        vaapi_vld    yuv420p10      1920x1080 >> tonemap_vaapi
        tonemap_vaapi        >> VAAPI        vaapi_vld    nv12           1920x1080 >> hwdownload
        hwdownload           >> -            nv12         nv12           1920x1080 >> format
        format               >> -            nv12         nv12           1920x1080 >> format
        format               >> -            yuv420p      yuv420p        1920x1080 >> overlay
        overlay              >> -            yuv420p      yuv420p        1920x1080 >> format
        format               >> -            nv12         nv12           1920x1080 >> hwupload
        hwupload             >> VAAPI        vaapi_vld    nv12           1920x1080 >> 


03:45:23.555 subtitle_kickoff: call subtitle_resend_current 52 frame->format: 1
03:45:23.829 elapsed=00:00:00.54 frame=    3 fps=0.0 q=0.0 size=N/A time=00:00:00.00 bitrate=N/A throttle=off speed=   0x    
03:45:24.474 elapsed=00:00:01.06 frame=    8 fps=7.5 q=-0.0 size=N/A time=00:00:00.25 bitrate=N/A throttle=off speed=0.242x    
03:45:24.982 elapsed=00:00:01.57 frame=   12 fps=7.6 q=-0.0 size=N/A time=00:00:00.38 bitrate=N/A throttle=off speed=0.245x    
03:45:25.382 elapsed=00:00:02.09 frame=   15 fps=7.1 q=-0.0 size=N/A time=00:00:00.51 bitrate=N/A throttle=off speed=0.245x    
03:45:26.025 elapsed=00:00:02.61 frame=   20 fps=7.6 q=-0.0 size=N/A time=00:00:00.73 bitrate=N/A throttle=off speed=0.282x    
03:45:26.538 elapsed=00:00:03.12 frame=   24 fps=7.7 q=-0.0 size=N/A time=00:00:00.86 bitrate=N/A throttle=off speed=0.277x    
03:45:26.926 elapsed=00:00:03.64 frame=   27 fps=7.4 q=-0.0 size=N/A time=00:00:00.99 bitrate=N/A throttle=off speed=0.273x    
03:45:27.577 elapsed=00:00:04.16 frame=   32 fps=7.7 q=-0.0 size=N/A time=00:00:01.25 bitrate=N/A throttle=off speed= 0.3x 

log 1

>>>>>>  Processing Plan
        Name                                        CanDoInHW  WillDoInHW  Reason                                                 
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec                                          
        VideoInput                               >> True       True        Same adapter (/dev/dri/renderD128), same hardware co... 
        Scaling                                  >> True       True                                                                
        ToneMapping (when possible)              >> True       True                                                                
        VideoOutput                              >> True       True        Hardware encoder                                        
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec  

log 2 PGSSUB CPU

>>>>>>  Processing Plan
        Name                                        CanDoInHW  WillDoInHW  Reason                                                 
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec                                          
        VideoInput                               >> True       True        Same adapter (/dev/dri/renderD128), same hardware co... 
        Scaling                                  >> True       True                                                                
        ToneMapping (when possible)              >> True       True                                                                
        SubtitleOverlay                          >> False      False                                                               
        VideoOutput                              >> True       True        Hardware encoder                                        
        VAAPI GeminiLake UHD Graphics 600 - H... >> True       True        Hardware Codec 

 

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