Repository navigation
Videos and Live Photos videos from iPhone not treated #491
Replies: 1 comment
|
There is a concrete filename-matching issue worth testing before changing permissions further. In the current For your first example, try an isolated copy containing just: The second file should be a copy of your existing Your Live Photo case is separate: an MP4 cannot be matched to a HEIC sidecar by that filename rule. On a test copy, after confirming they are genuinely the same capture, a copy of the HEIC sidecar named Finally, distinguish filesystem dates/organization from embedded video metadata: the README treats embedding dates with ExifTool as a separate step. Please include the exact helper version and whether “not treated” means no matching date, no output file, or unchanged embedded QuickTime metadata. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
First of all thanks for this wonderful tool.
However I'm having difficulties to get all videos (and a few pictures) treated.
Usage context;
I'm executing the Linux binary gpth-linux with the command "./gpth-linux -i FOLDER -o FOLDER" with a user that has full rights on all the files in the specified folders. I even chmoded files to 777 and executed the binary in sudo to be sure nothing related with file access could prevent modification. So the tool HAS access to json file, can read it and has the rights to modify the MP4 or MOV files. It indeed worked for thousands of .HEIC, .png, .jpeg pictures so far but 100% of the videos are failing.
Observations;
I've noticed 2 use cases:
Example; a file named "IMG_6608.MOV"

Here is the complete .json content; (GPS position hidden for my privacy)
{
"title": "IMG_6608.MOV",
"description": "",
"imageViews": "17",
"creationTime": {
"timestamp": "1705772353",
"formatted": "20 Jan 2024, 17:39:13 UTC"
},
"photoTakenTime": {
"timestamp": "1705767125",
"formatted": "20 Jan 2024, 16:12:05 UTC"
},
"geoData": {
"latitude": XX.XXX,
"longitude": XX.XXX,
"altitude": XX.X,
"latitudeSpan": 0.0,
"longitudeSpan": 0.0
},
"geoDataExif": {
"latitude": XX.XXX,
"longitude": X.XXXX,
"altitude": XX.X,
"latitudeSpan": 0.0,
"longitudeSpan": 0.0
},
"url": "https://photos.google.com/photo/AF1QipNZ6i2hsJbEzHbvQEcaDRHtef9HT4W-btGbXs8x",
"googlePhotosOrigin": {
"mobileUpload": {
"deviceType": "IOS_PHONE"
}
}
}
where we can see that the file name is correct so I don't get why the script cannot alter the corresponding file.
Example; a file named "IMG_6606.MP4"

Here is the complete .json content; (GPS position hidden for my privacy)
{
"title": "IMG_6606.HEIC",
"description": "",
"imageViews": "10",
"creationTime": {
"timestamp": "1705751628",
"formatted": "20 Jan 2024, 11:53:48 UTC"
},
"photoTakenTime": {
"timestamp": "1705749609",
"formatted": "20 Jan 2024, 11:20:09 UTC"
},
"geoData": {
"latitude": XX.XXX,
"longitude": X.XXXX,
"altitude": XX.X,
"latitudeSpan": 0.0,
"longitudeSpan": 0.0
},
"geoDataExif": {
"latitude": XX.XXX,
"longitude": X.XXXX,
"altitude": XX.X,
"latitudeSpan": 0.0,
"longitudeSpan": 0.0
},
"url": "https://photos.google.com/photo/AF1QipP8xj6KvCtU5t7A1DCLGOB3snwYJXNJ27tnLjv7",
"googlePhotosOrigin": {
"mobileUpload": {
"deviceType": "IOS_PHONE"
}
}
}
Here, it is more obvious as the .json file only mentions the HEIC picture. Is the tool taking this case into consideration? If yes then I don't understand why it woudln't work.
Is there a verbose mode I could use so that we could try to find a solution ? I'm sure I'm not the only one concerned.
Side note : Why "hardcoding" the Google Takeout folder structure in the algorithmic instead of program the tool to fetch each and every subfolder recursively ?
All reactions