Closed ghost closed 6 years ago
Please ensure use USB 3.0 port and run with correct device index, e.g. ./sample/bin/camera 1
You could run
<sdk>/tools/list_devices
in the Terminal to see the indexes. See "/samples/README.md" to learn more.
About "corrupted data (0 bytes)", FFMpeg prints this information because that V4L2/the driver isn't clearing up properly after the capture.
However, our SDK did not depend on FFMpeg on Linux since 1.6.
when runngin ./sample/bin/camera
Dequeued v4l2 buffer contains corrupted data (0 bytes).
what is this??