[avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Michael Kohne
I'm using ffmpeg 4.1 to grab an rtsp stream (includes both H.264 video and
G.711 audio) from a Sony EP580 IP camera.

If I transcode to mpeg4v2 and aac to a single avi file, things seem to work
fine.
This command line will go for as long as I like (I regularly do 15 minutes
at a go).

ffmpeg -min_port 62000 -max_port 62004 -i rtsp://192.168.0.113/media/video1
-codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0 -f avi
/data/PatientData/vidtmp/test.avi


If I instead use the tee muxer to make two avi files:

ffmpeg -min_port 62000 -max_port 62004 -i rtsp://192.168.0.113/media/video1
-codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0 -f tee
"[f=avi]/data/PatientData/vidtmp/one.avi|[f=avi]/data/PatientData/vidtmp/two.avi"

Then within 2 minutes of starting the stream, it fails with the errors:
[avi @ 0x9873ba0] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 1104 >= 1104
[avi @ 0x987d2a0] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 1104 >= 1104

I've repeated these tests over and over for a week or so now, so I am
fairly confident that it's not simply that the camera is janky some of the
time. I've also tested using the rtsp stream 'rtsp://
184.72.239.149/vod/mp4:BigBuckBunny_175k.mov'. That stream does not produce
any errors with the tee muxer.

Note that those errors both appear to come from the avi muxers, not the tee
muxer, which is why I find it surprising: if the camera's output causes
this, then why doesn't it happen with the single avi muxer?

Test note: the tee invocation is the simplest command line that I could
come up with that produces the problem. In the real world one avi muxer
goes to a pipe for a live output display, and the other goes to the segment
muxer to produce output files in manageable chunks.

I did also try this with the latest ffmpeg snapshot (as of yesterday
morning), and there was no difference in behavior.

Any clues as to how to debug this would be greatly appreciated.


ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-11)
configuration: --prefix=/data/SHR4634/ffmpeg/build
--extra-cflags=-I/data/SHR4634/ffmpeg/build/include
--extra-ldflags=-L/data/SHR4634/ffmpeg/build/lib --extra-libs='-lm -ldl
-lpthread -lrt' --enable-gpl --enable-nonfree --disable-libfdk_aac
--enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libfreetype --enable-libspeex --enable-libtheora --cpu=i686
--enable-runtime-cpudetect
libavutil      56. 22.100 / 56. 22.100
libavcodec     58. 35.100 / 58. 35.100
libavformat    58. 20.100 / 58. 20.100
libavdevice    58.  5.100 / 58.  5.100
libavfilter     7. 40.101 /  7. 40.101
libswscale      5.  3.100 /  5.  3.100
libswresample   3.  3.100 /  3.  3.100
libpostproc    55.  3.100 / 55.  3.100

OS is CentOS 6, 32 bit.


Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
[hidden email]

--






Celebrating 20 Years

Transforming Neurocritical Care

Moberg
Research, Inc.

224 S Maple Street, Ambler, PA 19002

24/7 Customer
Support: 888.662.7246

www.moberg.com <https://www.moberg.com/>


_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Carl Eugen Hoyos-2
2019-02-20 19:40 GMT+01:00, Michael Kohne <[hidden email]>:
> I'm using ffmpeg 4.1 to grab an rtsp stream (includes both H.264
> video and G.711 audio) from a Sony EP580 IP camera.

> If I instead use the tee muxer to make two avi files:
>
> ffmpeg -min_port 62000 -max_port 62004 -i rtsp://192.168.0.113/media/video1
> -codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0 -f tee
> "[f=avi]/data/PatientData/vidtmp/one.avi|[f=avi]/data/PatientData/vidtmp/two.avi"

Please test current FFmpeg git head and provide the command
line together with the complete, uncut console output.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Michael Kohne
./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0
-f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
/data/vidtmp/out.txt 2>&1

Output attached as out.txt.

