_FileGetProperty - Retrieves the properties of a file

[BrewManNH]

Do you mean Office 2007, or maybe Windows 7? I don't have access to either so I can't test it with them. I did check an xlsm file saved from Office 2016 and those poperties showed up for that version on Win10. 

[robertocm]

sorry for the late reply and imprecision:

Windows 7 with Office 2007

Many Thanks!

[esh]

This is very helpful. thanks!

what about CHANGING file properties? anyone manage to do it?

the stuff i found online doesnt work (uses DSOfile)

 

[Nine]

@esh.  I suggest you start a new thread in General Help and Support.  Show what you have done so far.  Explain clearly what you want to achieve and have been unsuccessful. 

[lIlIIlIllIIIIlI]

 

#include <_FileGetProperty.au3>

filter(@scriptdir & '\video.mp4')

Func _FileGetFPS($fullpath, $property)
   $prop = _FileGetProperty($fullpath, $property)
   $string = stringsplit($prop, '.', 2)
   return $string[0]
endfunc

func filter($p)
   $frames = _FileGetFPS($p, 'Frame rate')
   if ($frames < 23) then
      msgbox(1,'Video low fps', $p & @crlf & 'Frame rate: ' & $frames)
      FileDelete($p)
   endif
endfunc

video.mp4 is a regular video at 30.00 fps. filter() shows 30 < 23 being true, because the "30" is evaluating to 0. It works as expected when i remove the first character of either $string[0] or $frames before making a comparison/converting to number/int. So there is some invisible character X at the beginning of the string.

I noticed this earlier when trying to do a similar thing for grabbing frame rate. it had some character before everything else. Is this deliberate? It seems weird, but what do i know. I know it isn't white space because i tried stringstripws with 8 option for removing everything

Edited February 15, 2021 by lIlIIlIllIIIIlI
typo

[TheXman]

You are right,  For some reason there is a "?" (0x3F) in the beginning of the bit rate, data rate, and frame rate values.  What's really odd is the "?" doesn't show up in _ArrayDisplay of the 2D array of all properties.

Edited February 16, 2021 by TheXman

[TheXman]

I did a little more digging...  The "?" was just the default character for an unprintable character.

For me, the mysterious character at the beginning of the the "Frame Rate" property value is a Left-to-Right Mark (LRM).  Its unicode codepoint is U+200E.  Why some of the property values have a LRM is still a mystery.

I have slightly modified your _FileGetFPS() function to remove the LRM if it exists.  With that modification, the script works as expected.

Func _FileGetFPS($fullpath, $property)
    $prop = _FileGetProperty($fullpath, $property)

    ConsoleWrite("$prop before = " & StringToBinary($prop, 3) & @CRLF) ;Display binary wchar string

    ;If string property value starts with a Left-to-Right Mark (0x200E), then remove it.
    If VarGetType($prop) = "String" Then $prop = StringRegExpReplace($prop, "^\x{200E}", "")

    ConsoleWrite("$prop after  = " & StringToBinary($prop, 3) & @CRLF) ;Display binary wchar string

    $string = stringsplit($prop, '.', 2)
    return $string[0]
EndFunc

Console:
 

$prop before = 0x200E003300300020006600720061006D00650073002F007300650063006F006E0064
$prop after  = 0x003300300020006600720061006D00650073002F007300650063006F006E0064

 

Edited February 18, 2021 by TheXman

[Champak]

This function strip apostrophes from the paths string. Is there a specific reason why? I have a particular path that has an apostrophe in it and was going out my mind trying to figure out why this wasn't working until I saw that. Everything seems to work fine once that was commented out, so just curious as to why that would have been put in in the first place.

Thanks.

[argumentum]

..you'd have to ask "2017 BrewManNH" 🤷‍♂️
It seem to work just fine without that line.