Optimizations for Remote File Systems

How-to guides, frequently asked questions, not-so-obvious features, etc
Post Reply
User avatar
rednoah
The Source
Posts: 19141
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Optimizations for Remote File Systems

Post by rednoah »

1.
rednoah wrote: 05 Nov 2016, 14:58 FileBot uses MediaInfo Image to read properties like {vc}, {ac}, {channels}, {resolution}, etc from the container file.
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
Disable media parser permanently via the net.filebot.media.parser system property:

Code: Select all

filebot -script fn:properties --def net.filebot.media.parser=none



2.
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.
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.

Disable xattr per call via the -no-xattr command-line flag:

Code: Select all

-no-xattr
Enable xattr via .xattr folders:

Code: Select all

filebot -script fn:properties --def net.filebot.xattr.store=.xattr
:idea: Please read the FAQ and How to Request Help.
Post Reply