You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Uwe Simon (Jira)" <ji...@apache.org> on 2021/03/17 18:05:00 UTC

[jira] [Created] (OPENMEETINGS-2595) Recording not created: ffmpeg message: LBRR frames is not implemented.

Uwe Simon created OPENMEETINGS-2595:
---------------------------------------

             Summary: Recording not created: ffmpeg message: LBRR frames is not implemented.
                 Key: OPENMEETINGS-2595
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2595
             Project: Openmeetings
          Issue Type: Improvement
          Components: Recordings
    Affects Versions: 6.0.0
            Reporter: Uwe Simon
            Assignee: Maxim Solodovnik


After update to 6.0.0 sometimes recording a converence is not possible.

In the openmeetings.log I see for one file

many

messages

Output #0, wav, to '/opt/omdata/streams/7/rec_76_af415d00-96ab-4839-8f3f-467c5d0ef54d_WAVE.wav':
 Metadata:
 ISFT : Lavf57.83.100
 Stream #0:0(eng): Audio: pcm_s16le ([1][0][0][0] / 0x0001), 32000 Hz, stereo, s16, 1024 kb/s (default)
 Metadata:
 title : Audio
 encoder : Lavc57.107.100 pcm_s16le[opus @ 0x563d132a7a40] 
*LBRR frames is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.*
[opus @ 0x563d132a7a40] Error decoding a SILK frame.
[opus @ 0x563d132a7a40] *Error decoding an Opus frame.*
[opus @ 0x563d132a7a40] LBRR frames is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[opus @ 0x563d132a7a40] Error decoding a SILK frame.
[opus @ 0x563d132a7a40] Error decoding an Opus frame.
[opus @ 0x563d132a7a40] LBRR frames is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
.....

In the recording I have 8 webm files, 7 of them no errors, but only one causes this issue.

 

It is reproducable when I call

ffmpeg -y **-i /opt/omdata/streams/7/rec_76_af415d00-96ab-4839-8f3f-467c5d0ef54d.webm -af aresample=32k:min_comp=0.001:min_hard_comp=0.100000 /opt/omdata/streams/7/rec_76_af415d00-96ab-4839-8f3f-467c5d0ef54d_WAVE.wav

 

Via google I found a solution that a ffmpeg should be called with an additional parameter

-acodec libopus

So I called manually

ffmpeg -y *-acodec libopus* -i /opt/omdata/streams/7/rec_76_af415d00-96ab-4839-8f3f-467c5d0ef54d.webm -af aresample=32k:min_comp=0.001:min_hard_comp=0.100000 /opt/omdata/streams/7/rec_76_af415d00-96ab-4839-8f3f-467c5d0ef54d_WAVE.wav

This call off ffmpeg generates the .wav file successfully.

 

Is there any place where I can configure the call of ffmpeg?

I only found the path



--
This message was sent by Atlassian Jira
(v8.3.4#803005)