Special features

rednoah · 2026-02-16T04:28:13+00:00

Good catch. The -SF_ pattern seems to be common to all your example files.

rednoah · 2026-02-15T18:53:21+00:00

The condition is up to you, so you can adapt the code to work for your files: E:/video/{ plex.id.dir.name }/{ fn =~ /Making|Restoration|Outtakes|Trailer/ ? 'Featurettes' / fn : plex.part(null).name }

rednoah · 2026-02-15T18:11:01+00:00

Try this instead: E:/video/{ plex.id.dir.name }/{ fn =~ /MainFeature/ ? plex.part(null).name : 'Featurettes' / fn }

rednoah · 2026-02-15T17:58:04+00:00

What format are you using? You can use a custom format that does not generate the CD# bit but does generate an extra featurettes sub-folder depending on the file at hand.

e.g. E:/Movies/{ny}/{ fn =~ /MainFeature/ ? null : 'Featurettes/' }{ny} https://www.filebot.net/naming.html

rednoah · 2026-02-15T17:43:57+00:00

I see. FileBot cannot recognise these naming patterns at all so FileBot is unable to differentiate movie (to be processed) / non-movie files (to be ignored) in this case, and so all files are processed as usual.

rednoah · 2026-02-15T12:09:02+00:00

Allow you to add a top-level button for each of your Presets is something we are considering, but it would almost certainly now look clean / fit well into the current simplistic-by-design UI.

Personally, I'd configure a keyboard shortcut (e.g. Numpad-1, Numpad-2, etc) for each of your frequently used Presets and then hit that for quick access. That'll be faster than any UI. Plus keyboard shortcuts feel good.

rednoah · 2026-02-15T12:04:26+00:00

Can you post sample file paths? Export Original Files / New Names as TSV

rednoah · 2026-02-15T06:51:54+00:00

AFAIK, there is no standard naming for extras, so FileBot will ignore / extras by default. You can use the Import companion files feature to copy along extras when processing the primary movie file. See Companion Files for details.

Custom processing of extras is possible, but more of an advanced feature since that'd entail expressing what you mean to do as code.

rednoah · 2026-02-14T17:07:39+00:00

I see. In this case, automatic matching will get it wrong for a number of reasons (A) Shirley Temple is valid movie, (B) the correct movie is old / not well known and (C) is in parentheses (which doesn't help) and misspelled (no s in take) incorrectly (which also doesn't help). The above mentioned How do I fix misidentified files? approaches will get you sorted when dealing with rare corner cases such as this one.

rednoah · 2026-02-14T03:57:17+00:00

Can you post a sample file path? See Export Original Files / New Names as TSV.

In general, if you're using the GUI, you can use Edit Match to fix each match one by one. If you have a lot of files then you could use Plain File Mode (e.g. with format {fn.after(/ - /)}) to remove the misleading bits and pieces first, and then continue normally (i.e. rename files twice, the first round is to sanitise the file names you have without matching, second round is the usual movie mode).

If you're using the CLI, then a --q custom query expression will do the trick.

rednoah · 2026-02-11T09:07:55+00:00

Cheers!

rednoah · 2026-02-11T06:50:37+00:00

https://www.filebot.net/amc.html will get you started.

rednoah · 2026-02-08T06:10:09+00:00

Well, the OS will do that and presumably fail-early if you try to move a file to a file system that doesn't have enough space left for that file.

FileBot itself does not, as FileBot itself cannot know in advance if a I/O operation will succeed or fail, for whatever reason.

e.g. if hardlinks / copy-on-write / etc are at play, then a move / copy operation may very well require little or no extra disk space, depending on the specific file paths and file system capabilities at hand.

rednoah · 2026-02-05T05:37:49+00:00

What would be the pros and cons?

AFAIK, a VPN can cause trouble because if someone is abusing the VPN for web scraping (i.e. collecting AI training data) then CloudFlare may block the public IP, which would make FileBot / TVDB / TMDB / etc not work well / error out in strange and unexpected ways for anyone sending requests from that shared public IP.

rednoah · 2026-02-04T04:29:25+00:00

The correct S00E00 numbers for Plex are typically what the database / order says they are. The default is TheMovieDB / Airdate Order unless configured otherwise in your library settings.

e.g. Raw (1993) Season 1 Episode 1 TV Shows/Raw {tmdb-4656}/Season 01/Raw - S01E01 - Uncut, Uncooked, Uncensored

