Skip to main content
lionel29
Participant
June 15, 2026
Question

problème de saccade après exportation

  • June 15, 2026
  • 4 replies
  • 42 views

bonjour me voici avec un problème que j’arrive pas a résoudre, j’ai fait l’achat d’un DJI mini 5 pro et j’utilise le profil D-Log M et la norme de codage H.265 en MP4, 4k 30fps et quand je suis dans première pro et que j’exporte mon rendu final ma vidéo saccade complètement, du genre 1 image toute les 3 seconde et ça toute la durée de la vidéo. j’ai essayer d’exporter sous plusieurs format et rien n’y fait que faire? 

je précise que j’ai ce soucis seulement avec première pro.

4 replies

R Neil Haugen
Legend
June 16, 2026

It isn’t reading the long-GOP file that’s the problem, like a standard player does. Are you familiar with the long-GOP format? There are only complete actual image frames like every 9-60 typically on those, called iframes.

In between are only datasets ... of the 1) pixels that will change beetween there and the next iframe; 2) those that have changed since the last iframe, and 3) both.

 

So the computer needs to create up to 60 frames or more just to play the next frame. For playback, that’s not such a big problem. But for editing, that’s huge. As in editing, the computer is grabbing bits and pieces, and many of the bits have iframes invovled either before that bit or after, so the computer has to find all those and again create and store to RAM/cache the image frames to have them ready for playback.

 

Now ... throw on some effects, some audio processing (which is lot more resource-intensive than many realize) and you get a massive load. It work with/for/teach pro colorists, most of them working on “heavy iron”, massive computers with 256Gb of RAM, multiple GPUs, massive SSD hardware RAIDs ... and they hate long-GOP media to grade, most often doing transcodes to ProRes before loading it into Resolve.

 

So what you’re asking your computer to do is actually more intensive typically than working 8k RED RAW files.

 

Hence the suggestion to cut resource demands down by exporting to ProRes then converting to long-GOP.

Everyone's mileage always varies ...
Community Expert
June 16, 2026

What version of Premiere Pro are you using?
 

H.265 is a Long GOP format and very CPU-intensive. If you are also exporting to another Long GOP format, that combination can be a lot for your system to handle.


As a first step, try exporting to ProRes 422, then convert that file to your final delivery format.

lionel29
lionel29Author
Participant
June 15, 2026

Non cela ne fonctionne pas non plus, c’est vraiment qu’avec première pro que j’ai se soucie la. Mon ordinateur n’a pas de soucis pour lire la 4K.

Community Expert
June 15, 2026

First I’d try importing the final video into Premiere and try playing it. If it plays fine inside of Premiere it could be your computer having trouble playing it back properly.