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

DJI osmo pocket 3 120p footage drops frames on export in premiere, but works on different computer

Community Beginner ,
Sep 16, 2024 Sep 16, 2024

Copy link to clipboard

Copied

Premiere Pro version 24.6.1 build 2

OS Windows 11 10.0.22631 Build 22631

 

I'm stuck here, and I'm filming a project in 7 days that I'd like to use the osmo for, and hopefully use this computer for. For those not familar, the osmo 4k 120p setting actually spits out a 29.97 fps video instead of the regular 120p you'd expect from say a Sony FX3.

Yesterday I was making a silly thing, a tiktok with a timelapse with some b-roll. At first I thought it was because of doing a timelapse and the slow motion footage on the same timeline, but in troubleshooting I've gone all the way down to just selecting 5 seconds of a clip and trying to export it. I'm an in house video/photo guy for a company and as such have a second editing rig that I use for their projects, very similar in specs and it works fine, scrubs fine, playback fine, export fine.

Things I've tried / looked at:

making sure my SSD isn't too full

uninstalling and reinstalling premiere

checking to ensure the version of premiere that works on my other computer is the same as the version I have on the computer in question

Proxies

Trying CBR, 1 pass and 2 pass

Specs on computer that works: Intel i7 11800H, 64gb ram, A4000 graphics

Specs on computer that doesn't Ryzen 7 5800x3d, 64gb ram, 3070ti graphics

I'm completely baffled here.

Views

140

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 ,
Sep 16, 2024 Sep 16, 2024

Copy link to clipboard

Copied

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.



<"moved from cc desktop bugs">

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 ,
Sep 16, 2024 Sep 16, 2024

Copy link to clipboard

Copied

Please post screenshot of sequence settings, export settings and media info.

 

>> making sure my SSD isn't too full

80 % means full.

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 ,
Sep 16, 2024 Sep 16, 2024

Copy link to clipboard

Copied

LATEST

First, Premiere needs minimally 4-5 times the expected size of the final file after exporting 'free' during the export process. So ... I don't know if that's an issue, but it's possibly in play here.

 

Second ... you are dealing with DJI drone media, probably the nastiest long-GOP stuff made in-camera. So how the individual computer works with long-GOP is crucial to playback/performance when editing that stuff.

 

So I would guess your Intel computer is a lot better with that specific form of long-GOP than the Ryzen rig is.

 

Even within Intel machines, there are major differences. The "k" chips all have internal "iGPUs" and can utilize their long-GOP encoding/decoding processes. The  Intel chips with "F" in them ... don't. And struggle with long-GOP work.

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