We have problem with some composed recordings using always mode. The recording file is only showing a black screen, without audio and video.
I think this is very rare, because after hundreds of recordings, this is the second case I got with a black screen. The logs look the same as those with perfect recordings, would you have any idea how to find some fault, considering that it is something very difficult to reproduce?
I attached the log below.
OpenVidu server logs doesn’t show anything unusual.
How many participants appear usually in the recordings? In there only one participant, some connection problem can arise from time to time. If several participants are recorded, it is very rare if all of them are missing.
I see in the logs you are using CAMERAS, is this a new camera perhaps? Some cameras are hard to manage due to packet loss or incompatible codec.
It the session being watched by a real person? He/She can confirm the session was performing as expected and the problem is only in the recording?
Thanks for answering.
There are usually 1 to 2 participants that appear on the recordings.
In this room, there were 2 publishers and 70 subscribers.
I don’t think I understand your question about cameras. I do not know the specification of the devices.
We have an extensive chat history from that room. I noticed that at the beginning of the session, someone comments that “everything is stuck here”. After that the conference flowed normally, but the recording went black.
This recording is about 30 minutes long, which is exactly how long the call lasted. It was recorded using the new beta recording container. I believe that a new container that solved many other problems that we had previously, that’s why I was so intrigued by this one.
It seems there is an rare problem with recording container. In 2.15 version, we have made some improvements to container, so it is possible the problem is solved.
If it happens again, then we will need to implement some recording container debugging procedure to know what is happening inside it.
Hi Micael,
It happened again, I believe it is the second case with the 2.15 beta image.
Please, could you help us to implement container debugging?
thank you
Hello @Thiago_Henrique,
Right now it is not possible to debug the recording container in a proper way. We are working on this right now. We expect to publish a new beta of the new container in a few days to understand what is going on inside it.
Regards
Hello @micael.gallego,
I have container debug of black screen record. Curiously, chrome_debug.log was not generated, as in other debug records.
You could check please? The file link is at the end of the message.
I think this is related to 2 composed records started exactly at the same time:
{“id”:“Sala37974”,“name”:“Sala37974”,“outputMode”:“COMPOSED”,“resolution”:“1920x1080”,“recordingLayout”:“CUSTOM”,“customLayout”:“conf/”,“sessionId”:“Sala37974”,“createdAt”:1599003954411,“size”:0,“duration”:0.0,“url”:null,“hasAudio”:true,“hasVideo”:true,“status”:“started”}
{“id”:“Sala37978”,“name”:“Sala37978”,“outputMode”:“COMPOSED”,“resolution”:“1920x1080”,“recordingLayout”:“CUSTOM”,“customLayout”:“conf/”,“sessionId”:“Sala37978”,“createdAt”:1599003954411,“size”:0,“duration”:0.0,“url”:null,“hasAudio”:true,“hasVideo”:true,“status”:“started”}