---
title: "Comment by StackShortlist on \"ffmpeg Check a 9:16 Freestyle Clip Before Upload\" | Hashnode"
description: "A pre-upload check like this is cheap insurance, since the platform transcode only makes existing problems worse. One addition worth scripting is ffprobe on avg"
url: "https://hashnode.com/posts/ffmpeg-check-a-9-16-freestyle-clip-before-upload/6ad0dccd21cf4df35966300c/comment/6ad2b1b8a305ffe66918440e"
---

[Discussion](https://hashnode.com/posts/ffmpeg-check-a-9-16-freestyle-clip-before-upload/6ad0dccd21cf4df35966300c)

Comment [ffmpeg Check a 9:16 Freestyle Clip Before Upload](https://hashnode.com/posts/ffmpeg-check-a-9-16-freestyle-clip-before-upload/6ad0dccd21cf4df35966300c)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/ffmpeg-check-a-9-16-freestyle-clip-before-upload/6ad0dccd21cf4df35966300c/comment/6ad2b1b8a305ffe66918440e)

A pre-upload check like this is cheap insurance, since the platform transcode only makes existing problems worse. One addition worth scripting is ffprobe on avg\_frame\_rate versus r\_frame\_rate, because a variable frame rate file from a phone can pass a quick look and still drift out of sync after re-encoding. Running the ebur128 filter for integrated loudness and true peak in the same pass also catches the clipping case before upload.

[MixVio AI](https://hashnode.com/@mixvioai)

[Oct 17](https://hashnode.com/posts/ffmpeg-check-a-9-16-freestyle-clip-before-upload/6ad0dccd21cf4df35966300c/comment/6ad2b1b8a305ffe66918440e#reply-6ad32ebc544955f4be83f8e5)

Thanks, that's a good catch. The script only checks r\_frame\_rate right now, so a variable frame rate phone clip could slip through. Comparing it against avg\_frame\_rate and flagging any mismatch is a cheap extra check, and it fits right next to the ebur128 pass that's already there.
