-
A Question for Working Professional Editors Using FCPX.
-
[Richard Herd] “I was thinking if two editors were editing the same thing. (Mike is working on audio and Mari is working on picture.)”
Just like FCP7, you can’t work on the same project at once without consequence.
Each would need their own Project but could reference the same media.
Jeremy
-
What about avid and or premiere?
-
[Aindreas Gallagher] “there you go see? – someone who actually honest to God knows what they are talking about.”
Yeah, I’m going to quote Andrew, just so people think I’m smart.
Unattributed of course. -
[Richard Herd] “What about avid “
Avid has a project sharing system, it’s one of it’s strengths, but it’s not cheap. There are cheaper ways to do it on more generic storage, but everyone says the ISIS system is rock solid.
Premiere will be just like FCP7, which is a lot of manual work, but it does not allow same project level collaboration.
Of course, there’s third parties like Editshare that help with this process as well, which I’m sure means that LIghtworks will probably hook in to their system fairly easily. metaSAN v5, which was recently released, also has some project sharing tools, but I haven’t had a chance to check them out.
Jeremy
-
[Jeremy Garchow] “We use metaSAN which is file based, so that might have something to do with it. It also works over ethernet as well. I have not tried it on volume level as it’s not how it’s setup over here.”
I’ve been trying to get a definitive answer on this, and have yet do do so. From what I can tell, FCPX is discriminating by filesystem. metaSAN is not its own filesystem like Xsan, but rather a shared HFS+.
One thing is for sure, SAN Locations are very poorly documented, especially in terms of technical requirements.
Best,
Andy -
[Andrew Richards] “but rather a shared HFS+.”
It gets weirder, our storage is actually NTFS.
It’s a windows “all in one” box with CPU/storage served out via fibre in a chassis.
metaSAN handles all the translation.
Jeremy
-
[Jeremy Garchow] “It gets weirder, our storage is actually NTFS. “
Well damn, now I haven’t even got a hypothesis.
Best,
Andy -
[Jim Giberti] “Unattributed of course.”
well, that goes without saying..
https://vimeo.com/user1590967/videos
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
Jeremy, the Dumb and Dumber (1994) clip is absolutely GOLD.
[Bill Davis] Most of the “here’s how this works” stuff takes place next door in the FCP-X Techniques forum.
Totally understand, however wasn’t the original post about “how to or how do”…?
[Kevin Zimmerman] “My question is pretty simple, and it’s intended for editors who are working with FCPX in a professional work environment, for paying clients.
How do you deal with the one edit per project architecture of FCPX? I think there are many, many issues to spiral out of control over with FCPX, but this framework that Apple is created — where a project IS a single timeline, and therefore IS a single cut — baffles me. And I have no idea how I would work around it.
The idea that, with clients in the room asking to see a subtle difference between two versions of an edit (“here’s one that starts with the wide, here’s one that starts with a medium,” that kind of thing), I need to actually click between different PROJECTS is just… well, I find it laughably useless.”
Makes me laugh how sidetracked this post has become.
Anyway since Kevin hasn’t been back to ask further questions, I think I’ll just sit back and enjoy where this post has headed 🙂
All the best to all.
-
[Bill Davis] “This space is largely for arm wrestling, rambling screeds and low grade, seldom serious character asssasination.”
Can we have this as a subtitle for this forum please mods? It sums us up soooo well 😉
_________________________________
Before you criticise a man, walk a mile in his shoes.
Then when you do criticise him, you’ll be a mile away. And have his shoes.*the artist formally known as Jaymags*
Reply to this Discussion! Login or Sign Up