Marcus Meissner

nothing shines out of the diff between those. can you try gphoto2 --wait-event=1s --set-config opcode=0x9127,0xd1ac --wait-event=1s --debug --debug-logfile=d1ac.log and attach d1ac.log here?

can you specify some more lines of this hexdump before the quoted lines?

can you quote also the 2 hexblocks before this hexblock?

usually little endian is used. so 01066a if you want to be sure, you can take 170 pictures so it wraps into the next byte to see which is incremented....

thanks! the OLCInfo is a binary blob with a careful handcrafted and reverse engineered parser... and its close to the end of the blob, so it might take a bit...

can you also do the following: gphoto2 --wait-event=1s --set-config opcode=0x913d,0x1000 --wait-event=1s --debug --debug-logfile=0x1000.log gphoto2 --wait-event=1s --set-config opcode=0x913d,0x0800 --wait-event=1s --debug --debug-logfile=0x0800.log gphoto2 --wait-event=1s --set-config opcode=0x913d,0x0400 --wait-event=1s --debug --debug-logfile=0x0400.log gphoto2 --wait-event=1s --set-config...

i just added to current libgphoto2 GIT a option to do this in one run gphoto2 --set-config testolc=1 --debug --debug-info=olc.log if you can send the olc.log ?

ah sorry, missed your previous comment. no specific need. in the 0x1000 block is the shuttercount stuff I think 1.059027 ptp (2): event 0: EOS event OLCInfoChanged (size 24) 1.059040...

the nikon dslr actually seem to return this during capture when liveview is running, but we currently do not decode and present that info via the API. which nikon?

basically yes. the camera sends back a blob of data on this command, and 1 big part is the JPEG of the liveview, and there is a structured datablob (in...