Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - peterd

Pages: [1]
I love qBittorrent, and have been using it for years, but every once in a while I like to see what's out there. I tried Vuze recently, and while it has enough things I didn't like to rule it out for day to day use, one feature it had that I really liked was the ability to recognize when more than one torrent was trying to download the same file (I believe by checksum, as opposed to file name) and to share that progress between the torrents. It may also have been able to identify the same pieces across torrents by checksum, which would actually be more valuable. I also may be totally misunderstanding how it works, I am not an expert on bittorrent internals.  ::)  I believe the features is called swarm discovery.

I like to download some older stuff with very few seeders, so this is a feature that would be very valuable for me. In addition to personal benefit for the individual qBittorrent users, it would also be good for the swarm. I've often found that by doing this technique by hand across multiple torrents it allows people to pick up pieces that they are missing, and encourages folks to stay on longer to share the pieces that they have. I've been able to complete many downloads of older torrents using this method.

This feature would be valuable enough to me that I'd be willing to put up a bounty for its completion.

Please let me know if there is a different/better place to post feature requests.

Generic / Feature request: Export torrent file as modified
« on: August 04, 2019, 09:41:55 pm »
I often will import a torrent file and find that the name of the torrent itself and/or the name(s) of the downloaded file(s) are not sufficiently descriptive, so I modify them in qBittorrent. This all works fine. But then let's say that I archive that torrent, and then later on I want to re-verify it, seed it, etc. I then have to remember how I renamed the file(s) and possibly directory as well in order to reload it.

It would be great to be able to export a torrent file that includes my modifications, without having to create a whole new torrent. There are enough duplicate torrents for the same file(s) out there already.   :P

Is this something that people would be interested in? If so, is there a different/better place to file this as a feature request?

Windows / 4.1.7 out?
« on: August 04, 2019, 09:08:27 pm »
My running 4.1.6 client notified me that there is a 4.1.7 version out, so I downloaded it from I then went to look at the main site, and the ribbon still says 4.1.6, no mention in the News, and the Download page still has 4.1.6.

Is this new version legitimate? Did FH jump the gun?

SF has it as well, same SHA256 checksum for the 64 bit version:

Generic / "Checking resume data" when adding a torrent
« on: April 17, 2018, 06:45:10 am »
For some time now I've been running into an issue where sometimes if I add a torrent that already has something downloaded, qbt will do a check, then it will enter a loop where it will continuously restart the check with the message "Checking resume data." If the torrent is completely downloaded it will pop up the message box saying that the download is complete every time, but it never breaks out of the loop. I have to pause the torrent manually (or delete it).

I did some searches and found that this problem is related to the fastresume data, but the only solution I found was to delete the downloaded content and start from scratch. But that's not a solution if I'm loading up a torrent because it needs seeders, or if I just want to validate a torrent's contents.

I did find two workarounds. One is to check the "Skip hash check" box when I load the torrent. Then I can pause it, do "Force recheck," and then unpause it. The other workaround is to uncheck the "Recheck torrents on completion" option in Advanced before I load the torrent. (I routinely leave that option enabled.) The fact that either of those workarounds work implies to me that there is some sort of race condition between setting the flag that indicates that the torrent has been checked, and updating the fastresume data. But that's just a WAG. In any case, it doesn't seem to me that either of those should be needed.

To make things more weird, it doesn't happen with every torrent. And there is no clear pattern. It both does, and does not happen with single file torrents (with and without subdirectories), multi-file torrents, fully downloaded, partially downloaded, and it happens in both Ubuntu and native Windows (4.0.4 on both, but it's been happening for a long time). The fact that it happens with so many different circumstances reinforces my belief that it's some sort of race condition.

Happy to provide more data, test, etc.

... and of course, thanks for a great client!   ;D

Pages: [1]