KevinAtlee 3 Posted September 6, 2025 Posted September 6, 2025 Hello, could someone identify why this file was transcoded using CPU/Software instead of the available NVENC? Transcoding works fine on the majority of my library with NVENC, just noticed my CPU load spike during this transcode. Is it just a DV licensing issue? I was under the impression with an HDR base layer it wouldn't be an issue. Excerpt from ChatGPT: If you transcode Profile 8.1, Emby will still ignore the DV metadata and encode the HDR10 base. That’s fine, but you’re back to CPU because Emby won’t engage NVENC for DV-tagged input. Thanks! ffmpeg-transcode-b2acaf08-32f7-476d-a957-1dfb6f7cb559_1.txt
GrimReaper 4739 Posted September 6, 2025 Posted September 6, 2025 (edited) 2 hours ago, KevinAtlee said: Hello, could someone identify why this file was transcoded using CPU/Software instead of the available NVENC? Your GPU is not even listed as available decoder/encoder: Quote >>>>>> Selected Codecs Decoder Automatic software decoder Encoder x264 Max Bitrate: 781 Mbit/s Color Formats: YUV420P, YUVJ420P, YUV422P, YUVJ422P, YUV444P, YUVJ444P, NV12, NV16, NV21, YUV420P10, YUV422P10, YUV444P10, NV20, GRAY8, GRAY10 - Bit Depths: 8, 10, 12, 14 Profiles: Baseline Profile (Level 6.2), Main Profile (Level 6.2), High Profile (Level 6.2), High 10 Profile (Level 6.2), High 4:2:2 Profile (Level 6.2), High 4:4:4 Predictive Profile (Level 6.2) >>>>>> FindVideoEncoder - MediaType: h264, UseHardwareCodecs: False, HWA-Mode: Advanced Info Checking: 'x264' Info Check successful - selecting 'x264' >>>>>> FindVideoDecoder - MediaType: hevc, UseHardwareCodecs: False, HWA-Mode: Advanced Info Checking: 'Automatic software decoder' Info Check successful - selecting 'Automatic software decoder' Info Tone Mapping would be desired, but software tone mapping is disabled Can you share hardware detection log, and screenshot of your Transcoding settings in Emby? Edited September 6, 2025 by GrimReaper
KevinAtlee 3 Posted September 7, 2025 Author Posted September 7, 2025 It appears to be visible to Emby, logs attached, thoughts? hardware_detection-63892754986.txt
softworkz 5066 Posted September 7, 2025 Posted September 7, 2025 Logs are showing that there's a flag set which indicates to disable hw accelerated transcoding: One reason for this is the lack of a valid Emby Premiere Subscription But it can also be simply due to a preceding transcode attempt which failed. So - assuming that there's a valid Premiere subscription, the answer should be visible in the preceding FFmpeg log rather than this one. 1 1
KevinAtlee 3 Posted September 7, 2025 Author Posted September 7, 2025 I’ve always had a registered lifetime Premiere subscription, and it appears to still be in good standing. Would it be the log immediately before this log, or could it be any number of logs before this? If so, I’ve got some searching to do, and what exactly would I be looking for? Should restarting Emby Server and / or restarting the Emby Server docker reset this flag? Thanks!
softworkz 5066 Posted September 7, 2025 Posted September 7, 2025 1 minute ago, KevinAtlee said: Would it be the log immediately before this log, or could it be any number of logs before this? If so, I’ve got some searching to do, and what exactly would I be looking for? Should restarting Emby Server and / or restarting the Emby Server docker reset this flag? Oh - no. This is always only just about a specific playback case: If one way doesn't work, another one is tried and maybe a 3rd one. Think about it like "HW transcoding has failed, let's try sw transcoding" - but that's all happening as a result of a user initiating playback (e.g. clicking "Play"). When you initiate playback again, it all happens in the exact same way like before - the "flag" I mentioned doesn't persist. 1 minute ago, KevinAtlee said: Would it be the log immediately before this log Yes, the one or two preceding logs.
KevinAtlee 3 Posted September 8, 2025 Author Posted September 8, 2025 I've found a log where NVENC was attempted, but failed on tone mapping? Hopefully someone can point me in the right direction here. Log attached, thanks! ffmpeg-transcode-86a48261-99fb-4d87-be5d-26c6192fa8c4_1.txt
Happy2Play 9780 Posted September 8, 2025 Posted September 8, 2025 Dev will have to comment on the errors, but appear driver related. 11:31:29.799 Stream mapping: 11:31:29.799 Stream #0:0 (hevc) -> scale_cuda:default (graph 0) 11:31:29.799 setparams:default (graph 0) -> Stream #0:0 (h264_nvenc) 11:31:29.799 Stream #0:1 -> #0:1 (eac3 (native) -> ac3 (native)) 11:31:29.799 Stream #0:2 -> #1:0 (subrip (srt) -> webvtt (native)) 11:31:29.799 Stream #0:0 -> #1:1 (copy) 11:31:29.799 Stream #0:3 -> #2:0 (subrip (srt) -> webvtt (native)) 11:31:29.799 Stream #0:0 -> #2:1 (copy) 11:31:29.799 Press [q] to stop, [?] for help 11:31:29.884 [tonemap_cuda@f4 @ 0x55a8253f56c0] cu->cuLinkAddData(link_state, CU_JIT_INPUT_PTX, ff_tonemap_ptx_data, ff_tonemap_ptx_len, "tonemap.ptx", 0, ((void *)0), ((void *)0)) failed -> CUDA_ERROR_INVALID_PTX: a PTX JIT compilation failed 11:31:29.884 [tonemap_cuda@f4 @ 0x55a8253f56c0] CUDA linker output: ptxas application ptx input, line 1037; error : Feature '.branchtargets directive' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1044; error : Feature 'brx.idx' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1157; error : Feature '.branchtargets directive' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1164; error : Feature 'brx.idx' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1277; error : Feature '.branchtargets directive' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1284; error : Feature 'brx.idx' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1400; error : Feature '.branchtargets directive' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1407; error : Feature 'brx.idx' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1893; error : Feature '.branchtargets directive' requires PTX ISA .version 6.0 or later ptxas application ptx input, line 1900; error : Feature 'brx.idx' requires PTX ISA .version 6.0 or later ptxas fatal : Ptx assembly aborted due to errors 11:31:29.885 Error while filtering: Generic error in an external library 11:31:29.885 Failed to inject frame into filter network: Generic error in an external library 11:31:29.885 Error while processing the decoded data for stream #0:0 11:31:30.062 Conversion failed! But have you tried changing your decoder order to see if it makes a difference? >>>>>> Hardware Decoders for hevc [X] NVDEC NVIDIA GeForce RTX 4060 - H.265 (HEVC) [ ] CUVID NVIDIA GeForce RTX 4060 - H.265 (HEVC) 2
softworkz 5066 Posted September 8, 2025 Posted September 8, 2025 @KevinAtlee Please update your Nvidia drivers: Hardware Acceleration on Linux
KevinAtlee 3 Posted September 8, 2025 Author Posted September 8, 2025 I'm presently on what appears to be the latest stable driver: Driver Version:580.82.07
softworkz 5066 Posted September 8, 2025 Posted September 8, 2025 Did you read the doc page` I referenced?
KevinAtlee 3 Posted September 8, 2025 Author Posted September 8, 2025 I did, not to say I couldn't have missed something. I'm using Unraid, so the NVIDIA Driver plugin handles driver installation / updates. I did verify with the NVIDIA link in the doc you referenced, and it is the latest driver. Should I be doing this differently?
softworkz 5066 Posted September 8, 2025 Posted September 8, 2025 From the docs I referenced: Often, Linux distros are excluding some parts of the Nvidia drivers which Emby needs, so the driver version is not a good advisor. The golden advice has always been to go to the Nvidia site and follow their driver instructions - unconditionally. For Unraid though, I'm unsure/don't know. Maybe do a forum search here to see what other Unraid users have done - I don't want to give any wrong advice, but otherwise, the solution has always been to follow Nvidia instructions for driver installaton.
KevinAtlee 3 Posted September 9, 2025 Author Posted September 9, 2025 From what I've gathered, installing from the NVIDIA site, and not the plugin would be a poor life choice. FWIW, after some more testing, this happens to all media that is scaled down from 4k to HD, and requires tone mapping. If doing one task or the other, there is no issue, and the transcoding, or the tone mapping runs on the GPU without fail. I believe it's only the case on DOVI content with an HDR base layer, but I can't seem to find 4K HDR content in my library that doesn't have a DOVI layer for testing. I downloaded your Transcoding Tests plugin, and have it running now. Another excerpt from ChatGPT: What actually bit you is the CUDA tone-mapping filter in Emby’s ffmpeg build. Your other log shows Emby attempted an all-GPU pipeline (NVDEC → scale_cuda → tonemap_cuda → NVENC) and then crashed with a PTX JIT error (CUDA_ERROR_INVALID_PTX … requires PTX ISA .version 6.0+). After that failure, Emby retried in software, which is why you saw CPU x264. This is a filter/PTX compatibility issue. It seems to think it's an Emby issue, but that's well outside my wheelhouse.
Jdiesel 1431 Posted September 9, 2025 Posted September 9, 2025 Agreed with not installing the Nvidia drivers from the Nvidia website on Unraid. Stick with the plugin. You could try copying the command and running it in the terminal to see if it runs on a standard ffmpeg instance. This would rule Emby's custom ffmpeg.
softworkz 5066 Posted September 9, 2025 Posted September 9, 2025 8 hours ago, KevinAtlee said: Another excerpt from ChatGPT That output always depends on what you're asking for (and how). Our FFmpeg hasn't changed for years and I've never seen that error, so I can tell for sure that it's a configuration/setup issue on the Unraid device (or our Unraid package/image). Unfortunately, I'm not familiar with Unraid devices, neither with Emby running under Docker, so my abilities in helping with the issue are limited. This is the only advice I could dig out: Enable the NVIDIA runtime in the Emby Container Edit the Emby container in Unraid (Advanced View): In “Extra Parameters”, add either: --gpus all (modern) or --runtime=nvidia (legacy) Add environment variables: NVIDIA_VISIBLE_DEVICES=all NVIDIA_DRIVER_CAPABILITIES=all These two env vars control which driver libraries (NVENC/NVDEC and PTX JIT for CUDA) get mounted into the container. Restart the container and test. Those exact Unraid UI steps (Extra Parameters + the two NVIDIA_* env vars) are the standard guidance in the Unraid Nvidia Driver plugin thread Test Command (run inside the Emby container) # Check whether the PTX JIT library present (injected by the runtime)? ls -l /usr/lib*/libnvidia-ptxjitcompiler.so* /lib*/libnvidia-ptxjitcompiler.so* 2>/dev/null If the command shows nothing, the runtime didn’t inject the compiler → recheck NVIDIA_DRIVER_CAPABILITIES and the runtime flag.
KevinAtlee 3 Posted September 9, 2025 Author Posted September 9, 2025 (edited) I agree, easily biased, so I don't follow it blindly. My "Extra Parameters" --runtime=nvidia --env NVIDIA_VISIBLE_DEVICES=all --env NVIDIA_DRIVER_CAPABILITIES=all ls -l /usr/lib*/libnvidia-ptxjitcompiler.so* /lib*/libnvidia-ptxjitcompiler.so* 2>/dev/null Output: [root@d31c6e69c629 /]# ls -l /usr/lib*/libnvidia-ptxjitcompiler.so* /lib*/libnvidia-ptxjitcompiler.so* 2>/dev/null lrwxrwxrwx 1 root root 37 Sep 8 07:24 /lib64/libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.580.82.07 -rwxr-xr-x 1 root root 0 Aug 15 03:08 /lib64/libnvidia-ptxjitcompiler.so.570.153.02 -rwxr-xr-x 1 root root 39422584 Sep 2 09:21 /lib64/libnvidia-ptxjitcompiler.so.580.82.07 lrwxrwxrwx 1 root root 37 Sep 8 07:24 /lib/libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.580.82.07 -rwxr-xr-x 1 root root 0 Aug 15 03:08 /lib/libnvidia-ptxjitcompiler.so.570.153.02 -rwxr-xr-x 1 root root 39422584 Sep 2 09:21 /lib/libnvidia-ptxjitcompiler.so.580.82.07 lrwxrwxrwx 1 root root 37 Sep 8 07:24 /usr/lib32/libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.580.82.07 -rwxr-xr-x 1 root root 0 Aug 15 03:08 /usr/lib32/libnvidia-ptxjitcompiler.so.570.153.02 -rwxr-xr-x 1 root root 54510228 Sep 2 09:21 /usr/lib32/libnvidia-ptxjitcompiler.so.580.82.07 lrwxrwxrwx 1 root root 37 Sep 8 07:24 /usr/lib64/libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.580.82.07 -rwxr-xr-x 1 root root 0 Aug 15 03:08 /usr/lib64/libnvidia-ptxjitcompiler.so.570.153.02 -rwxr-xr-x 1 root root 39422584 Sep 2 09:21 /usr/lib64/libnvidia-ptxjitcompiler.so.580.82.07 lrwxrwxrwx 1 root root 37 Sep 8 07:24 /usr/lib/libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.580.82.07 -rwxr-xr-x 1 root root 0 Aug 15 03:08 /usr/lib/libnvidia-ptxjitcompiler.so.570.153.02 -rwxr-xr-x 1 root root 39422584 Sep 2 09:21 /usr/lib/libnvidia-ptxjitcompiler.so.580.82.07 [root@d31c6e69c629 /]# Transcode Test results attached, thanks Execution on 2025-09-08 2131h.etra Execution on 2025-09-08 2131h.etrd Edited September 9, 2025 by KevinAtlee Added logs
softworkz 5066 Posted September 9, 2025 Posted September 9, 2025 @KevinAtlee - from where did you install Emby Server? Did you replace our included FFmpeg with a custom compiled build?
KevinAtlee 3 Posted September 9, 2025 Author Posted September 9, 2025 (edited) On Unraid, through Community Applications, https://github.com/binhex/arch-emby I personally made no modifications, and from what I can gather, neither did binhex. Info from the console: "[root@d31c6e69c629 /]# ^[[200~grep -a -- '-ffmpeg ' /proc/$(pgrep -f EmbyServer.dll | head -n1)/cmdline | tr '\0' ' ' [root@d31c6e69c629 /]# # Expect: ... -ffmpeg /usr/bin/ffmpeg-emby ... [root@d31c6e69c629 /]# ~which ffmpeg-emby readlink -f /usr/bin/ffmpeg-emby ffmpeg-emby -version | head -n 3 strings /usr/bin/ffmpeg-emby | grep -E 'softworkz|Emby LLC' | head /usr/bin/ffmpeg-emby ffmpeg version 5.1-emby_2023_06_25_u1 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 15.2.1 (GCC) 20250813 configuration: --disable-alsa --disable-doc --disable-ffplay --disable-libpulse --disable-librtmp --disable-libxcb --disable-openssl --disable-shared --disable-vdpau --disable-vulkan --disable-xlib --enable-chromaprint --enable-cuda-llvm --enable-fontconfig --enable-gpl --enable-gnutls --enable-iconv --enable-libaribb24 --enable-libass --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libmfx --enable-libmp3lame --enable-libopus --enable-libtesseract --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --enable-lto --enable-nvdec --enable-nvenc --enable-static --enable-vaapi --enable-version3 [root@d31c6e69c629 /]# which ffmpeg ffmpeg -version | head -n 3 /usr/sbin/ffmpeg ffmpeg version n7.1.1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 15.1.1 (GCC) 20250425 configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-frei0r --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libdvdnav --enable-libdvdread --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgsm --enable-libharfbuzz --enable-libiec61883 --enable-libjack --enable-libjxl --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libplacebo --enable-libpulse --enable-librav1e --enable-librsvg --enable-librubberband --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpl --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-shared --enable-vapoursynth --enable-version3 --enable-vulkan [root@d31c6e69c629 /]# sha256sum /usr/bin/ffmpeg-emby /usr/bin/ffprobe-emby 2ef121cc5ab7b2d138228b4366eaf6e5c706a3da0a30864e0bf3435ed48507d8 /usr/bin/ffmpeg-emby dd5fc3db773adf664d2bf802f711f00bc827e77c09d21b2ed346a0a78a8b39ed /usr/bin/ffprobe-emby [root@d31c6e69c629 /]# " Edited September 9, 2025 by KevinAtlee Added logs
softworkz 5066 Posted September 9, 2025 Posted September 9, 2025 8 minutes ago, KevinAtlee said: On Unraid, through Community Applications, https://github.com/binhex/arch-emby Sigh... I wish I had noticed earlier. I already said that our FFmpeg hasn't changed for years and I've never seen that error before - but I've been too focused on driver setup. Always use our official FFmpeg binaries please. There's no support for custom builds (this issue perfectly illustrates why - ) 1
KevinAtlee 3 Posted September 9, 2025 Author Posted September 9, 2025 I've migrated to the official EmbyServer for Unraid through Community Applications. I'm now getting this message, which I believe to be a permissions issue: No compatible streams are currently available. Please try again later or contact your system administrator for details. I tried scanning the libraries again, but it doesn't appear to see the media at all. Whenever I try to get to the EmbyServer docker console I get: OCI runtime exec failed: exec failed: unable to start container process These are the two docker run commands for comparison, binhex-emby being the existing working copy. docker run -d --name='Emby' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="Emby" -e 'UID'='99' -e 'GID'='100' -e 'GIDLIST'='2' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8096]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/MediaBrowser/Emby.Resources/master/images/Logos/logoicon.png' -p '8096:8096/tcp' -v '/mnt/user/media/':'/mnt':'rw' -v '/mnt/transcodes/transcode/':'/transcode':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia --env NVIDIA_VISIBLE_DEVICES=all --env NVIDIA_DRIVER_CAPABILITIES=all 'emby/embyserver:latest' 580aa873100a8a345fdd06715d8b857999f299b5e6c2de45023d08382a1dc65a The command finished successfully! docker run -d --name='binhex-emby' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="binhex-emby" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8097]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/emby-icon.png' -p '8097:8096/tcp' -v '/mnt/user/appdata/binhex-emby':'/config':'rw' -v '/mnt/transcodes/transcode/':'/transcode':'rw' -v '/mnt/user/media/':'/media':'rw' 'ghcr.io/binhex/arch-emby' --runtime=nvidia --env NVIDIA_VISIBLE_DEVICES=all --env NVIDIA_DRIVER_CAPABILITIES=all 'emby/embyserver:latest' a7b2efcaf512caf4a5495b15849324ceecccd3157d7ca55844646fb80637c7af The command finished successfully!
Luke 42077 Posted September 9, 2025 Posted September 9, 2025 3 minutes ago, KevinAtlee said: I've migrated to the official EmbyServer for Unraid through Community Applications. I'm now getting this message, which I believe to be a permissions issue: No compatible streams are currently available. Please try again later or contact your system administrator for details. I tried scanning the libraries again, but it doesn't appear to see the media at all. Whenever I try to get to the EmbyServer docker console I get: OCI runtime exec failed: exec failed: unable to start container process These are the two docker run commands for comparison, binhex-emby being the existing working copy. docker run -d --name='Emby' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="Emby" -e 'UID'='99' -e 'GID'='100' -e 'GIDLIST'='2' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8096]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/MediaBrowser/Emby.Resources/master/images/Logos/logoicon.png' -p '8096:8096/tcp' -v '/mnt/user/media/':'/mnt':'rw' -v '/mnt/transcodes/transcode/':'/transcode':'rw' -v '/mnt/user/appdata/emby':'/config':'rw' --runtime=nvidia --env NVIDIA_VISIBLE_DEVICES=all --env NVIDIA_DRIVER_CAPABILITIES=all 'emby/embyserver:latest' 580aa873100a8a345fdd06715d8b857999f299b5e6c2de45023d08382a1dc65a The command finished successfully! docker run -d --name='binhex-emby' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="binhex-emby" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8097]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/emby-icon.png' -p '8097:8096/tcp' -v '/mnt/user/appdata/binhex-emby':'/config':'rw' -v '/mnt/transcodes/transcode/':'/transcode':'rw' -v '/mnt/user/media/':'/media':'rw' 'ghcr.io/binhex/arch-emby' --runtime=nvidia --env NVIDIA_VISIBLE_DEVICES=all --env NVIDIA_DRIVER_CAPABILITIES=all 'emby/embyserver:latest' a7b2efcaf512caf4a5495b15849324ceecccd3157d7ca55844646fb80637c7af The command finished successfully! Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!
softworkz 5066 Posted September 9, 2025 Posted September 9, 2025 36 minutes ago, Luke said: Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks! @Luke - He had provided logs already, but now it's not about a playback problem anymore, but about "How to install the official Emby Server" on Unraid. Unfortunately, I cannot help with that myself...
Solution KevinAtlee 3 Posted September 9, 2025 Author Solution Posted September 9, 2025 That was my bad, /media mapping was retained in the library settings, resolved. Shoutout to Emby support, the binhex container was recommended for ease of GPU configuration, but it was in fact the problem. The official EmbyServer docker is not having any issues with DOVI HDR10 4K content being converted to HD. Apologies for the string along, I didn't know any better myself. I owe yeah a beer! TLDR - Use official EmbyServer on Unraid / Ensure correct permissions. Thanks! 2
softworkz 5066 Posted September 9, 2025 Posted September 9, 2025 @KevinAtlee - You're welcome. I'm glad to hear that it's resolved for you now!
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