Since upgrading to Vegas Pro 23, I’ve started experiencing a small but noticeable audio dropout at the point where GoPro clips join.

I run a 3‑camera setup around my aircraft and edit everything using Vegas multicam. I’m aware that GoPro’s encoding isn’t always ideal, but this issue only appeared after moving to VP23 — VP22 never showed this behaviour.

At the moment, the problem makes Vegas Pro 23 unusable for my GoPro workflow. From what I’ve learned, the root cause seems to be related to how VP23 handles GoPro AAC audio padding, rather than Vegas itself being “broken”, but the end result is the same: I can’t reliably use VP23 unless there’s a workaround. I have tried legacy encoders but it makes not difference.

Copilot explains it like this:

Vegas Pro 23 switched to a newer AAC engine that is:

More accurate
More standards‑compliant
Less forgiving of GoPro’s padding metadata
Less tolerant of discontinuities between clips

This means:

When two GoPro clips meet, the padding is preserved
When Vegas re‑encodes to AAC, the padding becomes a tiny silence
You hear a “blip” or “dropout” at the join
So the difference isn’t your workflow — it’s the audio engine upgrade.
🎯 Why this affects GoPro specifically

GoPro AAC audio includes:

Encoder delay
Priming samples
End padding
Sometimes spatial audio flags (MAX)