T. Payton
Forum Replies Created
-
Gearald,
Check out this thread too:
https://forums.creativecow.net/thread/344/9165
– T.
——
T. Payton
OneCreative, Albuquerque -
That should work just dandy. The difference between FCP legacy and FCP X is that FCP Legacy could only access a small amount of RAM. So 4 GB of RAM was just dandy in legacy. FCP X is in the 64bit world and will try to use as much RAM as you got. So 4 GB of RAM is really pinching it.
Also the graphics card is nearly everything in FCP X. An old machine with good graphics card works well, but a new machine with a cheesie card would not be good.
——
T. Payton
OneCreative, Albuquerque -
What year is that iMac?
——
T. Payton
OneCreative, Albuquerque -
The video card will be the deciding factor.
Here is some info:
https://support.apple.com/kb/HT4664
And yes you will need to up the RAM. I would just max it out. Probably only $100.
As far as is it work the $300 for FCP. Download the trail and give it a go.
https://www.apple.com/finalcutpro/trial/
——
T. Payton
OneCreative, Albuquerque -
[John Heagy] “Events shared out via AFP with sparse images
Avoiding the magnetic timeline by placing down a single slug.”
If they had a XSAN they wouldn’t have to use sparse disk images, but because of it it makes a nice container for archiving, and transport.
I believe the comment about not using the primary storyline was just for that type of project. I believe he clarified it at the end.
We have to admit that the Final Cut team has not yet addressed collaborative editing. However, based on their track record of innovation of FCP, I’m sure what they come up with will be excellent and in line with MultiCam, Roles, etc. I think this video series shows that even as it stands now FCP X can work in a shared environment pretty well.
BTW I’m still working on that tutorial to show RED, proxy media with multiple editors, but I’m slammed with work at the moment. Sorry it is taking a while.
——
T. Payton
OneCreative, Albuquerque -
I don’t have the tutorial finished yet, but this is a rather extensive “walkthrough” of how shared media can work with FCP X:
This should be very helpful.
——
T. Payton
OneCreative, Albuquerque -
Elliot,
This is actually a similar workflow to what we have at our office. 2 editors sharing media and projects. It really only takes a few minutes to setup once you understand the concepts and the potential gotchas. I’m trying to put together a video/ write up on how to do this and post it as a tutorial here but it will take a few more days to pull it together. If you need immediate help, you can contact me through my company web site.
onecreative.net
——
T. Payton
OneCreative, Albuquerque -
I’ll see what I can do. BTW, this might be useful to check out from Ripple Training:
FCPX – Media Management & Collaboration
——
T. Payton
OneCreative, Albuquerque -
I’m probably making it sound more complicated that it is. The workflow is actually the same as it would be in FCP 7 with the exception of how events/projects need to be duplicated in FCP X opposed to in the Finder.
The fellow who showed me XSAN and FCP X actually said he thought it was better in FCP X than it was in 7.
Agreed that Apple can make it better because there isn’t really a cooperative workflow in FCP X yet.
Hit me up with any questions.
——
T. Payton
OneCreative, Albuquerque -
I think I can help. However, although I should state that while I was briefly trained on XSAN and FCPX by an XSAN guru, I don’t run an XSAN myself at my office. Therefore this is based on testing I have done on my system, but the principles are completely transferable to XSAN.
This is actually fairly straight forward if you keep everything well organized. The key would be never copy your footage to a FCP X event that will be used for editing, and therefore always use “symlinks” to your footage on your XSAN.
First organize your 5K footage and your Proxy Footage in separate folders on a location in our XSAN ** (see note below for some options) then begin by importing your project into a single “master” Event. Organize this master event as much as you would like for a starting position for the editors. Then duplicate the event 2 times, command-D, (one for each editor) and copy manually in the finder to a XSAN location. Then each editor would add that XSAN location in FCP X to store their event and project. Make sure the events and projects have unique names. You editors can now edit freely, adding favorites, notes, etc. to their particular event.
Once their editors are done, manually copy all the events & Projects to a single SAN Location so they are all in the same Event and Project folder. (Make a backup copy of the projects & events before hand). Then with that “master” SAN location set in FCP X, combine your timelines as necessary. When you are happy with the results you can relink to your 5K R3d in all three events quickly. To do this make another backup of your events & projects and then command click and select all three events and choose File > Relink Event Files and choose all to relink to your R3D footage. If the proxies are named correctly it should find all your R3D files quickly. Ensure that your timeline is the correct resolution and you should be good to go.
** Note about proxies. While possible, it would be quite tricky to use the built in Proxy functionality of FCP X to switch between full resolution and proxies. It would involve a rather complicated process of creating symlinks in your event/Transcoded Media/Proxies. But you could create a “Ingest” Event that would hold your original footage and create proxies too. For this ingest event you would “Copy clips to Final Cut Event Folder”. The event would then be a well organized place for your r3d files (in “event name”/Original Media”) and your proxy files (in [event_name]/Transcoded Media/Proxy media). You could even add additional footage to this ingest event after editing begins. This ingest event would not be the event you duplicate for your editors, it would simply organize your media and create your proxies. You can get an idea of how this would work here:
https://images.apple.com/finalcutpro/docs/Final_Cut_Pro_X_Xsan_Best_Practices.pdf
I hope this helps. Run some tests and see if this works for you.
——
T. Payton
OneCreative, Albuquerque