For one particular movie (Vivarium 2020), I'm getting this error when manually fetching artwork from the CLI. Command: filebot -script fn:artwork.tmdb ./ I'm running that from within the directory holding the video file. It outputs: Volumes/Super Storage/Video/Movies/Vivarium (2020) => Vivarium (202...

Got it. I didn't realize I needed single tickets around the format.

I've always had quotes around it and now see the error in my ways.

I've started using Radarr and thus need the file's quality in the filename so this stupid program knows it's downloaded something already. I'm trying: {plex.derive{" [$vf, $vc, $ac]"}} But my .workflow (I'm using this as a service) gets an error: The action “Run Shell Script” encountered an error: “...

All good now, thanks for the help.

My 4k movies are going to the right place with the right formatting and artwork. My other movies and TV shows are going to the right place for Handbrake to process them to change their container and reduce filesize.

Thanks again for the help!

Thanks. I think I've got something that's working now.

Now to download my first 4k movie and see if this all works (or test from command line if it doesn't!)

Okay, if I switch to -script fn:amc, I get the right Plex structure.

But my 4k movie is moving into the regular Movies folder, so I think I need to rename that test file so Filebot knows it's 4k. Or maybe my if else isn't working right. I'll keep poking at it.

Console shows success, it moved the file, just not to the right location: [email protected] Video % /usr/local/bin/filebot -rename Avengers\ Endgame\ \(2019\) --output "/Volumes/Super Storage/Video/To Be Processed" --action move --conflict skip -non-strict --log-file amc.log --def "movieFormat=Movie...

I must be some kind of moron, because that's not working for me, either. I tried: /usr/local/bin/filebot -rename Avengers\ Endgame\ \(2019\) --output "/Volumes/Super Storage/Video/To Be Processed" --action move --conflict skip -non-strict --log-file amc.log --def "movieFormat={fn =~ /2160p|4K|4k|UHD...

I'm not quite there. This script is working to sort the movies into either Movies or Movies 4k depending on their quality, but: It's not putting them into their own folders like my original script did, which I need to make Plex happy. I've been mucking with it today trying to get it to move the file...

I think I've got it. I found a post on Reddit where someone was trying to do something similar, but without the Transmission tagging bit. I changed my postprocess.sh script to: #!/bin/sh -xu # Input Parameters ARG_PATH="$TR_TORRENT_DIR/$TR_TORRENT_NAME" ARG_NAME="$TR_TORRENT_NAME" ARG_LABEL="N/A" # ...

I'm running the AMC postprocess when a torrent finishes in Transmission and it's working perfectly, but I want to make a change. Here's my current working script: #!/bin/sh -xu # Input Parameters ARG_PATH="$TR_TORRENT_DIR/$TR_TORRENT_NAME" ARG_NAME="$TR_TORRENT_NAME" ARG_LABEL="N/A" # Configuration ...

Weird, it just started working on its own when I ran it again from the CLI.

Must have been something up at TVDb's end in the API.

I've been running an amc script for years at this point and it's always worked flawlessly. Last night, I noticed a few new shows I'd downloaded didn't have artwork in Plex, so I set out to manually update them this morning. When I run the script to fetch artwork, Filebot just comes back as done, but...

Yeah, that’s the error. I’ve tried everything I can think of and can’t fix it. My $HOME is set properly in my bash profile. Should it be set somewhere else, for Hazel to see it? The only thing I didn’t try was changing /bin/bash in the Hazel script editor. I’ll try that when I get to my desk. Maybe ...

Another post has this same error, and it's suggested that $HOME may be set wrong.

My $HOME path is set to , which is my user profile and seems correct to me.

I've got most of my automation working perfectly, except one thing. Once AMC does its thing, Hazel sees a new .mp4 in a directory and moves it to its final home, where Plex sees it. Once there, Hazel should also see there's a new directory and run a simple bash script of filebot -script fn:artwork.t...

Fixed it.

I must not have fully uninstalled Java11.

For anyone else having the issue on MacOS, go to /Library/Java/JavaVirtualMachines and delete Java11 from there, which should force you back down to Java10 and life will go back to normal.

I ran a brew update the other day to update some of my packages, and something that updated caused my Filebot automation to break. I'm running a postprocess.sh script from Transmission: /usr/local/bin/filebot -script fn:amc --output "$CONFIG_OUTPUT" --action move --conflict skip -non-strict --log-fi...

Ok, I’ll try finding some steps to update the jar manually and hope that fixes things.

Thanks for the help.

Is there a plan to update brew with the fix?

I think the FileBot jar change you mentioned is over my head, unless there’s a guide somewhere I can at least try following.

I'm running Mac OS and seeing the zero bytes issue a few other folks are, so I'm trying to upgrade. I run brew update && brew upgrade && brew cask install filebot --force --appdir=~/Applications and it completes, but I'm still running 4.7.9 and not 4.7.13, like the troubleshooting guide recommends. ...

I am now successful at getting it to run reliably, just had to get the right output path. Now I just need to set myself a weekly reminder to go clean out the completed torrents directory (since clean=y will only delete empty directories and a bunch of essentially junk gets left behind once the origi...

I'll check out the presets and muck with the automation some more. I did get the automation to work on my Desktop with some files, so I think it's just my output path. One question for clarification; the script should only run against a torrent file once, right? I think I'm confusing myself because ...

I'm not sure how it's interpreted. I tried a number of things until I got it to work. Then, for whatever reason, it stopped working. I don't know what I changed to make it stop working, but I can't get it working again. I'll go back to the UI and do this the old fashioned way. I can't get the script...

I think I found it.

Trying in my script now.