• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

TRES GROSSES LENTEURS DANS ADOBE PREMIERE

Explorer ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

Bonjour

Je vais tenter d'être le plus explicite possible.

j'ai une grosse config PC

j'ai mes applis adobe à jour, windows 11 à jour... 64 Go de ram

ma séquence finale fait 2560x1440

je monte des séquences 4k tournées via mavic pro, nikon z6 ou d500 et gopro.

J'ai généré les proxies et travaille en ayant activé les copies allégées. Avec ce mode, les vidéos sont bien lues, c'est parfait (sauf les vidéos du mavic qui accrochent toujours) Du coup, j'ai regénéré des vidéos 2 fois plus petites pour que les proxies soient eux aussi plus légers. Et là, tout est nickel 😉

Sauf que... une fois le montage fini, je réactive (ou non) les copies originales. Et remplace les séquences BD générées par les HD originales (vous suivez toujours ?) mais là, deux problèmes de tailles :

- les séquences ne sont plus calées comme les BD l'étaient... (du grand n'importe quoi)

- aucune vidéo n'est lue de manière fluide. Pire, la tête de lecture posée sur la séquence et il faut attendre près de 4' pour afficher une image !!

Pourquoi ??

Merci de l'aide

TOPICS
Error or problem , Freeze or hang , Performance , User interface or workspaces

Views

238

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

I think the main problem is the media. That is quite loaded to the long-GOP stuff, where there are only a few actual frames of video. Nearly every 'frame' is actually just a small data set of pixels that have changed since the last iframe (complete frame), will before the next, or both.

 

The DJI rigs are at times putting over 100 data sets in-between actual video frames. That requires the computer to find all referent iframes, decode them, then do ALL the in-between there and the current playhead frames, storing the data somehow, just to play back the next frame.

 

Doesn't count any other effects you may have applied. Which only adds to the computer load.

 

So ... yea, proxies for playback, but still, trying to export is going to take a while.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

la traduction google ne donne pas de réponse très compréhensible mais j'ajoute néanmoins que ces mêmes vidéos sont parfaitement lues avec n'importe quel lecteur... (VLC, windows média...)

seul première ne les lit pas... c'est totalement anormal

j'ai beaucoup de mal à comprendre comment je peux bosser

Merci de votre retour

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

Assuming that there is correlation between a simple video player and a very complex app like an NLE is as common as it is useless.

 

Simple players ONLY deal with one clip, period. They simply play it from beginning to end, and have no other load on the system but decoding/decompressing one clip.

 

That's not even  remotely the workload of a full NLE like Premiere. Premiere must grab many bits and pieces of different video files, decode/decompress, apply video and audio processing to them, then display the frame-after-frame playback.

 

Which is several orders of magnitude more CPU and system load, read/write cache work to max your system out ... none of which is done by any video player app.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

I strongly suggest you transcode everything to an all iframe format like the appropriate flavor of prores.  I know it will generate large files and this process will take some serious amount of time, but it will probably solve the problem.    May not be a solution for you...  given your schedule and drive space...    but that's the way I work when I'm given problematic mpeg formats.  

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

ça fait une bonne soixantaine de clips à convertir, mais si ça résoud le problème (plutôt en le contournant) alors pourquoi pas. Même si cela demeure totalement hallucinant puisque DJI n'est pas un inconnu dans le monde vidéo et que, visiblement, adobe n'est pas capable de gérer les fichiers générés par leur matériel.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 04, 2024 Jan 04, 2024

Copy link to clipboard

Copied

J'ajoute que je reste surpris de lire qu'on trouve "normal" qu'il puisse exister une différence entre deux identiques clips, dont l'un n'est que le premier clip, réduit en poids mais dont la l:ongueur est absolument la même. Même si techyniquement, vous ayez une explication, dans la pratique, ce n'est pas compréhensible. Prenez un fil en 4k et un autre converti pour ne peser que quelques centaines de mégas, hormis la qualité qui s'en trouverait dégradée, la longueur du film reste la même et chaque séquence est à sa place...

Ce que j'en dis...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 05, 2024 Jan 05, 2024

Copy link to clipboard

Copied

LATEST

You have a basic misunderstanding of the nature of the files, the way each codec type works. "We" can't fix that, we can only describe to you the differences and so give the what is different and why.

 

For example, an 8k Red RAW file is normally far easier for playback in all NLEs than any recent DJI high-framerate 4k file. 

 

My 4k BRAW files are much 'larger' on disc, than a 4k Mavic file, but again, playback is total butter with the BRAW. Not ... necessarily so with the LONNNNNGGGGGG-GOP of the DJI files.

 

I work for/with/teach pro colorists, nearly all of them Mac geeks, and for software, either in Resolve or the incredibly expensive (but awesome) Baselight. These people all have "heavy iron", computers that are HUGE compared to yours and mine. Their monitors cost several times our entire computer system, and that doesn't count multiple high-speed 16 to 32 TB RAID arrays feeding their computer files.

 

All of them .... when getting a job with any notable amount of DJI/drone/long-GOP media, transcode that stuff before adding the t-codes into their system. They don't want to mess with grading that ... file type.

 

And that isn't on "Abobe" at all.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines