Loading video...

Video Failed to Load

Go Home

Revisited an old ogre concept as a pre-production visualization exercise. Built key images in Photoshop, brought them into motion in Firefly Boards, added facial animation from my own performance. A great way to see ideas move earlier and better inform what comes next.

57,316 views • 7 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

On Figma Motion, my demo & review. This is one of those updates that clicked swiftly into my workflow. Like in my 3D pipeline, using this stick shift animation, I emphasize hardware feedback with motion from Figma Motion. Assets are animated in Fig Motion and loaded into Blender as video textures for mesh and material control. It's advantageous since it is built into an ubiquitous ecosystem. A lot of work these days start in Figma even for someone like me that works outside the tool frequently. Can't over-emphasize my appreciation for the schema used to introduce motion to nearly all properties. Reminds me of how motion works in Blender - with better complexity management. Better than introducing more menus for those. Ease curves iD between keyframes is also an improvement over existing systems. Having spent some time on the tool, here are updates I'll like to see to Figma Motion. These are based on my immediate needs as at the time of working on this demo: • Using modifier keys (CMD, Shift, Ctrl) to jump / nudge across the timeline. E.g: holding down Shift key to make the playhead jump 100ms etc. • Jump to previous or next keyframe. • Better anchor point trails • Renaming layers from the timeline as well. • Editable custom bezier styles: after saving a style, I should be able to edit the curve - just as you can edit colour styles. • Enable transform on the timeline. I should be able to flip or scale keyframes. I hope to continue trying more ideas. Craft focused tools have had to take a backseat in recent times. Pleasing to see this come to light.

seyi

28,910 views • 29 days ago

.Google Cloud killed its own opening video 3 weeks before Google Cloud Next. In rehearsals, VP of Marketing Sarah Kennedy Ellis looked at the opener her team had built and called it. It was using AI, but not enough of it to actually showcase what the product could do. So they rebuilt it from scratch. In 3 weeks. Here's how it came together, straight from her SaaStr AI 2026 session: - It started on a napkin. A creative director sketched the concept by hand, then fed it into Nano Banana to generate the source images and inspiration. - The story was Google's own history. The 1998 origin garage. Dino. The original server rack that was actually built out of Legos. 138 Easter eggs packed into the video, prompted from Google's own lore. - Then they added motion with Veo and stitched it all together with a few custom agents built on the Gemini Enterprise platform. - The agents improvised. They prompted for balls representing customers, and the model added a burst of water that was nowhere in the brief. It injected its own creativity into a physical, on-stage moment. - The hardest part was the most physical: resolution. Max output was 4K. The screen at Next is the size of a 737. They had to upres from 4K to 12K using a custom Deep Mind model, the same one used for the Wizard of Oz production at the Sphere. Top Takeaways: 1️⃣ The old version of this project needed an agency, a much bigger budget, and a lot more than 3 weeks. That whole path collapsed into an internal team using their own tools. 2️⃣ And the same video was impossible a year earlier. They tried similar work the prior year and it was too early, mostly because of the upres wall. Twelve months later it shipped on the biggest screen they had.

Jason ✨👾SaaStr.Ai✨ Lemkin

18,773 views • 25 days ago