Crash when Compiling a Video


Hey all, Trying out Datamaster for the first time and using the Video Overlay Feature. I managed to get the Video Synced Perfect I can play it but when I click “Accept Offset” it just freezes, left the program for 25min to see if it was just trying to process, not sure If I am missing something?

Regards Sven

Mine does the same, I even tried a very expensive computer with the latest i9 processor and it still wouldn’t work.

Hi Sven, tagging @Wtd here as well.

We haven’t seen issues with manual synchronization like this before, so any details you can provide will help us investigate. Most importantly, please send the video file you’re using (via WeTransfer or similar) and let us know your Windows version.

Thanks!

Sorry for the late Reply here you go, added the logs and the video, from about 2:04 in the data does it match the video.
on windows 11 using a RTX3580 on the laptop.

Hi, thanks for sharing all the data. I will investigate it.

What camera does this video come from?

Hi there l, thanks for the reply. I tested out a Insta 360x3

Hi, please see attached link.

This is the second part of my track session. It was recorded on a GoPro 11 in 1080p.

Also note that the ADU data for this track needs the start/finish tweaking to allow all the laps to be displayed in DM.

Thanks
Wayne

Hi, thanks for the upload. Unfortunately, the video file appears to be corrupted — it shows 0B in size and can’t be played with any standard player. Could you please reupload it?

Hi please try this link

2 Likes

Quick update on what I’ve found so far:

I tested both a high-res and a compressed video file on my Windows 10 machine. Both played fine — playback was a little choppy, but manual sync worked as expected. The +1 sec button didn’t jump to the end, and accepting the offset didn’t cause any weird behavior.

Since I’m working remotely right now, I won’t be able to check it on a Windows 11 setup until Monday, but I’ll follow up then.

I also looked into the BugTrap crash log you shared (link). It turns out the crash isn’t directly caused by video playback, which is a good sign. In your case, it happened when pressing Next frame while the video cursor was outside the valid range. I’ll protect agianst that in the next build.

Sven’s crash looks more random — I couldn’t reproduce it exactly, but I’ll be adding a fix just in case.

Figuring this out is high on my list, so I’ll keep the updates coming.

2 Likes