Closed Nabstar3 closed 2 months ago
Fallenbagel
commented
2 months ago The estimated time doesn't come from the downloader but from sonarr/radarr. These tools sync every two minutes with the actual client. And we sync to them.
There's nothing we can do about this. We don't connect to download clients.
Fallenbagel
commented
2 months ago @Nabstar3 #866 should provide a way to refresh the timings once implemented. You can follow that issue for the development progress c:
gauthier-th
commented
2 months ago Description
Currently, Jellyseer displays estimated download times for requested titles that often differ significantly from what the actual downloader states. This discrepancy can lead to confusion and frustration among users who rely on accurate timing information to plan their downloads effectively.
Desired Behavior
We would like Jellyseer to either synchronize its estimated download time calculations with those provided by the downloader itself or implement a more accurate algorithm for estimating wait times. This would ensure that users receive consistent and reliable information regarding when their requested titles will be available for download.
Additional Context
Currently, when a user requests a title for download through Jellyseer, the estimated download time displayed can be significantly different from what the downloader actually indicates. This issue persists across multiple instances and does not seem to improve with different network conditions or download priorities.
Here is an example of the issue:
Jellyseer estimates a download time of 24 hours for a requested title. The downloader interface indicates a remaining download time of 6 hours
. Such discrepancies not only confuse users but also hinder their ability to effectively manage their downloads. We suggest exploring options to improve synchronization between Jellyseer's estimated times and those provided by the downloader, or enhancing the algorithm used to calculate these estimates.
Improving this feature would greatly enhance user experience by providing more accurate and reliable information, thereby reducing frustration and improving overall satisfaction with Jellyseer's download management capabilities.
Code of Conduct
* [x] I agree to follow Jellyseerr's Code of Conduct
Just curious, did you use ChatGPT to write this? I mean wtf is this:
Such discrepancies not only confuse users but also hinder their ability to effectively manage their downloads. We suggest exploring options to improve synchronization between Jellyseer's estimated times and those provided by the downloader, or enhancing the algorithm used to calculate these estimates.
Nabstar3
commented
2 months ago Just curious, did you use ChatGPT to write this? I mean wtf is this:
LOL, yeah I did generate this issue with ChatGPT. The description and behavior were alright in my opinion and I didn't extend my review to the additional context.
Fallenbagel
commented
2 months ago Just curious, did you use ChatGPT to write this? I mean wtf is this:
LOL, yeah I did generate this issue with ChatGPT. The description and behavior were alright in my opinion and I didn't extend my review to the additional context.
There is no "algorithm" or so. We don't calculate the estimated values. Which is why it made no sense
Description
Currently, Jellyseer displays estimated download times for requested titles that often differ significantly from what the actual downloader states. This discrepancy can lead to confusion and frustration among users who rely on accurate timing information to plan their downloads effectively.
Desired Behavior
We would like Jellyseer to either synchronize its estimated download time calculations with those provided by the downloader itself or implement a more accurate algorithm for estimating wait times. This would ensure that users receive consistent and reliable information regarding when their requested titles will be available for download.
Additional Context
Currently, when a user requests a title for download through Jellyseer, the estimated download time displayed can be significantly different from what the downloader actually indicates. This issue persists across multiple instances and does not seem to improve with different network conditions or download priorities.
Here is an example of the issue:
Jellyseer estimates a download time of 24 hours for a requested title. The downloader interface indicates a remaining download time of 6 hours
Improving this feature would greatly enhance user experience by providing more accurate and reliable information, thereby reducing frustration and improving overall satisfaction with Jellyseer's download management capabilities.
Code of Conduct