qBittorrent
qBittorrent copied to clipboard
qbittorrent
Pieces Tab
I have recently switched to qBittorrent and have been very pleased with its resource usage and download performance. However one feature I miss having a Pieces Tab. It would go next to the "General", "Tracker" and "Peers" tabs. The Pieces tab would display each piece currently being downloaded by qBittorrent. The following is a description of each column:
# - the piece's number in the .torrent file.
# of Blocks - the number of 16 KiB blocks that compose that single piece.
Availability - the number of times this piece is seen completed within the group of peers you are currently connected to. Blocks - the graphical progress bar for the piece. You could use different colors for different blocks. For example: Dark blue means the data has been downloaded and written to disk. Medium blue means the data has been downloaded, but remains in the cache in memory, unwritten to disk. Light blue means the data has been requested from a single peer. Green means the data has been requested from multiple peers. Blocks only turn green during endgame mode. White means the data is is available in the swarm, but has not yet been downloaded.
Completed - the number of blocks completed in the piece.
Mode - the general evaluation of the speed at which the piece is being transferred by the peer. A piece's mode can be either fast, medium, or slow.
Priority - shows the priority qBittorrent has assigned the piece based on the priority of the file(s) it belongs to.
Size - the size of the piece.
Any update on this wishlist bug ? This would put it to parity with other torrent clients such as deluge (on GNU/Linux) and utorrent (on windows). Having some sort of progress on each piece would make it the best. This is especially necessary when you have big pieces (4 MB or 8 MB) and speed is an issue.
Looking forward to implementation of the above.
oneswarm has pieces tab and it lags progi something terrible not seen it on my copy of deluge though you sure its there.
On 9/8/13, shirish [email protected] wrote:
Any update on this wishlist bug ? This would put it to parity with other torrent clients such as deluge (on GNU/Linux) and utorrent (on windows). Having some sort of progress on each piece would make it the best. This is especially necessary when you have big pieces (4 MB or 8 MB) and speed is an issue.
Looking forward to implementation of the above.
Reply to this email directly or view it on GitHub: https://github.com/qbittorrent/qBittorrent/issues/228#issuecomment-24030790
Who knows the web better than anyone? Rogue_Spider and Google.
OneSwarm is based on the Azureus and written in Java. qBittorrent is written in C, so it should be able to achieve much better performance. Since Deluge is also based on the libtorrent-rasterbar library and does not have any performance issues displaying piece data, qBittorrent should also be able to implement it. If the user desires, they can always disabled it by closing the Pieces Tab.
in Deluge, the pieces tab is a plugin, see https://github.com/nicklan/Deluge-pieces-plugin for inspiration.
Offtopic: qBittorrent is written in C++ I would consider implementing this, but I have so much to do. qbt is basically 1.5man-show right now.
To the users can you attach screenshots of the different visual implementations, for inspiration? For examle IIRC:
- utorrent just has a list of the currently downloading pieces
- Azureus has a grid with each cell representing a piece. Each cell has a different colour depending if it is downloaded/being downloaded/written to disk/etc.
actually i noticed with oneswarm a great improvement of speed and its ability to find more peers in the p2p environment so if a download stalls out or looks dead i switch it over its my fallback from qbit
On 9/9/13, sledgehammer999 [email protected] wrote:
To the users can you attach screenshots of the different visual implementations, for inspiration? For examle IIRC:
- utorrent just has a list of the currently downloading pieces
- Azureus has a grid with each cell representing a piece. Each cell has a different colour depending if it is downloaded/being downloaded/written to disk/etc.
Reply to this email directly or view it on GitHub: https://github.com/qbittorrent/qBittorrent/issues/228#issuecomment-24123586
Who knows the web better than anyone? Rogue_Spider and Google.
This is not in the v3.2.0 so looks like it will take a long long time for it to happen.
I would love to see a piece map like in Bitcomet. It is very useful to spot the moment when video file is ready for starting to watch in preview download mode. I think it is must have feature for all bittorrent clients.
@evsh: Do you think you might be able to work on this?
Given all your work on per-file availability, I think you are the most qualified for implementing this idea.
pffff i know why i hate qbt, because hey utorrent has this since almost first alpha version. well.
Something like this ?
FYI, I using Iceberg theme but I need to test with vanilla theme.
There is still work to be done (more testing, fix some issues, read coding guidelines, etc) before PR. But you can test it here
If you have any suggestions, I'm open to it.
@midoriiro commented on 2021. máj. 9. 16:08 CEST:
Something like this ?
FYI, I using Iceberg theme but I need to test with vanilla theme.
There is still work to be done (more testing, fix some issues, read coding guidelines, etc) before PR. But you can test it here
If you have any suggestions, I'm open to it.
Without builds I for one can't really try it.
@midoriiro
Feel free to submit a draft PR, so that CI can run on this repo and other users can download builds to test as you develop. You are not expected to fully comply to coding guidelines and such while the PR is in draft state. Once it is ready, you can take it out of draft state and request reviews.
Really miss this feature. It's been 10 years since it's been open, any update on this? @midoriiro @sledgehammer999
I honestly don't understand the devs of qbitorrent. They have probably the best torrent client out there but decide to be dense about random stuff like this. This and a persistent flag option for sequential downloads are the only things keeping me from switching to qbitorrent fully (coming from utorrent who has them built-in and deluge with plugins) and every mention of them (or even provided PR) seem to be dismissed.
@parthagar
I don't work anymore on this feature since 2021, if I remember well, the devs team agreed to not integrate it as is. Currently I don't have time to work on it but my code is still available on my fork if someone want to continue this feature.
@jnvillar commented on Aug 22, 2023, 11:22 PM GMT+2:
is this feature dead?
Originally posted by @jnvillar in https://github.com/qbittorrent/qBittorrent/issues/228#issuecomment-1688949605
Can't be. It never existed. :) Any way, while it would be nice, the lack of it doesn't take away much of QB's utility.
