mirror of
https://github.com/jellyfin/jellyfin-web
synced 2025-03-30 19:56:21 +00:00
Suggest ImageExtractionTimeoutMs changes for Idle priority
After seeing repeated logs about `ffmpeg` being started then killed for being unresponsive, I tracked down this configuration setting on GitHub. So far, my Trickplay generation is much more reliable with a timeout of 30,000 instead. See: jellyfin/jellyfin#13116
This commit is contained in:
parent
8fea5c0da0
commit
1837e50376
1 changed files with 1 additions and 1 deletions
|
@ -1780,7 +1780,7 @@
|
|||
"PriorityBelowNormal": "Below Normal",
|
||||
"PriorityIdle": "Idle",
|
||||
"LabelProcessPriority": "Process Priority",
|
||||
"LabelProcessPriorityHelp": "Setting this lower or higher will determine how the CPU prioritizes the ffmpeg trickplay generation process in relation to other processes. If you notice slowdown while generating trickplay images but don't want to fully stop their generation, try lowering this as well as the thread count.",
|
||||
"LabelProcessPriorityHelp": "Setting this lower or higher will determine how the CPU prioritizes the ffmpeg trickplay generation process in relation to other processes. If you notice slowdown while generating trickplay images but don't want to fully stop their generation, try lowering this as well as the thread count. Increasing the 'ImageExtractionTimeoutMs' value above 20,000 may be needed for the 'Idle' priority.",
|
||||
"LabelImageInterval": "Image Interval",
|
||||
"LabelImageIntervalHelp": "Interval of time (ms) between each new trickplay image.",
|
||||
"LabelWidthResolutions": "Width Resolutions",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue