You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Prytsepov Andrey (JIRA)" <ji...@apache.org> on 2017/12/20 12:55:00 UTC

[jira] [Created] (OPENMEETINGS-1792) Bug in view record from OM in online/offline mode

Prytsepov Andrey created OPENMEETINGS-1792:
----------------------------------------------

             Summary: Bug in view record from OM in online/offline mode
                 Key: OPENMEETINGS-1792
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1792
             Project: Openmeetings
          Issue Type: Bug
          Components: Audio/Video
    Affects Versions: 4.0.0
         Environment: OM 4.0.0, Windows 10 Professional
            Reporter: Prytsepov Andrey
            Assignee: Maxim Solodovnik
            Priority: Critical
         Attachments: 20171213_записи.7z, 20171215_записи.txt

Not work records in OM 4.0.0.
ffmpeg was compiled by fresh instruction https://cwiki.apache.org/confluence/download/attachments/27838216/FFmpeg%20compilation%20in%20Windows%2010.pdf?version=4&modificationDate=1513618557000&api=v2.
Before it tried ffmpeg early versions, same errors.

Algorithm:
1. Follow in OM to room
2. Make record
3. exit room
4. go to records, but it not available to see it online or offline by downloading mp4

Errors always not the same. Sometimes i don't have errors and i can view and download record, but even if i got no errors i can view it after reboot Windows, because ffmpeg use files. After reboot sometimes i don't get errors and can view record.

I tried to get in test directory *.flv and *.wav files from "C:\red5\webapps\openmeetings\streams\11". I tried to make mp3, mp4 by ffmpeg without OM. In OM i do the record, get error, and get files that get record, with them i tried to do it in ffmpeg without OM. There is no problem to convert by ffmpeg without OM files *.flv, *.wav, but it is manual and video and audio are separated in different files, so it is no used in practice.







--
This message was sent by Atlassian JIRA
(v6.4.14#64029)