BitmapLiveSource.FPS does not seem to affect the rate at which BitmapLiveSourceLiveContentEvent is called.

MIP
, ,
1

Dear support,

I have Corporate 2017 R3 installed on the Dev machine.

Looking at the “MediaRGBVideoEnhancementLive” SDK sample:

In the “InitializeVideo” void, just after constructing the “BitmapLiveSource” object, I set the Frame rate like this:

_bitmapLiveSource.FPS = 10;

The “BitmapLiveSourceLiveContentEvent” is called at 12/ 25 / 16 events per second (assuming this is called for each frame = FPS) depending on the camera selected? All the Cameras are set to 8 FPS in the management Client.

Setting the BitmapLiveSource.FPS seems to have no effect?

Is there any way of controlling the Framerate precisely?

Best regards,

Werner

2

BitmapLiveSource.FPS has no effect, I found that too while testing, let me do alittle more research on that.

Meanwhile I am curious as to your observation that the framerate is not corresponding with how the camera is setup..

In my testing the frequency is corresponding with the setup of the camera stream. Please double-check if the rate does not fit with the configuration in the Settings and Streams tab for the camera.

Note; it is possible to make a rule that changes the FPS for a camera to something else than what is in the Settings and Streams tab for the camera. Check whether this is the case in your system.

Alternatively use the Smart Client live view having diagnostics overlay on to see the frame rate the camera is currently streaming.

3

Hi Bo,

Appreciate the help.

You are correct about the configured frequency.

I have built my own tool to accurately regulate frame frequency, but it would be preferable to be able to adjust the frame rate directly on source.

all the best

4

Hoping this Helps someone:

I found a BAD side effect on SDK 2018 R2. Having designed a solution on 2017R3, I was getting Expected Frame Rates. I set the ​BitmapLiveSource.FPS = XX. Without giving it much thought, although we now that this does not effect the actual received FPS. As soon as I upgraded to 2018 R2 (Skipped R1) My actual received FPS dropped to 1(and less) FPS for all devices…

After Investigation I found that Removing the “BitmapLiveSource.FPS = XX” line, the Frame rates normalised.

5

When using H.264 / H.265 we have decided that frame rate reduction does not save any resources, as all frames need to be decoded anyway.

So the GOP oriented codec will use key-frames-only, or all-frames. While MJPEG codec stream can in fact control FPS in more detail on the client side.

Consider to configure multiple streams, and select a sream if other FPS or resolution is needed.

6

Thanks Anders,

Appreciate the Clarification.

Regards,

Wernerr