[Feature] Disable cache?

[CurlyFlow]

Hi, i would like to disable the cache for some librarys because the files are already on a cache drive so that doesnt really make sense in my setup. After they are processed they get moved.

Is that possible to add as a feature?

[HaveAGitGat]

Hi @CurlyFlow, not 100% sure what you're asking but Tdarr needs a cache location to temporarily work on files. This location can be anywhere and can be set in the Library settings Transcode cache option. So you can put it on your cache drive or wherever else. Cache from Tdarr's perspective just means directory to temporarily work on files and is unrelated to any OS cache features.

[CurlyFlow]

Hi, yes i know what it does.

location -> cache -> location

Since in my case the location (/mnt/some/location) = cache (/mnt/some/cache), there is no reason for me to move the file. (same disk)

You know, my location, is not my archive...

lets say you download, convert and then add to archieve...

[HaveAGitGat]

Sorry still not sure what you mean. If you're wanting to have the cache folder on the same as your cache disk then can place it there. The Tdarr transcode cache folder is essential as it's temporary folder for Tdarr to work on files. It's not right to have this done in the original file location as there could be all sorts of conflicts such as file name issues, locked files, interference from other applications etc.

@supersnellehenk are you familiar with Curly's use case here?

It maybe sounds like you're wanting to put the file in a specific location after processing for archiving? You can do that with a flow e.g:

[HaveAGitGat]

@CurlyFlow if you're able to re-word your request to make it clearer then can have another look but seems like you're misunderstanding what the Tdarr cache is. It's a directory for Tdarr to work on files temporarily and it needs to be somewhere, it can't be disabled.

For example:

In flow route 1: The file will be processed in the Tdarr cache and moved back to the library. You can put the cache on the same disk/drive as the source file so that when the file is moved back to the source it happens instantly.

In flow route 2: File does not need to processed, cache is not used. Maybe you thought the cache is still being used here but, to clarify, it's not.

[CurlyFlow]

Sorry for the confusion.

My flow looks normal. I just want to save one move, because its for me already from the starting point in a temp directory... so it doesnt need to be copied moved or whatever, i dont know what impact that makes if that "fast move thing" is on

If you say you need a temp file for working on it, then it would mean im asking to move it to the same directory the original is. (is that currently possible?)