Bezier easing between any two keyframes in Adobe Premiere Pro. Everything below takes under a minute — if it doesn't solve it, write to us and a person will answer.
Every message gets a reply. To get a useful one first time, include your Premiere Pro version, your operating system, the ZFlow version from Settings → About, and what the panel's status strip said when it went wrong.
Changed your mind? Pick a different curve and it re-eases in place — no stacking keyframes on top of each other. Press the trash button and you're back to your two original keyframes, with their original values.
The playhead is over an audio item, a gap, or a clip on a hidden track. ZFlow reads video track items only.
Either the playhead is outside that property's keyframes, or the two keyframes are less than two frames apart. Hover the chip — the tooltip tells you which.
Effect Controls is showing a different clip than the one you think is selected. When a clip is selected, ZFlow targets only that clip — that is deliberate, so a batch never touches something you didn't mean.
One Ctrl/Cmd+Z takes back the whole ease in a single step, not one keyframe at a time.
In the standalone .zxp build for machines without the Creative
Cloud app, use the panel's own Undo button instead — the older extension
interface can't group writes into one undo step.
They live in the plugin's own storage on that machine. Use Library → Export pack to write them to a file, and Import pack to load them on another computer.
It's the graph After Effects users already read: only your two parent keyframes, with influence handles, everything ZFlow wrote between them hidden. The zero line is magnetic, so a keyframe that should hold still before it moves lands on exactly zero. Prefer the classic view? Settings → Graph → Value.
No. It never connects to anything, and it collects nothing about you. See the privacy policy.
.zxp version exists for machines without the Creative Cloud desktop app, supporting Premiere Pro 13 and laterIf ZFlow does something wrong on your timeline, that's worth an email even if you found a way around it. Tell us the property, the frame rate, how far apart the keyframes were, and what you expected instead. Reports like that are how the last several bugs got fixed.