starred/qBittorrent

Fork 0

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

[Feature Request] Automatically set 'Download in sequential order' and 'Download first and last pieces' flags after adding torrent #4591

New issue

Closed

opened 2026-02-21 17:24:00 -05:00 by deekerman · 8 comments

deekerman commented

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

Owner

Originally created by @KulaGGin on GitHub (Aug 3, 2016).

Please, add this function. Yes, I have read threads:
https://github.com/qbittorrent/qBittorrent/issues/164
https://github.com/qbittorrent/qBittorrent/issues/1404
http://wiki.vuze.com/w/Sequential_downloading_is_bad

I don't care if sequential download is a 'bad' or a 'good' thing or if it is natively supported by BitTorrent technology etc. This feature is available in other BitTorrent clients and it's missing in qBitTorrent, so it is a problem which should be fixed.

There is option to download files in sequential order and it works perfectly fine when you want to watch movie right after you started downloading it: you add torrent and set 'Download in sequential order', in less than 30 seconds later you can open video file with PotPlayer, for example, and start watching movie instead of waiting 15-25 minutes to download it completely.

I watch a lot of movies and it is very uncomfortable to set flags every single time just to download files in sequential order.

Please, add option to set these flags automatically for all torrents. People are asking you to add this feature for years, you've released about 50+ updates since first request and you still didn't do it.

Originally created by @KulaGGin on GitHub (Aug 3, 2016). Please, add this function. Yes, I have read threads: https://github.com/qbittorrent/qBittorrent/issues/164 https://github.com/qbittorrent/qBittorrent/issues/1404 http://wiki.vuze.com/w/Sequential_downloading_is_bad I don't care if sequential download is a 'bad' or a 'good' thing or if it is natively supported by BitTorrent technology etc. This feature is available in other BitTorrent clients and it's missing in qBitTorrent, so it is a problem which should be fixed. There is option to download files in sequential order and it works perfectly fine when you want to watch movie right after you started downloading it: you add torrent and set 'Download in sequential order', in less than 30 seconds later you can open video file with PotPlayer, for example, and start watching movie instead of waiting 15-25 minutes to download it completely. I watch a lot of movies and it is very uncomfortable to set flags every single time just to download files in sequential order. Please, add option to set these flags automatically for all torrents. People are asking you to add this feature for years, you've released about 50+ updates since first request and you still didn't do it.

deekerman closed this issue

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

deekerman commented

2026-02-21 17:24:04 -05:00

Author

Owner

@menzow commented on GitHub (Sep 9, 2016):

I also required this change.. Since it's literally one line of code, I decided to fork the repository, enable this flag by default, and re-compile.

You can see the commit here:
github.com/menzow/qBittorrent@8d2126c2a4

This works like a charm.

It's a matter of principle from the developers to not implement this feature, and I can respect this. Since the project is open source and really easy to compile, I think it's better to just implement it yourself and compile your own version of qBittorrent. I'm not even a C++ developer, or experienced in compiling software, but I was able to figure this out with minimal effort.

@menzow commented on GitHub (Sep 9, 2016): I also required this change.. Since it's literally one line of code, I decided to fork the repository, enable this flag by default, and re-compile. You can see the commit here: https://github.com/menzow/qBittorrent/commit/8d2126c2a4d85257bba8c53a4a0a7e74bf6b016f This works like a charm. It's a matter of principle from the developers to not implement this feature, and I can respect this. Since the project is open source and really easy to compile, I think it's better to just implement it yourself and compile your own version of qBittorrent. I'm not even a C++ developer, or experienced in compiling software, but I was able to figure this out with minimal effort.

deekerman commented

2026-02-21 17:24:04 -05:00

Author

Owner

@nextgenthemes commented on GitHub (Oct 17, 2016):

Well think is is pain in the ass when you need to compile yourself rather then get the latest version with apt-get on ubuntu from ppa or official source.

