rawshift_video_core::VideoEncoder ships as a finished trait seam with no implementations — send-frame / receive-packet / flush, mirroring the decode side. Nothing implements it, and rawshift-video's feature tree has no -encode flags because there is nothing for them to gate.
Worth settling before anyone starts:
- Which codecs.
docs/SUPPORT.md rules out shipping software H.264/HEVC on patent grounds, and that reasoning applies to encode at least as strongly. Hardware encode is available — this machine's VAAPI driver exposes VAEntrypointEncSlice for H.264, HEVC and AV1 — so a hardware-backed encoder is the path that fits the existing policy.
- Which containers. Muxing is a separate problem from encoding;
mp4-atom writes boxes as well as reading them, so MP4 muxing is within reach.
Follow-up to #39.
rawshift_video_core::VideoEncoderships as a finished trait seam with no implementations — send-frame / receive-packet / flush, mirroring the decode side. Nothing implements it, andrawshift-video's feature tree has no-encodeflags because there is nothing for them to gate.Worth settling before anyone starts:
docs/SUPPORT.mdrules out shipping software H.264/HEVC on patent grounds, and that reasoning applies to encode at least as strongly. Hardware encode is available — this machine's VAAPI driver exposesVAEntrypointEncSlicefor H.264, HEVC and AV1 — so a hardware-backed encoder is the path that fits the existing policy.mp4-atomwrites boxes as well as reading them, so MP4 muxing is within reach.Follow-up to #39.