<title> Out of sync audio on MP4 and webm

[angela487]

Is there an existing issue for this? (Please actually search the issues, instead of just checking the box)

• I have searched the existing issues

Bug description

I recorded a meeting yesterday, it downloaded in MP4 and I have downloaded it from the dropdown in webm. In both versions the audio is out of sync.

Steps To Reproduce

Recorded on Google Meet
Downloaded the files
played on quicktime
uploaded to VEED.io
Both versions out of sync

Environment including version

- Beesy: 
- OS: MacOS Sequoia 15.6.1 
- Browser: Chrome
- Media Player: Quicktime

Attachments

No response

[piyu-sh]

Hey @angela487 , what do we mean exactly by 'out of sync' here ?

Also could you please try playing the video in vlc media player as well just to rule out if its a format/codec issue ?

[angela487]

When I say out of sync, I mean the audio and the video don't match up. To fix it I had to move the audio forward a few seconds.

I have just played it with VLC and it does match up on there.

[piyu-sh]

I think its a common problem with quicktime e.g. found this on apple forums

Should we resolve this considering it works fine with vlc, so not an extension issue but a quicktime player one ?

[angela487]

It was the same when playing the webm file on chrome, and when I imported it into veed.io. When I played it in VLC is wasn’t out of sync but the audio was horrible quality (even though it was fine – just out of sync – on the others) Other downloads from beesy have played fine on QuickTime and imported fine into VEED.

…

On Thu, 16 Oct 2025 at 17:48, Piyush ***@***.***> wrote: *piyu-sh* left a comment (pi-ra/beesy-issue-tracker#91) <#91 (comment)> I think its a common problem with quicktime e.g. found this <https://discussions.apple.com/thread/252680507?sortBy=rank> on apple forums Should we resolve this considering it works fine with vlc, so not an extension issue but a quicktime player one ? — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYZ7PRZV75PTASIUTAJ3YTT3X7D6PAVCNFSM6AAAAACJIW6ZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJRG42TSMJSGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[piyu-sh]

Do you remember anything specific about this particular recording which you did different? e.g. using headphones or changing any settings

Also was it only for this recording and its working fine since then ?

[angela487]

No, nothing different hardware-wise. Perhaps I had updated something in the meantime. I haven't had to record again since so I don't know. I am concerned it might happen again though, so will find another solution. Appreciate your help.

…

On Fri, 17 Oct 2025 at 19:03, Piyush ***@***.***> wrote: *piyu-sh* left a comment (pi-ra/beesy-issue-tracker#91) <#91 (comment)> Do you remember anything specific about this particular recording which you did different? e.g. using headphones or changing any settings Also was it only for this recording and its working fine since then ? — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYZ7PRZLKJWYZB6COJCUQIT3YEVODAVCNFSM6AAAAACJIW6ZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJWGU2TQNBSGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[piyu-sh]

@angela487 can you go to extensions from browser settings and go to beesy and enable error logs ?

After that, can you try recording a sample meeting, just to confirm its a recurring issue ?

And also share what you see in that error section enabled earlier.