DPX Keycode metadata in Nuke

Does anyone know why Nuke reads keycode from a DPX in perfs instead of frames? I was replicating a telecine workflow by burning in TC and KK onto some footage. Via Avid reconformed in Baselight. However the the Keycode burnt in (from Nuke) have the last two digits going up to 64 (64 perfs per foot of film) as opposed to Baselight – and other apps I tried – that goes up to 16 (16 frames per foot).

I didn’t even realise Keycode could be read differently.

No Responses to “DPX Keycode metadata in Nuke”

Post a Comment