Closed neo-neo1 closed 7 months ago
Are there any nzbToMedia logs?
Generally, these "obfuscated" filenames are replaced by the download name by nzbToMedia so that processing can complete. Otherwise there is often a "rename" file in the download itself. nzbToMedia should find such rename file (rename.bat, rename.sh etc.) then read the contents of that file, find out if it is a valid rename command for a file (or multiple files) in the download, then apply those renames... this way the user doesn't have to run the rename file (and potentially run any un-wanted commands that are hidden within).
So, my expectation is that nzbToMedia should handle this for you. I'd just need to see the logs to understand what is/isn't happening.
Not directly a nzbToMedia "issue", but it's adjacent. Clinton Hall & this community has been particularly helpful and I'm curious if nzbToMedia has anything to fix such scenarios. Every once in a while I will have a successful nzb download only to find out the filename is
abc.xyz.e2d39aabb41d64.mkv
or another variation ofabc.zyz-XXXX
and Medusa will deny the post process request nzbToMedia sends it. This issue is very prevalent among season packs on Usenet and is independent of a specific indexer or release group.I use nzbToMedia with NZBGet and Medusa. Is there any additional scripts I should look into running on NZBGet?
Thanks in advance
Log from Medusa