Pipeline
Frame.io
On the web
Link a card to Frame.io and every cut your editor uploads there arrives on the card as the next version, with the comments on it as notes at their second. Replies go back, and approving in either place approves in both: the approved cut lands in Projects, ready to schedule. You and the client never leave MORR; the editor never leaves Frame.io.
Not captured yet
This picture is taken from the running app, not drawn by hand. Run npm run docs:shots to take it.
pipeline-frameio.png
Set it up
- 1Connect Frame.io once, in SettingsSettings, then Integrations, then Connect Frame.io, and sign in with the Adobe account you use for Frame.io. It connects the workspace you have open, so everyone on its pipeline can link cards. Owners, admins and members can connect it; everyone in the workspace can see that it is connected and as whom.
- 2Open a card and choose Link Frame.ioIt sits at the top of the card's Review.
- 3Pick the project, then where in itLink the whole project, open a folder and Link this folder, open a version stack and Link this stack, or Link this file. The cuts already there come over at once, oldest first.
| You link | What arrives on the card |
|---|---|
| A project | The cuts at the top of the project, and the versions of any stack there. Folders inside it are left out; link the folder instead. |
| A folder | Every video and picture in it, and the versions of any stack in it. |
| A version stack | Every version in the stack, in the order they were uploaded. |
| A file | That file. |
What syncs
| From Frame.io to MORR | From MORR to Frame.io | |
|---|---|---|
| New cuts | The next version on the card, marked with Frame.io's logo. It plays right here. | A cut uploaded in MORR stays in MORR. |
| Comments | A note at the same second, under the author's name, with Frame.io's logo in place of a face. | A note you write on a Frame.io cut is posted there at the same moment, starting with your name. The note says Sending to Frame.io… until it is there. |
| Replies | Under the comment they answer. | Reply under any note. Frame.io's API cannot post a reply under a comment, so it arrives there as a comment at the same moment, naming who it answers. |
| Done | A comment marked done there is resolved here. | Resolving a note here marks its comment done there. |
| Edits | An edited comment updates its note. Notes from Frame.io are edited in Frame.io. | , |
| Deleting | A comment deleted there leaves the card. | Deleting a note you wrote here deletes the comment it posted. Deleting somebody's Frame.io comment here takes it off the card only. |
| Approval | Approved as the newest cut's Status approves the card. | Approving the card sets the newest cut's Status to Approved. |
Approve once
Frame.io keeps one Status for a file, not one answer per person, so Approved there stands for everyone the card asked: each approver's row is marked approved, with a note saying it came from Frame.io and who set it. A card that asked for no approval starts asking Anyone, and has its answer. The log shows it with Frame.io's logo: *Maya Chen approved this in Frame.io*.
The moment a card is approved, in either place, its approved cut is copied from Frame.io into Projects, in a folder named for the card, and plays from there everywhere, a client's share link included. The original comes over when it is 1 GB or less and Frame.io lets it be downloaded; otherwise Frame.io's high-quality copy does. It counts toward the month's uploads like any upload, and the card says so if they are used.
What does not sync
| This | Why |
|---|---|
| Drawings on the frame, and files attached to a comment | The words arrive; the drawing and the attachment stay in Frame.io. Open in Frame.io on the card is one click away. |
| Needs Review and In Progress | They are Frame.io's working states, not a client asking for changes, so they leave the card as it is. |
| Asking for changes in MORR | The note arrives in Frame.io; the Status does not change. |
| Taking a cut off Approved in Frame.io | The card keeps its approval. The next approval here sets Frame.io's Status again. |
| Folders inside a linked project | Link the folder you want, so a project's archive does not pour onto one card. |
How fast
Frame.io tells MORR the moment something changes, and the card catches up within seconds. If Frame.io will not send live updates for a workspace (the person who connected it cannot manage them there), the card says checked every couple of minutes and MORR looks that often instead. Check now looks straight away.
When something is wrong
| The card or Settings says | What to do |
|---|---|
| Frame.io isn't set up yet | Nothing on your side. MORR's Adobe app is still being registered; this turns on by itself. |
| Connect Frame.io in Settings | Nobody has connected this workspace yet. An owner, admin or member connects it once. |
| Reconnect | Adobe stopped letting MORR in: the sign-in was revoked or expired. Reconnect in Settings, and everything waiting goes over at once. |
| Didn't reach Frame.io | A note could not be posted. MORR tries again by itself; the reason is on the note. |
| Frame.io has downloads switched off for this cut | Turn downloads on for it in Frame.io, and approve again, or bring the file into Projects by hand. |
| Who | Can |
|---|---|
| Owners, admins and members | Connect and disconnect Frame.io, link and unlink cards, Check now. |
| Everyone in the workspace | Watch the cuts, read the notes, write notes and replies that go to Frame.io. |