e.g. custom --conflict action that prefers HEVC over AVC : --conflict /path/to/VideoCodecOrder.groovy { from, to -> def score = { f -> ['HEVC':20, 'AVC':10][f.mediaCharacteristics.videoCodec] ?: 0 } score(from) > score(to) ? to : null } :idea: Note that this code only works for HEVC / AVC and any ot...

You'll probably want to run your own tests though.

Yes, the amc script will switch between TV mode and Anime mode automatically depending on the files at hand, by default, unless specified otherwise.

A. No, because --conflict auto only works with comparable (i.e. numbers) media properties, e.g. resolution, bitrate, file size, etc. B. Yes, because you can write your own Conflict Action and have your own custom code decide what to do about any given pair of files: https://www.filebot.net/forums/vi...

startDate is notably not the airdate of the first episode. startDate is a property of the series record, so it can be different from the airdate of the first episode, depending on what information TheTVDB staff has filled in. Looks like somebody has fixed the issue already, because I'm getting the ...

= is the assignment operator. This is completely wrong. Syntactically correct, but doesn't do what you think it does. == is the equals operator. Still wrong, because you're using a regex on the right-hand side. =~ is the regex-find operator. ==~ is the regex-match operator. Those make sense if you ...

https://discord.com/channels/2287231828 ... 3457718292


Fixed with FileBot r9700.

FileBot r9699 has been uploaded. The newly added debug logging might be helpful and explain the issue. Can you run tests with the latest revision please? https://get.filebot.net/filebot/BETA/ :idea: Make sure the use the *_universal.deb package. The *_amd64.deb package includes an embedded JDK 17 ru...

This message does indeed narrow it down an HTTP/2 issue somewhere: I will look into that method.

:?: Can you show us a screenshot of your use case? The Match button uses completely different algorithms now, which has pros and cons. The pro is that it's no longer limited to to matching exactly one item per file, the con is that it's no longer limited to matching exactly one item per file. https:...

Can you try again with these settings? filebot -script fn:properties --def net.filebot.logging.debug=ALL net.filebot.web.WebRequest.log.response=true net.filebot.web.WebRequest.v1=false :idea: There are known HTTP/2 issues on JDK11 and net.filebot.web.WebRequest.v1 forces HTTP/1 so this may be one p...

That's reasonable. Stripping away metadata like "Pa55ed thru XXXHub. L77t Gr88t5" makes perfect sense. :arrow: You can write new metadata via the tags script (make sure to read the docs thoroughly; make sure to run your own tests first) after you have processed the files with FileBot: filebot -scrip...

Sorry, I have no idea. I see that you've already enabled debug logging but no extra clues there. Getting different results is very mysterious, and shouldn't really be possible since it's the same code... Maybe TMDB is sending back invalid data sometimes? I'll see if I can add more debug logging. EDI...

How to use the {localize} dynamic localization binding?

How to use the {localize} dynamic localization binding?

How to use the {localize} dynamic localization binding?

How to use the {localize} dynamic localization binding?

UPDATE:

Invalid movie IDs in external NFO file may similarly break processing. FileBot r9689 fixes the issue on the movie side as well.

You have disabled the limits. This is not what you want: e.g. disable limits: filebot -script fn:properties --def net.filebot.media.clutter.size=0 net.filebot.media.clutter.length=PT0S :!: If limits are disabled, then FileBot will exclude all file paths that contain keywords such as Trailer , Sample...

:!: --def 'ut_label=Anime' and --order Absolute force the amc script to use Absolute Order to interpret your input files, and thus explicitly makes files not work for your normal TV series / SxE numbered input files. :arrow: If your files use S00E00 or SxE numbering, then your files are normal TV Sh...

I don't actually know how the JRE resolves host names. I'd assume that it's using the OS system services for DNS lookup. Using a custom local DNS server in the macOS settings might work, or manually adding IPs to /etc/hosts as you have already done.

:!: Note that this thread is for the amc script so all of the above is generally not applicable to the FileBot Desktop application. ---------------------------------------- :idea: You may be able to use Manual Matching to semi-manually process files that are ignored by auto-detection for one reason ...

:idea: Note that FileBot does not support IMDB. :idea: --filter is a Groovy expression that yields either true or false for a given Episode or Movie object. You generally cannot pass bash data structures, because bash will always "flatten" it into a String value since that's the only kind of value t...

You'll want to start rapid prototyping in the Format Editor and some test string / test file path: { 'TRUEFRENCH.MULTi.SUBFRENCH.CUSTOM.QC.'.matchAll(/(TRUEFRENCH)|[.](MULTi)[.]|(SUBFRENCH)|(CUSTOM)|[.](QC)[.]/) } [TRUEFRENCH, MULTi, SUBFRENCH, CUSTOM, QC] :arrow: You can then use f.path to access t...

FileBot will inherit your system settings by default. This should work for HTTP proxies at the very least. I don't know if the JRE supports socks5 proxies at all. Modifying the application bundle is definitely not supported though, since that will break code signatures, which in turn can lead to mac...