AMC: Subs for movies, not TV?

[Unsoluble]

Apologies if this is a FAQ; searching didn't turn anything up.

Any way to have the AMC grab subs for movies but not for TV?

Thanks!

[rednoah]

Sorry, not supported. The subtitles feature is either turned on or turned off.

[Unsoluble]

Gotcha. Thanks for clarifying!

[kim]

You can if you separate them like this:
put in one e.g. bat file

Code: Select all

filebot -script "amc.groovy" "D:\movies" --output "D:\Scaped" subtitles=en
filebot -script "amc.groovy" "D:\tv" --output "D:\Scaped"

[rednoah]

1.
This command doesn't make sense. Is it a -get-subtitles call or a -script call? It can only be one or another.


2.
The idea makes sense though. If you can make two different filebot calls for different kinds of input, then you can of course enable/disable subtitle support individually.

Personally, I'd run the suball script on a daily schedule, to fetch subtitles in a delayed manner, when they're more likely to be available. So you could schedule a daily suball run on your movie folder but not your TV folder.

[Unsoluble]

Oooo, I like the separate/scheduled suball idea. Thanks!

[kim]

Looks like you hard-coded strict mode ?

from AMC script:

Code: Select all

getMissingSubtitles(file: files, lang: languageCode, strict: true, output: 'srt', encoding: 'UTF-8', format: 'MATCH_VIDEO_ADD_LANGUAGE_TAG') ?: []

AMC = "Looking up subtitles by hash via OpenSubtitles" ONLY...
and NO... "Looking up subtitles by name via OpenSubtitles"

Why not make it so we can use strict/non-strict independent of the rename setting ?
(make the AMC able to do "Looking up subtitles by name via OpenSubtitles")

else why even have get subs build in the AMC (just call the suball) ?

also hard-coded "encoding: 'UTF-8'"
so when do " --encoding [UTF-8, Windows-1252] : Output character encoding" have any effect ?
(maybe update the info in the FileBot.cmd -help ?)
the "help" could really use an info update... that is more info would be nice... like some examples and what it can be used on / have any effect on

[rednoah]

1.
Yes, strict mode is hard coded in the amc script because no subtitles are better than good subtitles, plus non-strict search is a lot slower and and puts a lot more load on OSDB than simple hash lookups. The amc script subtitles support covers the single most common use case which covers the needs for most people. If you absolutely want subtitles, including bad ones, or delayed ones, then you should use the suball script on a schedule, where you can set all your preferences.


2.
filebot -help is only for filebot commands. Once you call a script, that script can do whatever it wants. The amc script is not a filebot command, so man filebot won't give you amc script options, just like man java will not give you filebot options.

[kim]

1.
"no subtitles are better than good subtitles" you mean
no subtitles are better than BAD subtitles ?

2.
I know "amc script is not a filebot command" and I'm on Windows so if "man" gives extra info then I can't see this ?
"encoding" is on this filebot command list so.... when do " --encoding [UTF-8, Windows-1252] : Output character encoding" have any effect ?
(when you hard-coded "encoding: 'UTF-8'" into getMissingSubtitles)

3.
It sounds like you can't see it from a noobs eyes, I don't think anyone new to filebot can use "help" on it's own and then know how to use it... now it's only for people who know and need to refresh memory

remember, the more info / examples you give in places like "help" = less work for you to e.g. answer the same thing again and again and again in forum...
and just maybe more people will know how to use it properly... there must be people who try filebot out, but think "I give op, this is to hard" and move on to another program

I have used filebot a long time now and there are still a lot I don't know...

[rednoah]

1.
Haha. Yes. BAD subtitles are the WORST.


2.
If you're using the amc script, then some options, such as --format or --encoding, have no effect. Not using UTF-8 for text files is a bad idea, so UTF-8 is forced by default.


4.
filebot -help is a reference for all the command-line options. Adding dozens of examples to man pages is not common practice. I could easily come up with 100 unique filebot command-line calls for various use cases, but that's not something that's supposed to be in a man page, which servers as quick reference what options there are, rather than what exactly each of them can do, in different circumstances, to accomplish different goals.

Examples for FileBot commands are here:
https://www.filebot.net/cli.html

More examples for usages you might not think of are here:
viewtopic.php?f=4&t=4788

The manual for the amc script is here:
https://www.filebot.net/amc.html

[kim]

2.
I still don't WHEN "encoding" has any effect ?

4.
Just add if each command can be used with script or not or something like that?

also add this to the bottom of help as text:

Examples for FileBot commands are here:
https://www.filebot.net/cli.html

More examples for usages you might not think of are here:
viewtopic.php?f=4&t=4788

The manual for the amc script is here:
https://www.filebot.net/amc.html

5.
a "[Windows] FileBot Command-Line Examples" would be nice

[rednoah]

2.
--encoding is used in -get-subtitles calls, and probably in -check calls as well when creating SFV files.

4.
All command-line options can be accessed by scripts, so any script may or may not use any of the standard command-line options.

5.
Most of them should be the same. There is no Windows equivalent for find and xargs, but you can always use Bash for Windows for those tasks.