Arlighty... so a package I have been building at 60fps now needs to be converted to 29.97. I know that, on a fundamental level that's not in and of itself hard to do via project convert mode, but I am fining that when I tell XPression to re-interpolate the keyframes, some things break. For example, single frame alpha ramps stop working as the file tries to condense 1 frame to something less than one frame, and some of my brute force animation curves (where in I manually build a curve with intermediate keys at 5-frame intervals) get... well... lumpy for lack of a better word. A few of the keys at 0 also vanish and need to be remade. Now, these aren't especially difficult adjustments to make, but they do end up costing me some time, and that resource is an extremely precious commodity these days.
So... I was wondering... what if I - upon changing the frame rate - tell XPression to 'do nothing' with the keys, and then add an event at the beginning of the scene director instructing the sequence to play at 2x (or I suppose 2.1x)? In my mind I feel like that should work, since leaving keys where they are and (roughly) halving the frame rate would result in 1-second animations now taking 2-seconds, and said Event at 2x would bring them back in time, but I wonder if there are any gotchas or pitfalls to using that approach?
Any thoughts?