6 qBittorrent

Clinton Hall edited this page 2019-11-04 12:28:05 +13:00

Table of Contents

• qBittorrent

qBittorrent

Support for Client V4.1.0+ only

If you are using qBittorrent, perform the following steps to configure postprocessing for "TorrentToMedia":

1. Rename the autoProcessMedia.cfg.sample to autoProcessMedia.cfg and edit the parameters:

    i.   [Torrent] clientAgent = qbittorrent
   

   ii. [Torrent] uselink = hard to allow hard-linking of files quicker and less harddisk used, if download and final location are on the same hard-disk set uselink = no to use normal copy options. Any movement across hard disks / network MUST use "no"

   iii. [Torrent] categories: all categories/labels/sub-directories used by your downloader.

    music,music_videos,pictures,software
   

   iv. [Torrent] compressedExtentions: all extensions you want to be identified and extracted

    .zip,.rar,.7z,.gz,.bz,.tar,.arj
   

   v. [Torrent] mediaExtentions: all extensions you want to be identified as videos and processed.

    .mkv,.avi,.divx,.xvid,.mov,.wmv,.mp4,.mpg,.mpeg,.vob,.iso
   

   vi. [Torrent] metaExtentions: all other extensions you want to be processed. other extensions will be ignored.

    .nfo,.sub,.srt,.jpg,.gif
   

   vii. [CouchPotato] & [SickBeard] category: you must set the category that is passed from these applications, or use AutoTools or some other method to define the label as custom1 tag. you can easily change that to another tag as desired.

    If using "blackhole-subdirectory", this is the last folder name used in the blackhole.
   
    e.g. tv or movies
   

   viii.[CouchPotato] & [SickBeard]: Configure the remaining settings as describes in nzbToCouchPotato and nzbToSickBeard on the autoProcessMedia.cfg page.

2. In qBittorrent set the PP script as.

    Windows:
    C:\full\path\python27\python.exe C:\full\path\to\nzbToMedia\TorrentToMedia.py ""%D"|"%N"|"%L"|"%I""
    Linux:
    C:\full\path\to\nzbToMedia\TorrentToMedia.py "%D|%N|%L|%I"
   

3. Output from TorrentToMedia will be logged where the scripts reside, in a file called "postprocess.log"