V4L2 frame buffer length fix + extra option for faster stdout frame dump #51
+343
−323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While attempting some integration of fswebcam in a raspberry Pi based project I became interested in a faster way to grab a raw frame dump (no transcoding, no processing, just a fast raw dump from the device directly through stdout). The actual length of the data captured in the V4L2 buffer was the first issue identified. Additionally the need for an option to disable post processing was identified, but the attempted solution might not satisfy everyone.