Thanks Tim, I’m not in front of the box at the moment. What do you mean stopped working?
It simply refused to export a clip with those settings. I never investigated.
Hi @ytf Can you point me to the ascii files?
Try this: /opt/Autodesk/mediaconverter/{flame_version}/profiles/MP4/video/H264
3 Likes
@john-geehreng Wasn’t it you who posted instructions here on how to do this?
@ytf I think I helped you with a constant bitrate preset, but that was based off of a post by @Jeff. Fortunately, we don’t have to do the ffmpeg stuff anymore.
1 Like
Now that we can finally export mp4s in 2025.2 I have come across the following issue. I delivered final masters as ProRes422hq and the SM versions as mp4s to a US client. Feedback from the audio post house was that their QC checks on the mp4s in Compressor show the mp4 deliveries are 2 frame longer in duration. Checking the deliveries back in Flame, Resolve, VLC and QT show the mp4 deliveries to be the correct duration. Making mp4s via Resolve from the ProRes422 masters give the correct clip duration in all applications mentioned above as well as Compressor. I have tried all mp4 preset variations from Flame with the same results, showing the extra 2 frames in Compressor. Any feedback on further troubleshooting the issue at hand?
Just to double check - the same file shows 2 extra frame in Compressor, but not anywhere else. Making a similar file with with something else other than flame, the files show correct frame count everywhere?
That sound to me like a meta data issue. Frames don’t appear or disappear, they exist in the video stream regardless of app. But how an app interprets meta data may make it think of stuff that doesn’t exist.
I’d compare the files from Flame and the comparison with various app that detail metadata, such as mediainfo, Switch, etc. to see if you can spot the discrepancy.
This could be as much a Flame bug as a Compressor bug.
And file a support case with ADSK. I don’t think this will be matter of settings but understanding what gets screwed up in metadata.
@allklier
the extra frames are only on the mp4 exports, prores422s are correct. That is the mind bending anomaly and this only shows up in Compressor.
I’ll investigate further.
try with a different audio codec… (not aac)
Can you actually see two extra frames in compressor? Like a frame where pixels are different than what the last frame should be?
I’m still not convinced that there are actually two separate physical frames in the file, vs. Compressor just saying that there are.
@eddiead have you reported the issue to out Support team?
I’m still in comms with the Audio Post House to get to the bottom of the issue and will report back as soon as I have clarity.
When you made the mp4, was it a foreground or background export? If it was only one, try the other.