Page 1 of 1
TV Series Cosmos.1980 unexpected Mismatch
Posted: 22 Dec 2020, 01:16
by cheaters
Odd mismatch when using
fn:amc and defining a
seriesFormat.
Using strict mode in the GUI did initially pull up a window to choose the series, but upon attempting it a second there is no renaming activity at all. After that the only way is to move into opportunistic mode where the top hit is the correct series.
Is there anything I could have done here to increase accuracy. This is pretty far off.
Code: Select all
[2020-12-21 18:57:59.656] Using persistent disk cache: /Users/john/.filebot/cache/0
[2020-12-21 18:58:00.923] Run script [fn:amc] at [Mon Dec 21 18:58:00 CST 2020]
[2020-12-21 18:58:00.949] Parameter: excludeList = /Users/John/.filebot/amc.excludes
[2020-12-21 18:58:00.949] Parameter: unsorted = y
[2020-12-21 18:58:00.950] Parameter: skipExtract = y
[2020-12-21 18:58:00.950] Parameter: seriesFormat = {plex.derive{' {thetvdb-'}{id}{'}'}{' - ['+allOf{tags}{vf}{vs}{crc32}.join(' ')}{']'}}{if (dc > 1) '.'+di}
[2020-12-21 18:58:00.950] Parameter: movieFormat = {plex.derive{' {imdb-'}{imdbid}{'}'}{' ['+allOf{tags}{audio.language}{info:video[0].displayAspectRatioString.colon('∶').replace('?', '')}{ws}{vf}{vs}{vc}{crc32}.join(' ')}{']'}}{if (dc > 1) '.'+di}
[2020-12-21 18:58:00.951] Parameter: ut_dir = /Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell
[2020-12-21 18:58:00.951] Parameter: ut_kind = multi
[2020-12-21 18:58:00.951] Parameter: ut_title = Cosmos.1980.04of13.Heaven.and.Hell
[2020-12-21 18:58:00.951] Parameter: ut_label = TV Shows
[2020-12-21 18:58:01.428] Use excludes: /Users/John/.filebot/amc.excludes (2496)
[2020-12-21 18:58:01.534] Input: /Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell
[2020-12-21 18:58:01.541] Process as TV Series [TV Shows]
[2020-12-21 18:58:01.543] Group: {Series=true} => [Cosmos.1980.04of13.Heaven.and.Hell]
[2020-12-21 18:58:01.570] Rename episodes using [TheTVDB] with [Airdate]
[2020-12-21 18:58:02.874] Lookup via [Cosmos 1980]
[2020-12-21 18:58:03.068] Fetching episode data for [Space: 1999]
[2020-12-21 18:58:03.550] [DUPLICATE] from [/Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell] to [/Volumes/PlexMedia/PlexServer_1/TV Shows/Space - 1999/Season 01/Space - 1999 - S01E19 - Ring Around the Moon {thetvdb-76366} - [1080p BluRay 2FA36770].mkv]
[2020-12-21 18:58:07.311] Processed 1 file
[2020-12-21 18:58:08.484] Done ヾ(＠⌒ー⌒＠)ノ
Re: TV Series Cosmos.1980 unexpected Mismatch
Posted: 22 Dec 2020, 04:17
by rednoah
If you have a fairly good idea what kind of shows you're going to process, then the
--filter option might be able to pass in a few hints to force the correct match:
viewtopic.php?t=2127
I do seem to be getting better results out-of-the-box though:
Code: Select all
filebot -rename *.mkv --db TheTVDB -non-strict --action TEST --log INFO
[TEST] from [Cosmos.1980.04of13.Heaven.and.Hell.mkv] to [Cosmos - 1x04 - Heaven and Hell.mkv]
Perhaps it's because I'm using the latest revision. Perhaps because I'm testing with a new clean file structure, no xattr, nfo files, etc. Perhaps something else entirely. Maybe you can do some trial and error testing to see what works and what doesn't.
Re: TV Series Cosmos.1980 unexpected Mismatch
Posted: 22 Dec 2020, 21:50
by cheaters
rednoah wrote: ↑22 Dec 2020, 04:17
Perhaps it's because I'm using the latest revision. Perhaps because I'm testing with a new clean file structure, no xattr, nfo files, etc. Perhaps something else entirely. Maybe you can do some trial and error testing to see what works and what doesn't.
Thank you.
Sorry, I don't understand what your CLI commands do, how they work, or what they prove
The filter idea really won't work in this situation, once and done.
File structure issues... these were single movie files with no cruft. I recently cleared cache before handling these files. Would that make a difference?
The amc script is calculating the crc32 and adding it to the original (seeding) file's xattr. Is the amc script supposed to be writing to the original file?
Below is the complete xattr of the original 13 files:
Code: Select all
$ find . -type f -iname "cosmos.1980*" | while read -r file; do xattr -l "$file"; done
CRC32: 72133166
CRC32: F60B9250
CRC32: AE69ECBC
CRC32: 2FA36770
CRC32: 21A26637
CRC32: 2BD25E52
CRC32: 40E05992
CRC32: 6AF33356
CRC32: 8BA2577F
CRC32: 78B982CF
CRC32: E9CD564E
CRC32: 376B6972
CRC32: 080BE61B
com.apple.lastuseddate#PS:
00000000 0F A8 E1 5F 00 00 00 00 D9 90 23 01 00 00 00 00 |..._......#.....|
00000010
Re: TV Series Cosmos.1980 unexpected Mismatch
Posted: 23 Dec 2020, 02:16
by rednoah
1.
jprokos wrote: ↑22 Dec 2020, 21:50
Sorry, I don't understand what your CLI commands do, how they work, or what they prove.
The command above shows that FileBot can rename the given file out-of-the-box, at least in my test case. Your response should be running the exact same command on the exact same file, to confirm that you indeed get different results. The next step is to then systematically narrow down what's different between our respective test cases and test environments.
2.
The
amc script does not add CRC32 xattr by default. However, if you are using a custom format that uses the
{crc32} binding, then that binding will store the computed value as xattr the first time around for next time around.
Note that reading / writing / deleting xattr does not change the file content:
https://www.filebot.net/help/xattr.html
Re: TV Series Cosmos.1980 unexpected Mismatch
Posted: 23 Dec 2020, 21:56
by cheaters
rednoah wrote: ↑23 Dec 2020, 02:16
jprokos wrote: ↑22 Dec 2020, 21:50
Sorry, I don't understand what your CLI commands do, how they work, or what they prove.
The command above shows that FileBot can rename the given file out-of-the-box, at least in my test case. Your response should be running the exact same command on the exact same file, to confirm that you indeed get different results. The next step is to then systematically narrow down what's different between our respective test cases and test environments.
Ahh! Thanks for the clarification.
Code: Select all
$ filebot -rename /Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell --db TheTVDB -non-strict --action TEST --log INFO
[2020-12-23 15:49:21.889] Using persistent disk cache: /Users/john/.filebot/cache/0
[2020-12-23 15:49:28.469] [TEST] from [/Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell] to [/Volumes/SeedDrive/complete/Space 1999 - 1x19 - Ring Around the Moon.mkv]
Removed
-non-strict to test
Code: Select all
$ filebot -rename /Volumes/SeedDrive/complete/Cosmos.1980.04of13.Heaven.and.Hell.1080p.Bluray.x265.AAC.MVGroup.org.mkv --db TheTVDB --action TEST --log INFO
[2020-12-23 15:57:51.980] Using persistent disk cache: /Users/john/.filebot/cache/0
[2020-12-23 15:57:54.016] Failed to identify or process any files
Could be a cache issue? However, I recently cleared caches for another issue.
I was told that this shouldn't be done regularly.
I don't know of tools to check this but poking around in the cache folder with a text editor I noticed something - "Space 1999" comes after the listing for "Cosmos" in
/Users/john/.filebot/cache/0/thetvdb_en_1c.data
Is it possible this data file wasn't created properly and there are malformed data separators?
Is there a way to check?
Re: TV Series Cosmos.1980 unexpected Mismatch
Posted: 24 Dec 2020, 05:39
by rednoah
1.
First we make sure that the problem is with FileBot, and not this specific file or folder, with a new clean file and folder structure:
Code: Select all
mkdir /Users/John/FileBot
cd /Users/John/FileBot
touch Cosmos.1980.04of13.Heaven.and.Hell.1080p.Bluray.x265.AAC.MVGroup.org.mkv
filebot -rename *.mkv --db TheTVDB -non-strict --action TEST --log INFO
[TEST] from [FileBot/Cosmos.1980.04of13.Heaven.and.Hell.1080p.Bluray.x265.AAC.MVGroup.org.mkv] to [FileBot/Cosmos - 1x04 - Heaven and Hell.mkv]
If the problem persists with a clean test case, then the next step is to upgrade FileBot, so that you're running the same revision that I'm running, and repeat the test case above:
viewtopic.php?t=1609
We know that it doesn't work for you. We know that it works for me. We just need to eliminated all the differences step by step. And when we find the step that makes it work / not work, then we have a clue as to what the underlying issue might be.
Use
filebot -script fn:sysinfo to confirm that you're running the revision of FileBot that you think you're running.
2.
jprokos wrote: ↑23 Dec 2020, 21:56
However, I recently cleared caches for another issue.
Since you've already cleared the cache and confirmed that it doesn't make a difference, we can assume that caching is likely unrelated to the problem at hand.