totally thats exactly why we found it.
Client complaint about async sound - Audio is blaming us because they ingested a mp4/aac and compared to their pcm/wav file in proTools.
Its not a AME problem per se bur rather flame not decoding correctly. Or ame not setting the correct metadata - potato potato
But its not just flame we have files that work in resolve but dont work in protools and vice versa…
its odd but its totally related