# Camera analysis adapt to Timewarp **URL:** \ **Category:** Flame Questions\ **Tags:** action, timewarp, 3d-tracking\ **Created:** [April 1, 2025, 7:33am UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576 "2025-04-01T07:33:23Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Fabi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fabi/32/14709_2.png) [@Fabi](https://forum.logik.tv/u/Fabi)\ **Post date:** [April 1, 2025, 7:33am UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/1 "2025-04-01T07:33:23Z")
Hi folks, we currently have to retouch timewarp artifacts and unfortunately the camera analysis does not work at all on the timewarp. It works great on the untimewarped plate, is it possible to adapt the tracking data to the timewarp? Unfortunately I have not yet found a way to do this. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/47_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [April 1, 2025, 12:59pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/2 "2025-04-01T12:59:26Z")
An eval expression on a copy of the tracked camera might work: eval(tracked camera, timewarp frame) But I’m just marking a guess till someone else pops in with a real answer. ---
**Author:** ![grantconnor](https://avatars.discourse-cdn.com/v4/letter/g/bc79bd/32.png) [@grantconnor](https://forum.logik.tv/u/grantconnor)\ **Post date:** [April 1, 2025, 1:55pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/3 "2025-04-01T13:55:26Z")
Somebody explained this to me a long time ago and it did work, but alas my brain has since decided I do not need to remember it. Luckily I wrote myself an email at the time explaining. Alas, reading it back I cannot remember much about it/doing it, so if you have any questions I am probably not your man… Hope it helps. _Once you have your camera and geo working, decide on the timewarp for the shot and build a TW node. Name it TW_ _In the action schematic, name your main camera, CAM1. Duplicate this and name it CAMTW._ _Feed the TW node into the back of your action that has the camera._ _Now go to the animation window. Scroll down until you find CAM\_TW_ _Select this, and then hit the right bracket key ]_ _This should bring up the expression bar._ _Type in eval(CAM1,TW.Timing)_ _CAM1 = Original camera_ _TW = TW node feeding into back of action_ _Timing = The timing parameter in the animation menu of the TW node._ _This should now place an ‘e’ next to the CAM\_TW in the animation menu._ _All that’s left to do now is go back to the schematic and choose then new camera to view through, ie. CAM\_TW_ \*If you want to project something, you would normally copy the camera, and on the ref frame, hit keep and only that keyframe would remain. When you do an expression to link to the timewarp node, it removes all individual keyframes and has a curve set in stone. \* _So, copy the new camera(CAM\_TW), go to the animation menu, select copied camera and uncollapse everything in it , and then on the right hit ‘bake’. This will give you individual points, so you can now ‘keep’ the ref frame you want._ **Also, make sure your timearp node is on motion, or feed in an ML timewarped clip into the background, and have the timewarp node outside of action to link your expression to.** ---
**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\ **Post date:** [April 1, 2025, 2:17pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/4 "2025-04-01T14:17:21Z")
This is the way. You’ll need to rebuild the tw as a timing tw rather than speed, then use the timing keyframes to drive the eval. Should work great. ---
**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\ **Post date:** [April 1, 2025, 2:28pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/5 "2025-04-01T14:28:55Z")
Not sure what version you have , but (I haven’t tried this with camera tracking) you might try using MLTW first then track that. I’ve had ok results doing this with traditional tracking. ---
**Author:** ![BenV](https://avatars.discourse-cdn.com/v4/letter/b/58956e/32.png) [@BenV](https://forum.logik.tv/u/BenV)\ **Post date:** [April 1, 2025, 4:17pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/6 "2025-04-01T16:17:13Z")
You should be able to do this as it can be done with normal tracking data I don’t of the bat see why it wouldn’t apply to a camera in action. I have it written down somewhere but I’m out and about today. The great @john-geehreng haha, would be the one to ask as he’s where I got the expression from back in the day. ---
**Author:** ![john-geehreng](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/john-geehreng/32/7195_2.png) [@john-geehreng](https://forum.logik.tv/u/john-geehreng)\ **Post date:** [April 1, 2025, 4:48pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/7 "2025-04-01T16:48:01Z")
I’ve always used the expression that Andy and Grant shared. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [April 1, 2025, 5:35pm UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/8 "2025-04-01T17:35:22Z")
I’ve had great results using MLTW to slow it right down, before applying your respeed curve. ---
**Author:** ![PVR](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/pvr/32/1288_2.png) [@PVR](https://forum.logik.tv/u/PVR)\ **Post date:** [April 2, 2025, 7:06am UTC](https://forum.logik.tv/t/camera-analysis-adapt-to-timewarp/12576/9 "2025-04-02T07:06:14Z")
Also the Flame Planar Tracker does not understand timewarped footage most of the times. Also when there are black bars as letterbox, it thinks that is part of the footage.