Having said that it still plays back really easy so I am thinking the wrong video file was uploaded. Just so you now the video has a lizard in it. It is hand held so that is why it might seem a little choppy for playback. Other people might want to test it out as well. I just don't think it is the correct video file. Having said that thanks for uploading it none the less because I do find it odd that the video codec is listed as H. Thanks you for uploading another video clip.
The second video clips is much harder to playback but my system can still do it. The JKL keys work just fine. I can play it back at full resolution with high quality enabled and even scrub it with ease. Having said that I cannot playback multiple layers like a picture in picture. In my properties panel the video file comes up as H. I hope some FCPX user will do the same.
The second video clip is much harder to playback using Premiere Pro. Does FCPX behave the same way? How to resolve AdBlock issue? Refresh this page. The Greg Protocols - Part 2: One month in It Already Is. Latest Forum Posts My Author nobbystylus FCP Trial vs. Full version crashes Author enno Which drone video settings should I choose for my Mac?
Author joema Export problem. Author Carambano My Author nobbystylus. Page: 1 2. Are you using a SSD? Some video codecs will playback and render better than others depending on the NLE. Ben Balser Offline Platinum Member bbalser. It depends on the video codec and computer. On an inexpensive laptop FCPX has an advantage but not so much on a desktop computer. High Quality and full resolution are not the same thing. What more could you expect? Thier wrote: Does anyone know why I would be getting choppy playback from footage that was shot with a GH5 at 4k Mbps I just tested this exact codec on FCPX Results: FCPX It would update frames pretty fast than a lag between the next frames.
Rather than allowing Final Cut to start rendering things automatically, we suggest taking control into your own hands. Start rendering certain parts of the timeline only when you need them to be rendered. The other card will be left available for the needs of 3rd party effects and other GPU users. The fastest combination will depend on your hardware and project. Having background playback switched off to allow Final Cut to be more responsive means you need to start the render process yourself.
Skimming is another option that can suck out a significant chunk of your computer resources. When you work with large frames and have both skimming and background render enabled, Final Cut can become extremely slow. The wait for each frame to be displayed can easily get to several seconds. On the other hand, skimming is an extremely useful feature of Final Cut. It can save you a ton of time if you are working on a massive project with multi-cam editing.
So if you see that your computer is choking, try turning off both normal timeline Skimming and Clip Skimming. These days almost any modern phone can shoot 4K clips, not to mention professional cameras and their capabilities. However, you do not always need to produce the final video in the same high resolution.
For example, large frame formats are not often used in online video platforms. It may be sufficient in some cases to upload a lower-resolution version. At times, you may also need to downsize a clip in the edit, for example, when you bring a larger clip to a smaller-resolution project or when you need to crop a part of the larger frame.
If done correctly, the size reduction can help to speed up the render process because applying Neat Video noise reduction to smaller frames is always faster than to larger frames. In Final Cut, you can control the size of the frames coming to the project using a Compound clip.
For example if you need to bring a 4K clip into a FullHD project:. Another option to avoid a slowdown in Final Cut is to disable the instances of heavy effects or filters Neat Video's Reduce Noise v5 is one of them after adding and setting them up in your clip. Using optimized media will allow you to edit faster.
The only downside of this option is the relatively large size of the optimized media files that may require some space on your hard drive. This is more likely in my view to be Lion or FCPX or the two in combination operating in some sub-optimal way.
There appears to be something very odd about the way Lion uses memory which was not evident in Snow Leopard.
I'd certainly wait for some updates of both software before splashing out on a purchase, if you can. Aug 4, AM in response to jizzlets In response to jizzlets. I have a new i7 2. I think just wait for the update. Apple rushed this software out it :. Aug 4, AM. Aug 4, AM in response to rhjph In response to rhjph. Like I said, I think it is the core 2 duo, but I'd wait for a point release before buying new hardware. The software is just not optimized for performance. Aug 4, AM in response to hafken In response to hafken.
Aug 4, PM in response to jizzlets In response to jizzlets. Aug 4, PM. Aug 22, PM in response to jizzlets In response to jizzlets. Although Im running on a slow machine, Im doing all the right things and still dropping frames even when editing in proxy and set in preferecnes to use proxy.
Clips pay smoothly for about 45 minutes while cutting and editing then it gets choppy, I usually have to restart FCPX so I can get another 45 minutes of non-choppy editing performance.
Running proxy, background render turned off, cut clean cuts, get choppy in timeline or browser after min of using software then I have to restart FCPX. Waiting for MBP but my setup is within spec and is annoys me that I can't even play proxy, is this right? Aug 22, PM. What you are saying regarding having no problems until minutes of editing is probably a bug in FCPX related to memory management. Once I've been editing for maybe minutes I end up having to quit and restart, because the app becomes too unresponsive.
So the best bet for you is to work with proxy media, quit and restart when things start slowing down, and hope that a performance update comes out before the MBPs do. Aug 24, AM. Aug 28, PM in response to hafken In response to hafken. Just doing cuts, no FX, no other apps running. Aug 28, PM. I understand Sep 2, AM in response to hafken In response to hafken. Sep 2, AM. I understand your frustration but the fact is your hardware specs are near the lowest end of what FCPX supports.
0コメント