Problem exporting MP4 - exported file freezes in playback before the end

[Chunky tuna]

I'm having a problem exporting MP4 files from ME (and indeed PP) whereby the exporting process seems to run and completes no problem. However when I play the resulting MP4 file back it freezes usually 4 or 5 seconds before the end of the clip. The clip itself appears to be the correct duration, it's just that the encoding process seems to hit an error and doesn't encode the last bit of the clip correctly.

I'm guessing it's an issue with the MP4 codec in the system given that the same issue occurs across the entire Adobe suite (inc AE). I've got a workaround at the moment which is to encode using Wondershare Converter, but that's irritating because I need to output to ProRes (or a different Codec) and then encode to MP4 - doubling the process.

I'm running Big Sur on an iMac 2014, using PP 2022 and ME 2022 - all up to date with the most recent updates.

Wondering if anyone else has had this issue and if there's a fix?

[Sumeet Kumar Choubey]

Hi there,

We're sorry to hear about this. Have you tried importing the exported media in Premiere Pro to check if it's playing properly in Premiere Pro? Also, have you tried switching Performance to Software Encoding (Export Settings > Video tab > Encoding Settings) for H.264 exports & checked if it's exporting properly?

Thanks,

Sumeet

[Chunky tuna]

Hey Sumeet,

Thanks for replying to this post. To answer your question, yes I have tried both software and hardware encoding and the result was the same unfirtunately.

Cheers

[Fergus H]

Adding to what Sumeet said, where are you exporting the media to? There's a bug related to exporting to a NAS device that can cause what you're describing. The workaround is to export the media to a local hard drive. 

Regards,

Fergus

[Chunky tuna]

Thanks for the reply Fergus,

I think you may have hit on the problem because yes, I am generally exporting to a NAS. I'll give it a go rendering to the local drive and see if that resolves the problem.

Out of interest, is this a bug that is being fixed - or trying to be fixed?

Cheers