-
-
Notifications
You must be signed in to change notification settings - Fork 396
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
V4l2 input #825
V4l2 input #825
Conversation
Signed-off-by: Paulchen-Panther <Paulchen-Panter@protonmail.com>
Hello @Paulchen-Panther 👋 I'm your friendly neighborhood bot and would like to say thank you for So that you and other users can test your changes more quickly, If you make changes to your PR, i create a new link to your workflow artifacts. Best regards, |
Signed-off-by: Paulchen-Panther <Paulchen-Panter@protonmail.com>
Here is your new link to your workflow artifacts. |
@Paulchen-Panther WHOAH! That's awesome! Thank you very much <3 This is exactly what I need for my EasyCap EMPIA chip based clone. Is there a buildbot where I could grab a build with this PR for my CoreElec? |
The good news: The build bot is exactly above your post. |
@Paulchen-Panther I'll contact Portisch, thank you one more time! |
How do I 'install' a PR build? |
@NKnusperer Yes. |
USB webcams no longer seem to be working since this implementation. My camera is recognised by Hyperion ng but throws the following errors: V4L2:/DEV/VI : Throws error nr: VIDIOC_STREAMON error code 5, Input/output error My webcam video format is: UYVY Thanks |
Summary
This PR reintroduces the input parameter into Hyperion. As in the classic version of hyperion, the input of a v4l device can be selected. As an example, I list the EasyCap Video USB Grabber (Fushicai UTV007), which also has two inputs (Composite / S-Video).
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
before:
now:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Fixes: #817