What is the timing mechanism for client-side snapshot capture?

Pakwa

August 20, 2026 12:32

Hi,

 

I ran into an issue while developing a plugin for the client's platform, and I would appreciate your help in troubleshooting it.

 

My plugin pushes events to the server based on IPC push events, using the frame timestamp provided by the server to the plugin.

 

As I understand it, snapshot capture should grab the video frame of the client's current channel. If recording is not enabled on the client side, it frequently results in 'No Data' errors, whereas enabling recording allows snapshots to be captured continuously.

 

However, in the client's production/live environment, snapshot capture occasionally results in 'No Data' errors, whereas in our development environment this almost never happens, and on my local machine, the success rate is 100%. Interestingly, if a user clicks on the video wall snapshot action, the recording from that exact moment can still be opened successfully.

 

I initially suspect this might be a network issue—specifically, that the server lacks sufficient caching, resulting in missing video buffers corresponding to that timestamp. But if that's the case, why is the corresponding recording still able to open? How can I verify that this is not an issue with my plugin?

0

• 

  williamjohn5987son

  August 21, 2026 05:02 Edited

  The fact that the recording can still be opened for the same timestamp suggests the video data exists, but the snapshot API may be requesting the frame before it is available in the expected buffer. I’d compare the exact timestamps sent by the IPC event with the timestamps of the frames actually available on the server, and log every snapshot request/result in both environments. Also test the same timestamp red humana login through the built-in snapshot action and your plugin.

  0

Please sign in to leave a comment.