Thank you very much! It's just the cache problem. $ filebot -list --q 76806 --filter 's==1 && e>375' Apply filter [s==1 && e>375] on [730] options Include [Tales of Demons and Gods - 1x376 - Episode 376] Include [Tales of Demons and Gods - 1x377 - Episode 377] Include [Tales of Demons and Gods ...

rednoah wrote: ↑19 Jul 2025, 14:42 https://www.themoviedb.org/tv/76806/season/8

Not season 8.
I mean season 1.
https://www.themoviedb.org/tv/76806/season/1

For the tv series with TMDB id 76806 https://www.themoviedb.org/tv/76806/season/1 The original number of episodes was 380. I added new episodes two days ago. See the following screen shot. https://img1.pixhost.to/images/7330/623580055_2025-07-19_22-11.png However, when I list episodes using filebot ...

I use the official container rednoad/filebot:xpra.

I have known that the gui uses -rename not the amc script. So I just need to use -rename in command line.

When processing a .iso file, filebot says that file does not exist. But in the gui mode it can process the file correctly. What's wrong? Run script [fn:amc] at [Fri Mar 21 04:34:59 CST 2025] Parameter: excludeList = /data/exclude.txt Parameter: movieDB = TheMovieDB Parameter: seriesDB = TheMovieDB ...

The system usually freezes when FileBot is matching metadata or loading filters (in the GUI). However, I later discovered through iotop that the package version of Emby was also performing a large amount of I/O operations at the same time. I suspect this is because I had added a large amount of data ...

I am using the Docker version of FileBot on my Synology DS218+. Regardless of whether it's the XPRA or VNC GUI version, it frequently causes excessive I/O usage when processing files. Checking with uptime command in the Synology command line shows that the I/O load can exceed 100. At this point, the ...

Thank you, it works!

In my filebot amc script, I have specified two media servers, jellyfin and emby. But in the output there is only the push command for jellyfin, not for emby. And I can see that the jellyfin has been updated but the emby has not. Is this a bug? ... --def jellyfin=172.17.0.1:10008 ...

Thank you very much! This method can solve my problem. $ filebot -rename *.mp4 --output . --format "{plex.id}" --db TheMovieDB::TV -non-strict --q 107371 --filter "e > 106" --mapper "episode.derive(1, e - 106)" --action TEST --log INFO [TEST] from [[一念永恒第三季].A.Will.Eternal.S03E38.2024.1080p.WEB-DL.H2 ...

Thanks for your reply! :idea: In this case I'd use the Linear Rename approach: $ filebot -list --q 107371 --db TheMovieDB::TV --format "{plex.id}" --filter "e >= 144" -rename *.mp4 --log INFO [MOVE] from [[一念永恒第三季].A.Will.Eternal.S03E38.2024.1080p.WEB-DL.H264.AAC-OurTV.mp4] to [TV Shows/A Will Eterna ...

Input episodes: S03E38 - S03E40 Output episodes: S01E38-S01E40 Output I want: S01E144 - S01E146 The two episodes S03E38 and S03E39 were manually renamed by me. The S03E40 is an episode newly added. How can I do this using --mapper ? My command is filebot -script fn:amc --lang=Chinese -non-strict ...

--q ID is just what I want!
Thank you very much!

By the way, in my case I use symlink instead of hardlink.

I hope that user-specified matching rules can be supported. For some anime series, the naming conventions for different seasons can be inconsistent. Episodes in each season may be numbered separately starting from 01, or all seasons' episodes may be numbered continuously from 01 without resetting ...

When dealing with directories of certain TV series where the naming conventions are non-standard, it becomes challenging to modify filenames due to requirements like seeding in private trackers (PT). Consequently, using FileBot's automatic matching may result in incorrect episode associations. So, I ...