./ffmpeg --version
ffmpeg version N-93214-g7e4d3db Copyright (c) 2000-2019 the FFmpeg
developers
built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-11)
configuration: --prefix=/data/SHR4634/ffmpeg/build
--extra-cflags=-I/data/SHR4634/ffmpeg/build/include
--extra-ldflags=-L/data/SHR4634/ffmpeg/build/lib --extra-libs='-lm -ldl
-lpthread -lrt' --enable-gpl --enable-nonfree --disable-libfdk_aac
--enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libfreetype --enable-libspeex --enable-libtheora --cpu=i686
--enable-runtime-cpudetect
libavutil      56. 26.100 / 56. 26.100
libavcodec     58. 47.102 / 58. 47.102
libavformat    58. 26.101 / 58. 26.101
libavdevice    58.  6.101 / 58.  6.101
libavfilter     7. 48.100 /  7. 48.100
libswscale      5.  4.100 /  5.  4.100
libswresample   3.  4.100 /  3.  4.100
libpostproc    55.  4.100 / 55.  4.100

Operating system is CentOS 6, 32 bit.


Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
[hidden email]


On Wed, Feb 20, 2019 at 5:40 PM Carl Eugen Hoyos <[hidden email]> wrote:

> 2019-02-20 19:40 GMT+01:00, Michael Kohne <[hidden email]>:
> > I'm using ffmpeg 4.1 to grab an rtsp stream (includes both H.264
> > video and G.711 audio) from a Sony EP580 IP camera.
>
> > If I instead use the tee muxer to make two avi files:
> >
> > ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
> 192.168.0.113/media/video1
> > -codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0 -f tee
> >
> "[f=avi]/data/PatientData/vidtmp/one.avi|[f=avi]/data/PatientData/vidtmp/two.avi"
>
> Please test current FFmpeg git head and provide the command
> line together with the complete, uncut console output.
>
> Carl Eugen
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".
--






Celebrating 20 Years

Transforming Neurocritical Care

Moberg
Research, Inc.

224 S Maple Street, Ambler, PA 19002

24/7 Customer
Support: 888.662.7246

www.moberg.com <https://www.moberg.com/>



_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".

out.txt (16K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Carl Eugen Hoyos-2
2019-02-21 15:24 GMT+01:00, Michael Kohne <[hidden email]>:
> ./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
> 192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0
> -f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
> /data/vidtmp/out.txt 2>&1

You do realize that by separating the command line
from the console output, you make it harder to
understand the issue?

Does it work with "-re"?

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Michael Kohne
On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos <[hidden email]> wrote:

> 2019-02-21 15:24 GMT+01:00, Michael Kohne <[hidden email]>:
> > ./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
> > 192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100
> -map 0
> > -f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
> > /data/vidtmp/out.txt 2>&1
>
> You do realize that by separating the command line
> from the console output, you make it harder to
> understand the issue?
>
I'll try to not do that in the future.


> Does it work with "-re"?
>
> No, -re has no effect. Here's a run with -re set - same issue as the
original run.

./ffmpeg -loglevel info -re -min_port 62000 -max_port 62004 -i rtsp://
192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100 -map 0
-f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
/data/vidtmp/out.txt 2>&1

ffmpeg version N-93214-g7e4d3db Copyright (c) 2000-2019 the FFmpeg
developers
  built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-11)
  configuration: --prefix=/data/SHR4634/ffmpeg/build
--extra-cflags=-I/data/SHR4634/ffmpeg/build/include
--extra-ldflags=-L/data/SHR4634/ffmpeg/build/lib --extra-libs='-lm -ldl
-lpthread -lrt' --enable-gpl --enable-nonfree --disable-libfdk_aac
--enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libfreetype --enable-libspeex --enable-libtheora --cpu=i686
--enable-runtime-cpudetect
  libavutil      56. 26.100 / 56. 26.100
  libavcodec     58. 47.102 / 58. 47.102
  libavformat    58. 26.101 / 58. 26.101
  libavdevice    58.  6.101 / 58.  6.101
  libavfilter     7. 48.100 /  7. 48.100
  libswscale      5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc    55.  4.100 / 55.  4.100
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 11 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 11 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 17 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 22 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 2 packets
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://192.168.0.113/media/video1':
  Metadata:
    title           : SONY RTSP Server
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: h264 (Baseline), yuv420p(progressive), 1280x720, 30
tbr, 90k tbn, 180k tbc
    Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> msmpeg4v2 (native))
  Stream #0:1 -> #0:1 (pcm_mulaw (native) -> ac3 (native))
Press [q] to stop, [?] for help
[h264 @ 0xaf4dcc0] cbp too large (144) at 24 1
[h264 @ 0xaf4dcc0] error while decoding MB 24 1
[h264 @ 0xaf4dcc0] concealing 3545 DC, 3545 AC, 3545 MV errors in I frame
Output #0, tee, to
'[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi':
  Metadata:
    title           : SONY RTSP Server
    encoder         : Lavf58.26.101
    Stream #0:0: Video: msmpeg4v2, yuv420p, 1280x720, q=2-31, 200 kb/s, 30
