v1.1.5 : ◆ AutoDownload: (new) Now able to download.◆ Log_GR: (del) Drop Error-Tracking-Loggr, the service is no longer available. ◆ TraktUpdateServices: (fix) Support added for new API restrictions. ◆ TorrentMonitor: (fix) Auto-Stop-All now works as intended. ◆ TorrentDialogs: (fix) magnetLinks were being submitted twice due to NWJS bug. Note that older versions are no longer supported. ◆ TorrentClient: (fix) qBitTorrent 4.5+ fix API call to remove torrent ◆ TorrentClient: (fix) Upgrade Tixati API for 2.86+. ◆ TorrentClient: (fix) replace deprecated rTorrent calls, add support for qBitTorrent 4.2+, ignore aria2 metadata file reports. ◆ TorrentClient: (new) Introducing tTorrent client. ◆ Languages: (new) Greek, Turkish, Slovak, South African English. Switch chromium-args: –flag-switches-begin –disable-features=HighEfficiencyModeAvailable –flag-switches-end. ◆ Standalone: (fix) Prevent Chromium 112+ freezing tabs if idle. ◆ Standalone: *(upgrade) NWJS 75.1 with Chromium 112. ◆ SearchEngines: (fix) EzTVag new domain (eztv.wf) and results, limetorrrents DL links and new domain, 1337x DL links, TPB ( 0.org), TPB mirror resolver, RarBG details links and RateLimit, torrentdownloads new domain, fix details link for Jackett indexers. ◆ SearchEngines: (del) KATcr is broken, TorrentZ2 is gone, ETTV is gone, Zooqle is gone. ◆ SearchEngines: (new) Add ETag (extratorrent.st), IsoHunt2 (), TGx (torrentgalaxy.to), EXT (ext.to), KATws (), Knaben (). This complements and progressively takes over from FanArt. ◆ TMDBArt: (new) Refactor image loading to use TMDB. ◆ FanArt: (fix) Previously the default image was selected, now select the first English image if available. Nightly : ◆ AutoDownload: (new) Now able to use series custom Seeders, custom Includes and custom Excludes.So this is effectively a dead end and 99% torrent in most cases are as good as 0% ones.Changelog what’s happening with the latest releases Renaming the video is not possible and would not work if it's not 100% (It can be previewed but will have no index). If the original seeder and all 100% seeders are gone, and the 99% guy remain, then everyone else will be seeding at 99%. So I think the explaination above is incorrect, I thinl there must be some kind of a glitch where, sometimes, when a torrent is moved or altered, some useless data gets missing : Hidden files ? Metadatas ? The Index ? If the metadata of a file were to be erased somehow but the video complete, then the torrent would no be detected as 100% I suppose. But the torrent says that the video is only 99,99% complete. My torrent was complete, I moved it away to another support, then downloaded the torrent again, replaced the files with the ones from the new HD, forced a recheck, and the recheck gave a 99,99% result. The steps are roughly the same in Windows, but I don't know a command that will truncate or partially copy a file.īumping on that, as I just happened to be the seeder of a 99.99% file, even though I have the full file. If qBittorrent realizes there are any more 99.x% downloaded files, set those to maximum priority as well.In qBittorrent, force recheck so the program realizes a big chunk is missing.Create a truncated copy: head -c > truncated.View file in file browser, so you can easily drag and drop to copy its full path.Set it at normal priority, but set all the other 99.x% files to maximum priority.Peers will still send you the small missing bits along with the missing 30 MB. What if there are multiple files stuck at 99.x%? The trick is to truncate one file (to convince peers to connect to you), but set the others at maximum priority so they download at the same time, despite that sending you those small bits isn't worth the time of peers. ![]() (At the end I will explain how to do this on WSL or OSX, and Windows users can share methods in the comments.) Deleting the last 30 MB of the file also works. Deleting the whole file, rechecking, and resuming the download gets the file. ![]() The reason I think my explanation is correct is that requesting more data always works. Is there a correct way to solve this within the torrent client? It seems the clients prefer to send big swathes of data to one person rather than little pieces of data to various clients. I think this happens because other peers decide we need so little data that it's not worth it to start sending it to us. I think we've all experienced files in a torrent that get stuck at >99%, even though there are plenty of seeds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |