Running autotag always results in "No files found" since updating to v3.5.3 about autotag

[jamerst]

I'm looking into a fix for this, but it looks like the cause is the order of the arguments.

If you put the paths before the options, it should work.

This isn't intended, so I'll see if I can fix it, but that's a workaround in the meantime.

[jamerst]

After some investigation, this appears to be related to an issue with the command line library AutoTag uses (dotnet/command-line-api#2210). It is related specifically to the nullable boolean options (--apple-tagging in your case) capturing the token after the option when it shouldn't.

Unfortunately I haven't been able to update the library version to include this fix because the version on nuget.org is over a year old, and there are significant API changes which have not yet been documented. I have been unable to migrate to the new version due to the complete lack of documentation. I've raised an issue regarding this (dotnet/command-line-api#2231) and I'll keep an eye on the library for any documentation improvements.

Workaround

I don't think I can fix this in AutoTag itself without breaking #16 again, so for now you'll just have to use the workaround of putting any of the nullable boolean arguments at the end. For your case you should run autotag --tv --tv-pattern "%1 S%2:00E%3:00 %4" show_name.s02e01.720p.mp4 --apple-tagging.

You can also use the config file to set the options instead of passing them on the command line as a workaround.

The affected arguments which need to be put at the end are:

• --verbose
• --no-rename
• --windows-safe
• --rename-subs
• --no-tag
• --no-cover
• --manual
• --extended-tagging
• --apple-tagging