fps, 30 tbn, 30 tbc
    Metadata:
      encoder         : Lavc58.47.102 msmpeg4v2
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1
    Stream #0:1: Audio: ac3, 44100 Hz, mono, fltp, 96 kb/s
    Metadata:
      encoder         : Lavc58.47.102 ac3
frame=   12 fps=0.0 q=21.0 size=N/A time=00:00:00.58 bitrate=N/A dup=1
drop=0 speed=1.16x
frame=   27 fps= 27 q=25.8 size=N/A time=00:00:01.03 bitrate=N/A dup=1
drop=0 speed=1.03x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 278 packets
[h264 @ 0xaf3d9c0] concealing 2165 DC, 2165 AC, 2165 MV errors in P frame
frame=   61 fps= 40 q=24.8 size=N/A time=00:00:02.03 bitrate=N/A dup=20
drop=0 speed=1.35x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 51 packets
[h264 @ 0xaef37c0] corrupted macroblock 79 34 (total_coeff=-1)
[h264 @ 0xaef37c0] error while decoding MB 79 34
[h264 @ 0xaef37c0] concealing 850 DC, 850 AC, 850 MV errors in I frame
frame=   79 fps= 39 q=31.0 size=N/A time=00:00:02.63 bitrate=N/A dup=23
drop=0 speed=1.31x
frame=   91 fps= 36 q=31.0 size=N/A time=00:00:03.03 bitrate=N/A dup=23
drop=0 speed= 1.2x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 54 packets
[h264 @ 0xaef37c0] Invalid level prefix
[h264 @ 0xaef37c0] error while decoding MB 66 32
[h264 @ 0xaef37c0] concealing 1023 DC, 1023 AC, 1023 MV errors in I frame
frame=  111 fps= 37 q=31.0 size=N/A time=00:00:03.70 bitrate=N/A dup=25
drop=0 speed=1.22x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 48 packets
[h264 @ 0xaf0c340] Invalid level prefix
[h264 @ 0xaf0c340] error while decoding MB 20 27
[h264 @ 0xaf0c340] concealing 1469 DC, 1469 AC, 1469 MV errors in I frame
frame=  118 fps= 34 q=31.0 size=N/A time=00:00:03.93 bitrate=N/A dup=25
drop=4 speed=1.12x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 8 packets
[h264 @ 0xaf24e80] concealing 2634 DC, 2634 AC, 2634 MV errors in P frame
frame=  136 fps= 34 q=31.0 size=N/A time=00:00:04.53 bitrate=N/A dup=25
drop=4 speed=1.12x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 6 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 1 packets
[h264 @ 0xaf4dcc0] out of range intra chroma pred mode
[h264 @ 0xaf4dcc0] error while decoding MB 2 35
[h264 @ 0xaf4dcc0] concealing 847 DC, 847 AC, 847 MV errors in I frame
frame=  151 fps= 33 q=31.0 size=N/A time=00:00:05.03 bitrate=N/A dup=25
drop=4 speed=1.11x
frame=  165 fps= 33 q=31.0 size=N/A time=00:00:05.50 bitrate=N/A dup=25
drop=4 speed=1.09x
frame=  177 fps= 32 q=31.0 size=N/A time=00:00:05.90 bitrate=N/A dup=25
drop=4 speed=1.06x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 54 packets
[h264 @ 0xaf5ad40] Invalid level prefix
[h264 @ 0xaf5ad40] error while decoding MB 66 32
[h264 @ 0xaf5ad40] concealing 1023 DC, 1023 AC, 1023 MV errors in I frame
frame=  195 fps= 32 q=31.0 size=N/A time=00:00:06.50 bitrate=N/A dup=26
drop=5 speed=1.07x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 39 packets
[h264 @ 0xaf52ec0] out of range intra chroma pred mode
[h264 @ 0xaf52ec0] error while decoding MB 75 30
[h264 @ 0xaf52ec0] concealing 1174 DC, 1174 AC, 1174 MV errors in I frame
frame=  206 fps= 31 q=31.0 size=N/A time=00:00:06.86 bitrate=N/A dup=26
drop=5 speed=1.05x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 8 packets
[h264 @ 0xaef37c0] Invalid level prefix
[h264 @ 0xaef37c0] error while decoding MB 25 12
[h264 @ 0xaef37c0] concealing 2664 DC, 2664 AC, 2664 MV errors in P frame
frame=  224 fps= 32 q=31.0 size=N/A time=00:00:07.46 bitrate=N/A dup=26
drop=5 speed=1.06x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 3 packets
frame=  235 fps= 31 q=31.0 size=N/A time=00:00:07.83 bitrate=N/A dup=26
drop=5 speed=1.04x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 25 packets
[h264 @ 0xaf24e80] negative number of zero coeffs at 23 27
[h264 @ 0xaf24e80] error while decoding MB 23 27
[h264 @ 0xaf24e80] concealing 1466 DC, 1466 AC, 1466 MV errors in I frame
frame=  256 fps= 32 q=31.0 size=N/A time=00:00:08.53 bitrate=N/A dup=26
drop=5 speed=1.06x
frame=  265 fps= 31 q=24.8 size=N/A time=00:00:08.83 bitrate=N/A dup=26
drop=5 speed=1.03x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 45 packets
[h264 @ 0xae738c0] concealing 848 DC, 848 AC, 848 MV errors in I frame
frame=  286 fps= 31 q=31.0 size=N/A time=00:00:09.53 bitrate=N/A dup=29
drop=5 speed=1.05x
frame=  296 fps= 31 q=31.0 size=N/A time=00:00:09.86 bitrate=N/A dup=29
drop=5 speed=1.03x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 48 packets
[h264 @ 0xaf56100] Invalid level prefix
[h264 @ 0xaf56100] error while decoding MB 79 30
[h264 @ 0xaf56100] concealing 1170 DC, 1170 AC, 1170 MV errors in I frame
frame=  316 fps= 31 q=31.0 size=N/A time=00:00:10.53 bitrate=N/A dup=30
drop=5 speed=1.04x
frame=  333 fps= 31 q=31.0 size=N/A time=00:00:11.10 bitrate=N/A dup=30
drop=5 speed=1.05x
frame=  348 fps= 31 q=31.0 size=N/A time=00:00:11.60 bitrate=N/A dup=30
drop=5 speed=1.04x
frame=  356 fps= 31 q=31.0 size=N/A time=00:00:11.86 bitrate=N/A dup=30
drop=5 speed=1.02x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 54 packets
[h264 @ 0xaf24e80] Invalid level prefix
[h264 @ 0xaf24e80] error while decoding MB 55 32
[h264 @ 0xaf24e80] concealing 1034 DC, 1034 AC, 1034 MV errors in I frame
frame=  376 fps= 31 q=31.0 size=N/A time=00:00:12.53 bitrate=N/A dup=31
drop=5 speed=1.03x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 47 packets
[h264 @ 0xaf3d9c0] corrupted macroblock 34 31 (total_coeff=-1)
[h264 @ 0xaf3d9c0] error while decoding MB 34 31
[h264 @ 0xaf3d9c0] concealing 1135 DC, 1135 AC, 1135 MV errors in I frame
frame=  391 fps= 31 q=31.0 size=N/A time=00:00:13.03 bitrate=N/A dup=31
drop=5 speed=1.03x
frame=  408 fps= 31 q=31.0 size=N/A time=00:00:13.60 bitrate=N/A dup=32
drop=5 speed=1.04x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 20 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 24 packets
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 3 packets
[h264 @ 0xae738c0] corrupted macroblock 53 24 (total_coeff=-1)
[h264 @ 0xae738c0] error while decoding MB 53 24
[h264 @ 0xae738c0] concealing 1676 DC, 1676 AC, 1676 MV errors in I frame
frame=  423 fps= 31 q=31.0 size=N/A time=00:00:14.10 bitrate=N/A dup=32
drop=5 speed=1.03x
frame=  437 fps= 31 q=31.0 size=N/A time=00:00:14.56 bitrate=N/A dup=32
drop=5 speed=1.03x
frame=  445 fps= 30 q=24.8 size=N/A time=00:00:14.83 bitrate=N/A dup=32
drop=5 speed=1.01x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 54 packets
[h264 @ 0xaf52ec0] concealing 1033 DC, 1033 AC, 1033 MV errors in I frame
frame=  467 fps= 31 q=31.0 size=N/A time=00:00:15.56 bitrate=N/A dup=34
drop=5 speed=1.03x
[rtsp @ 0xadfb340] max delay reached. need to consume packet
[rtsp @ 0xadfb340] RTP: missed 47 packets
[h264 @ 0xaef37c0] out of range intra chroma pred mode
[h264 @ 0xaef37c0] error while decoding MB 32 31
[h264 @ 0xaef37c0] concealing 1137 DC, 1137 AC, 1137 MV errors in I frame
frame=  480 fps= 31 q=31.0 size=N/A time=00:00:16.00 bitrate=N/A dup=34
drop=5 speed=1.02x
[avi @ 0xb1f0240] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 455 >= 455
[tee @ 0xae5b7c0] Slave muxer #0 failed, aborting.
[avi @ 0xb233b00] Application provided invalid, non monotonically
increasing dts to muxer in stream 1: 455 >= 455
[tee @ 0xae5b7c0] All tee outputs failed.
av_interleaved_write_frame(): Invalid argument
frame=  491 fps= 31 q=31.0 Lsize=N/A time=00:00:16.36 bitrate=N/A dup=35
drop=5 speed=1.03x
video:1366kB audio:186kB subtitle:0kB other streams:0kB global headers:0kB
muxing overhead: unknown
Conversion failed!

