mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Sort by file piece position on content tab #17144
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17144
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kompootor on GitHub (Sep 2, 2025).
Suggestion
On the "Content" tab of a torrent, an optional column could be the starting piece position, and perhaps another column could be the number of pieces the file occupies. These columns are iirc available in uTorrent.
I understand this information may be somewhat redundant with holding shift + hovering on the "General" tab, but when there are many small files, or many pieces, this is very difficult to determine precisely, and the importance of this I'll attempt to illustrate:
Use case
In a torrent with many small files, where many of the files are poorly or not seeded (such as nfo files), it can be not obvious to determine whether the files overlap the header or footer data of the main file(s) of interest. This overlap is therefore important to determine whether or not the data is effectively useless. (It is also important if using qbittorrent verify, when creating torrents, whether or not one has correctly arranged such small files in the correct position to avoid this reseeding problem, as opposed to using a separate torrent inspector program. In fact, just having an built-in or command-line-accessible torrent inspector with the program would be quite sufficient.)
Extra info/examples/attachments
Example: a torrent originally from the Internet Archive has a few small files: "..._meta.xml" , "..._meta.sqlite", and "__ia.thumb.jpg". If the torrent is a large music album, with few seeds, these files may be scattered and/or difficult to place with the mouse cursor on the "General" tab. If these small files are missing, the indication that a file shares data with these is that they have less than 100% availability, but it is not clear if this is at the header or footer. If the file is very slow to download and/or the position of the header is difficult to see in the "General" tab, a good chunk of the file has to be downloaded to check this, with a good bit of user attentiveness.
This is similar to #14394 and #7678 , but those are asking for graphical displays of individual file chunks, for which I haven't personally found too much need in comparison to just verifying header position (and hence a sortable column).