[DJI-log-discuss] Wrong handling in RECOVER Record

[Brett Spell]

I agree with Christian: it’s great to have both (scramble table or direct derivation) options, so thanks to you both (Ross and Daniel) for sharing the information with us.

 

Brett

 

From: DJI-log-discuss [mailto:dji-log-discuss-bounces at us.live555.com] On Behalf Of Christian U.
Sent: Sunday, January 19, 2020 10:28 AM
To: Discussion of DJI's log file formats
Subject: Re: [DJI-log-discuss] Wrong handling in RECOVER Record

 

i have to add #include <errno.h>

to  <http://gitlab.stora.local/produkte/dji/djiparsetxt/commit/6d14c9f58612d7abf0dcc7a670e6bd2c8eeea7db#cd4aa6484a5080c3e53d4f2c4b7b761f7d09d2f0> djiparsetxt.cpp to fix compiling with actual gcc

 

Am 19.01.20 um 15:46 schrieb Chris:

Great work Ross, 

And also Thanks Daniel for the Information. I think my english is too bad to completely get it. 

Daniel is it completely possible to implement an handler to generate the key on the fly with the information you gave ? 

I have tried to make an implementation based of an crc64 function in december but dont was able to recover all parameters to the gtekey function completely. 


best regards and happy new year to all 

Christian 

Am 19.01.20 um 14:03 schrieb Ross Finlayson: 



FYI, the latest version (2020-01-19) of the “djiparsetxt” code also improves the processing of RECOVER records, as a result of Christian’s feedback on December 20th. 


Ross Finlayson 
Live Networks, Inc. 
http://www.live555.com/ 



 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ns.live555.com/pipermail/dji-log-discuss/attachments/20200119/a7986ecd/attachment-0001.htm>