Hey there Logik. A little task I have been given to fit into a nuke pipeline is to export my timewarp node setups as a text document. In a format like this.
Not sure how nuke reads this or interprets fractional frames, but Flame always rounds down to the closest integer ('cause ya can’t have a fraction of a frame) so to be safe I would do that with your text file. I’m not sure how you are building the text file, but the expression “floor” rounds down.
Bake your timewarp curve’s frame channel, copy it and paste it to a channel of an axis in action and export raw from action with that channel selected in action.
That’s most of the way there. Nuke used to be able to import that directly as a discreet “lut”.
From flame, save your timewarps individually, with meaningful names.
Run this python script and point to /opt/Autodesk/$my_projekt/timewarp/flame/
Harvest the new files. (*.tw_key_values)
I would have written the conversion directly to nuke, but my beta license has expired, and the non-commercial version writes out hashed/encrypted gibberish.
N.B. this operates on keyframes from the timing channel, not from the speed channel. Read a couple of the '.timewarp_node’ files and you’ll figure out what data you want to keep or not.