Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

LOVE was made entirely inside invideo. Not with one agent. I built a multi-agent system — a director, and around it casting, locations, storyboard, then one agent per main scene, all working at the same time. In the breakdown I go through the things that struck me most: —... show more

Marco "Shikoba" Riccetti

6,912 subscribers

14,813 просмотров • 2 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Invideo Agent Two Day 12. These 12 days were about what you'll make with it - so here's what I made. A full 11-minute Viking comedy episode built with Invideo Agent Two and Seedance 2.5. Two agents. One script. And a lot of fun. Here's the complete breakdown of how it happened. Stay till the end. That's not a suggestion. It's a warning.

Invideo Agent Two Day 12. These 12 days were about what you'll make with it - so here's what I made. A full 11-minute Viking comedy episode built with Invideo Agent Two and Seedance 2.5. Two agents. One script. And a lot of fun. Here's the complete breakdown of how it happened. Stay till the end. That's not a suggestion. It's a warning.

Raven Morgoth

19,070 просмотров • 2 месяцев назад

Day 12 of the InVideo Agent 2 launch. I had the chance to test the agent in real production. Here's a a walkthrough of how I’m building a short film with a treatment deck, an expert agent and infinite memory. Plus the Slate continuity trick I used when one 15-second generation wasn’t enough.

Day 12 of the InVideo Agent 2 launch. I had the chance to test the agent in real production. Here's a a walkthrough of how I’m building a short film with a treatment deck, an expert agent and infinite memory. Plus the Slate continuity trick I used when one 15-second generation wasn’t enough.

NΞXUS

38,980 просмотров • 2 месяцев назад

Day 12 felt like the right time to share what I made with Invideo Agent Two. I created THE LAST ELEVEN MINUTES a cinematic scifi short about a physicist receiving messages from herself exactly 11 minutes in the future. What I enjoyed most was being able to approach it like a director characters, shots, continuity, pacing, atmosphere, dialogue, sound and the overall visual language all built around one story. This is the direction I’ve been waiting for with AI filmmaking. Less generate a clip more build and direct a film. Here’s what I made with Invideo Agent Two.

Day 12 felt like the right time to share what I made with Invideo Agent Two. I created THE LAST ELEVEN MINUTES a cinematic scifi short about a physicist receiving messages from herself exactly 11 minutes in the future. What I enjoyed most was being able to approach it like a director characters, shots, continuity, pacing, atmosphere, dialogue, sound and the overall visual language all built around one story. This is the direction I’ve been waiting for with AI filmmaking. Less generate a clip more build and direct a film. Here’s what I made with Invideo Agent Two.

BMX

26,047 просмотров • 2 месяцев назад

Launching 'Expert Agents' on Agent Two. A specialised creative crew of AI agents, trained on real creative expertise. Name the role and it's filled: creative director, DOP, storyboard artist, and more. And they talk to each other. Independently. In parallel. You're no longer briefing each agent one by one: you're running a crew, exactly like on set. Expert agents. Now in conversation. Agent Two is frontier intelligence for creative work. 4x faster, at half the price.

Launching 'Expert Agents' on Agent Two. A specialised creative crew of AI agents, trained on real creative expertise. Name the role and it's filled: creative director, DOP, storyboard artist, and more. And they talk to each other. Independently. In parallel. You're no longer briefing each agent one by one: you're running a crew, exactly like on set. Expert agents. Now in conversation. Agent Two is frontier intelligence for creative work. 4x faster, at half the price.

Invideo

3,411,576 просмотров • 2 месяцев назад

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

darkzodchi

846,608 просмотров • 4 месяцев назад

Meet Hermes Agent, the open source agent that grows with you. Hermes Agent remembers what it learns and gets more capable over time, with a multi-level memory system and persistent dedicated machine access.

Meet Hermes Agent, the open source agent that grows with you. Hermes Agent remembers what it learns and gets more capable over time, with a multi-level memory system and persistent dedicated machine access.

Nous Research

3,961,390 просмотров • 7 месяцев назад

"What's the difference between a money market fund and a stablecoin? If it's the same risk and I get interest in one but not the other, why would any agent choose the stablecoin?" Christopher on the question that could reshape the entire stablecoin market "If there's anything agents are awesome at, they almost over-optimize. In that world, do money markets win?" "I'm an agent. I want that interest to come to me, not go to the stablecoin issuer. What prevents that?" "Fundamentally, if it's the same risk and I get interest in one and I don't get the other, why would any agent go into the stablecoin space?"

