Use of uninitialized value in addition (+) in QuickTime:CreateDate

[tiwa]

I use
exiftool -stay_open True -@ -

When i try to write the quicktime:createDate, i got the error:

Code Select Expand


Warning: Use of uninitialized value in addition (+) in QuickTime:CreateDate (ValueConvInv)
Nothing to do.


The commands send are:

-lang
fr
-P
-QuickTime:CreateDate=2020:10:17 20:12:43
/somePath/someVideo.mp4
-execute

I try with quotes around the date without success.

What goes wrong? Where does the (+) came from?

[Phil Harvey]

What version of ExifTool are you using?  My first thought is that you should try updating to a recent version.

- Phil

[tiwa]

My exiftool version is 12.00

Writing exif:exifIFD:CreateDate or exif:exifIFD:DateTimeOriginal work well 

[StarGeek]

Try updating exiftool.  This might have been fixed in 12.12.

[tiwa]

I have upgrade to 12.20 and got the same message 

[Phil Harvey]

I have tried reproducing your observations using your exact arguments on a test file and I have no problems.

Can you see this effect when running the same command on the command line (without -stay_open)?

If you can't, then are you sure you are running the proper version when using -stay_open?  How exactly are you running exiftool then?

- Phil

[tiwa]

Hi Phil
I send you details on your mail
Yves

[tiwa]

I have install the Windows executable to try.

The update of the QuickTime:CreateDate has succeed 

[tiwa]

Thanks for the new version.

I upgrade my App on Android with the version 12.21. I still have an error but the message is different:

Code Select Expand


Warning: Error converting value for QuickTime:CreateDate (ValueConvInv)
Nothing to do.


[Phil Harvey]

Yes.  I knew this would happen.  The "uninitialized value" error (which should have been caught) is due to an improperly formatted date/time value.  The "Error converting value" error is what this should have said.  You still have some work to do at your end to figure out why you are sending ExifTool a bad date/time value.

- Phil

[tiwa]

Thank you Phil.
You got the point: My perl instance was missing the Time::Local module.
This thread can be closed.

[Phil Harvey]

The missing piece in this thread is found in this email communication:

On Feb 27, 2021, at 11:43 AM, Phil Harvey <philharvey66 at gmail.com> wrote:
The conversion to an int32u date value will also fail if your Perl doesn't have the Time::Local module.  Perhaps this is the problem?

- Phil