Like others have said in the other issue, it makes no sense to restrict this, since upload limits can set to 1kb/s by default THAT HURTS not this. Does this feature not already is only permitted when there are enough seeds? This is how uTorrent does it, they don't let you stream when it would hurt the swarm so that should be done if not already.

What about the idea to adding this at least to the dialog when the torrent opens? Did the dev say anthing about that idea yet?

@menzow Your fix should also add the "download first and last piece first" or not?

@nextgenthemes commented on GitHub (Oct 17, 2016): Well think is is pain in the ass when you need to compile yourself rather then get the latest version with apt-get on ubuntu from ppa or official source. Like others have said in the other issue, it makes no sense to restrict this, since upload limits can set to 1kb/s by default _THAT HURTS_ not this. Does this feature not already is only permitted when there are enough seeds? This is how uTorrent does it, they don't let you stream when it would hurt the swarm so that should be done if not already. What about the idea to adding this at least to the dialog when the torrent opens? Did the dev say anthing about that idea yet? @menzow Your fix should also add the "download first and last piece first" or not?

deekerman commented

2026-02-21 17:24:04 -05:00

Author

Owner

@gbdoin commented on GitHub (Nov 17, 2016):

This feature is long due. There are perfectly legitimate use cases for a feature like that, and clear ways to prevent abuse on the swarm I think. This is the kind of feature that could drive adoption, not kill it. What makes bittorrent strong is mass usage, not a pure and perfect implementation of the protocol. Someone probably needs to weight the advantages and disadvantages more seriously.

@gbdoin commented on GitHub (Nov 17, 2016): This feature is long due. There are perfectly legitimate use cases for a feature like that, and clear ways to prevent abuse on the swarm I think. This is the kind of feature that could drive adoption, not kill it. What makes bittorrent strong is mass usage, not a pure and perfect implementation of the protocol. Someone probably needs to weight the advantages and disadvantages more seriously.

deekerman commented

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

Author

Owner

@Seeker2 commented on GitHub (Jun 19, 2017):

Duplicate to the links referenced in the 1st post, please close.

@Seeker2 commented on GitHub (Jun 19, 2017): Duplicate to the links referenced in the 1st post, please close.

deekerman commented

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

Author

Owner

@kwstas86 commented on GitHub (Feb 25, 2018):

"People are asking you to add this feature for years, you've released about 50+ updates since first request and you still didn't do it."
"I also required this change.. Since it's literally one line of code"
Apparently the dev doesn't give a shit because it is TOO DAMN HARD to open session.cpp and add torrent->setSequentialDownload(true);

@kwstas86 commented on GitHub (Feb 25, 2018): "People are asking you to add this feature for years, you've released about 50+ updates since first request and you still didn't do it." "I also required this change.. Since it's literally one line of code" Apparently the dev doesn't give a shit because it is TOO DAMN HARD to open session.cpp and add `torrent->setSequentialDownload(true);`

deekerman commented

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

Author

Owner

@menzow commented on GitHub (Feb 26, 2018):

@kwstas86 like I said it's a matter of principle - not effort. That's why it has not been added.

Their reasoning is that too many people downloading a torrent in sequential order pollutes the seed pool and degrades network performance.

@menzow commented on GitHub (Feb 26, 2018): @kwstas86 like I said it's a matter of principle - not effort. That's why it has not been added. Their reasoning is that too many people downloading a torrent in sequential order pollutes the seed pool and degrades network performance.

deekerman commented

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

Author

Owner

@kwstas86 commented on GitHub (Feb 27, 2018):

@menzow k

@kwstas86 commented on GitHub (Feb 27, 2018): @menzow k

deekerman commented

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

Author

Owner

@sledgehammer999 commented on GitHub (May 11, 2018):

Duplicate of #164

Also locking conversation: https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-388520313

@sledgehammer999 commented on GitHub (May 11, 2018): Duplicate of #164 Also locking conversation: https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-388520313