-
Notifications
You must be signed in to change notification settings - Fork 10
Composite recording problems #6
Comments
We are creating a number of tests for the recorder precisely. I'll see if we can reproduce this in our test environment, so we can debug that. Thanks for the detailed report! I hope we can give more info during the next week. |
Hi, we have been working on improving composite and recorder. Could you check if the issue is fixed for you using the dev version? |
I'll give it a try as soon as possible, is dev version published or do I 2015-11-23 12:31 GMT+01:00 José Antonio Santos Cadenas <
|
Have a look at the documentation here |
You can also use version 6.2.0 that we released recently. This one has also the fixes for composite and recorder. |
Apparently it works properly, I have to make further tests, but I think you have spotted on the problem |
Can we close the issue then? |
Sure
|
Backgrounds
Composite is used only to record video from one user and audio for the rest of logged on users.
Composite is not used to deliver video nor audio to the logged on users, these negotiate independent WebRTC stream for each logged on user with the KMS
Detailed description
I have made several tests involving composite & hubport creation order:
In all these cases I can see a "black screen and no audio" during several seconds, the number of seconds is equal to the ellapsed time between "pipeline creation" and all "composite-recording infraestructure" initialization.
Apparently it should work if I create all "composite-recording infraestructure" when creating pipeline, and delaying recording to the moment that there are "at-least" two logged-on users. Unfortunately I have seen inconsistent behavior and also black screen.
Comparison with standalone recording features
If recorder is created for an individual webrtc stream (audio or audio&video) these problems not appear, you can create recorder whenever you want.
Workaround
Record each file in an indepedent way, use ffmpeg to combine files, invoking it from an embedded REST Server - as Jersey -
More information
This issue and detailed information could be seen in https://groups.google.com/forum/#!topic/kurento/FgHTaRYyp80
The text was updated successfully, but these errors were encountered: