Prototype media studio
Prove one repeatable media workflow before we sell anything.
Irie Media Studio is a working prototype for testing whether proof, screenshots, clips, and notes can become a useful package without losing source context.
Start from the way the work arrives.
Start fresh, import a Studio project JSON, or bring in a Pam / Video Studio promo bundle. Each path still has to prove that it creates a useful package.
Blank project
Start the first real proof run by hand and see where the workflow breaks.
Studio project JSON
Reopen an exported project and confirm the handoff can survive a round trip.
Promo bundle
Bring in a .iriepromo.json and verify the imported context still makes sense.
A proof workflow, not a prompt box.
The prototype should prove the boring-but-important parts first: asset safety, source context, timeline timing, captions, cleanup history, package validation, and export files.
Mark what is public-ready, crop-first, blur-first, internal-only, or discard.
Set the goal, audience, proof, CTA, constraints, and do-not-show rules.
Turn the brief into hook, proof, human angle, action, captions, and pacing.
Block unsafe clips and layers before anything ships publicly.
Download the files and verify another human, agent, or render worker can understand them.
FAQ
Plain answers.
Media Studio is still being proven. The job now is to make one real package work before expanding it.
What does Media Studio make?
It is meant to help turn proof, screenshots, clips, and notes into storyboards, timelines, captions, render notes, and export packages. We still need real runs to prove it.
Do I need another Irie product to use it?
No for prototype use. Start with a blank project first; integrations should only count after they create real projects end to end.
Who is it for?
Right now, Corey and trusted Irie collaborators testing whether this can become a repeatable production workflow.