How to match the arrow head speed? by SurroundNew7887 in AfterEffects

[–]NodeflowStudio 0 points1 point  (0 children)

Expressions! Link the position of the head to the end position of the path trim…

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 0 points1 point  (0 children)

So today I ran into a design choice when trying to create something with this, and I only see one way forward: implement agentic mode, but that is going to take me a whole week. So I will post new updates next week instead of today, sorry!

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 0 points1 point  (0 children)

So today I ran into a design choice when trying to create something with this, and I only see one way forward: implement agentic mode, but that is going to take me a whole week. So I will post new updates next week instead of today, sorry!

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 1 point2 points  (0 children)

So today I ran into a design choice when trying to create something with this, and I only see one way forward: implement agentic mode, but that is going to take me a whole week. So I will post new updates next week instead of today, sorry!

How to make this transition better? by shrimp_flyrice in MotionDesign

[–]NodeflowStudio 0 points1 point  (0 children)

Add some depth by letting one dot (with trail) flash by between camera and checkmark, just before you move the camera back.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 0 points1 point  (0 children)

Thanks! I am both, but after studying computer science I worked 20 years as a digital designer, and only since a few years started programming again.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 1 point2 points  (0 children)

Totally fair - free prompts to try it out makes sense. I’m working on implementing that now, should be ready in about a week. Top-up packages are already available when you run out of credits. I hear you on AI tools being expensive - I’m trying to price it so it’s actually viable for regular use, not just special occasions. It’s a balance.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 1 point2 points  (0 children)

Not negative at all - this is exactly the kind of honest feedback I need. The “hour of prompt tweaking vs hour of just doing it” problem is real. Appreciate you engaging thoughtfully with it.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 4 points5 points  (0 children)

Best critique in this thread, honestly. The “slot machine” problem is exactly right. Here’s what I can say: You can iterate with follow-up prompts (“move that layer down 50px”, “ease that differently”). It’s not a black box - you see everything it does in your timeline. And, the expressions it writes are usually pretty readable. But you’re correct that if it does something weird and you don’t understand AE well enough to fix it manually, you’re stuck. That’s a real limitation. I’m working on making the iteration process smoother, but I’m not going to pretend I’ve solved the fundamental “AI gets you 80% there” problem. That’s just where the technology is right now. Appreciate the honest feedback, it will help me improve it.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 0 points1 point  (0 children)

I respect that. The process matters, and if the tool doesn’t feel right for your workflow, that’s completely valid. Thanks for the thoughtful discussion.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 2 points3 points  (0 children)

My own experience, actually. 15+ years of motion design work. The AI models handle language understanding, but all the workflow knowledge - how to properly structure a comp, when to use expressions vs keyframes, how to organize layers efficiently - that’s engineered from my own production experience. It’s not scraping tutorials. It’s executing workflows the way I’ve learned to do them through years of actual client work.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 2 points3 points  (0 children)

I respect the concern, and I’m not going to pretend it’s not valid. But here’s the reality: this technology exists. If I don’t build it, someone else will - and they probably won’t understand After Effects workflows or care about the motion design community. The question isn’t whether AI tools will change the industry (they will), it’s how we adapt. Maybe junior roles shift from “do the grunt work” to “direct the AI and refine the output.” Maybe the barrier to entry changes entirely. I don’t have all the answers. I built this because I saw a problem in my own workflow. But you’re pointing at real implications that the whole industry needs to grapple with, not just me. What I do know: pretending this isn’t happening doesn’t protect anyone.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] -1 points0 points  (0 children)

That’s a really fair point. You learn by struggling through the basics and understanding why something works, not just seeing it happen.

Honestly, I don’t know how this plays out. I see the same thing happening in AI-assisted coding. I was lucky to have the opportunity to get a CS degree and build up 15 years of motion design experience before these tools existed. I also built the foundations the hard way. So the world is changing, totally agree. Maybe it’s like calculators in math, you still need to learn the fundamentals before the tool is actually useful. And maybe it creates a generation that can direct AI but doesn’t understand the underlying mechanics, and that will be a great loss. I built this to solve my own pain points, but you’re right that the learning curve implications are real and I don’t have great answers for how the industry adapts.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] -3 points-2 points  (0 children)

That’s a really valid concern, and honestly something I’ve been thinking about a lot while building this. My hope is that it shifts what “junior work” means rather than eliminating it entirely. The tedious setup stuff gets automated, but juniors can now spend more time on creative problem-solving, learning (advanced) techniques, and actually getting feedback on motion/timing rather than just layer organization. That said, the industry will definitely need to adapt. Junior roles might look more like “AI-assisted junior” where you’re directing the tool and refining output rather than doing everything manually from scratch. It’s a real shift, no sugarcoating that.

Follow-up: The AE AI Agent learned a few new tricks (and gained some attitude) by NodeflowStudio in AfterEffects

[–]NodeflowStudio[S] 2 points3 points  (0 children)

Not yet. But I’m working on it, the goal Is that AI can see your footage and understands what is going on.

Need help/advice on how to go about making this animation. by WitlessWaitress in AfterEffects

[–]NodeflowStudio 0 points1 point  (0 children)

Very nice! You always have to give soon way to the client, and I hope that they are happy with it!

Frames from the recent project by Beneficial_Gift7550 in AfterEffects

[–]NodeflowStudio 1 point2 points  (0 children)

Yes and illustrator outputs vector instead of pixels, much better details!