-
How is browser performance in FCP X on your machine?
-
This is exactly the performance hit stuff that through some old research I found was possibly tied in some part to the AVX Intel thing I mentioned before. It does not seem to be GPU/CPU relatable in terms of clock speed or cores alone. So in fact, my MBPr works much much better in this regard than my Nehalem MacPro does. I actually don’t even use it for FCPX editing. I export XML when im done from MBPr that is docked right beside and just use the MacPro for Resolve or whatever else.
The whole AVX thing could have nothing to do with it, but there is no doubt that there is something that makes the processor generation different in performance in current MacPros over newer stuff, even a mac mini frankly, just in terms of this type of performance.
Director, Editor, Colorist
http://www.trsociety.com -
[T. Payton] “I trying to scroll through a bunch of footage in filmstrip. Especially with my magic mouse trying to “flick’ up and down. It is painfully slow, jumpy and jerky.”
Hmm… I’m not seeing that here. Although, I typically only work with ProRes media (I do not believe in using native H264 camera files). Generally my clips are no longer than several minutes, since these are file-based recordings.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Yeah, I was going on the assumption that ProRes was being used. But thats def a no brainer, H.264 is terrible to edit with and should be avoided at all costs. FCPX makes the transcode process so easy theres almost no reason to consider it unless you literally had a one day turnaround or something.
Director, Editor, Colorist
http://www.trsociety.com -
Oliver,
This is what I am seeing on my end with ProRes footage. This event has 2100 clips:
https://www.youtube.com/watch?v=5twubw5-R50
——
T. Payton
OneCreative, Albuquerque -
Sorry for the double video on that last post. The preview on my post wasn’t showing the youtube embed correctly.
——
T. Payton
OneCreative, Albuquerque -
I’d say thats not odd behavior given the amount you are flicking through. If you change the thumbnail slider to be less representations over time that helps. But getting used to working in the clip name with film strip at top mode is what I’d recommend. You can flick through that with ease. and simple meta data additions could be inserted with keywords or columns to give you the same visual que of where your flicking too that the filmstrip achieves.
Director, Editor, Colorist
http://www.trsociety.com -
[Nicholas Kleczewski] “I’d say thats not odd behavior given the amount you are flicking through”
So you are seeing the same type of performance?
——
T. Payton
OneCreative, Albuquerque -
Yeah, I frankly don’t use that filmstrip view style ever. It does work better if you change the duration slider at the bottom to make less detailed views, but I never really found the advantage to it over seeing clip info with single film strip at top.
You could split the difference on the idea and drill down your raw footage with keywords and then when your flicking through, its a lot smaller version of the database to pull from and then you should get better performance. For instance, break up B-Roll by days or theme or location. Break out interviews, or whatever is simple. Then when you click that relevant keyword you are only pulling a narrow subset of all the events clips which should work a lot better.
Director, Editor, Colorist
http://www.trsociety.com -
Nicholas – are you on a MacPro also?
(BTW. From what all of you have said, this is looking like it is not a machine issue, but rather something with FCP X)
——
T. Payton
OneCreative, Albuquerque -
Ive run FCPX on just about every mac out right now sans the latest iMacs. I dont think what your running into is necessarily a machine or even FCPX limitation per se, you are attempting to do something there pretty unique. That is thousands of pictures, waveforms etc you are breezing through on any given flick. And its not the same as something like lightroom or Aperture in which the thumbnail never changes. Its a a dynamic process with every flick based on filmstrip length, whats around it, how big the window currently is, etc. So its a load on a whole other incalculable scale.
Im sure the engineers could thing of ways to improve that, but I can’t imagine it’d be any time soon. Also, solid state storage could help you in this regard. That little microsecond of delays your getting could be affected by read speeds, even if your on the fastest of fast affordable arrays, access time matters at the level your pinging large amounts of data here.
Director, Editor, Colorist
http://www.trsociety.com
Reply to this Discussion! Login or Sign Up