unable to mux webm

Dani

Member
everything worked ok until Dec 5,
then - whenever I try to mux the flashphoner output I get this error:

ffmpeg -i sh.webm -itsoffset -0.05 -i sh_s.webm -r 30 test.mp4


ffmpeg version 3.4.9 Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-44)
configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --docdir=/usr/share/doc/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' --extra-ldflags='-Wl,-z,relro ' --extra-cflags=' ' --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-version3 --enable-bzlib --disable-crystalhd --enable-fontconfig --enable-gcrypt --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libcdio --enable-libdrm --enable-indev=jack --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libmp3lame --enable-nvenc --enable-openal --enable-opencl --enable-opengl --enable-libopenjpeg --enable-libopus --disable-encoder=libopus --enable-libpulse --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libv4l2 --enable-libvidstab --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzvbi --enable-avfilter --enable-avresample --enable-libmodplug --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-libmfx --enable-runtime-cpudetect
libavutil 55. 78.100 / 55. 78.100
libavcodec 57.107.100 / 57.107.100
libavformat 57. 83.100 / 57. 83.100
libavdevice 57. 10.100 / 57. 10.100
libavfilter 6.107.100 / 6.107.100
libavresample 3. 7. 0 / 3. 7. 0
libswscale 4. 8.100 / 4. 8.100
libswresample 2. 9.100 / 2. 9.100
libpostproc 54. 7.100 / 54. 7.100
[matroska,webm @ 0xdcbf40] Invalid EBML number size tag 0x01 at pos 1427 (0x593)
sh.webm: Input/output error


what might cause this ?
(I can play the webm file on vlc)
 

Max

Administrator
Staff member
Good day.
everything worked ok until Dec 5,
Have you updated WCS at this time? If yes, did rollback to previous version help?
Please also clarify what WCS build do you use?
Also please chaek if ffmpeg was updated.
If there are no changes in software, seems like the problem is in stream published and recorded. If the problem is still reproducing, please provide a recording sample file using this form. Also please clarify how do you publish a stream including constraints example.
 

Dani

Member
Upgrading the server to the latest version solved that issue, although very strange as no version / code change happened when the format got corrupted.
 

Max

Administrator
Staff member
Upgrading the server to the latest version solved that issue, although very strange as no version / code change happened when the format got corrupted.
Perhaps there were some recording fixes or media packets parsing fixes between the latest build and the biuld you've used. The changes may not affect webm container directly.
 

Dani

Member
It happened again, from Jan 1st I can't mux again with this error:
[matroska,webm @ 0x1572f40] Invalid EBML number size tag 0x01 at pos 1427 (0x593)
sh978VID2020270.webm: Input/output error

Nothing was updated on the server.

I've uploaded the sample files using your form, and this is my ffmpeg command:
ffmpeg -i sh49VID2020319.webm -itsoffset -0.05 -i sh49VID2020319_s.webm -r 30 test.mp4
 
Last edited:

Dani

Member
sh49VID2020319.webm: Error in the Matroska file structure at position 303. Resyncing to the next level 1 element.

Resyncing successful at position 4527.

sh49VID2020319_s.webm: Error in the Matroska file structure at position 303. Resyncing to the next level 1 element.

Resync failed: no valid Matroska level 1 element found.

These are the errors when I try to use another muxer on the files I've uploaded.
 

Max

Administrator
Staff member
Could you try with ffmpeg 4.x ?
If you can play this file in VLC, ffmpeg 4.x might be a fix too.
 

Dani

Member
tried - same error:
ffmpeg version 4.4.1-full_build-www.gyan.dev
[matroska,webm @ 0000021e7b5ed080] Length 8 indicated by an EBML number's first byte 0x01 at pos 1427 (0x593) exceeds max length 4.
[matroska,webm @ 0000021e7b5ed080] Element at 0x4b ending at 0x804dbb8c53abd8 exceeds containing master element ending at 0x13f7
Input #0, matroska,webm, from 'sh49VID2020319.webm':
Duration: N/A, bitrate: N/A
[matroska,webm @ 0000021e7b5ee4c0] Length 8 indicated by an EBML number's first byte 0x01 at pos 1427 (0x593) exceeds max length 4.
[matroska,webm @ 0000021e7b5ee4c0] Element at 0x4b ending at 0x804dbb8c53abd8 exceeds containing master element ending at 0x13f7
Input #1, matroska,webm, from 'sh49VID2020319_s.webm':
Duration: N/A, bitrate: N/A
Output #0, mp4, to 'test.mp4':
Output file #0 does not contain any stream
 

Dani

Member
One more update- looks like restarting WebCallServer will solve this to new recordings (but not for the already made) plus - we now know that it solves it for a period of few days and then the error resume....
 

Dani

Member
I'll try that. I don't know if this belongs to a new thread - but I see we have issues with the muxed files. when I check the ffmpeg log I get these errors:
[mp4 @ 0x14a4da0] Non-monotonous DTS in output stream 0:1; previous: 24533609, current: 21660000; changing to 24533610. This may result in incorrect timestamps in the output file.

the file plays till 40% and than it hangs. so something is wrong in the webm files, which used to great in the past.

we are using 5.2.1109
 

Max

Administrator
Staff member
If this tweak does not help
Code:
webm_java_writer_enable=false
then we need an original streams dumps and debug logs to reproduce the problem. So you should collect a report as described here and traffic dump:
1. Enable client debug logs
2. Start tcpdump to collect
Code:
tcpdump -npi any -B 10240 -w log.pcap[CODE]
3. Publish the steams with recording in a couple of minutes (enough time to reproduce the recording file issue)
4. Stop publishing
5. Stop tcpdump
Send the report archive, traffic dump and recordings using [URL='https://forum.flashphoner.com/submit_en/?thread=aHR0cHM6Ly9mb3J1bS5mbGFzaHBob25lci5jb20vdGhyZWFkcy91bmFibGUtdG8tbXV4LXdlYm0uMTQwNDYv&required=report']this form[/URL].
 
Top