Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

Handling of frame data in Start_Streaming@buffer when Acquisition Stop is performed #181

Open
nak-biz opened this issue Apr 4, 2024 · 2 comments

Comments

@nak-biz
Copy link

nak-biz commented Apr 4, 2024

Hello,
When Acquisition Mode is set to "Continuous",
What happens to the frame data in the StreamingBuffer at 'Acquisition Stop'?

[Hypothesis]

  1. All frame data is ejected (cleared) and the Buffer becomes empty.
    After that, when 'Acquisition Start' is executed, Buffer from that point will be newly accumulated.

  2. If Acquisition Stop is executed, the Buffer will remain as it is.
    When Acquisition Start is executed, the previous Buffer data will be ejected (cleared) and the new Buffer data will be accumulated.

--
I confirmed the actual operation with Alvium 1800 U-158c or 240c and it seems to be 2.
Is this understanding correct? Also, is there any way to make it like 1?

@Teresa-AlliedVision
Copy link

VimbaPython is the Python API for our older SDK, so it will not receive any further updates or optimization.
Could you elaborate on what buffer you are referring to and what tests/code you used? Specifically the method for initalizing and stopping the acquisition.
If it is not specifically related to the Python API, please contact support through our website form.
https://www.alliedvision.com/en/about-us/contact-us/technical-support-repair-/-rma/

@nak-biz
Copy link
Author

nak-biz commented Apr 10, 2024

Thank you for your response.

Well noted.
I will ask the question once through the person in charge.
(In addition, I am not sure if this is specific to the Python API or not).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants