Recent Posts

Pages: [1] 2 3 ... 10
1
Your last proposal works like a charm (after having position the config file - this was the missing piece in my first trial).
Thanks again, your expertise and reactivity are really appreciated.
2
Newbies / Re: Can I change Make & Model without concern
« Last post by worx on Today at 09:34:41 AM »
Thanks for the update on this Phil.
3
Thank-you StarGeek!  That did the trick...GPSCoordinates are working perfectly now!
4
Metadata / Re: How to make a complete copy of a photo
« Last post by Fedor72 on Today at 08:23:54 AM »
Thank you
5
This should do it:

exiftool "-microvideooffset<${embeddedvideofile;$_=length($_)+56}" DIR

(I initially tried length + 56 but this didn't work because it took the length of "56" instead of the "$_" that is implied if the argument is missing :( )

- Phil
6
@Phil,
Thanks, it will be even more efficient but I didn't find the way to make it work.

This TAG has this value :
Embedded Video File             : (Binary data 4080978 bytes, use -b option to extract)

The value of MicroVideoOffset should be the integer from Embedded Video File TAG + 56.
So in the exemple above, at the end, we should have
MicroVideoOffset                : 4081034

Do you see a simple way to do it in 1 or 2 commands ?
7
Newbies / Re: Can I change Make & Model without concern
« Last post by Phil Harvey on Today at 08:10:44 AM »
[This is more for my reference than anything else...]

After studying the specification more closely I am convinced that the Pixel 4 writes the sample table box incorrectly.  According to the specification, each SampleEntry must begin with 6 zero bytes followed by a 2-byte data_reference_index.  I found the specification for the 'mett' sample entry used by the Pixel 4, and it extends the basic SampleEntry thus (from the ISO_IEC_14496-12 specification):

aligned(8) abstract class SampleEntry (unsigned int(32) format)
   extends Box(format){
   const unsigned int(8)[6] reserved = 0;
   unsigned int(16) data_reference_index;
}
class MetaDataSampleEntry(codingname) extends SampleEntry (codingname) {
   Box[] other_boxes; // optional
}
class TextMetaDataSampleEntry() extends MetaDataSampleEntry (‘mett’) {
   string   content_encoding; // optional
   string   mime_format;
   BitRateBox ();    // optional
   TextConfigBox (); // optional
}


Therefore, each 'mett' MetadataSampleEntry must still begin with 6 zero bytes and a 2-byte data_reference_index.  However, the Pixel 4 skips this and jumps straight to the content_encoding string, which is clearly wrong:

Code: [Select]
  | | | | + [SampleTable directory]
  | | | | | MetaSampleDesc (SubDirectory) -->
  | | | | | - Tag 'stsd' (50 bytes):
  | | | | |  1f4b07a: 00 00 00 00 00 00 00 01 00 00 00 2a 6d 65 74 74 [...........*mett]
  | | | | |  1f4b08a: 61 70 70 6c 69 63 61 74 69 6f 6e 2f 6d 65 74 61 [application/meta]
  | | | | |  1f4b09a: 00 61 70 70 6c 69 63 61 74 69 6f 6e 2f 6d 65 74 [.application/met]
  | | | | |  1f4b0aa: 61 00                                           [a.]

(The first SampleEntry starts immediately after the 'mett' identifier in the above exiftool -v3 output from a Pixel 4 video.)

Since the data_reference_index is needed to be able to rewrite the file properly, ExifTool can't edit these files without risk of further damage.  Google will have to fix this at their end.

- Phil
8
Metadata / Re: How to make a complete copy of a photo
« Last post by Phil Harvey on Today at 07:00:44 AM »
You could also add -jfif:all and -trailer to copy the JFIF segment and any JPG trailer.

- Phil
9
If you just need to set MicroVideoOffset to the size of the video in the Samsung trailer, you can do this quickly in batch mode for all files in a directory:

exiftool "-microvideooffset<${embeddedvideofile;$_=length}" DIR

- Phil
10
@StarGeek, @Phil Harvey, you are genius  ;)
It works perfectly.
I have now to extract all the video offset. Thanks to your example, I think I know how to do.
I have even been able to transform motions photos from an older smartphone (not recognized by Google photo) into motion photos recognized by Google photo.
On the older smartphone, the MicroVideo Tags are not created by the smartphone. So obviously, the website cannot recognize the file.
Let's hope that Google won't change the indentified Tag to something else  :).

Again, a big THANKS for your help.
I have work to do to change all the hundreds of photos I have.
Pages: [1] 2 3 ... 10