jacksen168 3 Posted October 26, 2025 Posted October 26, 2025 (edited) Hi! @Luke, I am very disappointed with this latest Emby server upgrade. 1. The library scanning function has become unreliable. It now ignores .ignore files in directories and still adds media files that should be excluded. 2. The hardware transcoding option, which worked fine in the previous version, is now broken. The Intel QuickSync HD Graphics 610 option no longer works, forcing the system to use software transcoding. and only the VAAPI HD Graphics 610 interface allows for hardware transcoding. 3. There are also problems with the filtering feature. When filtering for unwatched content, some watched items are incorrectly included. I cannot tolerate this new version and have already reverted to version 4.8.11.0. I no longer have the energy to participate in the improvement of your product. Original text (Chinese): luke我对这一次的Emby服务端升级表示很失望。 1.扫描库功能变得很不靠谱,扫描对目录中出现的.ignore文件无动于衷,依旧添加了应该被排除的媒体文件。 2.上个版本还好端端的硬件转码选项,这个版本我Intel QuickSync HD Graphics 610选项失效了,变成软件转码了。只有VAAPI HD Graphics 610 接口的能硬转了。 3. 筛选功能也出了问题,筛选未看过其中会混入一部分已看过 我受不了这个新版本,已经换回4.8.11.0版本,我也已不在有精力参与你的产品改进了 Edited October 26, 2025 by jacksen168
Luke 42077 Posted October 26, 2025 Posted October 26, 2025 Hi @jacksen168, apologies for the disruption. The ignore function has been changed but it is quite a bit more flexible than before. Have you taken a look at the instructions in the first post here?
Luke 42077 Posted October 26, 2025 Posted October 26, 2025 Quote 2. The hardware transcoding option, which worked fine in the previous version, is now broken. The Intel QuickSync HD Graphics 610 option no longer works, forcing the system to use software transcoding. and only the VAAPI HD Graphics 610 interface allows for hardware transcoding. 3. There are also problems with the filtering feature. When filtering for unwatched content, some watched items are incorrectly included. Hi, can we please look at specific examples of these? Thanks !
jacksen168 3 Posted October 26, 2025 Author Posted October 26, 2025 (edited) 52 minutes ago, Luke said: Hi, can we please look at specific examples of these? Thanks ! Okay, I have reinstalled the new version. Please find the ffmpeg logs attached for both transcoding options. 1. QuickSync HD Graphics 610: QuickSync:ffmpeg-transcode-e2340ace-2eca-43b8-8293-6b06259fea6b_1.txt 2. VAAPI HD Graphics 610: VAAPI:ffmpeg-transcode-14b88add-0660-453d-b6d2-1d7f1399c05f_1.txt As for the issues related to the changes in .ignore file handling, thank you for bringing them to my attention. The problem of the .ignore file being ignored has been fixed. This also resolved the accompanying filter function failure that was caused by the same change. However, the transcoding issue still requires your attention. Original(Chinese): 好吧,我就勉为其难安装回新版本,给你提供两种转码选项下的日志。 至于hanges .ignore我感谢你指出我的问题。 已解决.ignore的忽略问题,且筛选功能的失效也是因.ignore变更引发的,也一并被解决了。 但转码问题还没有解决,还要你看看。 Edited October 26, 2025 by jacksen168 1
Luke 42077 Posted October 27, 2025 Posted October 27, 2025 Hi, is this only an issue when tone mapping?
jacksen168 3 Posted October 27, 2025 Author Posted October 27, 2025 1 hour ago, Luke said: Hi, is this only an issue when tone mapping? No, this issue occurs specifically when hardware transcoding is triggered during bandwidth reduction (lower bitrate playback). When playing a video at a lower bitrate, the Emby backend console shows that transcoding is being triggered. However, the CPU usage is maxed out by the Emby ffmpeg process, which clearly indicates that it's falling back to software (CPU) transcoding. I don't recall this being a problem in the previous version. In this new version, only the "VAAPI HD Graphics 610" option works, while the "Intel QuickSync HD Graphics 610" option has completely stopped functioning. Original(Chinese): 不是,降低码率时调用硬件转码出现的问题。降低码率播放视频时,在后台控制台可以看到时有触发转码的,但CPU利用率却因emby的ffmpeg占满,这完全是在使用CPU软件解码吧?我记得上个版本是没有这个问题的。这个版本只有"VAAPI HD Graphics 610"可用,"QuickSync HD Graphics 610"完全失效了
Solution Bims0n 14 Posted October 27, 2025 Solution Posted October 27, 2025 This has already been documented, however not sure if it is already worked on after my latest submission.
jacksen168 3 Posted October 27, 2025 Author Posted October 27, 2025 5 hours ago, Bims0n said: This has already been documented, however not sure if it is already worked on after my latest submission. Okay, I understand. I will pay attention to whether the issue is fixed in the next version. 我知道了,我会在下个版本留意它是否被修复 1
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