starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Need an auto pause function (by day) #4775

New issue

Closed

opened 2026-02-21 17:30:00 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 17:30:00 -05:00

Owner

Originally created by @MrGamerChoi on GitHub (Oct 9, 2016).

I'm a new user that switched from Deluge since the new version of it is not stable and the old one is out of date.

Currently, I'm running a qbit-nox on my handless arm NAS. Before I switched to qbittorrent, I used the plugin called "Auto Remove Plus" which has a lot of options. As I use PT, I need to follow their rules. Basically, I need to seed to 2.0 / 3-7 day deadpans on file size. Deluged did a great job on it and didn't find the option for stop/pause seed after specific days.

Hope I could see this function in next update. Thank you.

Originally created by @MrGamerChoi on GitHub (Oct 9, 2016). I'm a new user that switched from Deluge since the new version of it is not stable and the old one is out of date. Currently, I'm running a qbit-nox on my handless arm NAS. Before I switched to qbittorrent, I used the plugin called "Auto Remove Plus" which has a lot of options. As I use PT, I need to follow their rules. Basically, I need to seed to 2.0 / 3-7 day deadpans on file size. Deluged did a great job on it and didn't find the option for stop/pause seed after specific days. Hope I could see this function in next update. Thank you.

deekerman

2026-02-21 17:30:00 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@thalieht commented on GitHub (Oct 9, 2016):

PR #4266 relevant.

@thalieht commented on GitHub (Oct 9, 2016): PR #4266 relevant.

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@MrGamerChoi commented on GitHub (Oct 9, 2016):

@thalieht So...if I'm correct, this is still work in process and is waiting to be added to the official release once all bugs are fixed ?

@MrGamerChoi commented on GitHub (Oct 9, 2016): @thalieht So...if I'm correct, this is still work in process and is waiting to be added to the official release once all bugs are fixed ?

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@thalieht commented on GitHub (Oct 9, 2016):

Actually it's considered finished by it's author but the maintainer hasn't come around to reviewing it yet.

@thalieht commented on GitHub (Oct 9, 2016): Actually it's considered finished by it's author but the maintainer hasn't come around to reviewing it yet.

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@Misiek304 commented on GitHub (Oct 9, 2016):

qBt project isn't moving very fast forward but it has some great developers working on it.
Currently the only setting for managing seeding torrents I can see is the ratio value, the torrent should reach before stopping seeding.

BTW. Which version of deluge worked for you best?

@Misiek304 commented on GitHub (Oct 9, 2016): qBt project isn't moving very fast forward but it has some great developers working on it. Currently the only setting for managing seeding torrents I can see is the ratio value, the torrent should reach before stopping seeding. BTW. Which version of deluge worked for you best?

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@MrGamerChoi commented on GitHub (Oct 9, 2016):

TL;DR: Deluge packages were broken so I switched to the latest Qbit and have no problem.

Thank you for the reply. The version of Deluge that worked for me would be 1.3.10 and libtorrent 0.15.xxx something like that. I would say it worked but not the best, with the same setting and same seed, my PC's (Deluge 1.3.13, libtorrent 1.1.0) at the same time would easily reach above 15mb/s. On the other hand, my older version Deluge on Debian NAS could only reach like 2xx to 3xx kb/s, same with upload speed. Once I update it to a newer version (libtorrent 1.1.0 deluge 1.3.13), it even breaks, I couldn't even run my deluge-console properly. After a lot of downgrading, reinstalling and even OS reset.

So I have decided to switch from Deluge to Qbittorrent. The version I'm using is v3.3.6 and libtorrent 1.1.0, after a week and it still works perfectly, I could finally reach >5mb/s.

@MrGamerChoi commented on GitHub (Oct 9, 2016): TL;DR: Deluge packages were broken so I switched to the latest Qbit and have no problem. Thank you for the reply. The version of Deluge that worked for me would be 1.3.10 and libtorrent 0.15.xxx something like that. I would say it worked but not the best, with the same setting and same seed, my PC's (Deluge 1.3.13, libtorrent 1.1.0) at the same time would easily reach above 15mb/s. On the other hand, my older version Deluge on Debian NAS could only reach like 2xx to 3xx kb/s, same with upload speed. Once I update it to a newer version (libtorrent 1.1.0 deluge 1.3.13), it even breaks, I couldn't even run my deluge-console properly. After a lot of downgrading, reinstalling and even OS reset. So I have decided to switch from Deluge to Qbittorrent. The version I'm using is v3.3.6 and libtorrent 1.1.0, after a week and it still works perfectly, I could finally reach >5mb/s.

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@Misiek304 commented on GitHub (Oct 9, 2016):

I tried Deluge before on Windows and Linux and I had serious stability issues. It crashed a lot. qBittorrent worked best for me but not without some of the developers attention and a bug fix somewhere in 3.3.4. Transmission was also nice but there was no native Windows app and the app itself looks more limited compered to qBt.

@Misiek304 commented on GitHub (Oct 9, 2016): I tried Deluge before on Windows and Linux and I had serious stability issues. It crashed a lot. qBittorrent worked best for me but not without some of the developers attention and a bug fix somewhere in 3.3.4. Transmission was also nice but there was no native Windows app and the app itself looks more limited compered to qBt.

deekerman commented

2026-02-21 17:30:06 -05:00

Author

Owner

@zeule commented on GitHub (Mar 22, 2017):

Closing as duplicate of #1646.

@zeule commented on GitHub (Mar 22, 2017): Closing as duplicate of #1646.