MrMackey 26 Posted February 12 Share Posted February 12 Greetings, I am using the Official Emby 4.8.1.0 Docker on Unraid when I try to play a movie with Hardware Accelerated Tone Mapping it doesn't start, I just get this error message after a few seconds. If I deactivate Hardware Accelerated Tone Mapping it works. Here are the logs from the failed attempt with Enable Hardware Accelerated Tone Mapping. embyserver.txtffmpeg-remux-32abfc33-2c41-4263-9fac-18cb8315eff4_1.txtffmpeg-remux-abc7e5a1-facb-435c-bad5-f2a9cf1ca5c7_1.txtffmpeg-transcode-e69e92c8-1b18-4cbd-a60c-d48b2b6f4500_1.txtffmpeg-transcode-f5bd6618-368e-4e51-9b03-c67d32865fe8_1.txthardware_detection-63843333437.txt Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 14 Share Posted February 14 @MrMackey Thanks for the logs. This might be just a bit too much for the Atom CPU/GPU, to do tone mapping on 4k frames. Can you please try: Whether it works when you scale down to a lower resolution in the client (like 720p)? Whether it works with Super-T instead of Extra-T (keep the low resolution)? Whether it works when changing all encoders and decoders to VAAPI? Thanks 1 Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 15 Author Share Posted February 15 (edited) @softworkz Thank you for your help! Indeed it is not the strongest igpu, but I believe I remember that it worked with emby 4.7.14 I tried with 720p but it was the same result the movie doesn't start at all. With Super-T the result was also the same the movie doesn't start at all. It only worked when I set it to Vaapi and Vaapi HW Tone Mapping. But this Tone Mapping is a little too dark for my taste. Here are the logs where it works with Vaapi HW Tone Mapping. embyserver.txtffmpeg-transcode-637be3a5-ea2e-41d3-aebd-32dc48a79590_1.txt Edited February 15 by MrMackey Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 16 Author Share Posted February 16 @softworkz Thankfully I made a full backup of 4.7.14 before updating to 4.8.1.0 So I installed the Docker version 4.7.14 for testing. There Hardware Accelerated Tone Mapping works with Quicksync and the transcoding speed is twice as fast. Here are the logs of version 4.7.14 embyserver.txtffmpeg-transcode-4a4305f2-8ebf-4a0b-94ab-21d92a6a488b_1.txthardware_detection-63843678663.txt Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 17 Share Posted February 17 Thanks for the logs. Yet, those from 4.7 are including a scale-down to 1080 opposed to the ones from 4.8, so it's not an equal comparison. But lets try to check the OpenCL driver installation. Can you please (install and) run clinfo inside each of the Docker containers? Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 17 Author Share Posted February 17 (edited) 1 hour ago, softworkz said: Can you please (install and) run clinfo inside each of the Docker containers? Unfortunately, I have no idea how I can run this in the docker container. I have not found a way to download anything in the Docker container. Edited February 17 by MrMackey Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 17 Author Share Posted February 17 1 hour ago, softworkz said: Yet, those from 4.7 are including a scale-down to 1080 opposed to the ones from 4.8, so it's not an equal comparison. That is interesting but I have set it to 4k 40 mbit Link to comment Share on other sites More sharing options...
Happy2Play 8296 Posted February 17 Share Posted February 17 14 minutes ago, MrMackey said: That is interesting but I have set it to 4k 40 mbit Don't know the thresholds but 4K -40mbps is irrelevant as only bitrate matters so you are getting scaling at 40mbps to 1080. Just like there is no such thing as 1080p - 4Mpbs. The resolutions really need to be dropped from the quality or enforce resolution with bitrate. But mentioned in other topics. 1 1 Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 17 Author Share Posted February 17 @Happy2Play Ahh, okay thanks for the explanation. Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 19 Author Share Posted February 19 @softworkz Could you tell me how I can install clinfo inside the Docker container? Unfortunately, all my attempts have failed. Link to comment Share on other sites More sharing options...
Luke 37100 Posted February 20 Share Posted February 20 8 hours ago, MrMackey said: @softworkz Could you tell me how I can install clinfo inside the Docker container? Unfortunately, all my attempts have failed. Hi there, what exactly happens when you try? Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 20 Author Share Posted February 20 (edited) @Luke Hello, First I tried to download clinfo in the docker container via apt-get, apk, yum, dnf, zypper. But none of them worked. Then I downloaded clinfo on my windows pc and copied it into the docker container and tried to start it but that didn't work either. Sorry for being so stupid but my knowledge about docker containers is quite limited. Edited February 20 by MrMackey Link to comment Share on other sites More sharing options...
alucryd 216 Posted February 22 Share Posted February 22 (edited) @MrMackeyOur images are based on busybox, so chances are you won't have what is required to run external binaries on it. The error you get is probably because it's not executable, a simple `chmod +x clinfo` should make it possible to run `./clinfo` afterwards, but only if it was built against a glibc version that is not newer than ours. We will ship our own clinfo in the next images so you could wait for that, or temporarily switch to the LinuxServer image which comes with a package manager and should let you install clinfo from its repositories. https://docs.linuxserver.io/images/docker-emby/ Edited February 22 by alucryd Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 @alucryd Many thanks for the update. I guess I have to use the LinuxServer image for 4.7.14. because it's not worth building it extra for this test, right? Link to comment Share on other sites More sharing options...
alucryd 216 Posted February 22 Share Posted February 22 Yeah, if you mean to stay on the stable release it would be easier to carry the tests out on the LinuxServer image. I could provide a prebuilt clinfo, but I can't give an ETA so the quickest route is LinuxServer for now. Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 @softworkz@alucryd Okay I used the LinuxServer Docker image and was able to successfully install clinfo. For both Docker container 4.7.14 and 4.8.1 the output was the same "Number of platforms 0" Do I have to install something else or include it when I run clinfo? However, the behavior was the same as with the official Emby Docker container: 4.7.14 Hardware Accelerated Tone Mapping works with Quicksync 4.8.1 Hardware Accelerated Tone Mapping dosent work with Quicksync Thank you very much for your help! Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 22 Share Posted February 22 It's interesting that clinfo shows 0 but still works on one of them. It's possible that the environment variable settings are missing. We have some stub scripts for ffmpeg which allows you to run ffmpeg manually in the same way as it is run by emby server. Those scripts are called like "emby-ffmpeg", probably in the "/bin" folder (I'm not sure for Docker). Can you try to copy "emby-ffmpeg" to "emby-clinfo" and then change the last line to execute "clinfo" instead of ffmpeg and run it this way? Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 @softworkz Hi, I have found the emby-ffmpeg in /app/emby/bin There I copied "emby-ffmpeg" to "emby-clinfo" and made the following changes as shown in the screenshot. I hope this is correct. However, when running it I got the same result Number of platforms 0 This attempt was with the Emby LinuxServer image 4.7.14 Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 22 Share Posted February 22 Okay, thanks this looks like all done right. Did you check whether OpenCL tone mapping is working with this Docker image? Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 (edited) Yes, I just checked it again to make sure, here are the logs again so you can have a also look This is from the Emby LinuxServer image 4.7.14 Oh wait how can I select OpenCL in 4.7.14? Or do you mean with the 4.8.1 Docker container? embyserver.txtffmpeg-transcode-4df408a5-2801-400e-85b5-b79408aeee79_1.txthardware_detection-63844223512.txt Edited February 22 by MrMackey Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 22 Share Posted February 22 (edited) Okay, this appears to be working. I couldn't remember it, but now I found the "secret" command in my notes which causes ffmpeg to list the OpenCL devices that it can "see" - which is more relevant (closer to the truth) than clinfo: emby-ffmpeg -v debug -init_hw_device opencl Can you please run this and show the result? Edited February 22 by softworkz Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 I have tried it but the command does not seem to work in the docker container. Link to comment Share on other sites More sharing options...
Lessaj 64 Posted February 22 Share Posted February 22 It seems to be expecting /opt/emby-server as the base path but you have it in /app/emby so update that in the script and try again. 2 Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 22 Share Posted February 22 4 minutes ago, Lessaj said: It seems to be expecting /opt/emby-server as the base path but you have it in /app/emby so update that in the script and try again. Thanks! That also explains why clinfo didn't work - the env variables weren't set correctly for the same reason. 1 Link to comment Share on other sites More sharing options...
MrMackey 26 Posted February 22 Author Share Posted February 22 (edited) @LessajThanks that was trick @softworkz Here are the results 4.7.14 4.8.1 Here are the results from clinfo clinfo4.7.14.txt clinfo4.8.1.txt Edited February 22 by MrMackey Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now