SOLVED!!!
Thanks so much for the direction! Adjusting the frame rate by using the ‘hour’ byte was what was needed!
We did, however, run into a good bit of confusion about how all of that worked. But after some digging into it we realized the following:
- The expected value in the hour byte is across a 0-127 range.
- There are 4 frame rates represented in this range: 24fps, 25fps, 29.97fps and 30fps
- The 0-127 range is divided into 4 blocks of 32.
- 24fps is in the first block (0-31), 25fps in the second block (32-63), 29.97fps in the third block (64-95) and 30fps in the fourth block (96-127)
- The first value in each block is hour zero. Once it reaches hour 24 the timeline locates back at zero and starts again. So in the first block the value of 23 will locate to hour 23. The value of 24 will locate to zero and the value of 25 will be hour one, etc.
- This means the value of 32 (the first value of the second block of 32) will be hour one of the 25fps set. 64 is hour zero of the 29.97set, and 96 is hour zero of the 30fps set.
- In the ‘hour’ byte, you specify the value of the hour and framerate you are after - then convert it to hex. I’ll try to upload a PDF of a table that shows all these values.
Thanks so much for your help in this! SOLVED!!!
Darren “Hexed No More” Ingram
Decimal to Hex for MMC key (002).pdf (110.2 KB)