--






Celebrating 20 Years

Transforming Neurocritical Care

Moberg
Research, Inc.

224 S Maple Street, Ambler, PA 19002

24/7 Customer
Support: 888.662.7246

www.moberg.com <https://www.moberg.com/>


_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Michael Kohne
On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne <[hidden email]> wrote:

> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos <[hidden email]>
> wrote:
>
>> 2019-02-21 15:24 GMT+01:00, Michael Kohne <[hidden email]>:
>> > ./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
>> > 192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100
>> -map 0
>> > -f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
>> > /data/vidtmp/out.txt 2>&1
>>
>> You do realize that by separating the command line
>> from the console output, you make it harder to
>> understand the issue?
>>
> I'll try to not do that in the future.
>
>
>> Does it work with "-re"?
>>
>> No, -re has no effect. Here's a run with -re set - same issue as the
> original run.
>
> <snip log from previous message>

Given that -re didn't work, is there something else I should be doing to
try to understand this?
I'd prefer to not double my CPU usage by avoiding the 'tee' muxer.
I guess the first question is: Is this a bug in some way? Is it supposed to
do this for some reason that's unclear to me?

Thanks!

--






Celebrating 20 Years

Transforming Neurocritical Care

Moberg
Research, Inc.

224 S Maple Street, Ambler, PA 19002

