Docker - Renaming Issue

Any questions? Need some help?
Post Reply
Urlryn
Posts: 16
Joined: 18 Sep 2014, 22:29

Docker - Renaming Issue

Post by Urlryn » 08 Jul 2019, 01:34

Hey Red!

Been a long while since I posted! :)

Using Docker via Unraid.
Posted about this in the forum support there but they had recommended posting here. Well life got busy and I completely forgot about it and finally getting around to asking about it.

Ran into a strange issue using the [{crc32}] attribute during the matching/fetching process.
When you do the initial fetch it is only adding the brackets [] to the filename. Not the actual crc number inside of the brackets. Sometimes its all of the files in a series..sometimes its random ones.

I did figure out a workaround. Before you go and select rename....you can go to the edit format option. Then without changing anything just click "use format".
It updates the name correctly with the crc32 like its supposed to for all files.

I thought it might be a error in my format (due to upgrades or something)....so i deleted it and just used {n} [{crc32}] and got the same results as described above.

Thanks,
Urlryn

User avatar
rednoah
The Source
Posts: 16115
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Docker - Renaming Issue

Post by rednoah » 08 Jul 2019, 02:45

What does the log say?
viewtopic.php?f=5&t=1868

:idea: {crc32} can't not work. If there's no [00000000] pattern in the file name, and no nearby *.sfv file, then FileBot will compute the {crc32} from the file content itself. Assuming that FileBot has read-access, it can't not work, but it might take a long time reading the entire file to compute the crc32 checksum.

:!: If it indeed does not work, then it's an IO error preventing FileBot from reading the file content. That doesn't really happen for normal local files, but if network shares are involved, then things can get flaky.
:idea: Please read the FAQ and How to Request Help.

Post Reply