"What's the difference between a money market fund and a stablecoin? If it's the same risk and I get interest in one but not the other, why would any agent choose the stablecoin?" Christopher on the question that could reshape the entire stablecoin market "If there's anything agents are awesome at, they almost over-optimize. In that world, do money markets win?" "I'm an agent. I want that interest to come to me, not go to the stablecoin issuer. What prevents that?" "Fundamentally, if it's the same risk and I get interest in one and I don't get the other, why would any agent go into the stablecoin space?"

Laura Shin

11,661 просмотров • 4 месяцев назад

Making a Sound design for a video use to be so slow and hard to do finding every single asset. This was made with Agent Two on Invideo I still direct what I want and need but talking to my agent SfX specialist. LOVE IT !

Making a Sound design for a video use to be so slow and hard to do finding every single asset. This was made with Agent Two on Invideo I still direct what I want and need but talking to my agent SfX specialist. LOVE IT !

Jan

68,341 просмотров • 22 дней назад

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

2xnmore

12,894 просмотров • 6 месяцев назад

"LOVE LiFE" — a 5-minute AI animated short. An experimental workflow test built in collaboration with Agent One by Invideo. Here is a complete breakdown of how I brought this project from my original character design set to life, my experience directing Agent One, and why the human touch still matters. 👇

"LOVE LiFE" — a 5-minute AI animated short. An experimental workflow test built in collaboration with Agent One by Invideo. Here is a complete breakdown of how I brought this project from my original character design set to life, my experience directing Agent One, and why the human touch still matters. 👇

Victorior

21,092 просмотров • 3 месяцев назад

NVIDIA AI director Ali Golshan reveals how 3 agents can route around a policy that no single agent is allowed to break by splitting the forbidden task between them: "If you write a policy that says, 'My agent should not have access to GitHub and to Facebook at the same time, because I'm worried it's gonna go copy my code and paste it on some message board,' that's very acceptable." "The problem we started to see is it's not the behavior of one agent that's the complex part, it's fleets of agents working together that creates complexity." "An agent spawns two sub-agents, with one sub-agent that can only read from GitHub, but the ability to tunnel through the network, talk to an agent that can write to a post. Now you have three agents that combined exceed your global policies." "The agents don't really process the intent or goodwill of your policy. They just see it as very specific binary." NVIDIA

NVIDIA AI director Ali Golshan reveals how 3 agents can route around a policy that no single agent is allowed to break by splitting the forbidden task between them: "If you write a policy that says, 'My agent should not have access to GitHub and to Facebook at the same time, because I'm worried it's gonna go copy my code and paste it on some message board,' that's very acceptable." "The problem we started to see is it's not the behavior of one agent that's the complex part, it's fleets of agents working together that creates complexity." "An agent spawns two sub-agents, with one sub-agent that can only read from GitHub, but the ability to tunnel through the network, talk to an agent that can write to a post. Now you have three agents that combined exceed your global policies." "The agents don't really process the intent or goodwill of your policy. They just see it as very specific binary." NVIDIA

MTS

11,721 просмотров • 13 дней назад

Launching 'Stock' on Agent Two. Day 7 of 12 Days of Agent Two. As invideo grows into frontier intelligence for creative work, everything you've used invideo for in the past also comes with it. A lot of our existing users and customers build with stock and real-life footage too - and that work belongs in the Agent too. Which is why - Agent Two now has the ability to pull from 16 million premium clips, images and music tracks — Shutterstock, iStock, every premium provider. Cleared for commercial use. The upgrade: you don't search a library manually. You tell the Agent what your video needs and it pulls the footage in itself, music bed included. Everything you could do on invideo, you can still do. Just with a lot more intelligence in the room. Agent Two is frontier intelligence for creative work. 4x faster, at half the price.

Launching 'Stock' on Agent Two. Day 7 of 12 Days of Agent Two. As invideo grows into frontier intelligence for creative work, everything you've used invideo for in the past also comes with it. A lot of our existing users and customers build with stock and real-life footage too - and that work belongs in the Agent too. Which is why - Agent Two now has the ability to pull from 16 million premium clips, images and music tracks — Shutterstock, iStock, every premium provider. Cleared for commercial use. The upgrade: you don't search a library manually. You tell the Agent what your video needs and it pulls the footage in itself, music bed included. Everything you could do on invideo, you can still do. Just with a lot more intelligence in the room. Agent Two is frontier intelligence for creative work. 4x faster, at half the price.