24/7 Customer
Support: 888.662.7246

www.moberg.com <https://www.moberg.com/>


_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically increasing dts to muxer only when using tee muxer

Carl Eugen Hoyos-2
2019-03-05 16:45 GMT+01:00, Michael Kohne <[hidden email]>:

> On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne <[hidden email]> wrote:
>
>> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos <[hidden email]>
>> wrote:
>>
>>> 2019-02-21 15:24 GMT+01:00, Michael Kohne <[hidden email]>:
>>> > ./ffmpeg -min_port 62000 -max_port 62004 -i rtsp://
>>> > 192.168.0.113/media/video1 -codec:v msmpeg4v2 -codec:a ac3 -ar 44100
>>> -map 0
>>> > -f tee "[f=avi]/data/vidtmp/one.avi|[f=avi]/data/vidtmp/two.avi" >
>>> > /data/vidtmp/out.txt 2>&1
>>>
>>> You do realize that by separating the command line
>>> from the console output, you make it harder to
>>> understand the issue?
>>>
>> I'll try to not do that in the future.
>>
>>
>>> Does it work with "-re"?
>>>
>>> No, -re has no effect. Here's a run with -re set - same issue as the
>> original run.
>>
>> <snip log from previous message>
>
> Given that -re didn't work, is there something else I should be doing to
> try to understand this?
> I'd prefer to not double my CPU usage by avoiding the 'tee' muxer.
> I guess the first question is: Is this a bug in some way? Is it supposed to
> do this for some reason that's unclear to me?

The tee muxer is very special, I hoped that somebody
else who has used (or better: implemented) it would comment.

You could test the delay and adelay filter, I don't know the exact options out
of my head but I am curious if they at least can delay the issue you see.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".