-
Sharing
-
[James Ewart] “Does this really mean that 200 editors can be accessing the sam file for their edits concurrently? And all play back a timeline with a clip from that file in their timelines at the same time?”
Yes! That is exactly what that means. Media lives in ONE location. Anyone with access to the system can use that media AT THE SAME TIME. No copying, no moving, just find it and use it.
EVERYTHING that we do uses more than one editor. At the very least we have an editor and an assistant editor collaborate on a cut. More likely, it is 20-25 people all collaborating on a cut, an episode, a series. So, while most people debate the merits of the “X” timeline, or 4K resolution, I focus on shared workflow. This latest change in “shared libraries” is a step in the right direction, but there’s quite a long journey ahead for anyone to deploy “X” at scale.
-
I am struggling to get my head round that. Instant? No buffering or delay like on Sky Movies or planes?
The editors can all rename these clips in their “bins” without affecting the names of the original files?
(FCP 7) was really annoying with this. X does not seem to care what you call the clips in your bins/events.
-
[James Ewart] “No buffering or delay like on Sky Movies or planes?”
No delay.
Seriously. Click and play.
RE: Renaming. AVID allows for renaming, since it maintains it’s own internal database to keep track of every object as a unique item. However, from a practical POV, we do NOT allow editors to do that. It would simply be too confusing for other team members to find something. Therefore, we maintain a logical naming system such as 1225A01CC = (Translation: December 25, A cam, 1st load, Creative Cow).
If you want to rename a clip “swish pan to CU”, then put that in the notes column! -
What If I have already made a note in the column for that clip like “swoosh to CU – VG”?
Could I personalise it? Or do my log notes get transposes onto the data of the original clip with Avid?
Who gets to do the original log notes?
Because it seems with FCP X it does not matter if I rename the clip it does not affect its name of the original clip in the “Library”.
Hope that question is not banal.
-
[Mark Raudonis] “Yes! That is exactly what that means. Media lives in ONE location. Anyone with access to the system can use that media AT THE SAME TIME. No copying, no moving, just find it and use it.”
To be fair, all major NLEs can do this, including FCPX. We do it all the time.
That’s not the tricky part. The tricky part is seeing what everyone else is doing and being able to use parts of their projects and have them update in real time. Or giving back write permissions so someone else can take over from where you left off.
Currently, Avid wins in this regard, although Lightworks has some capabilities too.
-
[Mark Raudonis] “Therefore, we maintain a logical naming system such as 1225A01CC = (Translation: December 25, A cam, 1st load, Creative Cow). If you want to rename a clip “swish pan to CU”, then put that in the notes column!”
The importance of proper clip naming conventions cannot be stressed enough. Because of adhering to strict naming conventions I am able to get a lot more power out of the sorting and search features in FCP7. This is one of the reasons I prefer the Aja Ki-Pro to all other digital recorders – it has master control software that enables comprehensive clip naming during production over multiple recorders.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Almost every NLE creates little tiny cache files, even Avid, even FCP7.
You can stripe your array to help with this process, and our SAN has adjustments that you can make per client for help with this if it ever becomes a problem. It hasn’t been a problem for us. Pr used to give us fits with it’s constant caching, but an update to Pr solved it.
With FCPX, you don’t have to keep the files on the SAN if you don’t want to. Moving things around is very very easy.
Every new mac with PCIe storage, regardless of CPU/GPU/Computer power or form factor, has storage that is probably faster than all but the fastest of RAIDS. That sharing PDF that is floating around mentions this.
This means that, for the first time, the SAN is actually the ‘bottleneck’ in terms of throughput. This, of course, presents new ways of working and perhaps new ways of thinking about what and where media needs to be, and how a team accesses media.
You don’t have to believe in what Apple seems to be doing, but in my mind, these aren’t half baked ideas despite FCPX not having this capability at launch.
-
[James Ewart] “What If I have already made a note in the column for that clip like “swoosh to CU – VG”?
Could I personalise it? Or do my log notes get transposes onto the data of the original clip with Avid?”
Avid rights and permissions are bin-based. On the hard drive the “project” is really just a folder with .avb files which represent the various bins in the project. As one editor accesses a bin by opening it, they lock the other editors out and retain the only means by which to write to that bin. All other editors can view the contents of the bin and even use the clips inside to continue editing, but they can’t save any new clips to that bin or rename anything.
The owner of the bin however, can do both. If they injest a new clip to that bin or rename an existing clip, it will show up to other editors after the owner has saved the bin. Once you close a bin, you lose the lock and the next editor to open it will have permission to make changes.
How this translates to a workflow: Editors who work on the same show typically work on sequences which represent a block or “act” of a show. Each sequence is usually in a separate bin because otherwise only one editor would be able to make changes to those sequences. Editors also typically create their own folders inside a project to organize bins specific to how they like to work. That way, if you needed to organize some clips into a particular order, you’d create a custom bin for that which would live in your folder for easy access. This keeps editors from messing around with the organized bins in a project which contain the main media for editing. That stuff was already organized by the AEs and shouldn’t be touched or changed by individual editors because it could screw everyone up.
Andy
https://www.timesavertutorials.com
-
Thanks I’m just wondering what options the 200 different editors have for personalising the clips they see in their bins with Avid without affecting the original media file logging notes?
-
It looks like it will work for me well. Two editors and one or two assistants.
Reply to this Discussion! Login or Sign Up