-
FCPX and very occasional lag.
-
[Jeremy Garchow] “collaboration in FCPX is no good”
I think the potential for collaboration in X is just fine, especially with some of the stuff John has shown. Its just not up to the industrial strength that ISIS can bring, but far fewer people need that.
I DO have to say that Bin sharing in Avid has been a delight for me, and I wish more NLEs allowed me to put together such a nice portable kit that I could then consolidate for others. Its really handy. When I was last using Avid before this re-up, portable storage wasn’t even part of the picture.
-
I am still working off of internal SATA drives in a 2006 MacPro 1,1, 12GB RAM, and a 5770. …I’m hoping for a new MacPro but should probably just buy an iMac.
I definitely have to occasionally render certain things in the timeline, and also transcode to prores or prores proxy for certain source codecs, but I can’t say that I encounter sluggishness all that much.
Now that I have gotten used to the built in CC I don’t find myself needing 3rd party CC plugins all that much.
I agree with John; as much as I love After Effects, it really is time to learn Motion fully.
-
[Chris Harlan] “I think the potential for collaboration in X is just fine, especially with some of the stuff John has shown. Its just not up to the industrial strength that ISIS can bring, but far fewer people need that. “
True. And i may be repeating a post I made in another thread here… But previously, duplicating a project + used clips, or duplicating an event, copied all the original source media to the duplicate… even if the original project/event was using referenced media. This made the duplicates A-gigantic, and B-broke all connection to shared media. This sucked . :-/ However, As of .08 that’s no longer the case, it will just copy the symlinks. Huge improvement that facilitates basic bay to bay project sharing – pretty much just like duplicating a project in 7 and handing it to someone else. Getting there…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “True. And i may be repeating a post I made in another thread here… But previously, duplicating a project + used clips, or duplicating an event, copied all the original source media to the duplicate… even if the original project/event was using referenced media. This made the duplicates A-gigantic, and B-broke all connection to shared media. This sucked . :-/ However, As of .08 that’s no longer the case, it will just copy the symlinks. Huge improvement that facilitates basic bay to bay project sharing – pretty much just like duplicating a project in 7 and handing it to someone else. Getting there…
“Thanks, I hadn’t realised that had been fixed
Steve Connor
There’s nothing we can’t argue about on the FCPX COW Forum
-
[Steve Connor] “Thanks, I hadn’t realised that had been fixed”
Me neither, Saw it on Alex4d’s blog the other day and tried it out. Very nice, and very useful fix.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Jeremy Garchow] “Yeah, but it’s weird when people say the collaboration in FCPX is no good, when in fact, it works OK if you know how to use it,”
I’m not sure I agree there. Collaboration is all about project sharing. There are way more workarounds with X than with “legacy” or PPro. None are as good as Avid Unity/ISIS/Interplay or apparently Lightworks. I think there’s still a lot of work to be done.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
We had these lags until it was discovered that the Mac Pros we booting in 32 bit mode. Just a thought.
-
[Oliver Peters] “There are way more workarounds with X than with “legacy” or PPro. None are as good as Avid Unity/ISIS/Interplay or apparently Lightworks. I think there’s still a lot of work to be done.”
While i agree with your assesment of Avid etc, I think that with the fix I mentioned above, it’s now pretty much on par with FCP Classic, with a couple added steps. I guess one can already do full Event/Project sharing with X using SAN locations/Sparse disks, though that belief is based on others experiences rather than my own. But as far as handing sequences back and forth in a centrally shared media environment (if files are local it’s a problem, but it would be in Classic as well), It seems like it’s pretty much the same.
In Classic to share an entire project just duplicate it and give the duplicate to the other editor who opens it and goes on their merry way. To share a sequence, make a new project, copy the sequence into it and hand the project off.
In X… .08 anyway… you can just duplicate the event, and hand it off. Editor 2 puts it in their FCP events folder, and opens it up. To share projects associated with that event as well, duplicate them. put them in a folder (all from within FCP X of course, not the Finder!), and give that to editor 2 as well, who puts it in their projects folder. 2 or 3 extra steps, same result.
To hand off a sequence, duplicate + used clips (no render files), hand off duplicate project and new “used clips” event. Done.
So, while not quite as idiot proof as 7, not wildly different now either… Unless I’m missing something.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “In X… .08 anyway… you can just duplicate the event, and hand it off. Editor 2 …… To hand off a sequence, duplicate + used clips (no render files), hand off duplicate project and new “used clips” event. Done.”
Agreed.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “I’m not sure I agree there.”
I said it was “OK”, not Avid Isis, and there’s a huge difference.
So you would say that collaboration in FCPX is not OK?
It doesn’t work like FCP7 (or Pr) at all.
Reply to this Discussion! Login or Sign Up