As a freelancer, it would be more useful if I could activate a new machine and the old machine would deactivate automatically.
I can easily see a situation where I couldn't deactivate, like the death of a motherboard, or no longer working at a company and forgetting to deactivate before being thrown out the door! Maybe a site wide recommendation or a new way to license but it would really help.
Hi Michael! None of this sounds related to Flow. Try opening a support ticket with the site as a whole and maybe somebody on that team can get back to you?
As a freelancer, it would be more useful if I could activate a new machine and the old machine would deactivate automatically.
I can easily see a situation where I couldn't deactivate, like the death of a motherboard, or no longer working at a company and forgetting to deactivate before being thrown out the door! Maybe a site wide recommendation or a new way to license but it would really help.
Hi. Flow (latest update) is not appearing in AE 2024. Any advice?
You need to make sure it is installed in the version of AE that you are using.
In the aescripts + aeplugins manager app (https://aescripts.com/learn/aescripts-aeplugins-manager-app/), right-click and select 'Custom Installation' and make sure you are installing into the same version of After Effects that you are using. Please restart after installing.
After restarting you will find it under the Window menu in After Effects
Latest 1.5.2 version is not affecting the in handle of the keyframes in AE 2024. Updated AE to the latest version, tested it on multiple projects and the issue is everywhere. For example, this is what happens when I apply the maximum Flow curves (1,0,0,1) into keyframes: https://ibb.co/0qNHkzN
I hope this message finds you well. I’m encountering an issue with the Flow plugin and would appreciate your assistance.
When I apply easing to a motion, the handle for the first keyframe doesn’t appear, and as a result, the easing effect isn’t applied to it. This seems to prevent the expected smooth transition at the start of the animation.
I hope this message finds you well. I’m encountering an issue with the Flow plugin and would appreciate your assistance.
When I apply easing to a motion, the handle for the first keyframe doesn’t appear, and as a result, the easing effect isn’t applied to it. This seems to prevent the expected smooth transition at the start of the animation.
When I apply easing to a motion, the handle for the first keyframe doesn’t appear, and as a result, the easing effect isn’t applied to it. This seems to prevent the expected smooth transition at the start of the animation.
You've set the "ease direction" toggle to be either "ease in" or "ease out" (instead of "both").
When I apply easing to a motion, the handle for the first keyframe doesn’t appear, and as a result, the easing effect isn’t applied to it. This seems to prevent the expected smooth transition at the start of the animation.
You've set the "ease direction" toggle to be either "ease in" or "ease out" (instead of "both").
It's the setting beside the Apply button.
Thank you so much for your help! I’ve been stuck on this issue for three years, and your solution resolved it instantly. I really appreciate your support!
If you have a technical or customer support issue, please open a support ticket instead.
If you have a technical or customer support issue, please open a support ticket instead.
If you have a technical or customer support issue, please open a support ticket instead.
I hope this message finds you well. I’m encountering an issue with the Flow plugin and would appreciate your assistance.
When I apply easing to a motion, the handle for the first keyframe doesn’t appear, and as a result, the easing effect isn’t applied to it. This seems to prevent the expected smooth transition at the start of the animation.
Thanks in advance
I’ve been using Flow for some time, but whenever I apply it, After Effects shuts down.
I tried reinstalling the plugin and even reinstalled After Effects, but the same issue keeps happening.
I suspect it might be a conflict with Apple Silicon. Has anyone experienced a similar issue before?
I’m using an iMac with an M1 chip and macOS Sonoma 14.7.
If you know a solution, I’d appreciate your advice. Thanks!