I have modified DemoDriver SourceCode. Try to test the GetLiveFrameInterval method. I put 1000 frames into the queue from the start. Each time GetliveFrameInterval take one frame. Then record the time.
If I set FrameRate to 25,Type to Jpeg, It will take about 17.5 frames per second。
If I set FrameRate to 10,Type to Jpeg, It will take about 8 frames per second。
So,if I put frames into the queue as the FrameRate , may cause the queue oversize.
The DemoDriver and MIP SDK version is 2020R1 , XProtect version is 2020R2。 CPUusage is about 70%.
I tried the newest MIP SDK(2022R1) from NuGet/Github and the newst XProtect(2022R2).But it seems to be the same. The practical FrameRate will a bit lower than Setting FrameRate。
In additon,can I get the source code of DemoDriverDevice to have more tests?
DemoDriverDevice is using screen grabbing and that operation is known for high CPU usage. It means that the actual FPS of the device depends on how much CPU is available on the machine where it is running, and the higher FPS is set, the more CPU is needed. If there is not enough CPU available, the actual FPS will differ from the value set in the camera settings.