Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Adobe Premiere Pro MXF & Premiere Pro are battling for the soul of my computer

  • MXF & Premiere Pro are battling for the soul of my computer

  • Claire Presnall

    August 17, 2021 at 5:08 am

    I’m working on a project with 8 videos, 2-3 minutes each. Each video was shot by a different crew, but mostly they’re all MXF files. I have a separate project for each rather than making one mega nightmare project, and everything was going smoothly for 2 weeks until I tried to output my second video tonight to share for review in the AM (isn’t that always the way it happens).

    So the video that’s giving me trouble has locked up my computer. Failed in ME. Crashed PP. But I finally, in desperation, flattened my multicams & sent it to AE who just spit me out a lovely 422HQ which I took back into PP and spit out an h264 super easy.

    We’ve literally been just cruising right along with these 4k MXFs until 10:45 tonight. Now. Rainbow Wheel of Doom. It locks up EVERYTHING. But my activity monitor is like “we’re good. In fact, nothing is using much CPU or memory or anything.” But the computer says, “I hate you. Also, you can’t open anything. Even Finder has crashed.”

    A little more specifics. We usually get about 40ish seconds in, so I’ve tried removing/replacing shots. I’ve cleared the cache. I’ve restarted a dozen times. I started a new project and imported only my final sequence. I went back and grabbed an autosave. I’ve looked up the error code and found some suggestions for a Windows machine, but I’m running Mac.

    I’m running a MacPro tower that I bought this spring. It’s running
    BigSur 11.3.1 with 3.3 GHz 12-Core Intel Xeon W, 64 GB 2933 MHz DDR4,
    AMD Radeon Pro Vega II 32 GB. I’m running PP 2021 that I updated about a
    month ago. I may have an update waiting on either the OS or PP, but I
    hate to update mid-project, and I’ve been mid-project all summer.

    Premiere gave me Error Code 5 & didn’t like my file #62, so I removed it and still no luck.

    Here’s the info I got from Media Encoder:

    – Encoding Time: 00:02:31
    08/17/2021 12:05:12 AM : Encoding Failed
    ————————————————————
    Export Error
    Error compiling movie.

    Accelerated Renderer Error

    Unable to produce frame.

    Writing with exporter: H.264
    Writing file type: H264
    Around timecode: 00:00:43:13
    Rendering at offset: 42.251 seconds
    Component: H.264 of type Exporter
    Selector: 9
    Error code: -1609629695

    ————————————————————
    – Encoding Time: 00:05:00
    08/17/2021 12:12:49 AM : Encoding Failed
    ————————————————————
    Export Error
    Error compiling movie.

    Accelerated Renderer Error

    Unable to produce frame.

    Writing with exporter: H.264
    Writing file type: H264
    Around timecode: 00:00:36:08 – 00:00:38:04
    Rendering at offset: 36.370 seconds
    Component: H.264 of type Exporter
    Selector: 9
    Error code: -1609629695

    ————————————————————

    So if anyone has a solution other than send it through AE because AE obviously is your best friend and loves you unlike the nasty, evil, tricksy PP or set everything on fire and move into a cave (my 2 leading plans), I am all ears. Thanks!

  • Tero Ahlfors

    August 17, 2021 at 6:34 am

    Try turning off hardware accelerated encoding in Preferences – Media.

    Or render the whole sequence in a high quality format and use the preview files when exporting.

  • Claire Presnall

    August 17, 2021 at 6:44 am

    Cool. I’ll look into that just as soon as my next video that is ALSO doing this super fun thing that I am definitely enjoying finishes outputting from AE. That little box is definitely checked. I mean, it should also be checked in the first one which worked, but if memory serves that one didn’t have any multicams. Hmmm… The plot thickens (or perhaps thins).

    I’ll let you know if that fixes it.

  • Claire Presnall

    August 17, 2021 at 6:59 am

    So far, we’re still hanging up right at that 41 second mark. I don’t have time to sit and wait and see if we ever make it past that right now. But I’ll give it another go tomorrow and report back.

    I’m suspecting it has something to do with the multicams. I was having some issues with the audio on those getting blown out that required a bit of a brute force workaround.

  • Rob McGreevy

    August 17, 2021 at 1:21 pm

    We’ve had weird problems on our Mac setup and MXF’s in the past as well. Source clips would cut off early and not display completely in PP. So a 10 min. clip would only show the first 2 minutes in PP. You’d check it in Finder and it was all there. We’d load it in our PC based edit suite and it would work fine. Maddening! The thing that seemed to cure it for us was to convert the source MXF’s to ProRes before editing and that cleared it up.

  • Claire Presnall

    August 17, 2021 at 1:59 pm

    Ya know, I thought about doing that, but each video is hours of interview footage at 4k, and my fancy new baby has just been plugging away doing her thing, so I got cocky. And now I’m paying for it.

    Also, the lav audio is baked into the cam 1 footage, and when I transcoded it straight from the Finder through ME, it blew out the audio (like the multicam issue I describe in the next paragraph), which was part of my hesitation as well. No matter what settings I chose, it was like “let’s turn this baby up to 15. Fuzz is where it’s at!”

    But back to this issue. It’s definitely something to do with the multicams (which is funny that those aren’t the clips the error messages are fussing about). The 2 videos with 1 camera set ups exported just fine. Before sending to AE, I flattened the multicams since AE doesn’t seem to know what to do with them, and AE exported without issue. And when I was building the multicams, it was blowing out the main audio. I would have to move my audio then delete the top audio tracks because it was something baked into those tracks themselves.

    I think the moral of the story is MXFs are the devils codec.

  • Tero Ahlfors

    August 18, 2021 at 3:44 am

    MXF is not a codec, but a container. It can have all kinds of stuff in it.

  • Cathy Jackman

    August 20, 2021 at 12:42 pm

    Actually, my experience is that Multicam in Premiere Pro is the devilish problem.

    Coming to the end of a sizeable multicam project, Premiere began unable to handle my project. I tried everything that you did – this was on PC, and I even moved it to my Mac. In the end, I couldn’t afford any more downtime. I moved the project to Avid.

    I never found what exactly was causing the problem – was it audio, video? Adobe was not able to help. I hope you are able to figure it out – but I don”t think MXF files are the problem.

    Good luck

  • Rowdy Wiegmans

    August 20, 2021 at 2:42 pm

    A workaround might be to change container, clip by clip to pro res or dnh (or create a proxy batch) to see if it’s a single clip that gives you the problem.

    If not; explode from multicam to multitrack

    Still?; remove effects

    Then; export xml to see if davinci will do it

    Work your way backwards would be my advice.


    Good luck! 🙏


  • Claire Presnall

    August 20, 2021 at 3:52 pm

    Based on all my workaround attempts, I think you’re right that it’s the multicams vs the MXFs. The multicams were janking my audio levels too, and just being all around not friendly, but they seemed less irritated by the .movs and .mp4s. The multicam video was disabled at the sticking point, and we were seeing straight MXF b-roll (hearing multicam audio), so I was thrown off the scent. My error reports kept listing specific files and timecodes, making it :40ish seconds into a 3 minute edit, and I foolishly believed them, wasting 2 hours removing and replacing clips, trying to find the secret formula before flattening the multicams and sending everything through AE. The flattening was probably the fix, and the AE was probably unnecessary.

Viewing 1 - 10 of 12 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy