mmids
mmids copied to clipboard
MultiMedia Ingestion and Distribution System
WebRTC doesn't support AAC codec, so in order to ingest or serve audio via WebRTC we need to support Opus codec. This involves: * [ ] - Add `Opus` to...
Workflow steps should be created that allow either ingesting media via WebRTC or connecting via WebRTC to watch a stream. * [x] - Publisher connection handler * [x] - Watcher...
Building mmids requires openssl to build making it a bit more annoying to build when you don't want/need tls support. It would be nice if tls was an optional feature,...
Ensure gstreamer and webrtc are adequately commented.
Right now `ffmpeg_pull` can be used to pull HLS feeds. Since this utilizes an external ffmpeg client, this requires the use of the RTMP subsystem, which means we are tied...
We should have a `rtmp_pull` workflow step that can pull live video from an RTMP server and move that video through workflow steps. This should not use ffmpeg but instead...
We should be able to generate HLS feeds without relying on ffmpeg. This would give us much more control over how files are generated and cleaned up.
Mmids should be able to utilize the `rml_rtmp` library's `ClientSession` types to perform RTMP/s pushes, without relying on ffmpeg.
Having RTMP as the only boundary media protocol currently restricts media to h264 and aac. Supporting rtsp, rtp, and rtcp will allow ingesting and working with more types of media.