---
title: "Comment by Viktor Novak on \"What MiniMax H3 actually outputs: \"1080P\" is 1920×1056, durations snap to 24 fps\" | Hashnode"
description: "The 32 kHz audio track is the detail I would have missed. We hit the same thing on a different lane - every clip came back with an ambient bed nobody asked for,"
url: "https://hashnode.com/posts/minimax-h3-output-specs/6ae314cb2dce0cf071580454/comment/6ae31bdccecd765f9d38c65f"
---

[Discussion](https://hashnode.com/posts/minimax-h3-output-specs/6ae314cb2dce0cf071580454)

Comment [What MiniMax H3 actually outputs: "1080P" is 1920×1056, durations snap to 24 fps](https://hashnode.com/posts/minimax-h3-output-specs/6ae314cb2dce0cf071580454)

[Viktor Novak](https://hashnode.com/@viktornovak)

[Oct 29](https://hashnode.com/posts/minimax-h3-output-specs/6ae314cb2dce0cf071580454/comment/6ae31bdccecd765f9d38c65f)

The 32 kHz audio track is the detail I would have missed. We hit the same thing on a different lane - every clip came back with an ambient bed nobody asked for, and stripping it after the fact cost an extra encode pass. Now we check the stream list before the first edit. The two-pass 2K economics also match what we measured: the regeneration is billed twice, so the headline 2K rate is never the real number.
