Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-09-11 Thread Michael Kohne via ffmpeg-user
On Tue, Mar 5, 2019 at 11:25 AM Carl Eugen Hoyos  wrote:

> 2019-03-05 16:45 GMT+01:00, Michael Kohne :
> > On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne 
> wrote:
> >
> >> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos 
> >> wrote:
> >>
> >>> 2019-02-21 15:24 GMT+01:00, 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
> >>>
> >>> 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.
> >>
> >> 
> >
> > 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
>
>
Dredging up this question again - I have not had the time to play with the
delay and adelay filters, hopefully soon.

To refresh the memory, I'm trying to transcode a stream two to avi files by
using the tee muxer, and the errors are:
[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 got around the issue for the moment by simply double-encoding, but I want
to try to understand what's going on.

My question of the moment is:
Does the muxer (specifically the AVI muxer) push any kind of information
back upstream to the encoder?
Because if it does, then that might explain the problem - the tee muxer
might not be quite up to merging that info from two instances of the muxer,
and things go to hell from there.

Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
mhko...@moberg.com

-- 






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 


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-03-05 Thread Carl Eugen Hoyos
2019-03-05 16:45 GMT+01:00, Michael Kohne :
> On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne  wrote:
>
>> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos 
>> wrote:
>>
>>> 2019-02-21 15:24 GMT+01:00, 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
>>>
>>> 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.
>>
>> 
>
> 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
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-03-05 Thread Michael Kohne
On Fri, Feb 22, 2019 at 7:31 AM Michael Kohne  wrote:

> On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos 
> wrote:
>
>> 2019-02-21 15:24 GMT+01:00, 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
>>
>> 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.
>
> 

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 


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-02-22 Thread Michael Kohne
On Thu, Feb 21, 2019 at 9:35 AM Carl Eugen Hoyos  wrote:

> 2019-02-21 15:24 GMT+01:00, 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
>
> 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
  libavformat58. 26.101 / 58. 26.101
  libavdevice58.  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
  libpostproc55.  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.00, 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/20 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 

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-02-21 Thread Carl Eugen Hoyos
2019-02-21 15:24 GMT+01:00, 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

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
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-02-21 Thread 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
libavformat58. 26.101 / 58. 26.101
libavdevice58.  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
libpostproc55.  4.100 / 55.  4.100

Operating system is CentOS 6, 32 bit.


Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
mhko...@moberg.com


On Wed, Feb 20, 2019 at 5:40 PM Carl Eugen Hoyos  wrote:

> 2019-02-20 19:40 GMT+01:00, 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 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
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org 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 


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
  libavformat58. 26.101 / 58. 26.101
  libavdevice58.  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
  libpostproc55.  4.100 / 55.  4.100
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.00, 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
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/20 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=   37 fps=0.0 q=19.3 size=N/A time=00:00:01.42 bitrate=N/A dup=1 drop=0 
speed= 2.7x
frame=   53 fps= 51 q=31.0 size=N/A time=00:00:01.90 bitrate=N/A dup=1 drop=0 
speed=1.85x
frame=   68 fps= 44 q=31.0 size=N/A time=00:00:02.36 bitrate=N/A dup=1 drop=0 
speed=1.54x
frame=   83 fps= 41 q=31.0 size=N/A time=00:00:02.85 bitrate=N/A dup=1 drop=0 
speed= 1.4x
frame=   98 fps= 38 q=31.0 size=N/A time=00:00:03.44 bitrate=N/A dup=1 drop=0 
speed=1.34x
frame=  114 fps= 37 q=31.0 size=N/A time=00:00:03.92 bitrate=N/A dup=1 drop=0 
speed=1.28x
frame=  126 fps= 35 q=31.0 size=N/A time=00:00:04.41 bitrate=N/A dup=1 drop=4 
speed=1.23x
frame=  

Re: [FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically

2019-02-20 Thread Carl Eugen Hoyos
2019-02-20 19:40 GMT+01:00, 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 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
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] [avi @ 0x9873ba0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1104 >= 1104 [avi @ 0x987d2a0] Application provided invalid, non monotonically incr

2019-02-20 Thread 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
libavformat58. 20.100 / 58. 20.100
libavdevice58.  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
libpostproc55.  3.100 / 55.  3.100

OS is CentOS 6, 32 bit.


Michael Kohne

Senior Software Engineer
Office: 215.283.0860 x208
mhko...@moberg.com

-- 






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 


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".