Hello, I tried to migrate to the latest version (or any version for the matter) and I get stuck on “using config file: config.yml” with no other messages showing on the console.
What is worse is when I tried to revert back to my original version I still get stuck on the same message.
If I try to create a new db, I get stuck on “Optimizing Database”
We had an issue recently related to hanging while testing hardware decode support in ffmpeg. It should have been fixed, but it’s possible you’ve hit a corner case or something.
Which os are you running on, and which version of ffmpeg do you have?
I’m on Windows 11 (26100.6899), ffmpeg version 8.0
And you’re running stash version 0.29.3? Just as a sanity check, I’d re-download ffmpeg, as I think they fixed the hang without bumping the version number iirc.
If you’re still running into hanging with the latest stash version and redownloaded ffmpeg, can you try changing the loglevel to Debug or Trace in your config file, and see if there’s any more useful log output?
I am currently trying to run version 29.3 (but it does not work with any version).
Using Debug:
DEBU[2025-11-09 18:44:00] Reading plugin configs from [PATH]\plugins
DEBU[2025-11-09 18:44:00] Reading scraper configs from C[PATH]\scrapers
DEBU[2025-11-09 18:44:03] using ffmpeg: [PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffmpeg.exe
DEBU[2025-11-09 18:44:03] using ffprobe: [PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffprobe.exe
DEBU[2025-11-09 18:44:03] FFMpeg version 8.0.0 detected
DEBU[2025-11-09 18:44:03] FFProbe version 8.0.0 detected
Using Trace:
INFO[2025-11-09 18:38:45] using config file: config.yml
DEBU[2025-11-09 18:38:45] Reading plugin configs from [PATH]\plugins
DEBU[2025-11-09 18:38:45] Reading scraper configs from [PATH]\z_lmajdp\scrapers
DEBU[2025-11-09 18:38:46] using ffmpeg: [PATH]\Local\Programs\WingetUI\choco-cli\bin\ffmpeg.exe
DEBU[2025-11-09 18:38:46] using ffprobe: [PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffprobe.exe
DEBU[2025-11-09 18:38:46] FFMpeg version 8.0.0 detected
DEBU[2025-11-09 18:38:46] FFProbe version 8.0.0 detected
TRAC[2025-11-09 18:38:46] [InitHWSupport] Testing codec {H264 NVENC HQ profile h264_nvenc}: [[PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffmpeg.exe -hide_banner -v warning -hwaccel_device 0 -f lavfi -i color=c=red:s=1280x720 -t 0.1 -c:v h264_nvenc -profile p7 -tune hq -profile high -rc vbr -rc-lookahead 60 -surfaces 64 -spatial-aq 1 -aq-strength 15 -cq 15 -coder cabac -b_ref_mode middle -vf format=nv12,hwupload_cuda,scale_cuda=-2:480 -f null -]
TRAC[2025-11-09 18:38:46] [InitHWSupport] Testing codec {H264 NVENC h264_nvenc}: [[PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffmpeg.exe -hide_banner -v warning -hwaccel_device 0 -f lavfi -i color=c=red:s=1280x720 -t 0.1 -c:v h264_nvenc -rc vbr -cq 15 -vf format=nv12,hwupload_cuda,scale_cuda=-2:480 -f null -]
TRAC[2025-11-09 18:38:47] [InitHWSupport] Testing codec {H264 Intel Quick Sync Video (QSV) h264_qsv}: [[PATH]\AppData\Local\Programs\WingetUI\choco-cli\bin\ffmpeg.exe -hide_banner -v warning -init_hw_device qsv=hw -filter_hw_device hw -f lavfi -i color=c=red:s=1280x720 -t 0.1 -c:v h264_qsv -global_quality 20 -preset faster -vf hwupload=extra_hw_frames=64,format=qsv,scale_qsv=854:480 -f null -]
It’s definitely hanging on the QSV test, and it looks like the timeout test I put in isn’t working on Windows.
For reference: [Bug Report] QSV hwaccel on ffmpeg v8 is broken · Issue #6064 · stashapp/stash · GitHub
To work around this, I’d download ffmpeg from Builds - CODEX FFMPEG @ gyan.dev and place ffmpeg.exe and ffprobe.exe in the same directory as your stash config file.
I haven’t been able to reproduce the hanging issue on my Windows PC.
Yeah, it works doing this