We notice that Jibri depends on virtual audio and video devices to allow ffmpeg to capture the desktop audio and video. This seems to make Jibri resource-intensive. I’m wondering if anyone has tested a headless implementation of Jibri using the MediaStream Recorder API instead, which seems to be a simpler method.
The MediaStream Recording API makes it possible to capture the data generated by a MediaStream or HTMLMediaElement object.
This method could probably be implemented using headless chrome instead, but my guess is that there are reasons for doing it the way it’s being done now. Is it feasible to modify Jibri to work this way instead? Might anyone be able to explain the advantages / disadvantages of the different approaches?