Skip to main content
Bed30321077z973
Bed30321077z973
Inspiring
February 5, 2024
Répondu

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

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?

Ce sujet a été fermé aux réponses.
Meilleure réponse par 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.

1 commentaire

Bruce Bullis
Community Manager
Bruce BullisCommunity Manager
Community Manager
February 5, 2024

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.

Bed30321077z973
Bed30321077z973Auteur
Inspiring
February 5, 2024

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

That's the code essentially.

Bed30321077z973
Bed30321077z973Auteur
Inspiring
February 7, 2024

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 :

 


I might have discovered the source of the problem:

I tried to run the program in a way it treats different portion sof the timeline every run, so I would run it, it ends, then re run it (no breakpoint here just running the program multiple times)

and each time I would treat different portions of the timeline,

First obsevration:

The later the timeline is, the SLOWER the inserts were, for instant:

- Inserting 200 items in the first part of the timeline: 0.36second per insert

- Inserting 200 items in the part prior to the last part would have a rate of: 1.03s/insert

- Inserting only 100~is items in the LAST part of the timeline: 1.26s/insert (even slower than inserting 200 items in few moments back in the timeline)

 

Theory: Could it be somehow just the target area of the timeline affecting the inserts? If yes, why?

Another theory: could it be because my in's and out' are bigger the more I advance in the timeline, and that causing extra computation time? I think so.

In that case, creating subclips could be better choice after all! I will to explore that now ... I suppose.

Conditions d'utilisationAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices