Two problems with -stay_open

Started by rnicz, May 05, 2014, 06:24:31 AM

Previous topic - Next topic

rnicz

I noticed two problems in -stay_open mode of exiftool.

1. if -q switch is written to command file, exiftool does not returns {ready} response. With no -q exiftool works as expected.
2. if there are errors in processing (for example target images exists), exiftool reports error, but does not returns {ready} response.

In both cases processing loop hangs waiting for {ready} response.

At the moment I have not sample code for this issues: I can prepare simplified test code, if it is necessary.

I test it on Windows 8 with exiftool.exe v. 9.52 and 9.59

--
Best regards
RNicz

Phil Harvey

Quote from: rnicz on May 05, 2014, 06:24:31 AM
1. if -q switch is written to command file, exiftool does not returns {ready} response. With no -q exiftool works as expected.

Yes.  This is the way the -q switch works (read the docs).  If you want -q with a "{ready}" message, use -echo2.

Quote2. if there are errors in processing (for example target images exists), exiftool reports error, but does not returns {ready} response.

This shouldn't happen.

> exiftool -stay_open true -@ a.args
Error: 'b.jpg' already exists - a.jpg
    0 image files updated
    1 files weren't updated due to errors
{ready}


I got the "{ready}" message above for a file with a fatal error.

Here is a.args:

a.jpg
-artist=me
-o
b.jpg
-execute


- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).