106 karma · joined September 1, 2020
That being said, the coolest part with this Rough Cut was that it decided to stand in the footage of the kite to creatively imply the freefall portion of the skydive (because we aren't able to record while we're jumping out of a plane). This ability for it to creatively decided to imply the jump because of the limited footage is what I wanted to get across here.
We also do transcoding of all uploaded files to lower-res proxies, which can be re-linked when brought back into a more traditional NLE.
for example, if you have a workflow setup to create 5 clips from a podcast and add b-rolls and captions and reframe to a few different aspect ratios, any time you invoke this workflow (regardless of which podcast episode you're providing as input), you'll get 5 clips back that have b-rolls, captions, and are reframed to a few different aspect ratios
however, which clips are selected, what b-rolls are generated, where they're placed — this is all non-deterministic
you can guide the agent via prompting the tiles individually, but that's still just an input into a non-deterministic machine
same with returning that back to the user as manipulated output (text / code generation is much more rapid than rendering a video)
Video is hard, but it's also a fun modality which presents some interesting challenges. And is where content is converging towards.
we don't yet support that volume of footage (1TB), however if you'd like to try this at a smaller scale, you can already do this today with the Rough Cut tile — simply prompt it for the moments that you're interested in (it can take visual cues, auditory cues, timestamp cues, script cues) and it will create an initial rough cut or assembly edit for you.
I'd also recommend checking out the new Motion Graphics tile we added for animations. You can also single-point generate motion graphics using the utility on the bottom right of the timeline. Let me know if you have any questions on that.
if our goal is to bring more people into the fold, minimizing the steps for them to start editing is something we want to optimize for
that being said, being on the browser presents its own set of challenges, many of which are rightfully mentioned in this thread
it does present its own set of challenges, but something we've thought about
we've actually found that multimodal models are surprisingly good at maintaining temporal context as well
that being said, there's also a bunch of additional processing using more traditional CV / audio analysis we do to extract this information out as well (both frame-level and temporal) in your video understanding
for example, with the mean-motion analysis — you can see how subjects move over a period of time, which can help determine where important things are happening in the video, which ultimately can lead to better placements of edits.
they're very powerful, when you put them together, it almost feels like Cursor for Video Editing
our original name was Frame, only to realize that frame.io existed already.
we brainstormed names for a while and had several notes full of possible names
mosaic is one which stood out to us because it not only represents artwork, but also the tiles (nodes) in the canvas come together to form your mosaic — we thought that was a fitting name
we're using a mix of out-of-the-box multimodal AI capability + traditional audio / video analysis techniques as part of our video understanding pipeline, all of which become context for the agent to use during its editing process
how did you find the chat-first interface to work out for video? what we found is that the response times can be so long that the chat UX breaks down a bit. how are you thinking about this?