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.

Sign up for GitHub

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

Jump to bottom

Hardware Encoding/Decoding #67

Open
D1plo1d opened this issue Feb 1, 2023 · 1 comment
Open

Hardware Encoding/Decoding #67

D1plo1d opened this issue Feb 1, 2023 · 1 comment

Comments

@D1plo1d
Copy link

D1plo1d commented Feb 1, 2023

V4L2 supports hardware encoding and decoding via it's Memory to Memory (M2M) mode. Would it be possible to add support for hardware encoding to libv4l-rs?

This tutorial ( https://lalitm.com/hw-encoding-raspi/ ) seems to lay out how to do it for people how are fluent in C (ie. not myself, not without staring at it for a long time 😅).

Would this fit within the way things are setup in this library? Would it make more sense to try to build HW encode/decode separately on top of something like nix?

Also I'm not sure but this seems related to #15.
@MarijnS95
Copy link
Collaborator

Doesn't this crate already support all the necessary IOCTLs and memory mapping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@D1plo1d @MarijnS95