- January 16, 2021 at 2:30 am
That’s what I do frame.io. And if you cut the compound clip when you need to make the timeline shorter, all the edits stay in the right place, even though the sequence tc doesn’t match the compound clip/notes tc anymore.
- January 18, 2021 at 11:39 am
Frame io does offer some excellent features. My issue is that getting clients to buy in and learn the process has been a very mixed bag. Mostly people want ta vimeo link and that’s it. OTOH I did find a A short ripple video tutorial about revising with time code notes by replacing changed sections with gap clips, then using the time line index to identify and remove all gap clips once finished. This keeps the time code consistent with the notes while editing .
- January 18, 2021 at 2:12 pm
Love that option in frame.io 🙂
- January 18, 2021 at 2:13 pm
That’s odd, when you give the client a chance to make comments they jump at the chance all the time 🙂
I use Vimeo/YouTube if I don’t want them to chime in 😛
- January 27, 2021 at 4:39 pm
Hi Ben — working on avid here on longer form projects, but my best practice advice is to keep a folder of past versions of your sequence (v1, v2, v3, v4) and also notate when a version has been submitted to a client (v1, v2, v3 rough cut review, v4, v5, v6 fine cut review). That way you have backups of your interim edits, and also a record of exactly what edit the client reviewed. When going through client timecode notes, I can have the review sequence in the source monitor for timecode reference while I work on the new version. Since I’m often rearranging entire story bits, adding shots, removing shots, I can’t simply leave gaps in the sequence to preserve the timecode, so being able to jump back and forth between versions is essential.
- January 27, 2021 at 7:56 pm
Make a QT reference with the record timecode burned in before you make any changes. Then drop this QT reference onto a layer of your timeline and chop it up along with any changes you make. You can always SEE the previous timecode as it will be in the window burn of the QT reference.
- January 28, 2021 at 12:17 am
This has happened a few times – in retrospect I should have burned the time code
to the work in progress.
What I would do after making a few snapshots of the Project file,
I would go from the back forward, then the time stamps stay correct on the first pass thru.
It is stressful yet successful for me a few times.
- January 28, 2021 at 12:18 am
wow – some of that sounds like magic!
- February 4, 2021 at 2:09 pm
I do this daily, super simple.
First, Snapshot that project, then do not touch the snapshot version, just a good habit to get into.
Next, if you’re not using Frame.io, which I find invaluable (when the client finally gives in an goes along with things), place these revision notes into your project with Markers. “To Do” markers exactly. Then no matter what you edit, those markers are still in the exact place they need to be. Even if they shift in relation to timecode.
- February 4, 2021 at 2:39 pm
Do you know whether the free version of frame.io allow this, or will there be limitations?
Log in to reply.