Response stop recordings with INDIVIDUAL mode

OpenVidu v2 Issues developing apps
1
  • When I make a conference call about 30 mins or more than with INVIDUAL recording mode, then I stop record. After about 20s or more than, I received response from KMS. Why long time for processing?
  • Env for test: OpenVidu 2.15.0, KMS 6.14.0

Thanks for help!

2

What do you mean by “I received response from KMS”?

3

So sorry! My means the response from the openvidu-server. From the moment I did the send stop/recording API to the moment I received this response quite a while. Could you tell me why?

4

We haven’t experienced such problem.

When the session has less duration than 30 min do you see the same blocking time?

5

I can still continue my session for more than 30 minutes. I tried it for 50 minutes, everything was fine until I stopped recording. server response is too long, about 45s-50s with 50-minute session.

6

Is this OpenVidu CE or OpenVidu Pro?

7

I use OpenVidu CE. Thanks!

8

I was asking because in OpenVidu Pro there’s a download time that increases a little bit the time it takes for INDIVIDUAL recordings to be available. But if I’m not mistaken, you say that the process that takes 45-50s to return is the REST API call to /openvidu/apu/recordings/stop/ID, not the “ready” recordingStatusChanged event or something similar. Is that right? If it is, it’s something we have not really seen so far. The stopping process for INDIVIDUAL recordings should be pretty much immediate. Does it happen all the times?

9
  • I made a conference with 4 devices about 20 minutes. then I called api stopRecording by Postman, the time for response about 10.7s. with longer tests, longer response times.
  • I realized that after I called api stopRecording, the server started compressing the webm files into a zip file. Maybe after zip file compression is completed, the server will respond. is it right? If so, is there any way I can bypass this file compression timeout? Or is there a way to configure the server to not compress the files?
    image
    image850Ă—324 42.2 KB
10

Yes, that’s right. The compression of INDIVIDUAL recordings is a blocking operation. Until the recording is ready and available in its final status, the REST API call won’t return. Right now this cannot be disabled.

1 Like
11

I got it. Thanks for help!