Open namirfa opened 5 years ago
@namirfa Is this what they are seeing with their crash? Just running out of oomph?
So, this allows a query of the camera that enqueues (effectively) a marker that says that when the next timed frame-grab happens, that that image should be saved (without TF processing)? Or does it cause a frame-grab and save that (sans TF processing)?
In either case, 'twould seem that the name should include something about the lack of processing.
@fhcarter We might have been able to avoid the crashing by lowering the maxQueuedTasks property in the source configuration, though I am still not exactly sure what the source of that problem was. My suspicion is that it has to do with running out of oomph, since lowering the pollTime also seemed to help a bit as well.
This enhancement would allow the select statement to capture a new frame and save it without processing. I will change the name to something more like "saveNextFrameWithoutProcessing" (that seems a little verbose, I'll try to think of something more succinct).
@namirfa OK, that makes sense. Does the new query actually grab a frame? Or does it just mark that the next grab, whenever it is, should be saved.
@fhcarter It will actually go and capture a new frame. I think that will be easier than trying to mess around with the configuration for the polled requests.
@namirfa -- good -- I think that makes more sense. Would it make sense to simply add an optional parameter suppressImageProcessing
(which can be true or false) to the processNextFrame
operation parameters? Since there are already various save options, it seems like the image processing aspect is what's really changing.
@fhcarter Absolutely that should work, probably the easiest way to go about doing this. Thanks for the recommendation!
Currently, querying the object rec source with the "processNextFrame" parameter will capture a new frame and process it, optionally saving it locally or to VANTIQ.
This enhancement would enable a new query parameter, "saveNextFrame", which would capture a new frame and save it locally or to VANTIQ, without processing the frame.
@bruden01 @pburma This should hopefully improve the speed when refreshing the frame in the client.