Recently I’ve encountered a number of downloads where the processing does not automatically complete because the extracted folder contained within the .rar contains [ and/or ] in its name. eg: The.Blacklist.S02E05.The.Front.No.74.720p.WEB-DL.DD5.1.H.264-NTb extracts to a folder a [ as the first character and NZBDrone doesn’t process this until I manually edit the name to remove the [ and move it to the Drone Factory manually. Can these just be filtered out/ignored by NZBDrone?
Can you give the full path? Its not clear exactly what the issue is, we can’t simply drop [ or ] from the filename, its used in anime files and parsing is required before we know if its anime or not. I realize that CDH already knows some of this information, so I need to understand exactly what the problem is.
Well, in the above example:
NZBDrone searches for, and finds: https://pfmonkey.com/details/f2655b0bca462e390d5ca59c79de962c
14-10-21 20:31:37.0|Info|Nzbget|Adding report [[ The.Blacklist.S02E05.720p.WEB-DL.DD5.1.H.264-NTb] to the queue.
14-10-21 20:31:37.1|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone.Console
14-10-21 20:31:37.1|Info|DownloadService|Report sent to download client. [ The.Blacklist.S02E05.720p.WEB-DL.DD5.1.H.264-NTb
The .nzb it downloads is called: [ The.Blacklist.S02E05.720p.WEB-DL.DD5.1.H.264-NTb.nzb
It passes this to NZBGet which downloads it, unpacks it and moves it to: /temp/tvdrone/[ The.Blacklist.S02E05.720p.WEB-DL.DD5.1.H.264-NTb
Contained in that folder is the .mkv file: The.Blacklist.S02E05.The.Front.No.74.720p.WEB-DL.DD5.1.H.264-NTb.mkv (no leading bracket)
This sits in the tvdrone folder until I manually remove the bracket and space from the folder name, and then move it to my Drone Factory folder (see our email exchange earlier this week).
Hope this helps.
Looks like some bad REGEX on the indexer that isn’t removing the opening bracket, that release is probably named on the indexers I use. They should be able to fix it, the fix in drone will come when you can manually over ride the import instead of having to move it manually, which wasn’t planned to fix this problem, but it would.
Thanks for taking a look. Will contact the admins at pfmonkey and ask them if they’d take a look at their code.