I’m not sure if i understood this correctly about “timing curve” but:
You can copy the camera (with all the keyframes) and simple move the keyframes in the timeline for this camera. And even in the graph editor set a 2D cursor and scale everthing to make it “faster” or “slower”.
Ahh yes… i understand now… hmm so i’m triedto make a moving camera and some “timecurve” by simple animating some empty from between Z=0 and Z=1… then a driver (camera. location[2] ) could read the this as factor for the number of frames ( z-pos / frame )…
… to get the location of the camera at this frame…
But the simple expressions does not allow to get this info (AFAIK)… so maybe in python… (or geometry nodes)…
It might be useful to provide a simple blend file with the timecurve as you seems to already have build ??
Haha… in fact i have some similar setup… only didn’t delete the default cube
It’s bit ( or a lot ) messy yet… but i can copy a position coordinate from some other object on a specific frame via drivers… But to be honest i do re-search for a slightly cleaner way… for example not having a driver for ever three position and also rotation coordinates… (driver variables are some kind of weird…) And it’s “hardcoded” to the names also… (will adapt to your example… also for 3.6 but this shoudl work in 4 too)…
So i needd to put everything together… and because of the “complicated driver setup” also have to do some “docu”…
@Lumpengnom Thanks for this. I think the last step here will be to normalise my timing curve into a value between 0 -1 to drive the evaluation time, but this is really helpful thanks