Warning: 'End of processing at large atom (LargeFileSupport not enabled)' about exiftool-vendored.js

[medikoo]

After some fiddling, I've found that it works without any extra settings if .ExifTool_config with following content is placed at current working directory, large file support will be enbled

%Image::ExifTool::UserDefined::Options = (
    LargeFileSupport => 1,
);

Otherwise, as pointed in above comment, path to config file can be passed as first argument:

new ExifTool({
	exiftoolArgs: [
		"-config", path.resolve(os.homedir(), ".ExifTool_config"), "-u", "-stay_open", "True", "-@",
		"-"
	]
});

[mceachen]

When you build your instance of ExifTool, you can give it arguments. The default is ["-stay_open", "True", "-@", "-"]: you could try ["-api", "largefilesupport=1", "-stay_open", "True", "-@", "-"]:

import { DefaultExiftoolArgs, ExifTool } from "exiftool-vendored"

const et = new ExifTool({
  exiftoolArgs: ["-api", "largefilesupport=1", ...DefaultExiftoolArgs]
})

(please tell me if this works for you!)

[medikoo]

@mceachen great thanks for the response. Just tried that, and adding exiftoolArgs as you've proposed doesn't introduce any difference, I still get same warning

[mceachen]

You can also try setting up a config file for exiftool. see this forum post for details:

https://exiftool.org/forum/index.php?topic=3916.0

(closing as this is a config issue for exiftool rather than a coding issue for this module.)

[medikoo]

(closing as this is a config issue for exiftool rather than a coding issue for this module.)

This plugin embeds exiftool (it's not that the user installs it separately and then uses this module with it). So it'll be good to provide some hint on how this embedded ExifTool can be additionally configured. Currently, it's not clear to me.
I see two dependencies hosting it, exiftool-vendored.exe and exiftool-vendored.pl, where can I find the mentioned config file?

[mceachen]

The path to a config file can be set up as described here:

#27 (comment)