I use my Osmo Action 5 for recording music gigs.
I use a Movo VXR10 for the audio as the internal mic sound is too compressed for this purpose.
When recording for about 50minutes the audio lags about 40secs behind the video, which makes it unuseable.

My thoughts are the delay could be caused by
1. the mic
2. the 3.5mm to usb adapter cable
3. the sd card speed
4. the camera software (I'm on the latest firmware)

Confusingly the MP4 file was 52:46 long, but the backup .wav file recorded automatically with the internal mic was 52:02 long, but on playback you're listening to the external mic audio which is obviously the same length as the video as its in the same file.

I've done 2 tests this morning, clapping after 30 minutes recording to the microSD card and then the internal memory, and both of them are perfect, which should rule out the sd card being too slow. (It's Samsung evo select 512GB microSDXC 130MB/s Full HD & 4K UHD, UHS-I, U3, A2, V30), and also the mic itself (I have ordered a Zoom AM7 to try out to see if it's any better but can't see how it will be after this test)
But on the 50minute music video by 30mins the external mic audio is 30 secs behind the video!

Any suggestions to a cause or a solution?

many thanks!

Hi there,

Thank you for reaching out. We are truly sorry for the inconvenience you are experiencing.

Please provide the requested information below for us to check further on this issue with the relevant team.
*[Original Footage] with lagged audio recorded by Movo Mic, the video file name starts with "DJI"
*[Backup audio] recorded by OA5 Pro
*[OA5 Log]
*[OA5 firmware version]

We are looking forward to your response for further assistance. Thank You

DJI Gamora Posted at 10-30 22:18
Hi there,

Thank you for reaching out. We are truly sorry for the inconvenience you are experiencing.

Thanks for your reply. Folder with log, mp4 and audio backup here

https://drive.google.com/drive/folders/14oF8LtmAm-aqbcf1BkKl0rwD8pW0ds49?usp=drive_link

The firmware version was the one before the current release. The notes with the current release don't mention this issue so I assume won't fix it. I haven't had chance to confirm that yet.  ( the log file is still uploading 10.49 1/11/24 )