-
FCPX user interface responsiveness
Some people have mentioned it can be an issue, but this seems pretty stark.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
18 Replies
-
[Aindreas Gallagher] “Some people have mentioned it can be an issue, but this seems pretty stark.”
It seems so… And I’m seeing it too, though not as badly as the video example, on my work system. Oddly, on my little macbook air at home, it runs ridiculously responsively. Admittedly, not the same type of project, but it’s like night and day.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
My test is working on native HDV footage, and occasionally some AVCHD.
I don’t optimize because of the time and the storage demands, since this is documentary and I immediately throw out 90% of the material, looking for the “moments.” THEN the selects can be optimized, proxy etc.
So working with the raw Long GOP is a good test. MBPr 13″, i7, 16GB RAM, 1TB SSD — in other words, their max package on the little laptop. Should be similar to your Air I think.
Thing rips along fine on single timeline, up to 30% connected clips and all audio detached, double-tracked, EQ effects added. Even with titles over the top, a little slow to render but then moves just fine.
But put just TWO of those clips in a multi cam and try to work, it all falls apart. Convert over to proxy, and it it’s fine again.
The SSD working with external drive (2TB or 4TB RAID, FW-via-TBolt adapter) seems to make a big difference, as this is already better performance than my theoretically faster 2012 iMac.
Doug D
-
I still find it to be much less beach ball prone than earlier versions. Sometimes things seem to lag a bit, but not beachball.
For instance, I can modify audio channel information much more easily (turn on and off components, and name them) for 80 clips much faster than before. That process would certainly cause a beach ball.
The same media on the same SAN over an Ethernet connection on a new retina MBP runs a bit better than a 2009 MacPro connected via Fibre. I am waiting patiently for JetPacPro.
I feel like these lags are waveform and thumbnail creation. If I find some lag, I usually trash those caches, and the next time they rebuild, there’s much less lag.
-
[Jeremy Garchow] “I feel like these lags are waveform and thumbnail creation. If I find some lag, I usually trash those caches, and the next time they rebuild, there’s much less lag.”
On my most recent project, working the event browser in the list mode was largely useless, because it was very slow in writing waveforms and the thumbnail when I selected any given clip. It was faster to work in the filmstrip (icon) view, because once all the clips were populated, you could quickly move from one clip to the next.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Not sure how this fits into the sluggishness spectrum, but… (long post)
I have a large project, which is to say several hundred clips in an event in the library. Video is Red files, 5k, 23.98. All footage has proxies, generated from within FCP 10.1.1 (some files generated as far back as 10.0.9). Audio files are .wav. Audio & video made into synchronized clips for editing. No problems marking and synching the files (other than cursing the DP for not shooting an audio guide track on the Red, so I had to synch them all manually -grr!).
Finally started editing. Using Proxies. MacBook Pro 15″ retina. 16 gig ram. mid-level CPU. Not the latest, but one rev back. Files on G-speed, Raid 0, via fibre card in a Sonnet Echo PCI to Thunderbolt box. Viewer on 2nd computer screen via HDMI. USB audio in/out.
For the first time with FCP X, I’m getting fairly regular beach balling. Doing a lot of trimming, especially expanding audio to overlap, then collapsing back. Beach balls mostly when doing the audio stuff, especially if I move fast. Actual behavior: start to pull the end of the clip, nothing happens, audio often plays a frame or two repeating for a couple of seconds, then the beach ball, then everything catches up and is fine. Total time elapsed, less than 10 seconds. (Which seems like an eternity when I’m trying to finesse a cut.) Then all is well for at least several minutes. Then, seemingly at random, the lockup & beach ball again. Rinse and repeat for several hours.
Tried keeping the inspector window closed and changing timeline view to minimize video on the clips. No effect that I can detect. Haven’t tried switching to the simplest timeline view yet. Working with viewer on main monitor (default setup) doesn’t seem to help.
Interestingly, I sometimes see a lag in the video, almost like dropped frames stuttering, but very slight and not consistent. That shouldn’t be happening using proxy video in best performance mode.
None of this is fatal, just irritating. And my system has been very well-behaved up to this point, even using the broadcast out (Kona 3 in that same PCI to Thunderbolt box). Don’t remember if I upgraded to Mavericks or if it was already installed- did the first generation Retina 15″ come with ML or Mavericks?
Thoughts?
-
First thing to check is what the format of your timeline and the frame buffer the Kona are set to.
If theres a mismatch in settings, things can get really choppy. You have to turn off the A/V output, change the Kona settings, then turn on A/V output.
What are they set to?
(go cubbies)
-
Hi Jeremy.
Not using the Kona card on this, as I’m still saving my $$ for a sweet FS monitor and it’s not worth borrowing a broadcast monitor for the initial edit. So I’m just putting the viewer on the second monitor. (FWIW, I’ve never had problems with X and the Kona, as long as the latest driver was installed.)
The footage is 5k, and the timeline is set based on the first video clip. So I know my format and frame rate are correct. And I’m working strictly in proxy mode, as the MBPro chokes on the Red raw files, (at least at 5k).
-
[Jeff Markgraf] “And I’m working strictly in proxy mode, as the MBPro chokes on the Red raw files, (at least at 5k).”
Can you blame it? 🙂
[Jeff Markgraf] “Not using the Kona card on this, as I’m still saving my $$ for a sweet FS monitor and it’s not worth borrowing a broadcast monitor for the initial edit. “
So under the “Window” menu, A/V output is unchecked, is that correct?
-
Well…I’m still at work, so I can’t check until later. I would assume I unchecked it, ’cause I’d have to be a numbskull to have A/V on if I’m not using it. But then I’ve been known to emulate Curly on many an occasion, so.. (nyuck, nycuk!)
-
[Jeff Markgraf] “Well…I’m still at work, so I can’t check until later. I would assume I unchecked it, ’cause I’d have to be a numbskull to have A/V on if I’m not using it. But then I’ve been known to emulate Curly on many an occasion, so.. (nyuck, nycuk!)”
Me too! You might as well pull the Thunderbolt cable on it.
If that isn’t it, write back. There’s other things to check, too.
Reply to this Discussion! Login or Sign Up