Was no problem at all -- the beta build you supplied tied me over until the official release was published. Again, thanks for your help.

Thanks -- I have installed FileBot_5.1.5_amd64.rpm and its running well.

Understood. Thanks for your help.

Completed some additional tests with FileBot 5.1.4 (r10364) and could not find any additional problems so for use cases this build is good. Thank you.

Out of curiosity, do you plan on re-releasing 5.1.4 with this updated version or will you just wait and re-spin calling it 5.1.5.

Thank you. I pulled the latest beta FileBot 5.1.4 (r10364) and the issue is now fixed with your latest update. Its getting late here now so I'll run some additional tests tomorrow with this version but so far it seems okay including the gnome app icon.

I'm not seeing that file at all ... [plex]-[dokuro]:/data/Personal/Scripts$ ls -l /share/icons/hicolor/scalable/apps/filebot.svg ls: cannot access '/share/icons/hicolor/scalable/apps/filebot.svg': No such file or directory [plex]-[dokuro]:/data/Personal/Scripts$ Unfortunately https://get.filebot.net...

Alas /usr/bin/filebot already has ... [plex]-[dokuro]:/data/Personal/Scripts$ ls -la /usr/bin/filebot lrwxrwxrwx 1 root root 33 Jul 29 17:33 /usr/bin/filebot -> /usr/share/filebot/bin/filebot.sh [plex]-[dokuro]:/data/Personal/Scripts$ ... so it won't work. For the moment I'll just stick with 5.1.3 u...

I upgraded to FileBot 5.1.4 today and afterwards filebot would not start with an access denied error. [plex]-[dokuro]:/data/Personal/Scripts$ filebot bash: /usr/bin/filebot: Permission denied [plex]-[dokuro]:/data/Personal/Scripts$ Checking /usr/share/filebot/bin/filebot.sh ... [plex]-[dokuro]:/data...

Yeap, we are saying the same thing. Thanks as always for your help.

BTW... just so you are aware in case you are not. The year is used as a hint in matching with plex, its not a requirement for plex naming standards. Using the matching id from either tmdb or imdb is a MUCH better way of matching with plex making the year obsolete.

Thanks for confirming, had a feeling that was the case but wanted to be sure I was not missing something. Thanks again.

I'm currently using ... { ~plex.unix * {" {tmdb-$id}"} % {" [$vf $vcf]"} } ... as my movie filebot naming. This gives me ... \Avatar (2009) {tmdb-19995}\Avatar (2009) [1080p HEVC].mp4 \Avatar (2009) {tmdb-19995}\Avatar (2009) [1080p HEVC].eng.forced.srt However, I'd like to see i...

Okay, bingo! I had `FileBot_5.1.1_amd64.deb` so I went and grabbed beta `FileBot_5.1.2_amd64.deb` from 10th Oct and ... filebot -mediainfo -r "/data/MediaServer/8a-TV/Anime" --file-filter 'f.video' --filter 'episode && none{ episode as String == episodelist.find{ it.episode == epis...

Here you go... (they look identical to me): plex@dokuro:/data/Personal/Scripts$ filebot -mediainfo -r '/data/MediaServer/8a-TV/Anime' --filter 'f.video' --format '{f}' | grep tmdb-78204 /data/MediaServer/8a-TV/Anime/Sword Art Online Alternative: Gun Gale Online (2018) {tmdb-78204}/Season 01/Sword Ar...

I failed to test the miss script myself for changed specials and you are correct, it does indeed detect changes so I'm all good with this. Thanks. I am however still at a loss why find-episode-metadata-changes.sh does not work when using a higher level folder path. So, for example: sh find-episode-m...

Unfortunately as discussed in this first part of this comment viewtopic.php?p=61035#p61035 it does not work unless I run it on individual shows themselves rather than root directory. I guess I could script it to run on each show but the miss script runs better.

I understand this is very much an edge case but could a flag be added or is there a way to run filebot -script fn:miss /path/to/media so that it will include specials ? I'm pretty sure we don't want this by default but it would be nice if someone wanted to find missing specials that they could. BTW....

Your response has confirmed what I suspected. I think I'll just go with {vcf} over {vc} as that will give me consistent format in the naming of my media and will always find standard used. Thanks again for your help.

Here you go: Castle in the Sky (1986) {tmdb-10515}/Castle in the Sky (1986) [1080p AVC].mp4 # /data/MediaServer/14a-Movies/Animated/Castle in the Sky (1986) {tmdb-10515}/Castle in the Sky (1986) [1080p AVC].mp4 General #0 Count : 348 StreamCount : 1 StreamKind : General StreamKind/String : General S...

For context, here is the renaming syntax I'm using for my movies { ~plex.unix * {" {tmdb-$id}"} % {" [$vf $vc]"} } . Sometimes however the $vc part of this syntax will report AVC and other times x264. Two examples below: Justice League: Warworld (2023) {tmdb-1003581}/Justice Leag...

Very good. Thank you again. This worked perfectly.

Quick question. I've enabled extended attributes via filebot -script fn:properties --def net.filebot.xattr.store=.xattr and am wondering what would be the best way to validate if extended attributes actually exist ? I was initially thinking something like find <path to tv shows> -mindepth 3 -maxdept...

Thank you again. The updated movie syntax to include -file-filter "f.video" --filter "movie && none has returned the expected results. Much appreciated. However, I'm not having much luck testing the episodes one. When I run (which is directed at the show level directory) fileb...

Not sure what to say regarding the clear cache but my experience in the past week is that when TMDB changed the titles for these two episodes https://www.themoviedb.org/tv/114461-ahsoka/season/1/episode/4 and https://www.themoviedb.org/tv/693-desperate-housewives/season/6/episode/13 that the miss sc...

I had a look at the update to the miss script topic where you added This script additionally checks for changes in metadata where previously stored xattr metadata does not exactly match current online episode metadata. (e.g. find files where the episode title was changed in the online database) and ...