A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/staxrip/staxrip/issues/1610 below:

ffindex file generated at wrong location when using custom temp folder · Issue #1610 · staxrip/staxrip · GitHub

Describe the bug
When opening an mkv file, while a custom temp folder is set, StaxRip creates the ffindex in the source folder. When the video is first loaded via Avisynth, the cachefile key for FFVideoSource points to the temp folder, where a new ffindex cache is generated as well.

Expected behavior
StaxRip should use the temp folder to generate the ffindex file. This works as expected, when the temp folder is not set manually.

How to reproduce the issue

  1. Start with Automatic Workflow
  2. Go to Project->Options->Path
  3. Set 'Temp Files Folder' to any location (e.g. C:\test)
  4. Confirm and open an mkv file (e.g. C:\input\source.mkv)
  5. This will create two .ffindex files (e.g. C:\test\source.ffindex and C:\input\source.mkv.ffindex)

Provide information
As far as I can tell, StaxRip creates the source.mkv.ffindex file via ffmsindex.exe. When loading the avisynth script, FFVideoSource is run with a filename in the temp folder as cachefile location (which does not exist yet) and will index again. I could verify that it's those two processes by running them manually and comparing the checksum on the resulting files (which are different between ffmsindex and FFVideoSource).

Used StaxRip version: 2.44.5

I don't think this is related to the source file, but if so I can provide an example file.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4