Filebot Download Mirror REPACK
Wardex Walker
Somewhat strangely, while its source code is still available at GitHub and can be manually compiled to generate a working binary, the legacy binaries are no longer available on the FileBot website. Additionally, while SourceForge still lists a FileBot project mirror, the links are simply dead. One can speculate this is because the source code has already been released to the public and cannot be revoked, but offering the binaries would detract from the new pay model, and the effort of compiling the binaries is used as an inconvenience factor for those wishing to utilize legacy versions of FileBot. In other words, all previous builds have been yanked and removed from as many servers as possible in order to (potentially) increase revenue streams.
Therefore, below is a mirror of the last two available FileBot 4.7.8 and FileBot 4.7.9 distributions along with a list of binary checksums for those wishing to validate that this archive has not been tampered with or the sake of academic curiosity.
I have been using filebot to automate the filing of TV shows and movies that are downloaded by my NAS into another folder structured by year, in the case of movies, and show and season, in the case of TV shows.
The change detection only triggers for new directories, files that were open for writing and have been closed, and for files moved into the directory. Opening or writing to a file doesn't trigger it, nor does reading a file. However, some other file in the directory could get written, causing FileBot to run on the whole thing. I don't know if filebot is smart enough to detect when files have opened file handles to them.
On the other hand though, I am having an issue that I imagine most other people using the docker are having too... All drives are spun down, file gets downloaded, then passed to filebot... which then spins up the drive it's writing to, essentially bypassing the cache drive.... why is this occurring? Or why is it sendig a signal to spin up the drive? Is there a method or command to throw in the script to disable this or is there something in one of the parameters thats doing this and I don't know it?
That much I understand, however, if for example: I have nzbget download something, process it, then pass it to the array, using cache drive, with settings so all downloads are technically moved later, why does it not send the signal to spin up the drive, where as with filebot, this is happening? Is it because it's download the metadata separately and is causing this?
I am having an issue that I imagine most other people using the docker are having too... All drives are spun down, file gets downloaded, then passed to filebot... which then spins up the drive it's writing to, essentially bypassing the cache drive.... why is this occurring? Or why is it sendig a signal to spin up the drive? Is there a method or command to throw in the script to disable this or is there something in one of the parameters thats doing this and I don't know it?
As you can see in this image take from command line, permissions are a problem, since the download is done by nzbget (nobody) and filebot writes as root, and also seems to be writing DIRECTLY to the array, rather than using the cache drive.
Of course FileBot is going to write to the output dir, but from the docker container's perspective it can't control what unraid does with that write, or even that unraid exists. This seems like a general unraiddocker issue that's not related to filebot. To confirm, you could modify your other containers to also use /mnt/user/... and I bet you'll see the same spin-up behavior.
I'm not blaming filebot or even this docker for that, a random spin up could even mean that the drive itself on the spindown delay needs to be reinforced again.... just saying, there's something odd about it when I don't have the issue with any other docker handling files that go to the array.
When I get a chance I'll do some experiments, but I don't know how filebot could be somehow telling unraid to spin up the drives, or what I could do to prevent that. The only thing I could imagine doing is filing a bug against unraid.
For some reason, the Emby on TrueNas does not detect the file same way as Ubuntu Emby does. Most of my files was name like this "Show name Season 1 - 5". Because of this, I had to rename ALOT of my files to meet the metadata god approval. (Still working on this). I found filebot to be very good at renaming files.... 95% of the time.
Sure, All The files were under TV shows. Using the show Black mirror as an example. All the files were name as "Black Mirror Season 1 - 1" etc. Emby was only able to find ONE of the episode per season, and that one episode that was found, can be a random episode in that season folder and can have a miss match metadata along with it. This was not an issue on ubuntu so I just use this type of naming format on 70-80% of my other media files. It was fix once I change the naming format to "Black Mirror - S01E01" etc, but thats alot of files I have to go through, but i'm doing it..... slowly but surely.
The "Action --copy" option is probably the simplest and easyest method even though you would have to manually relocate content through uT to your organized folder and delete the copy in your seeding folder, if you wanted to seed for eternity without duplicates. So do some reading on that filebot amc script and use it to automatically process all your downloads. I really wish there was a better way to handle post processing within uT. Honestly how hard would it be for uT to integrate in a automatic rename/relocate natively so that we can have an organized media library AND seed?!?!? At the very least GIVE US SYMLINK SUPPORT!
Instead of toying with uTorrent's location, the script creates a mirror of the torrent files as folders/symlinks in another location. You can then manually rename / move the links in the place of your choice - the original data remained untouched. This script allows you to have your data scattered around several drives but still keep them all in the same folder somewhere.
Save it in your torrent download root as "symlinks.py". Place yourelf into it in command line, then by doing the following command, you mirror everything in the folder to another location - great as the first step:
In regards to "doing so much work for nothing", I would highly recommend you take another look at filebot. It takes maybe 2hrs to set up the AMC script but then it AUTOMATES everything, I hardly see that as hard work.
ok kool guys yes i know i am a twat that did this!
just trying to install filebot and java to run as a tv show rename and i googled my but off
and tried what i have googled and that's where i came un stuck only really know windows