(See notes below on another much shorter project with the same overload issues: 30-minutes total, multiple clips, multiple timelines).Īnd, yes, I am running the uhd original in HD monitoring, with HD timeline and grading, optimized and cached. This exercise, while very satisfying with respect to the artistic goals attempted so far, gradually kills it as the data builds up.Īnd, yes, I did break the timeline into separate clips and even into separate timelines. Perhaps 12 nodes, with multiple parallel node face and objects, with keys, key mixers, etc. This leads to tracking various aspects of the foreground and background, applying various simple color, luminescence, contrast, blur and vignette effects. Yes, to confirm, this is a single 2-hour take, an interview recording, primarily a head & shoulders shot, intended to be a beautiful production. Surely this show is larger than normal but the big boys must work with even larger shows.
Plus taking a couple of minutes or more just to save. This debilitating problem really stops further work, as adjustments, say, to color boost, simply do not register immediately and only show up after a few seconds. Ram use is between 24-30 Gig, so almost total continuous utilization. To be sure, this is a longer show, two hours, single video track, and I have window tracking and adjustments throughout. Video is ProRes HQ UHD shot on Shogun from Sony. System is Win 10 Pro, 6-core, 32Gig ram, all SSD. And Windows Process Explorer shows less than 10% CPU and the GPU monitor shows no GPU activity when saving. Recent problem: it now takes minutes to save or internally process color adjustments. Are people finding it performing on a par with Quicktime, or are there some teething issues?
There is a release note with the newest version regarding the new Black Magic solution for Quicktime, which is no longer supported.
0 kommentar(er)
