aravis

aravis copied to clipboard

To to so these steps seem to be necessary: 1 - Send a DISCOVERY_CMD with the flag "Allows broadcast of acknowledge" enabled (necessary flag value 0x11). 2 - Use the...

danrauch

Cameras don't always use the standard names for the most common features, like exposure, image rate, etc... Currently, ArvCamera checks for vendor and model, and behave differently when needed. The...

EmmanuelP

gvdevice: improve auto packet size

2

The computation of the expected test packet was wrong on some platform, so don't use sizeof. Also, GevSCPSPacketSize increment was not correctly take into account. And finally, don't limit the...

EmmanuelP

Auto negotiation of packet size doesn't seem to working all the time

3

**Describe the bug** Aravis seems to use a wrong size for IP-layer headers, this lets any reception of test-packets fail. The auto negotiation never test for packet sizes above the...

ebfarias

Using the buffer size does not work with variable frame size. We should use the trailer packet instead. See #720

EmmanuelP

Use the trailer packet instead. See #720

EmmanuelP

draft, port range is fixed to 10000..10010

EmmanuelP

Aravissrc times out when frame acquisition is not at a fixed frame rate

20

**Describe the bug** Not able to use aravissrc as a source when triggering the camera by hardware. The pipeline does not send the buffer downstream. The goal is to generate...

PauloFavero

On gst pipeline create do not exit if buffer is empty if TriggerMode = On. Fix #528

lc-spxl

Running two cameras simultaneously is problematic

3

**Describe the bug** If I run two cameras simulatenously application crashes in a few minutes. I see following messages in output: ``` [09:31:06.748] 🅸 stream-thread> [GvStream::find_frame_data] Discard late frame 2590...

aldoshkind