In our application whenever we change the geometry of the camera we stop, tear
down the stream, make a new one, and start again:
https://github.com/areaDetector/aravisGigE/blob/master/aravisGigEApp/src/aravisCamera.cpp#L1243
It seems a little clumsy, but it works.
Thanks,
Tom
-----Original Message-----
From: aravis-bounce@xxxxxxxxxxxxx <aravis-bounce@xxxxxxxxxxxxx> On Behalf
Of Werner Zeindl-Nagele
Sent: 23 July 2018 08:00
To: aravis@xxxxxxxxxxxxx
Subject: [aravis] how to remove input-queue buffer in v0.5.x (2nd try now in
plain text)
Hi,
here once again my questions now in text format (not using IBM worse ;-)
we are currently using aravis v0.3.1 for a Basler GigE cam. For some
reasons we want now upgrade to aravis v0.5.x. As I've recognized the
arv_stream_pop_input_buffer() has become private since v0.3.5. So
what I want to know is how I can now remove(free) an input buffer? In
our current application we have to handle frequent changes of the
read-out-region for a grab in a grab-preparation phase some time
before the effective image aquisition starts (e.g. in movement phases
of our machine). Some times it can happen that a already prepared
snap is aborted before capture and in this case I used the
arv_stream_pop_input_buffer() to remove the buffer which never will
be grabbed in. How can I handle this use case now in newer aravis
versions to avoid a buffer grow on the input queue?
best regards
Werner
Confidentiality Notice:
This Email, and any attachments, may contain internal or confidential
information and is intended solely for the individual to whom it is addressed.
It may contain sensitive or protectively marked material and should be
handled accordingly. If this Email has been misdirected, please notify the
author immediately. If you are not the intended recipient you must not
disclose, distribute, copy, print or rely on any of the information contained
in
it or attached, and all copies must be deleted immediately.
