Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to hold files until they have not been modified for x seconds #1122

Open
ToasterUwU opened this issue Nov 27, 2024 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@ToasterUwU
Copy link

Please put plugin requests/bugs at: https://github.com/HaveAGitGat/Tdarr_Plugins

Is your feature request related to a problem? Please describe.
When I copy a really big file into my library, like 80GB kind of big, there will be a time when Tdarr sees the file and puts it in the queue even tho its not done copying yet. I know there is an option to hold for X seconds after finding it, but that makes this process needlessly long and unreliable.

Describe the solution you'd like
I would like an alternative setting to the "hold for x seconds" option, where I tell tdarr to hold until the file has not been modified for X seconds. That way I can set it to 5 minutes, and than 5 minutes after its done being copied, it starts transcoding.

Describe alternatives you've considered
I thought about using the existing feature, but this would not actually make sure it doesn't start transcoding before its done copying unless i put the hold time to something very very high, but that would also mean that there is a long time where i cant watch my media because its not transcoded yet.

Additional context
Im hoping this can be done soon and fast. I have no idea what the codebase looks like, but at least in theory it should be a simple addition.

@dennix85
Copy link

I second for this,
I use the built in future for now, I have to set it to 45min,
Sometimes the file will be copied in 15min but sometimes the disk or network is too busy that it can take up to 45min.
But this also mean for files that are smaller than the said 80~100gb for remuxes
These files will also wait through the set time, waisting unnecessary time.

@ForestQ
Copy link

ForestQ commented Nov 28, 2024

Still looking for a solution. My old solution with multi-node encoding using Carbon Procoder somehow addressed this issue by retaining the partially copied file. It also had an option to re-encode Again and Again if the encoding failed, and eventually, the files would be successfully encoded. In Tdarr, I set it up so that files with larger sizes are encoded by a different library configured to hold files for 3 hours. It's very inconvenient, but it works.

@HaveAGitGat HaveAGitGat added the enhancement New feature or request label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants