Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add ability to download internal bits of a video-file based on CONTAINER & EXTENSION COMPATIBILITY #10778

FernanDK opened this issue Jun 8, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jun 8, 2019

if a file with pre-determined extension is detected inside the torrent, prioritize the download of its initial and last parts so that automatic identification of its internal components can commence. Say for example a Matroska container also known as .MKV extension file has been detected.

Once the internal bits of the .MKV have been properly targeted, through the GUI allow the user to select for download whichever internal bits he wants, say for example only the audio or only the video or only the subtitle of the MKV, the default mode is to download all internal bits to complete the file 100%.

This is extremely useful for video file sharing and will be very much appreciated by the entire community. It's a feature of such grand value for the entire bittorrent community that it could affect the popularity of the app in an unprecedented way.

Technically it is possible to separately download internal bits of the container extension if its matrix address list is known. The matrix list is typically located in the start or end of the video-file and it's also very small, usually 1 megabyte or less. This procedure can be done without editing the file at all and doesn't affect duplicity-check (hashing) when the file is fully complete. The most widely used containers already support this feature because videostreaming was introduced on the past decade, so the only thing holding this from happening inside the torrent scene is writing the code.

No other bittorrent client has done this. Being the first to deliver this to the community in a properly functional and consistent way might easily secure qBitorrent's position as the favorite's bittorrent-client for the next decade.

I'm eager to hear opinions and thoughts regarding this, from everyone. Tell me what you got.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.