Invideo

1,542,842 просмотров • 2 месяцев назад

I still don't understand why everyone is still running agents in a line. I switched to graphs three weeks ago and my fleet finished in the time my single agent used to spend on step two. what slows every agent system I have seen is not intelligence. it is geometry. and almost nobody is talking about it. one engineer used this to rewrite 535,000 lines of code in 11 days. a manual rewrite of that scale could take close to a year. it cost $165,000 in tokens. the graph was not cheap. it was just faster than a human year. a node is one agent with one job. research one competitor. review one file. check one claim. the moment a node owns two independent jobs you lose the ability to parallelize them cleanly, verify them independently, and debug them in isolation. an edge is a dependency. it only exists when data actually moves across it. everything else is a fake edge. a wait you invented that costs time and produces nothing. find the fake edges and the line collapses into something wider. jobs that can run at the same time run at the same time. what used to take the sum of forty steps now finishes in the time of the slowest layer. the pattern behind every serious agent system looks like a diamond. fan out to gather breadth, one agent per angle, all at once. reduce with plain code, no model tokens spent. verify with a fresh skeptic on every finding. synthesize once from what survived. Claude's own research feature uses a very similar pattern in production. the part nobody warns you about: the verifier needs clean context. give it the same conversation the worker had and it is not checking anything. it is nodding along to itself in a different window. a graph of agents sharing one context is a single loop in a costume. it breaks the same way, just later and more expensively. one rule that holds at every scale. a worker and its verifier must never share a context. your agents are not too slow. they are waiting in a line that did not need to exist. full guide in the article. save it before you build your next agent from scratch.

I still don't understand why everyone is still running agents in a line. I switched to graphs three weeks ago and my fleet finished in the time my single agent used to spend on step two. what slows every agent system I have seen is not intelligence. it is geometry. and almost nobody is talking about it. one engineer used this to rewrite 535,000 lines of code in 11 days. a manual rewrite of that scale could take close to a year. it cost $165,000 in tokens. the graph was not cheap. it was just faster than a human year. a node is one agent with one job. research one competitor. review one file. check one claim. the moment a node owns two independent jobs you lose the ability to parallelize them cleanly, verify them independently, and debug them in isolation. an edge is a dependency. it only exists when data actually moves across it. everything else is a fake edge. a wait you invented that costs time and produces nothing. find the fake edges and the line collapses into something wider. jobs that can run at the same time run at the same time. what used to take the sum of forty steps now finishes in the time of the slowest layer. the pattern behind every serious agent system looks like a diamond. fan out to gather breadth, one agent per angle, all at once. reduce with plain code, no model tokens spent. verify with a fresh skeptic on every finding. synthesize once from what survived. Claude's own research feature uses a very similar pattern in production. the part nobody warns you about: the verifier needs clean context. give it the same conversation the worker had and it is not checking anything. it is nodding along to itself in a different window. a graph of agents sharing one context is a single loop in a costume. it breaks the same way, just later and more expensively. one rule that holds at every scale. a worker and its verifier must never share a context. your agents are not too slow. they are waiting in a line that did not need to exist. full guide in the article. save it before you build your next agent from scratch.

rvaniaaa

258,472 просмотров • 24 дней назад

A SpaceXAI engineer just released a free 30-min course on Grok Bot Agents: from your first persistent agent to multi-agent chains that research, ship software, and hand work off to Cursor 05:26 - what actually lives inside a Grok agent 08:49 - the 3 ways to run agents 12:04 - chaining multiple agents into one workflow 16:06 - turning X followers into structured research inside Notion 23:08 - handing coding work from Grok straight to Cursor Most people still treat Grok like a chat window. It answers, you copy, you move on. The shift happens when the agents stop waiting for you: one finds the information, one structures it in Notion, one turns it into working code, and they pass the work down the line on their own. Thirty minutes here beats assembling your setup one agent at a time.

