docs.rs failed to build waycap-rs-0.2.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
waycap-rs
A high-level Wayland screen capture library with hardware-accelerated encoding for Linux environments.
Features
- Hardware-accelerated video encoding (Using VAAPI or NVENC)
- Audio capture with Opus encoding
- Copy-Free video encoding leveraging pipewire's DMA Buffers
- Multiple quality presets for various use cases
- Cursor visibility control
- Simple, ergonomic API for easy integration
Requirements
- Linux with Wayland display server
- XDG Desktop Portal
- PipeWire
- VA-API compatible hardware for VAAPI encoding
- CUDA compatible hardware for NVENC encoding
Installation
Add this to your Cargo.toml:
[]
= "0.2.0"
Examples Usage
use ;
use ;
Primary Use Case: WayCap
This library was created primarily to support the development of WayCap -- a low-latency screen recorder targetting Wayland Linux DEs. waycap-rs originally lived within this application but was broken out to split library and application logic, you can read more about that project over at its github page
https://github.com/Adonca2203/WayCap
Contributing
Contributions are always welcome and encouraged, feel free to open a PR with any features you think may be missing.
Currently I have planned adding the following:
- Capturing more than system audio -- Support for microphones
Areas for Improvement aside from the things already mentioned:
- Any optimizations for the library's core capture logic.
- Documentation around the public facing APIs.
- Bug Reports via github Issues
- Platform Testing as I am currently limited by my hardware
- Leverage the GpuVendor field of EGL to dynamically set the target encoder
Pull Request Guidelines
- Fork the repository based off the
mainbranch. - Write clear and well documented with comments where appropriate.
- Unit Tests if applicable.
- Code Examples in
/examplesif applicable. - Include references to issues if applicable.