Hardware Transcoding on Linux (Ubuntu)

[djronnieg 1]

Specifically an Ubuntu 18.04 LXC within Proxmox; it appears that the GPU is configured correctly aside from the apparent fact that it doesn't "work". That is, I can play a movie and transcode it but my CPU's are doing all of the work while my GPU is idle.

I figured that a 4K movie would be a god test since I would naturally lower the quality on my phone or browser. I've attached the transcoding log and server logs.

If my method if testing isn't good, how should I go about testing hardware transcoding? I'm open to any advice on troubleshooting or resolving the issue (if there is even an issue).

Side note -- the "nvidia-smi" command does yield the following output:

 

Please let me know if any other info is needed or steps required on my part. Thank you.

embyserver.txt ffmpeg-transcode-4e429f71-b9d7-4f20-b05b-2818032b9594_1.txt

[Luke 42078]

Hi, can you try the native package as a test for comparison purposes?

[djronnieg 1]

 

Firstly, I apologize for not responding sooner. A few hours after my initial post, I did manage to fix the issue all on my own. I was ready to send a triumphant follow-up, that evening, but then my friend "broke" the GPU configuration while he was kindly helping me setup another GPU for use with a VM (GPU pass-through for 1070). The latter is unrelated but the work affected the Nvidia driver had the effect of making the Quadro unusable.

Anyway, my friend fixed the oopsie a couple of days later, and I've been happily using the Quadro with the Emby container for the past couple of weeks. Although it has been working well (as far as I can tell), I figure that it never hurts to provide data, whether for comparison or helping others in the future.

Among the attachments is the terminal output from the "nvidia-smi" command which I issued from the host and the LXC during playback and transcoding. 
Attachments: "host_nvidia-smi.txt", and "LXC_nvidia-smi.txt"
+ a screen recording showing the realtime output from 'Htop' and nvidia-smi' ("2022-06-12 17-09-36-1.m4v").

In addition to the Emby server log (embserver.txt). I've included three transcodeing logs which I beleive correspond with the times at which I changed the bitrate from the Emby App on my Android phone.

Transcoding Logs:
5:12:38 PM
ffmpeg-transcode-4bac4f79-abdb-4e8b-8302-5813e939658d_1.txt

5:13:30 PM
ffmpeg-transcode-7750909c-1249-4ffc-b572-7b379f23417f_1.txt 

5:12:38 PM
ffmpeg-transcode-d5177c54-23eb-47c4-96ca-aff0b812f1f3_1.txt

I

I didn't test Emby on the host itself (natively) as requested since the underlying issue was resolved. I'm generally reluctant to install apps on to the host (natively), especially if they require a lot of dependencies that aren't already present, but if it's something that the dev team still wishes to do, let me know.

Beyond that, let me know if you have any questions or if there is anything else that I can do.

 

Thank you,

Ron

ffmpeg-transcode-7750909c-1249-4ffc-b572-7b379f23417f_1.txt ffmpeg-transcode-d5177c54-23eb-47c4-96ca-aff0b812f1f3_1.txt ffmpeg-transcode-4bac4f79-abdb-4e8b-8302-5813e939658d_1.txt LXC_nvidia-smi.txt host_nvidia-smi.txt embyserver.txt

[Luke 42078]

HI, are you able to update to Emby Server 4.7?