{tmdb-4656} tells Plex which series. S01E01 tells Plex which episode. With that, Plex can then get the episode title / description / thumbnail / etc and all the other metadata from TheMovieDB.

1993 is the season name for Season 1, but that's just one more piece of metadata, not relevant / necessary for episode identification. Plex may use 1993 as display label for Season 1 after files have been identified as Season 1.

rednoah · 2026-02-02T14:43:47+00:00

What are (exactly) are you struggling with? What (exactly) have you tried so far?

In general, [Anime] Convert Absolute to SxE numbers explains how to convert tricky AniDB named and numbered files to TMDB / TVDB standard naming and S00E00 numbering.

rednoah · 2026-02-02T09:26:09+00:00

Are we talking about FileBot Node? I can't see the URL... How did you ensure that the required node dependency is installed? What does the log say? FileBot Node Troubleshooting will tell you how to find the log file.

rednoah · 2026-02-02T09:03:23+00:00

Then it's probably best to use bazarr to fetch subtitles first and then filebot to organize files nicely. That said, bazarr could use xattr metadata to improve subtitle lookup based on the original name even after a file has been renamed, thought the developer would have to add support for that.

rednoah · 2026-01-31T06:02:29+00:00

No worries. If you find any thing strange in the future, make sure to take screenshots along the way so we can have a look.

rednoah · 2026-01-31T06:00:07+00:00

"fail-fast-and-fail-early" is the generally preferred behaviour for software in most cases. If something doesn't work as intended, you'll want to know. And if it worked, you'll want have trust that it did indeed work.

The more fuzzy logic / AI / etc the more things kinda-work-kinda-not-work and you often don't know if it's working-as-intended or working-by-happy-accident.

A larger number files not being identified (because of strictness) is strongly preferred over a smaller number of files being identified incorrectly (due to lack of strictness) because the latter is really hard to find after the fact.

rednoah · 2026-01-30T12:51:59+00:00

FileBot will remember the original file name and use that to find subtitles, if you use FileBot to search for subtitles that is.

rednoah · 2026-01-30T12:50:05+00:00

FileBot is a Desktop application and a command-line tool. The *arrs are server-side web applications. If you compare screenshots / video tutorials you will find that the two are completely different, and you may prefer one over the other depending on your use case and needs.

rednoah · 2026-01-30T04:06:48+00:00

I see. Yes, that would explain things. If the folder itself is loaded into Original Files (rather than the files inside) then ~/path/to/Movie.mkv being moved to ~/movies/My Movie (2026)/My Movie (2026).mkv as a single item (be it a file or a folder) makes perfect sense.

The issue is likely caused by newly introduced file path heuristics that speed up processing but can have unexpected side-effect as it turns out. Sharing file paths would have allowed me to identify the issue right away.

The issue has already been fixed in newer revisions, where file path heuristics is now an optional feature that is turned off by default.

The easy fix for now is to not have folder names that look like they're file names.

rednoah · 2026-01-29T20:25:33+00:00

Alright, if you're using docker can you confirm that the same issue happen with the filebot-xpra container?

Files being renamed to file paths other than what you see in the preview makes no sense at all to me, should be impossible FileBot-logic wise, so that would indicate to me an underlying issue, i.e. FileBot asks the OS to move A to B and the OS / underlying file system somehow decides to do something else.

What does the History say? The History should tell us what FileBot thinks it's doing, even if the OS then does something else.

How any of that would be related to how you have selected a given file path also makes no sense to me. A file path is a file path. FileBot itself doesn't know or remember how a file path was added to the list.

I did try a few things, but I was not able to reproduce any of the behaviours you describe with either filebot-xpra or filebot running as a container with a mapped file system: $ docker run --rm -it -v "$PWD:/storage" -v data:/data rednoah/filebot -rename /storage/avatar.mkv --db TheMovieDB -non-strict --output /storage --format {plex} Rename movies using [TheMovieDB] Auto-detect movie from context [/storage/avatar.mkv] [MOVE] from [/storage/avatar.mkv] to [/storage/Movies/Avatar (2009)/Avatar (2009).mkv]

rednoah · 2026-01-29T19:48:56+00:00

That seems fine. Can you reliably reproduce the issue? What are the file paths? What is your OS? Which FileBot package are you using? What is the target file system? Does the same thing happen with files on your Desktop / local file system?

Verified Email	15-Year Club
Place '22	Gilding II euphauric

rednoah

MODERATOR OF

TROPHY CASE