![]() Must be something with Windows that is not agreeing with ExiftoolGUI. StdoutEnd=PeekS(*buffer+result-15,15,#PB_Ascii)įindStart. 1 November 22, 2015, 04:50:33 AM Tried installing on another Windows 10 machine and there it works fine. ReadProgramData(param\ProgHandle,*buffer,result) If StdErr"":Verbose("/!\ ExifTool ERROR :"+StdErr+"0 StdErr.s=ReadProgramError(param\ProgHandle) Greetings, Before we get into this conversation, can you tell us what EF to RF adapter you are using If its not Canon, that alone might be the cause. Param\ProgHandle=RunProgram(param\ProgFilePath,"-stay_open True -",GetPathPart(param\ProgFilePath),#PB_Program_Open|#PB_Program_Read|#PB_Program_Write|#PB_Program_Error|#PB_Program_Hide) Protected Output.s,Stdout.s,StdoutEnd.s,StdErr.s,ExecuteID.s *Data=param\Execute(Str(ExecuteID))\RawOut ![]() ![]() StdErr=param\Execute(Str(ExecuteID))\StdErr Stdout=PeekS(param\Execute(Str(ExecuteID))\RawOut,MemorySize(param\Execute(Str(ExecuteID))\RawOut),#PB_UTF8) If param\Execute(Str(ExecuteID))\RawOut>0 (5) Drag and drop the renamed exiftool file to the exiftoolgui folder. So if Windows 7 is not set up to show file type extensions (which is the default setting), just rename file to exiftool. MessageRequester("Exiftools","Exiftool No Found",#PB_MessageRequester_Error) If you don't have it show file extensions you could be renaming it to which could be the possible cause of your problem. Procedure.b SetExecutableFilePath(FilePath.s) 1 Answer Sorted by: 0 Thank you StarGeek The problem was that I didn't have the exiftool command tool (the separate application of exiftool) in the right PATH env variable. Param\VerboseFileId=CreateFile(#PB_Any,"ExifTool.log") ReadyToUse.b #True if Stdout and StdErr is ready to use If a specified tag does not exist, a minor warning is issued and the line with. #Verbose=#True TODO #True or #False if you want a exiftool Log file ERRFILE Save names of files with errors -executeNUM Execute multiple. Exiftool info: ExifTool is a platform-independent Perl library plus a command-line application for reading, writing and editing meta information in a wide variety of files Description: use the verry good Perl Package Exiftool You need to download the file- exiftool (-k).exe, put it in the same directory as ExifToolGUI.exe BUT rename it to just exiftool.exe. Yo recomiendo uno en particular que se puede ejecutar tanto en Linux, MAC o Windows. Transfers metadata for OriginalDate, Make and Model from the source file."įor fullpath in Strip longest match of */ from startĭir="$" Thank you!Įcho "Converts an AVI video file to a MOV (QuickTime) video file. Just unzip ExifToolGUI.zip file into any directory, create Desktop shortcut and GUI is ready to use. I use the script in an Automator schell script, with settings "The service receives marked FILES OR FOLDERS in FINDER" with shell "bin/bash" and Pass input "as argument". The above example will output something similar to: test1.jpg: No header data found. For the string in Shell() for exiftool, one would use the full drive:path. Perhaps it's a problem with the first part of the script, getting the actual file name ("$fullpath") and that's where the problem is? The first call fails because the image has no header information. I can only guess at why your Shell() command failed since you did not post code. And I have tried looking at forums and manuals and exiftool tags and so on and I am lost. I have tried the command in Terminal on a file and it works, I get a variable with for instance "$make" or "$model" that I can see with "echo". Those are the three lines in the code with exiftool. I have been trying to execute this script (Automator, Shell script) with ExifTool and FFmpeg commands, that I found on this thread ( ) and when I run it I always get this error: "line 31:exiftool:command not found" and the same for line 32 and 33.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |