Skip to main content
mandicreally
Inspiring
May 3, 2021
해결됨

New DJI Air2S footage exports as still images only...

  • May 3, 2021
  • 9 답변들
  • 5343 조회

So I just got the latest DJI Air 2S drone and shot some footage with it yesterday.  The video is 5472x3078 4:2:0 10-bit footage in a HEVC (H.265) codec at 23.98 fps.  I brought it into Premiere, let the footage create a Sequence, then changed the Resolution to 3840x2160.  Did a quick 1 minute edit of the footage, including reframing the shots using the extra resolution or scaling the footage down to fit the Sequence.  I rendered the footage in the timeline and it played back fine (surprisingly well for H.265 actually).  

Then the trouble.  I first exported it as a lower Bitrate 1080p (h.264) video to just upload onto Social Media.  That resulted in a series of static images.  So I tried again using the 4K YouTube (h.264) preset of Premiere, and same thing.  It has my cuts where they should be, as well as the reposition / scale changes, but everything is just a series of still images.  Namely the first frame of each video clip is just statically sitting there all pretty like, until the cut and then it is the next clip's first frame.

Anyone experience this before? This is a new one on me.  Exports went smoothly both times but clearly something is way off.

이 주제는 답변이 닫혔습니다.
최고의 답변: Ann Bens

Transcode footage to a more edit friendly format such as Prores or Cineform before brining it into Premiere.

9 답변

Inspiring
February 23, 2023

This is nuts. I've been editing this same Mavic2 Pro drone footage for a long-term client for years and suddenly this footage no longer works in Premiere Pro, nor does it export properly. It exports out as a still image.

What's worse is that since in my situation I am working from pre-built selects timelines in some case done quite awhile back, I have to transcode the source file into ProRes via Media Encoder, bring that ProRes .mov into Premiere, match up the start and end points, and then replace the clip in the timeline. This is because even transcoding it to ProRes from the existing timeline does not work! Really so bonkers. I have to do this for dozens upon dozens of clips, and I wouldn't feel right charging the client for this time as it's not something they should be paying for. So I eat this time and cost.

This is possibly the straw that breaks the Premiere back for me. Why can't Adobe fix issues like this which were not present in previous versions?

Editing in 23.1.0 on a Windows 10 machine with Ryzen 5950x processor, 64GB ram, GeForce RTX 3080

mandicreally
mandicreally작성자
Inspiring
June 14, 2022

Over a year later, still an issue.  Anyone else notice that most of the "Solves" on this forum aren't actually fixes, but just workarounds?  Transcoding the footage isn't "fixing" the situation, it is finding a way to work around the flaw in Premiere.

I don't backup the ProRes footage after an edit, so I end up with 2 of the footage files during the editing process just taking up space.  

Anyone know if htis is an issue on the Mavic 3 as well? 

Participating Frequently
November 22, 2022

Just started another thread with exactely the same issue from an Air 2 drone that had me just walled in for 20 hours trying other workarounds I found on YouTube. Nothing worked. Total frustration. Worked fine for 3 Video edits and on the fourth it all capped out just because I added some more color grading totally unacceptable. Had to download shutter encoder, 20 hours down the drain. Learned a lot but... Seriously? 

mandicreally
mandicreally작성자
Inspiring
November 22, 2022

I work with/for and teach pro colorists, most of whom have rigs that would probably make yours look positively anemic. They certainly do to mine. My 24 core Ryzen w 128GB of RAM, 2080Ti, and twin Nvme drives, everything else on large internal SSDs ... is a puppy besides their rigs. (And cost about a quarter too ... )

 

They routinely t-code all H.264/5 files that come in with a job because they don't want to be stuck grading that in Resolve or Baselight. On their "heavy iron". They t-code to ProRes, DNx variants, or Cineform. And dump the t-codes at the end, of course.

 

So folks with truly massive machines assume they will t-code any H.264/5.

 

And it seems most editors, with gear about a quarter as powerful, are outraged at the thought they might be better setup if they t-coded something.

 

Humans are really weird at times.

 

Neil


As a solo production making video content multiple times a week, it is all about speed.  Sure I can transcode all of my H.265 footage to ProRes, but now I've got redundant files on my drive.  When I have multiple projects going at the same time, even my 4TB SSD starts to get cramped on space. And spending a couple hours transcoding footage before I can even begin an edit is a time sink all on its own.  Or worse yet having to clear drive space so I can fit the current project onto the drive, only to then have to move that other project back afterward.

 

If I was making a documentary where I had a month to edit it and knew the final product would be an hour plus in length? Sure I'd transcode.  That isn't my production world.  I'm producing multiple 1 to 20 minute videos a week as a solo shooter, editor, marketer, talent, and everything else under the sun. For me I need to dive into an edit and get it done asap.  Having to transcode footage is a hinderance to that.  My 16 core Ryzen / 3090Ti computer playsback 5.8K H.265 footage from my Lumix GH6 at Full native resolution without a hiccup. Why transcode if I don't have to? 

The problem here is that the H.265 footage from the Air 2S will playback and edit fine in Premiere, BUT when you export the video it will literally only be a still image of the first frame from the clip.  And a year and a half since I posted this discovery, it is still true.  That is a bug.


Workarounds aren't fixes. People on this forum are all to quick to absolve Adobe of any need to fix things by throwing out random "well just do these 3 steps you shouldn't have to do, and it works fine then!" workarounds. 

I'd be willing to bet that the majority of video clips edited in Premiere in 2022 are H.264/5.  Saying it "isn't an editing codec" is starting to feel like an outdated way of thinking, IMO. 

Enzoxs
Participating Frequently
April 27, 2022

Anyone know a solution for this yet? Same problem with my Air 2S footage, very annoying.

Participant
April 28, 2022

You can preprocess (transcode) all the footage to something more timeline friendly before bring the video into the project.  Formats like ProRes work well.

Participant
June 14, 2022

And how can I do that? Can you please teach me?!

Participant
January 6, 2022

Nearly a year later and this is still an issue. Please fix, Adobe.

mandicreally
mandicreally작성자
Inspiring
June 16, 2021

1.5 months later and this is still a problem. Adobe really makes it harder and harder to justify using them. 

Participant
June 16, 2021

I am having exactly this issue right now.  Which solution worked for you?

mandicreally
mandicreally작성자
Inspiring
June 16, 2021

I have to Transcode the footage into ProRes before I start editing. Then use the Transcoded footage. 

I didn't select that as "the answer" because I think it is complete BS and the fact that Adobe hasn't corrected it when folks clearly know it's a thing is ridiculous. 

Participant
June 16, 2021

What are you using to do the transcode, Premiere itself or another product?

This is utter BS.  I agree completely.  I will be getting on the phone today, I can tell.

Participating Frequently
May 3, 2021

I'm having a similar issue. I also have the latest DJI Air 2S drone but I'm using 4K 30fps. When I tried exporting then playing it back, it appears to be static images when it's just very very jumpy video. What gives? Didn't have this issue earlier that I recall. 

 

Also how do I export this project so that I can open it in the previous version 202 if the new 2021 is broken? I'm truly disappointed I can't export in the right format and quality like before.

Yegor Zadniprianyi
Participant
May 3, 2021

Still issue with 15.1 Premiere. Just downgrade to 15.0 and everyting will be ok. Adobe in each new update manage to break something...

Ann Bens
Community Expert
Ann BensCommunity Expert답변
Community Expert
May 3, 2021

Transcode footage to a more edit friendly format such as Prores or Cineform before brining it into Premiere.

mandicreally
mandicreally작성자
Inspiring
June 16, 2021

This fixed the issue. It is ridiculous and I should nto have to do it. My computer has the power to edit h.265 footage, I shouldn't have to transcode all of the footage I shoot on the drone. But this is the only solution that worked.