Importing complete torrents fails

[Stefan1971HH]

hello,
I've set up separate folders for incomplete and complete torrents.
What I tried to import old complete downloads:

1. attempt:
- move complete download to "complete" folder
- use "add torrent" to add corresponding metadata file
- point path to "complete" folder

result: torrent data aren't recognized, data are re-downloaded

2. attempt
- move complete download to "incomplete" folder
- use "add torrent" to add corresponding metadata file
- point path to "incomplete" folder

result: torrent data aren't recognized, data are re-downloaded

3. attempt
- move complete download to "complete" folder
- use "import existing torrent"
- point path at complete folder

result: torrent data aren't recognized, data are re-downloaded

I've seen a few very similar reports here, but no solution.
Help is appreciated.

thanks
Stefan
 

[ciaobaby]

Does the data in name field of the metadata match exactly with the topmost directory name?

[Stefan1971HH]

Yes.

[ciaobaby]

What version and OS?

Has the 'original' payload been retagged, loaded into a media player of one kind or another or altered in any way?

If you create a new torrent from the payload does the created info hash match precisely with the original hash?

[Stefan1971HH]

3.1.8      Windows 7 x64 pro
Payload wasn't changed (still recognized by µtorrent)
Creating a new Torrent from the Payload in qBittorrent failed with message "vector <T> too long"

[Stefan1971HH]

Ok I found out that this vector problem can be by selecting any Piece size = ... (32kb - 4 Mb)...
And yes, the new metadata file contained the hash of the payload.
Any more suggestions? So far, I have to continue using µtorrent for my seeding duties,
but will happily change to qBittorrent if we can solve this migration problem.

[ciaobaby]

the new metadata file contained the hash of the payload

As it should, but is the "new info hash" (torrent ID) identical to the original hash as shown in uTorrent?
That will tell you if the info key of the original meta data is EXACTLY the same as the meta data that the new location has created.


Just reading through your examples of what you have tried and one ommission is "point to the payload root directory" using "import existing" which may be how the original payload was created and the current "top" folder  may be one one uTorrent created rather than one that was in the original payload.

[sledgehammer_999]

The only true suggestion is to disable "save incomplete torrents in" feature. Unfortunately the "temp folder" logic is a bit fragile and usually ends being broken. It wasn't designed by me and I don't have time to debug this part of the code.

After you successfully import it you'll be able to enable that option again.

[Stefan1971HH]

@ciaobaby: Before my last post, I had just checked (with "Torrent File Hash Checker") if the payload is recognized by the newly created metadata-file. It was.
But now I can see that hash value displayed in the "general" section are different for the two metadata files (the original downloaded one and the newly created one).
Is that what you meant?-thanks

@sledgehammer_999: thanks, will try

[Stefan1971HH]

Basically, it seems to work with disabling ""save incomplete torrents in". There's a problem with importing payloads where I had changed the folder name though. If I move a renamed payload-folder from the µtorrent-completed folder to the qBittorrent-completed folder, import the corresponding metadata file and change the payload folder name in qBittorrent under "torrent content" accordingly (even before actually starting or checking the torrent), things get messed up. I most cases two payload folders were created (original name and new name) sometimes one as subfolder of the other.

[ciaobaby]

There's a problem with importing payloads where I had changed the folder name though.

That's because the metadata info key and the payload root folder are different.

You 'can' work around this by editing the original metadata using BEncode and setting the info -> name value to exactly the same as the new folder name OR vice versa to make the directory/folder name match the meta info -> name value.

Make sure you have a backup ... just in case.

[Stefan1971HH]

What I have tried is re-renaming the payload folder to its original name before importing, and after successful import renaming it in qBittorrent to the desired name. Seems to work.

[sledgehammer_999]

The importer needs a touch-up as it seems. It needs of a way to specify renamed root folder.

[Stefan1971HH]

Yes it could discourage some new users if their first experiences with this otherwise good program are troubles with imports. I'll continue using it now. Thanks for the help.