FileBot does parse file headers to read embedded media properties. This will be relatively fast since MediaInfo will only read the first few megabytes of each file, but if File I/O is expensive, then you'll want to configure FileBot to not parse embedded media properties at all.
Disable media parser per call via the -no-probe command-line flag:
Code: Select all
-no-probe
Code: Select all
filebot -script fn:properties --def net.filebot.media.parser=none
2.
Remote file systems typically do not support Extended Attributes so you'll want to configure FileBot to store metadata into a .xattr folder / plain file structure.rednoah wrote: ↑24 Oct 2012, 11:16 FileBot uses xattr (i.e. Extended Attributes / NTFS Alternative Streams) to store full metadata in filesystem attributes. These xattr are not to be confused with traditional tags that are embedded in the file content, but additional data streams stored in the file system for each file that are not part of the file itself. As such, xattr requires a filesystem that supports xattr, and xattr may be silently lost if files are moved to a filesystem that doesn't support xattr.
Disable xattr per call via the -no-xattr command-line flag:
Code: Select all
-no-xattr
Code: Select all
filebot -script fn:properties --def net.filebot.xattr.store=.xattr
3.
The FileBot Desktop application for Windows will integrate with the Windows Desktop by default. Disabling Windows Desktop integration may (or may not) speed up file system operations.
Disable Windows File Operation integration permanently via the useNativeShell system property:
Code: Select all
filebot -script fn:properties --def useNativeShell=false
Code: Select all
filebot -script fn:properties --def net.filebot.UserFiles.trash=Delete