Please make sure of the following things
AList Version / AList 版本
v3.64.0
Driver used / 使用的存储驱动
local
Describe the bug / 问题描述
The local driver uses d.thumbSize when calculating the md5 hash thumbnail name which is different from the local driver thumbnail size parameter (d.thumbPixel), this means that the thumbnail hash will use the wrong parameter for creating the hash (144 by default rather than 320 which is the default local driver thumbnail size).
Reproduction / 复现链接
Generate thumbnails with local driver using default parameters (144 for thumbSize and 320 for thumbPixel) and then from cli generate the md5 hash and thumbnail name and observe that the 320 width thumbnail generated does not produce the same thumbnail filename as the thumbnail generated with the 144 width parameter.
Config / 配置
defaults, using local driver
Logs / 日志
No response
Please make sure of the following things
I have read the documentation.
我已经阅读了文档。
I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。
I'm sure it's due to
AListand not something else(such as Network ,DependenciesorOperational).我确定是
AList的问题,而不是其他原因(例如网络,依赖或操作)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3.64.0
Driver used / 使用的存储驱动
local
Describe the bug / 问题描述
The local driver uses d.thumbSize when calculating the md5 hash thumbnail name which is different from the local driver thumbnail size parameter (d.thumbPixel), this means that the thumbnail hash will use the wrong parameter for creating the hash (144 by default rather than 320 which is the default local driver thumbnail size).
Reproduction / 复现链接
Generate thumbnails with local driver using default parameters (144 for thumbSize and 320 for thumbPixel) and then from cli generate the md5 hash and thumbnail name and observe that the 320 width thumbnail generated does not produce the same thumbnail filename as the thumbnail generated with the 144 width parameter.
Config / 配置
defaults, using local driver
Logs / 日志
No response