Inspiring

Answered

Is there a way to TURBO speed up premiere pro even more by making it use more GPU?

Forum|Forum|2 years ago
February 5, 2024
1 reply
1466 views

So I am performing lot of tasks right now, inserting numerous items to the tracks,

But I don't find it fast enough for me.

I want it to become REALLY REALLY insanely fast, be it if that meant HUGE use of GPU.

In the following screenshot I am showing what a machine is diplaying in term of GPU, CPU and RAM usage when running extendscript, I have another machine with more gpu than this one but in both cases the usage of GPU is not thaat important:

Something like pytorch (used in machine learning) something similar that would boost Premiere pro by using more GPU?

Maybe the slowness comes from javascript itself? Or both Premiere pro not being optimized for heavy use + javascript slowness?

This topic has been closed for replies.

Correct answer Bruce Bullis

ANOTHER theory (confirmed) is:

The more there are items on the tracks, the slower inserting new tracks get!

I know it because I did the experiment:

Added 100 items to a project had numerour other items before, is slower than adding 600 items to a project that has no items, even if its has bigger in and outs (they have no effect on performance), and even if we are at advanced times of the timeline (as long as there is no item BEFORE). (I did not experiment for items present AFTER, i mean, lets say we have numerous items at the end of the timeline and we want to add 100 items BEFORE them, I wonder if it will still get slower or not).

One solution would be to open multiple projects at once, and having items added to multiple timelines, so reduce number of items within one timeline,

But I have no idea if we can run the code on multiple projects at once or not, and if the performance will split or not.

Interesting speculation.

As before: If you can provide the actual ExtendScript you're using, a project w/media, and (IMPORTANT!) step-by-step instructions that reliably reproduce the behavior, we'd be glad to pursue it further.

Bruce Bullis

Community Manager

Without seeing your ExtendScript code, there's no way to provide any meaningful feedback on what might speed up its execution. Currently, there is no reason to think that moving to GPU processing, or machine learning(?!), would help anything.

Bed30321077z973Author

Inspiring

Importing the same item from media library to tracks multiple times. I want it to be WAY way faster.

That's the code essentially.

Bed30321077z973Author

Inspiring

Hello again,

I would need to make a new project that does the same thing as mine, but with random files, so you can reproduce it, that's why I wasnt able to send you the project to reproduce it.

It's simple to reproduce, take on project item, and insert it to the timeline with different in and outs and different insert time (makign sure they dont supperpose, (although overwrite could be used for the experiment?, I havnt tried it yet because I dont want it to overwrite))

In the meantime I have more info, I have done more experiments:

What I have noticed is that the more items ther is "OVER TIME" the slower the "api response, or PPRO reponse?" to the commmnds get.

For just 100 hunder insert command: 36.9 secs => 0.367 per insert()

if you add 4 more items while adding those 100 firts items (kind of in parallel, i mean its 5 items by 5, 100 times, but that does mean anything because ites probably sequential anyway, anyway the total of inserts would be..see text after parentheses), for a total of 500 insert() within a short time, you can do it in 62 secs => 0.12 an insert()

So we are getting FASTER with more item, but this is only because its the beginning!

Now the problem comes when continue to add stuff LATER ON,

From the experiments I have done, Here is what I can report:

After severals tens of hunderds of "inserts" I noticed that inserting 5 items, would take 9 to 10 seconds.

We are down to One insert() per 2~ seconds?

Which is actually ULTRA slow.

Whereas in the first hunderds of inserts, the process was quick and fast, 62 seconds for 500 items or so. That's like: 0.12 seconds an insert!

But later on, My timing was: I can add 500 if I wait (500x2seconds.. ), so that's 1000 seconds, = 16.67 minutes . :(, that's really a lot! Especially if you have another 500 items (we are up to 30 minutes, then 45min.. then 1H process, yes yes 1h process)

I will have to try to make a ready to use extendscript for you, but I will need time for it, but if you are curious and can make it faster than me, then as I said, simply make a process that use one project item and insert it in the track in different times about severals tens of hunderds of time and YOU WILL OBSERVE how insert()s will get very slow (I went from 0.12s per insert to 2 seconds per insert which is very significant)

If any idea comes to mind, please do share. I will continue experimenting to see.

I have even MORE info:

Actually it was 600 items not 500,

The most disturbing here is that, I think this WILL SUPRISE you:

If you have a duration in the time line called "duration", and you:

Situation A): add one projectitem to the same track, about 300 times, all over 3x the duration.

Situation B): add addi 600 items withing 1X duration (so within 3 times less portion of the time line)

Situation B would be much faster: 0.12s/insert, situation A would be 0.43s/insert.

Extra situation:

- Situation C: if you just insert 100 items within 1X duration. You would not get faster than inserting 600 items within the same duration. (0.367 per insert() as previously stated)

here is an illustration :

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded