Closed OlivierLDff closed 1 year ago
I've correctly rebased on 0.10 to fix conflict introduced by my other PR.
Can you undo the rebase? Apologies, I was fixing the PR in my IDE, 0.10 is dead and is in "unless-this-kills-your-system-no-more-updates" mode
I'm not sure to understand, this PR was already targetting 0.10 branch, like my other PR. There were a conflict due to the lock introduced, I needed to fix for the merge to be possible. I guess this is quite an important bug fix, having frame rate divided by 2 doesn't kill the system, but make the library unusable on linux. 13 fps instead of 25 for a camera isn't acceptable
I would gladly cherry pick my multiples commits later and create other PR for the senpai branch, but it doesn't compile at the moment so I can't check if this works.
Ah. Apologies. Yeah, I'll make sure to cherry pick this and #127 for later.
Yes, I will do as soon as senpai branch will be compiling.
fix #128
stream.next
push internal buffers to v4l then callstream.start
. By default withnew
buffer count is 4.121 directly call
stream.start
, without setting any buffer. This result in v4l only having 1 buffer (I guess), so because there is no double buffer (or more), 1 frame out of two is skipped.I used the following python script to benchmark expected camera behavior:
And the following rust code:
The performance regression can easily be observed in v4l examples too by adding
stream.start
:https://github.com/raymanfx/libv4l-rs/blob/867d9b122fde603ff7f1bfcdf19de48845c9e1f7/examples/stream_capture_mmap.rs#L26-L29