antgiant
antgiant
Google randomizes the the timings [plus or minus 15 minutes](https://developers.google.com/apps-script/reference/script/clock-trigger-builder). This is a hard limit that Google has created so it is unlikely to change. Sorry.
@zachwhalen actually did incorporate this feature as a part of the Setup sheet on the current version.
Most of the time that happens because of a space or tab at the end of the API keys in the spreadsheet.
It appears that the current version works around this by using a next--> pointer that moves instead of actually rotating the values.
The remainder of this suggestion has actually been incorporated into the code already.
Would it be acceptable to offload the actual reading and writing to the very battle tested and popular [ExifTool](https://exiftool.org/)? [ExifTool](https://exiftool.org/) - [Reads and writes a huge number of metadata formats...
Hey thanks I had missed that issue. I’m confused by your file format comment though. ExifTool reads and writes XMP just fine and the list of [file formats supported by...
If I find time to add it would you be open to a pull request? My thought is to add an on page load hook that takes the URL parameters...
Just noting that this is related to #415, as solving this is actually the more general case of solving #415.
Hmm actually I just noticed that the 4,900 index crash started right around when the app was updated to Apple's CLIP model. Perhaps they are related?