fpcalc results should be cached preventing regeneration

All your suggestions, requests and ideas for future development
Post Reply
sbarnea
Posts: 16
Joined: 04 May 2014, 21:06

fpcalc results should be cached preventing regeneration

Post by sbarnea »

Fpcalc results should be cached preventing regeneration if the file was not changed.

That's a essential requirement for using it in a media center where you use symlinks to generate the the browsable directory structure.

Without this feature the processing would take hours and hours.
User avatar
rednoah
The Source
Posts: 23004
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: fpcalc results should be cached preventing regeneration

Post by rednoah »

filebot shouldn't be run on files you have already processed in the first place

:!: You're wasting the free AcoustID webservices unnecessarily!!! :evil:

EDIT: FileBot imposes a 3 requests / second flood limit on AcoustID usage. So this is the bottle neck, not the fpcalc call. And the requests are already cached 2 days / 20k items max. I guess I can increase that.

EDIT2: With FileBot r2266+ caches for AcoustID webservices are now set to 2 months / 200k items
:idea: Please read the FAQ and How to Request Help.
Post Reply