Windows 10 64 Problem

[Oskar]

If you want to avoid installing Perl only for ExifTool, I offer a stripped down Strawberry Perl together with an own launcher:

https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows

That's easier to install and lightweight.

P.S.: Just out of curiosity: What was your motivation not to use the "stand-alone Windows executable" offered at the ExifTool site?

Thank you for your offer! The advertised increased speed of the Perl ExiftTool  I also have the feeling that the full Perl version offers access to all the commands while the executable has a smaller number of available commands.

[obetz]

The advertised increased speed of the Perl ExiftTool

Can you point me to the place where higher speed is advertised?

Oliver

[Stan Wickham]

I poked around the registry

Code Select Expand


Computer\HKEY_CLASSES_ROOT\.pl
Computer\HKEY_CLASSES_ROOT\Perl_program_file\shell\Execute Perl Program\command

and found that Strawberry Perl decided not to set an Open Command.

Instead, they implemented their own verb, Execute Perl Program, and defined it C:\Perl\Strawberry\perl\bin\perl.exe "%1" %*. That's the same default action that Oskar found to be correct. In his case, with Active Perl, that action was associated with the verb 'Open'. (As a side note, to my new understanding of Windows File Association, the default verb is displayed at the top of the contextual menu that appears when you Right-Click on a file of a given type. Here the file type is '.pl'.)

@ Oskar Your question and sleuthing confirmed that my configuration works. Kudos to the visual artist.

Now on to creating and using the ARGFILE in R.

[Oskar]

The advertised increased speed of the Perl ExiftTool

Can you point me to the place where higher speed is advertised?

Oliver

Unfortunately I cannot find it anymore. But I know for sure it was written somewhere. The only reference I could find is here: https://www.exiftool.org/index.html#performance when it speaks of batch processing. As far as I know batch processing is available only for the Perl distribution but not for the Windows executable - am I wrong?

[obetz]

(...The advertised increased speed of the Perl ExiftTool)

Unfortunately I cannot find it anymore. But I know for sure it was written somewhere. The only reference I could find is here: https://www.exiftool.org/index.html#performance when it speaks of batch processing. As far as I know batch processing is available only for the Perl distribution but not for the Windows executable - am I wrong?

The "stand-alone Windows executable" has the same batch processing capabilities, including -stay_open.

There are minor differences, e.g. the installed version doesn't have the "parameters taken from magic file names" and a different method of printing the help, but you usually won't notice this.

[StarGeek]

The only reference I could find is here: https://www.exiftool.org/index.html#performance when it speaks of batch processing. As far as I know batch processing is available only for the Perl distribution but not for the Windows executable - am I wrong?

That reference is in regards to the common practice of using command line loops to call a program once for each file (see Common Mistake #3), which is especially prevalent among Powershell and Bash experts.  While this is required for some programs, such as FFMpeg, because exiftool's startup hit is so great and it already has powerful batch ability, looping should be avoided with exiftool.