[Bart Stevens]

I was able to get the track nailed down, but still couldn’t get the scale working where I could use it.
My track would stick (using the liquify filter, and still image), but with the scale data, the entire frame was scaling up and down to stabilize.
I’m not sure if it was reversed or not. The rapid scaling of the whole frame would lead me to suspect no, but the track was “sticking”. So not sure..
If I deleted the scale info, and still linked it with expression, the track sticks and the shot looks “normal” (without rapid scaling up and down).
Seeing that the AE tracker doesn’t use scale data, I’m not sure if I’m getting much out of the information anyway.
Working good enough right now, but the question is still there.

[Bart Stevens]

Ah ha, thank you very much!
Using the same scale expression in the pre-comp was the part I missed.
Sometimes the obvious can stare right at me, and I still don’t see it.
Thanks for the clarification of Andrews tutorial too. It’s helpful to understand the principals of the technique.
Cheers,
Bart

[Bart Stevens]

Maybe I didn’t communicate clearly.
The expression is working correctly from Mocha, it’s just the second step in using the information in After Effects.
The footage scales up and down to “stabilize”, but I can’t get that to reverse.
The Andrew Kramer tutorial addresses the position ( swapping anchor point data with positional), and rotation (with the *-1 expression).
But his method using the After Effects tracker doesn’t create scale data, and I wondering if there is way to use it? Or if that will help with the accuracy of the track.
Hopefully that makes sense.
Thanks

[Bart Stevens]

I can’t be exactly certain, because it was a while ago, and currently my workflow is a little different. But I don’t think I was able to get around the “in cut” issue. I think I had to re-do my edit unfortunately. Sorry I couldn’t be more help.

[Bart Stevens]

You’re the Man Dan.
Thanks for the help,
-Bart

[Bart Stevens]

Thanks for the feedback Ted,
I have the luxury of being able to test on a D.C server and through some trial and error, I found a successful workflow:

Project working space:
Universal Camera Film Printing Density
16 or 32(float) color depth
Linearize working space
compensate for scene-referred profiles

import dpx sequences as REC709 (if exported from non- DCDM-colorspace environment)
import dpx sequence as DCDM xyz ( if exported in that format in previous render)

import .R3d as REC709 (embedded rgb)

Export DPX sequence in the DCDM xyz gamma 2.6 5900K

[Bart Stevens]

never mind – wrong fps in encoding proxy

[Bart Stevens]

Thanks for the info, yes I’ve also been in contact with Cineform support and have had limited success.
If I export the quicktime with RGBA channel premultiplied, trillions of colors, and 4:4:4 color depth, it will export a file.
Unfortunately I’ve experienced some strange color artifacts with these settings, and that has not been successfully resolved.

[Bart Stevens]

I’m also looking at LTO archive solutions, Windows Adobe Suite workflow.
How did your solution work out?

[Bart Stevens]

Thanks for the info Ben. Although the error message is similar, it sounds like a different issue. My render fails almost immediately when launched. I tested mouse movement anyway, but it still fails. Thanks for the help anyway.
Solid motion graphics reel too.