Anti-slop checks: decode, sync, and a verified MP4
Autoretto runs on automation. But automation is not trust. Trust comes from verification. So every release, from a quiet ambient loop to a loud rock track, goes through the same set of quality gates. They are not there to judge taste. They are there to catch broken files, fake success, and sloppy handoffs.
The first gate is real audio decoding. When Suno hands back a track, it arrives as a file, usually in an audio format. A file that exists is not the same as a file that plays. So our pipeline opens that file and decodes it with an actual audio decoder. Not a header read. Not a file-size check. A full decode. We confirm the track has a valid sample rate, a channel count, and a duration that matches what Suno reported. If the decoder fails or the numbers mismatch, the gate fails. This catches corrupted exports and truncated generations before they get anywhere close to a viewer.
The second gate is audio-to-video sync. Autoretto builds visuals from your artwork and your motion choices. Some releases add Sora-generated cinematic motion. All of that gets assembled into a single timeline. But assembly is not the same as alignment. We check the actual video stream against the actual audio stream. We look at the duration of both. We confirm the video starts when the audio starts and ends when the audio ends. On a beat-synced video, we also confirm that the visual cuts or motion cues occur at the timestamps the project defined. The goal is simple: no silent lead-in, no video that runs past the final note, no beat that lands off by half a second.
The third gate is the most stubborn. We refuse to claim a publish without a verified MP4 artifact. That means the final output of the assembly step must be an MP4 file that exists on disk, has a non-zero size, and passes a container check. We parse the MP4's structure, read its moov atom, and confirm it contains both the audio and video tracks we think it contains. We also run a quick integrity check on the file's duration. If any part of that verification fails, we do not mark the release as published. We do not assume it will be fine later. We do not write a success log and hope. The publish state is set only after the artifact is real.
These three gates work together as our anti-slop layer. Slop is not a word about genre or taste. Slop is what happens when a system produces output that looks done from the outside but is broken on the inside. An audio file that won't decode. A video that drifts out of sync. A publish claim backed by a missing file. Those failures are easy to miss if you only glance at a dashboard. The gates force us to look closer. They turn 'probably fine' into 'verified fine'.
When a gate fails, the run stops. It does not retry automatically in a blind loop. It marks the release as failed and sends a signal that a human can inspect. Sometimes the failure is transient, and a clean retry works. Sometimes it reveals a deeper problem, like a bad prompt or a tooling issue. Either way, the failure is visible. That visibility is a feature. A system that never fails is not trustworthy. A system that fails and tells you honestly is.
These checks are not optional add-ons. They run on every release, every time, regardless of whether the creator is on a free plan or a heavy schedule. The cost is a few seconds of compute. The benefit is that when Autoretto says your release is published, you can trust the word. The MP4 exists. The audio plays. The video moves with the sound. That trust is the whole point.