As far as the computer just stopping on account of being overloaded somehow, yea, it would be good if that didn't occur. I'm glad a staffer says they're checking that out.
As for "in general"? Ok ... I clearly don't now your exact details, so some of this will fit, some may not. Still, for many reading this over time, it's information they should have at hand.
A lot of the time, when people say their computer can handle like 8k H.265, they mean for playback in QuickTime or VLC. Which is not at all the same as with an the load any NLE puts on the computer, which is several magnitudes greater than any simply video player.
So ... specifically ... does your computer handle 8k long-GOP playback on sequences in Premiere? As that is all that counts. If so, quite impressive and cool.
Next, Warp is again a massively demanding effect, far greater than even 10 instances of Lumetri stacked on a clip. I know, I've tested that comparison in the past. I'm not seeing that you actually comprehend that load in practical terms.
And I only worry about "in practical terms". "In theory ..." isn't of any use, as neither thee nor me is a development supervisor so we can't change anything, only ask. But for working ... you do what works.
Next, a lot of users do not realize that all an NLE like Premiere does is create metadata files. Period.
That sequence? There isn't a "physical" sequence anywhere. Never has been.
It's only a bunch of text/metadata giving the sequence 'form' data (fps and all) plus a listing of the clips used (from this to there ...) with the listing of any effects and the listing of what the effects are set to.
Warp produces massive data ... per-frame of every clip with Warp applied! ... all of which is added to the sequence and therefore project file.
Take a project without Warp applied. Check the total size on disc of the project file.
Now ... apply Warp to 20 five or more second clips on a sequence. Check your size on disc of the project file ... and ... yowza ...
You dramatically expand the size of your project file by 'leaving' Warp applied to a bunch of clips. And that does affect all sorts of things in your project!
As the file size of the project bloats up, the entire project takes longer to load. Sequences will have more metadata in them, which has to be pulled and stuffed in RAM/cache during playback. You will hit a point at which, during playback, it has to dump some of the RAM/cache files and load more.
And gee ... you start hitting playback slowdowns and glitches just because of the massive amount of metadata constantly in process. Plus with so much demanding use of resources both to manage RAM/cache loads and in/out, and to run playback and to add effects as set to the image ... you can start getting "anomolous" problems.
Something gets processed out of order and glitches appear in the image. Or ... get written to the sequence or project file.
That's why I don't recommend applying Warp in batches, and leaving it 'on' the clips.
I want to avoid the project bloat and probably inevitable project or sequence glitches that will occur sporadically from doing so.
But then, I'm a practical guy. What works, works, and for me, leaving tons of Warp "lying around", doesn't work. At. All.
But of course, everyone's mileage always varies.
12
Replies
AdChoices