add/append torrent name to save path #3596

Open
opened 2026-02-21 16:51:43 -05:00 by deekerman · 20 comments
Owner

Originally created by @Snurre86 on GitHub (Dec 18, 2015).

Want a checkbox in with "add/append torrent name to save path" in "options\downloads\Hard Disk" and in the "Display torrent content and some options" dialog box.

Might be an issue with:
-Character path length limits?
-Combining "append the label of the torrent to the save path" and "add/append torrent name to save path"

add torrent dialog - save options
torrent name to save path - options

Also see: #4417

Originally created by @Snurre86 on GitHub (Dec 18, 2015). Want a checkbox in with "add/append torrent name to save path" in "options\downloads\Hard Disk" and in the "Display torrent content and some options" dialog box. Might be an issue with: -Character path length limits? -Combining "append the label of the torrent to the save path" and "add/append torrent name to save path" ![add torrent dialog - save options](https://cloud.githubusercontent.com/assets/7798635/11911803/5ebc911c-a622-11e5-9775-576309d8fdd3.png) ![torrent name to save path - options](https://cloud.githubusercontent.com/assets/7798635/11911747/aaca5708-a620-11e5-9cd6-c8814c60f3ce.png) Also see: #4417
Author
Owner

@thalieht commented on GitHub (Dec 18, 2015):

So you want to add yet another folder that contains the folder that is automatically created containing the contents of the torrent? Or you're downloading crappy torrents who just dump all their files in save path (assuming they exist) or i don't understand what you're asking?

@thalieht commented on GitHub (Dec 18, 2015): So you want to add yet another folder that contains the folder that is automatically created containing the contents of the torrent? Or you're downloading crappy torrents who just dump all their files in save path (assuming they exist) or i don't understand what you're asking?
Author
Owner

@Snurre86 commented on GitHub (Dec 18, 2015):

Yes if I download torrents with 1 file in it, it will just dump it in the downloads folder with stupid names like video.avi etc.

@Snurre86 commented on GitHub (Dec 18, 2015): Yes if I download torrents with 1 file in it, it will just dump it in the downloads folder with stupid names like video.avi etc.
Author
Owner

@Chocobo1 commented on GitHub (Dec 18, 2015):

So you want to add yet another folder that contains the folder that is automatically created containing the contents of the torrent? Or you're downloading crappy torrents who just dump all their files in save path (assuming they exist) or i don't understand what you're asking?

Yes if I download torrents with 1 file in it, it will just dump it in the downloads folder with stupid names like video.avi etc.

So that option you suggested should only apply to single-file torrents. Some thing like: "Create folder for single-file torrent"

@Chocobo1 commented on GitHub (Dec 18, 2015): > > So you want to add yet another folder that contains the folder that is automatically created containing the contents of the torrent? Or you're downloading crappy torrents who just dump all their files in save path (assuming they exist) or i don't understand what you're asking? > > Yes if I download torrents with 1 file in it, it will just dump it in the downloads folder with stupid names like video.avi etc. So that option you suggested should only apply to single-file torrents. Some thing like: "Create folder for single-file torrent"
Author
Owner

@Snurre86 commented on GitHub (Dec 18, 2015):

I don't really have an overview of what torrents that has this issue yet, but I assume that single file torrents are not the only torrents with this issue. For now I would say that I would make the option available to all torrents added with the "add torrent dialog" and later to all of them when I know more.

@Snurre86 commented on GitHub (Dec 18, 2015): I don't really have an overview of what torrents that has this issue yet, but I assume that single file torrents are not the only torrents with this issue. For now I would say that I would make the option available to all torrents added with the "add torrent dialog" and later to all of them when I know more.
Author
Owner

@Snurre86 commented on GitHub (Dec 18, 2015):

You might be right that qbt already do this with torrents with 2 or more files not sure however.

@Snurre86 commented on GitHub (Dec 18, 2015): You might be right that qbt already do this with torrents with 2 or more files not sure however.
Author
Owner

@EraYaN commented on GitHub (Dec 18, 2015):

Yes, multi-file torrents already get a directory (by design). So this would be for single file torrents only.

@EraYaN commented on GitHub (Dec 18, 2015): Yes, multi-file torrents already get a directory (by design). So this would be for single file torrents only.
Author
Owner

@Snurre86 commented on GitHub (Dec 18, 2015):

It is not 100% accurate as the torrent name do vary from the directory but I think that is not to big a deal. For now just go with the single file torrents and we can see if the issue still prevails and make changes from that if needed.

@Snurre86 commented on GitHub (Dec 18, 2015): It is not 100% accurate as the torrent name do vary from the directory but I think that is not to big a deal. For now just go with the single file torrents and we can see if the issue still prevails and make changes from that if needed.
Author
Owner

@Snurre86 commented on GitHub (Dec 18, 2015):

Then again if we add it for torrents with 2 or more files and remove the auto directory it will be possible to get all the files directly in the download folder if wanted. related to #588 #4417

@Snurre86 commented on GitHub (Dec 18, 2015): Then again if we add it for torrents with 2 or more files and remove the auto directory it will be possible to get all the files directly in the download folder if wanted. related to #588 #4417
Author
Owner

@chrishirst commented on GitHub (Dec 19, 2015):

There is a fairly well known problem with this, which causes much confusion when trying to reload the torrent to a client at some future date. The additional top level folder is NOT part of the metadata, so unless the user knows or remembers to remove the additional folder a re-check will fail, as will using "Import Existing Torrent" in qbittorrent.

This has been a continual problem for people migrating to other clients from uTorrent, (see this thread for example), which DOES add this additional folder.

@chrishirst commented on GitHub (Dec 19, 2015): There is a fairly well known problem with this, which causes much confusion when trying to reload the torrent to a client at some future date. The additional top level folder is NOT part of the metadata, so unless the user **knows** or remembers to remove the additional folder a re-check will **fail**, as will using "Import Existing Torrent" in qbittorrent. This has been a **continual problem** for people migrating to other clients from uTorrent, (see [this thread](https://qbforums.shiki.hu/index.php?topic=3224.0) for example), which DOES add this additional folder.
Author
Owner

@EraYaN commented on GitHub (Dec 19, 2015):

To fix that it, might be helpful to have qbitorrent scan folders to find the files themselves, first just filename based and then maybe even file signature based. Recheck also fails when the files are in their "finished" folder, to have the recheck work you need to move the files to the incomplete folder, just a huge mess.

@EraYaN commented on GitHub (Dec 19, 2015): To fix that it, might be helpful to have qbitorrent scan folders to find the files themselves, first just filename based and then maybe even file signature based. Recheck also fails when the files are in their "finished" folder, to have the recheck work you need to move the files to the incomplete folder, just a huge mess.
Author
Owner

@chrishirst commented on GitHub (Dec 19, 2015):

Yes, multi-file torrents already get a directory (by design).

Not actually "by design" if you are assuming it is the receiving peer that adds the folder, the sub folder IS how 'multi-file torrents' are created, so the 'sub folder' IS actually part of the payload.

@chrishirst commented on GitHub (Dec 19, 2015): > Yes, multi-file torrents already get a directory (by design). Not actually "by design" if you are assuming it is the receiving peer that adds the folder, the sub folder IS how 'multi-file torrents' are created, so the 'sub folder' IS actually part of the payload.
Author
Owner

@EraYaN commented on GitHub (Dec 19, 2015):

Yes it's in the metadata right? (So by design of the torrent file structure then I guess, or because of the limitations that are)

The torrent creator decides that folder name, right?

@EraYaN commented on GitHub (Dec 19, 2015): Yes it's in the metadata right? (So by design of the torrent file structure then I guess, or because of the limitations that are) The torrent creator decides that folder name, right?
Author
Owner

@Snurre86 commented on GitHub (Dec 19, 2015):

"might be helpful to have qbitorrent scan folders to find the files themselves, first just filename based and then maybe even file signature based."

Then "also delete files on the hard disk" in delete conformation is going to be really unsafe. It could potentially delete all copies of those file on the whole system.

@Snurre86 commented on GitHub (Dec 19, 2015): > "might be helpful to have qbitorrent scan folders to find the files themselves, first just filename based and then maybe even file signature based." Then "also delete files on the hard disk" in delete conformation is going to be really unsafe. It could potentially delete all copies of those file on the whole system.
Author
Owner

@EraYaN commented on GitHub (Dec 20, 2015):

It could just check if the file was in use by any other torrent. But we are really derailing the thread now ;)

@EraYaN commented on GitHub (Dec 20, 2015): It could just check if the file was in use by any other torrent. But we are really derailing the thread now ;)
Author
Owner

@Drnice1983 commented on GitHub (Mar 11, 2016):

What happened here? I wouldl ike to see that function too. It´s somethink like a batch can do, even after the torrent is finished. But I assume that this needs a recheck or something then?
123.avi will be copied to \123\123.avi
that would help me a lot!

@Drnice1983 commented on GitHub (Mar 11, 2016): What happened here? I wouldl ike to see that function too. It´s somethink like a batch can do, even after the torrent is finished. But I assume that this needs a recheck or something then? 123.avi will be copied to \123\123.avi that would help me a lot!
Author
Owner

@Snurre86 commented on GitHub (Mar 12, 2016):

If the torrent name is 123 the folder will be 123 even if the file has the same name, but in my opinion this only makes sense when the torrent name is "Sintel (2010)" and the file name is "video file.avi". This will result in a folder named "Sintel (2010) with a file named "video file.avi" in it instead of just a file by the name of "video file.avi" in the download folder.

@Snurre86 commented on GitHub (Mar 12, 2016): If the torrent name is 123 the folder will be 123 even if the file has the same name, but in my opinion this only makes sense when the torrent name is "Sintel (2010)" and the file name is "video file.avi". This will result in a folder named "Sintel (2010) with a file named "video file.avi" in it instead of just a file by the name of "video file.avi" in the download folder.
Author
Owner

@Drnice1983 commented on GitHub (Mar 13, 2016):

quote:
If the torrent name is 123 the folder will be 123 even if the file has the same name
/quote

yes thats exactly what I need.

@Drnice1983 commented on GitHub (Mar 13, 2016): quote: If the torrent name is 123 the folder will be 123 even if the file has the same name /quote yes thats exactly what I need.
Author
Owner

@abegreen commented on GitHub (May 31, 2020):

Single file torrents are named differently than Torrent Name and metadata fetch fails to find a match. Please just add option to append torrent name when moving files or give us an example how we can do it by external command or script.

We are not stupid nor we download crappy torrents, Rutorrent has this option for over 10 years and I've seen people all over internet asking for this but you act like we are morons.

@abegreen commented on GitHub (May 31, 2020): Single file torrents are named differently than Torrent Name and metadata fetch fails to find a match. Please just add option to append torrent name when moving files or give us an example how we can do it by external command or script. We are not stupid nor we download crappy torrents, Rutorrent has this option for over 10 years and I've seen people all over internet asking for this but you act like we are morons.
Author
Owner

@klepp0906 commented on GitHub (Dec 6, 2022):

yeap. just ran into this. swapped from manual to categories and when all was said and done, found a bunch of stuff missing files. looked to be all cross seeded stuff which i begrudgingly removed to start with a clean slate at least.

there was stuff left. after looking into it. torrents with the same name (a zip) but different filesize as different files on the inside.

@klepp0906 commented on GitHub (Dec 6, 2022): yeap. just ran into this. swapped from manual to categories and when all was said and done, found a bunch of stuff missing files. looked to be all cross seeded stuff which i begrudgingly removed to start with a clean slate at least. there was stuff left. after looking into it. torrents with the same name (a zip) but different filesize as different files on the inside.
Author
Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

  1. Please select/click the 👍 &/orreactions in the original/opening post of this ticket.

  2. Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
    (new/existing contributors/developers are always welcome)


DO:

  • Provide constructive feedback.
  • Display how other projects implemented same/similar etc.

DO NOT:

  • Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
    (These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#3596
No description provided.