Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDMI-grabber and optimization #157

Open
jjsarton opened this issue Sep 8, 2022 · 0 comments
Open

HDMI-grabber and optimization #157

jjsarton opened this issue Sep 8, 2022 · 0 comments

Comments

@jjsarton
Copy link

jjsarton commented Sep 8, 2022

I have performed tests with an HDMI-grabber attached to a USB-3 input. The video source was from a video camera.
The frame rate for the v4l2 device was 50 FPS, this result of processing the data 50 time per second. For WebRTC purpose this is not ideal and processing only all 2., 3,… frames may be good.
For such applications, we can stream to the virtual v4l2 device with a size of 640×360 instead of the size of 1920×1080 for the camera input. Processing the data with the full acquired picture size result to a high CPU load. Reducing the size of the input stream to the output stream size result in 1/3 processor time.
With an actual i9 system, I had 15.4 ms, e.g., 4.5 ms. On an older system, the values were 72 ms and 18 ms.

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

No branches or pull requests

1 participant