1

Hello, I'm using the system to capture and replay golf swings from two cameras using a UDP trigger. It all works great using 2 instances of the application: one instance with 2 capture windows saving to separate (non cloud sync'd) folders and one instance with 2 replay windows watching the 2 capture folders set to 25% speed.

I saved the configuration using the Workspaces feature then exported the link to the desktop so my kids can just click on it to load the replays easily. But after closing the application, then reopening with the link, the two replay windows will (usually) properly start playing the most recent file in the folder, but the capture windows will only properly load 1 of the cameras. The other camera stays black. And when the UDP trigger happens neither capture window captures and updates the video in the folder.

To get it working I need to close both windows in both instances and open them back up. If I only close/open new capture windows, the replay windows still won't update with new files in the folder.

Note: I am using a static filename for the capture files so that the system auto-overwrites the files to prevent having to manually delete all the videos.

Is this user error on saving or setup?

Thanks

2

Thanks for the description, I'll do some tests.

When the trigger happens do you see the capture window switching to recording at all with the red bar? Or is it not armed at all and the trigger is completely ignored?

If it's recording but the output file is not updated it's probably because it's already opened in the playback window as you mention using a static filename. Can you try with a dynamic filename just to see if that's the cause of the problem? (Just enabling "auto-numbering" should be enough to test this).

If that's the origin of the problem it might be tricky, maybe we need a different mechanism where it cycles between a few files instead of just one. This could be an extra option next to "auto-numbering" for the max allowed number and when it reaches that number it goes back to 0 and starts again.

3

Yes, the capture window switches to recording with the red bar for both capture windows, but when I check the file size for the captured video for the capture window that is black, the file size is 0 bytes.

I also created new windows using dynamic filenames (the default date/time based names) and it behaved the same way. It worked great after initial setup, but when I closed the windows then reopened them using the saved workspace link one of the capture windows was black and the file size after a trigger event was 0 bytes.

So it looks like it's not the file naming causing the issue.