Closed abdul-mueed-shz closed 1 year ago
I am not sure I have fully understood the problem. Are you saying that it is impossible to perform an INDIVIDUAL recording of a Session, and at the same time broadcast it?
No, I think the recording issue is related to something wrong with our configuration. Our main point of focus was that we cannot broadcast individual streams to an rtmp url. You replied to us through the openVidu support email. We got our answer now that it's not possible to broadcast streams in the individual mode. I think we can close this issue now. Thanks a lot for your cooperation and quick reply.
Describe the bug We are using OpenVidu Pro 2.27.0. While creating the openVidu session using the rest api for the defaultRecordingProperties I am setting outputMode as INDIVIDUAL. The default output mode is COMPOSED. The recording is created sucessfully when I am using the COMPOSED output mode. But for INDIVIDUAL recording mode, The zip file which is created which should have separate recordings of all the streams has only a single json file and the files array in the json file is empty. Similar to this If I try to broadcast a session which has the outputMode set as INDIVIDUAL , I get an internal server error(500) from the openVidu server. But for the COMPOSED output mode the session is broadcasted sucessfully. I am using the openVidu rest apis to perform the actions described above and I am using Django Rest Framewok as my application server:
Expected behavior Irrespective of the outputMode the session streams should be successfully recorded or broadcasted. For the INDIVIDUAL output mode the zip file created should have the recording files of all the session streams and the session should be broadcasted sucessfully
Wrong current behavior For the INDIVIDUAL output mode of the defaultRecordingProperties the zip file created has no recording files and the server throws an internal server error when It is tried to broadcast the session.
OpenVidu tutorial where to replicate the error This is an intermittent issue, there are no particular steps involved to reproduce the issue. Only clue is that every time it occurred, a large file more than 1GB was involved.
Additional context The code for creating the session is:
` @action(detail=False, methods=['get'], url_path='(?P.+)/session')
def create_session(self, request, paper_code):
if request_has_any_right(self.request, [UserRight.ATTEMPT_EXAM]):
user = request.user
user_exam = get_object_or_404(UserExam, user=request.user,
paper__code=paper_code, exam__entity=user.entity,
is_deleted=False)
`