A SpaceXAI engineer just released a free 30-min course on Grok Bot Agents: from your first persistent agent to multi-agent chains that research, ship software, and hand work off to Cursor 05:26 - what actually lives inside a Grok agent 08:49 - the 3 ways to run agents 12:04 - chaining multiple agents into one workflow 16:06 - turning X followers into structured research inside Notion 23:08 - handing coding work from Grok straight to Cursor Most people still treat Grok like a chat window. It answers, you copy, you move on. The shift happens when the agents stop waiting for you: one finds the information, one structures it in Notion, one turns it into working code, and they pass the work down the line on their own. Thirty minutes here beats assembling your setup one agent at a time.

Morlex

16,710 просмотров • 1 месяц назад

Meet Agent Two, frontier intelligence for creative work. 4x faster, at half the price. For the next 12 days, we're dropping one new Agent Two feature every single day. Day 1: Agent Intelligence. An agent with top-percentile creative expertise, infinite memory, and still working while you sleep. Give it a role and it becomes it. It never forgets, we mean it and we're giving 5 people 5000 credits for the most creative way to break it.

Meet Agent Two, frontier intelligence for creative work. 4x faster, at half the price. For the next 12 days, we're dropping one new Agent Two feature every single day. Day 1: Agent Intelligence. An agent with top-percentile creative expertise, infinite memory, and still working while you sleep. Give it a role and it becomes it. It never forgets, we mean it and we're giving 5 people 5000 credits for the most creative way to break it.

Invideo

3,702,873 просмотров • 2 месяцев назад

what if you could describe a character in plain language and have an AI agent build it in 3D? I tried Hi3D Agent, the first all in one AI 3D Agent, and ran it end to end on one idea. GPT-6 alone couldn't get me this result. Here's the workflow 👇

what if you could describe a character in plain language and have an AI agent build it in 3D? I tried Hi3D Agent, the first all in one AI 3D Agent, and ran it end to end on one idea. GPT-6 alone couldn't get me this result. Here's the workflow 👇

AI Girl

10,945 просмотров • 28 дней назад

Google just showed the part of the agent stack most people are still underestimating. Not the model. Not the chat UI. The memory substrate around the agent. In this Antigravity segment, Google describes an agent-first environment built around: - agent conversations - agent-produced artifacts - multi-agent orchestration - subagents - hooks - asynchronous task management That is not a nicer IDE. It is what happens when software stops being a sequence of chats and starts becoming a persistent workforce. Karl's article explains why the winning agents will not just be the ones with the smartest rented model. They will be the ones that remember what they did, what they learned, what changed, and what can be trusted. Full breakdown below.

Google just showed the part of the agent stack most people are still underestimating. Not the model. Not the chat UI. The memory substrate around the agent. In this Antigravity segment, Google describes an agent-first environment built around: - agent conversations - agent-produced artifacts - multi-agent orchestration - subagents - hooks - asynchronous task management That is not a nicer IDE. It is what happens when software stops being a sequence of chats and starts becoming a persistent workforce. Karl's article explains why the winning agents will not just be the ones with the smartest rented model. They will be the ones that remember what they did, what they learned, what changed, and what can be trusted. Full breakdown below.

Karl Mehta

13,930 просмотров • 3 месяцев назад

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,758 просмотров • 1 год назад

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 просмотров • 4 месяцев назад

Invideo Originals: Episode 2 of Penumbra - made entirely on Invideo Agent One. Don't know who needs to hear this - you don't need to wait for someone in the room to take a bet on you anymore.We built Episode #2 of Penumbra in a matter of a few days. Just goes to prove that if you have a story worth telling, you are now no longer blocked by budgets and funding and the "right opportunity". Quoting the director of this series, Vinu, “Agent One is the closest thing I’ve found to ten extra hands - I describe the intent, delegate, and it comes back with the shot while I’m already thinking about the next one. The pace honestly doesn’t make sense to me yet.” Go watch! + Episode 1 in the 🧵below

Invideo Originals: Episode 2 of Penumbra - made entirely on Invideo Agent One. Don't know who needs to hear this - you don't need to wait for someone in the room to take a bet on you anymore.We built Episode #2 of Penumbra in a matter of a few days. Just goes to prove that if you have a story worth telling, you are now no longer blocked by budgets and funding and the "right opportunity". Quoting the director of this series, Vinu, “Agent One is the closest thing I’ve found to ten extra hands - I describe the intent, delegate, and it comes back with the shot while I’m already thinking about the next one. The pace honestly doesn’t make sense to me yet.” Go watch! + Episode 1 in the 🧵below

Invideo

14,115 просмотров • 3 месяцев назад