10/31/2023 0 Comments Fcpx still frameIt must be caching on the first pass, even if it doesn't display them, but for some reason able to display once it's been cached? One thing I noticed is that the first time I play the sequence, it drops frames like crazy, but then the next time, it plays them more or less correctly. I'll try the conversion idea, but I'd rather have FPCX do a better job with stills in the first place. The stills I'm cutting with are the same resolution as HD video, so it's not like they're very high res and need downsampling. You would think using stills would be less overhead, not more.Īlso, making a folder of stills into a folder of individual 5 sec QT movies seems inefficient and process heavy. My guess is that cutting a timeline made up of very short duration (1-6 frame) micro edits would exhibit the same problems. When you bring stills directly into FCPX, they're given a nominal duration (10 secs) as if they're a video clip and so I'm wondering if FCPX actually differentiates. Interesting idea, but I'm curious how or whether FCPX treats video differently from stills in a structural sense, if at all. but I'm wondering if FCPX plays better with compression/decompression of other formats than JPEG. The panels I'm cutting with are b&w line art, so I don't care about color fidelity, bit depth etc. I'm wondering does anyone know what the Preroll/Postroll settings affect in terms of performance? Also, does FCPX prefer other still formats like PNG, TIFF or Targa for playback purposes. I did try moving the FCPX file within all of the media it an external SSD on Thunderbolt, and it makes no difference. The process is more like animation and less like Ken Burns and not at all an image sequence with a unified frame rate. The end result is an animatic/ boardomatic which is of course a QT, but while I'm working in the timeline, I need the frames as they are so that I can adjust their lengths and replace them with updated artwork etc. Sorry Karsten, but the point is to keep them adjustable as stills in the timeline, not bake them into a movie. I vaguely remember, when doing my first steps in FC/e on a Cube, I was told the same trick - then, the reason was 'weak horsepower' to handle so much jpgs. You drag all jpgs into a timeline, export a Master, re-import to FCPX, and add from there? I even opened up Premiere yesterday in a fit of frustration, until I remember that cutting this kind of stuff in FCPX is way easier, despite the crappy performance.Īny thoughts on how to improve performance to acceptable levels? Live action video seems to work fine, but FCPX seems to get gummed up on timelines with just stills. The playback is so spotty that its often hard to judge edit points and timing. Sometimes, it will just skip right over fast moving frames and hold the longer frame prior to the faster moving sequence. But I will often get dropped frames, especially when a sequence has a section of stills at relatively short duration each. Most of the frames are on for about 6-12 frames, sometimes less, sometimes more, depending on the scene timing. The first time around, the performance is generally the worst. It seems like despite switching between Better Performance/Better Quality in the the viewer View pulldown, I get lots of dropped frames depending on whether I've played the sequence once or played it again. I'm cutting very low complexity B&W jpegs (200 kb each) into storyboard reels. When I'm cutting storyboard animatics, in a 1080/24p timeline, playback performance is all over the map quality-wise. OK first the specs: El Capitan, FCPX 10.2.2, Mac Pro 2013 8 core/64gb RAM, Dual 700, SSD Boot Drive, Promise Pegasus 6 Drive Raid
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |