https://trac.ffmpeg.org/ticket/494#comment:5

The dated link above shows the same bug, I'm seeing now using Pazera Video to MP4 1.5 Converter(I encoded a xvid with 5.1 ac-3 track to H264 recently) using updated FFMEG, but I thought it was fixed as the bug was reproduced and found 7 years ago by developers? Maybe it is a build error?

The odd thing is using Pazera Audio Extractor 2.9 no such ac-3 errors manifest doing the audio separately, but they are all FFMG based are they not? Thanks for any insights.