First, thanks for feedback
paulcx wrote: Fri Dec 04, 2020 6:35 pm
- It kept the "Added on" and "Completed on" dates, and my uploaded ratios for many years of torrents!
Otherwise my entire time history of torrenting would have been gone.
(I think this was what was meant by "Save date, metrics,status" in the thread's initial post)
I will note that bt2qbt not transfer global statistics, everything else that is possible to transfer, we will transfer.
paulcx wrote: Fri Dec 04, 2020 6:35 pm
-It did not save changes I made to the torrent name within the qBT window.
(E.g, a torrent might originally have been poorly named "s03" but missing the show title.) So unfortunately those occasional comments are gone (unless I look for them manually on screen when running uTorrent).
You mean renamed torrent in utorrent\bittorrent transfers with original torrent name (s03, in your example)?
paulcx wrote: Fri Dec 04, 2020 6:35 pm
- I didn't use the Replace command to replace paths. I assume that's for changing where the downloads are stored.
I just did it in a separate step beforehand: After copying all the downloads to a new folder, Copying rather than Moving to have a backup, I used the Bencode software to find and replace all the path names in uTorrent's giant resume.dat file, to point to the right locations for .torrent and downloaded files. Bencode is out there on the web.
Yes, that's what it was made for. Initially, the option was made for migration between platforms (for example, from Windows to Linux), it is necessary to change paths (e.g. "D:\\films\" to "/home/user/films"). But I have another tool for batch changing tracker or paths:
https://github.com/rumanzo/qbtchangetracker
paulcx wrote: Fri Dec 04, 2020 6:35 pm
- Yes as stated one needs to deal with incomplete torrents individually. E.g, there were some old ones not quite seeded that I hoped would eventually have complete downloads. I had used the system where incomplete torrents were marked with ".!uT" (rather than keeping the file name unchanged). Then qBittorrent wouldn't find the file at all, so I'd find and replace .!uT with .!qB, and look for those torrents in qBT and Recheck them for % completion.
I forgot about this option, and will make a note in the readme
paulcx wrote: Fri Dec 04, 2020 6:35 pm
- For those having issues setting up the Windows command line, here's what I did as an example:
Ran Command Prompt as Admin. I used quotes below just because one of my path names had a space in it.
The command was:
-------------
bt2qbt_v1.8_amd64.exe -s "D:\qbt\= torrents" -d "C:\Users\[MyLogin]\AppData\Local\qBittorrent\BT_backup" -c "C:\Users\[MyLogin]\AppData\Roaming\qBittorrent\qBittorrent.ini"
-------------
It's correct, but for many users don't nessesary. 99% users can (and they really do) just run binary file and click few times enter. I've even seen similar instructions on some local forums ("1. download 2. run 3. enter 4. enter 5. done").
paulcx wrote: Fri Dec 04, 2020 6:35 pm
The "-s" is supposed to be "Source directory that contains resume.dat and torrents files". I guess since I hadn't stored my torrents files in the default system drive folder for uTorrent stuff (....\Appdata\Roaming\...), I didn't have the resume.dat file in the same folder as the torrents files, so I copied it over to where the .torrent files were, so both would be in the same folder for this software to access.
If yours torrent files automatically saves to another directory, in resume.dat you will see full path to torrents, and bt2qbt understand it. Default path for resume.dat (if it is not portable version) - %APPDATA%/uTorrent
bt2qbt is set to standard location initially
paulcx wrote: Fri Dec 04, 2020 6:35 pm
The "-d" is supposed to be "Destination directory BT_backup". I didn't know what that meant but things only worked when I used the -d command. The BT_backup folder gets filled with .torrent files and .fastresume files, all with hashed file names. So you don't see the original usually readable .torrent file names. (Meanwhile, the readable torrent files are in that source directory mentioned for the -s command.)
If you setup qbittorrent with default settings, BT_BACKUP will be %LOCALAPPDATA%\qBittorrent\BT_backup
bt2qbt is set to standard location initially
paulcx wrote: Fri Dec 04, 2020 6:35 pm
The "-c" is supposed to be "Source directory that contains resume.dat and torrents files" but that's confusing, and is the same as what was written for "-s". Ignore that statement, and just put in a path that points to the file qBittorrent.ini, which is what Rumanzo also put in the first post. That's all that's needed.
Thanks, this is a bug. When I changed the library for working with flags, I made a mistake.
-с flag it's destination of qBittorrent.ini (I will fix readme in next release), it need for transfer tags.
paulcx wrote: Fri Dec 04, 2020 6:35 pm
That file of course stores qBittorrents' preferences & options, which the software tries to transfer over as much as possible from uTorrent. Presumably some settings are transferred over, but many are not. E.g., qBT has its own default settings on maximum connections, connections per torrent, etc. Or for example Rate Limits are treated differently, the max up and down speeds, so I had to set my time-of-day based limits up again.
I didn't put in more features than I needed or what I could physically do. The program is not perfect, but it is better than it was before (some ruby stuff). The transfer of settings is not included in the functionality of the program.
In general, if you are not migrating between platforms, if you have standard installations of the uttorrent and qBittorrent, you don't need cmd or powershell and described flags above at all.