Home/News | About | Download | Documentation | Forum | Bug Reports | Contact | Donations | Consulting | Projects | Legal | Security | FATE


converted file is jerky

Discussions about problems encountered using ffmpeg.
Forum rules
FFmpeg is in a state of perpetual development and we do not currently have the person power to backport fixes to official releases. As such, if you wish to query or report a bug, you must try with the latest development branch revision of FFmpeg to confirm the issue still exists. The latest FFmpeg can be downloaded from here: http://www.ffmpeg.org/download.html

converted file is jerky

Postby neuronetv » Sat May 18, 2013 9:25 am

I'm running openRTSP on a centos 5 server (command line only) and I'm recording video streams from an axis 207MW network camera using openRTSP. The raw video file created by openRTSP is called video-MP4V-ES-1 (with no extension) and the following command works in converting it to mp4:

# ffmpeg -i video-MP4V-ES-1 cam4a.mp4
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Input #0, m4v, from 'video-MP4V-ES-1':
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: mpeg4 (Advanced Simple Profile), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 19 tbr, 1200k tbn, 1k tbc
[libx264 @ 0xa56cce0] using SAR=1/1
[libx264 @ 0xa56cce0] using cpu capabilities: MMX2 SSE2Fast SSEMisalign LZCNT
[libx264 @ 0xa56cce0] profile High, level 2.2
[libx264 @ 0xa56cce0] 264 - core 132 r2310 76a5c3a - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - <link deleted> - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=19 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'cam4a.mp4':
Metadata:
encoder : Lavf55.7.100
Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 19456 tbn, 19 tbc
Stream mapping:
Stream #0:0 -> #0:0 (mpeg4 -> libx264)
Press [q] to stop, [?] for help
frame= 189 fps= 52 q=27.0 Lsize= 675kB time=00:00:09.84 bitrate= 561.6kbits/s dup=111 drop=111
video:672kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.413922%
[libx264 @ 0xa56cce0] frame I:1 Avg QP:21.98 size: 46003
[libx264 @ 0xa56cce0] frame P:75 Avg QP:21.00 size: 8390
[libx264 @ 0xa56cce0] frame B:113 Avg QP:25.20 size: 107
[libx264 @ 0xa56cce0] consecutive B-frames: 19.0% 1.1% 7.9% 72.0%
[libx264 @ 0xa56cce0] mb I I16..4: 10.0% 79.1% 10.9%
[libx264 @ 0xa56cce0] mb P I16..4: 0.9% 1.9% 0.3% P16..4: 35.5% 3.4% 5.2% 0.0% 0.0% skip:52.7%
[libx264 @ 0xa56cce0] mb B I16..4: 0.2% 0.0% 0.0% B16..8: 7.6% 0.1% 0.1% direct: 0.1% skip:91.9% L0:37.6% L1:60.1% BI: 2.3%
[libx264 @ 0xa56cce0] 8x8 transform intra:63.6% inter:71.7%
[libx264 @ 0xa56cce0] coded y,uvDC,uvAC intra: 64.4% 66.8% 33.6% inter: 10.8% 11.5% 6.5%
[libx264 @ 0xa56cce0] i16 v,h,dc,p: 36% 47% 15% 1%
[libx264 @ 0xa56cce0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 11% 49% 4% 5% 2% 7% 4% 6%
[libx264 @ 0xa56cce0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 34% 8% 18% 8% 7% 6% 8% 6% 5%
[libx264 @ 0xa56cce0] i8c dc,h,v,p: 49% 29% 19% 3%
[libx264 @ 0xa56cce0] Weighted P-Frames: Y:0.0% UV:0.0%
[libx264 @ 0xa56cce0] ref P L0: 81.0% 4.7% 10.0% 4.2%
[libx264 @ 0xa56cce0] ref B L0: 85.2% 13.4% 1.3%
[libx264 @ 0xa56cce0] ref B L1: 95.1% 4.9%
[libx264 @ 0xa56cce0] kb/s:552.77


problem is the resultant mp4 file is jerky when played. It freezes every few seconds for about a second and then carries on playing and is unwatchable. It does this in different players. If I rename the original raw file to video-MP4V-ES-1.mp4 I can play it in DivX player and the video is smooth but DivX is the only player that will play it and no other program can cope with the file, which is no good for my needs as I need to import it into video editors and such. How can I get a conversion to mp4 (or avi?) that will play properly like the original? I've tried several programs that are supposed to convert video files but nothing will work. These openRTSP raw dumps are a bitch and so far only the ffmpeg command will work in converting, albeit with jerky video. Thanks for any pointers.
neuronetv
 
Posts: 39
Joined: Sat May 18, 2013 9:07 am

Re: converted file is jerky

Postby burek » Sat May 18, 2013 2:21 pm

burek
 
Posts: 867
Joined: Mon May 09, 2011 10:16 pm
Location: Serbia

Re: converted file is jerky

Postby neuronetv » Sat May 18, 2013 2:47 pm

thanks but this is capture from a network cam, not a webcam. So far I haven't been able to find a command for ffmpeg to capture from a network cam.
neuronetv
 
Posts: 39
Joined: Sat May 18, 2013 9:07 am

Re: converted file is jerky

Postby burek » Sat May 18, 2013 2:55 pm

Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path out.mp4

Btw, if it's an IP webcam, it should have a web panel, accessible with web browser, where you could setup your mp4 output, so you avoid conversion from mpeg4 video to h264, using ffmpeg. You might tell your webcam to directly produce such a video and then use ffmpeg just to copy that to a file:
Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path -c copy out.mp4
burek
 
Posts: 867
Joined: Mon May 09, 2011 10:16 pm
Location: Serbia

Re: converted file is jerky

Postby neuronetv » Sat May 18, 2013 3:21 pm

sorry I'm getting nothing but silly problems with ffmpeg and I am using an ip cam, not a webcam.

# ffmpeg -i ffmpeg -i rtsp://your_cam_ip:port/additional_path out.mp4
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Input #0, rtsp, from 'ffmpeg -i rtsp://your_cam_ip:port/additional_path out.mp4':
Metadata:
title : Media Presentation
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: mpeg4 (Advanced Simple Profile), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 21.92 tbr, 90k tbn, 1k tbc
Stream #0:1: Audio: aac, 16000 Hz, mono, fltp
File 'out.mp4' already exists. Overwrite ? [y/N] y
[libx264 @ 0x97dae40] using SAR=1/1
[libx264 @ 0x97dae40] using cpu capabilities: MMX2 SSE2Fast SSEMisalign LZCNT
[libx264 @ 0x97dae40] profile High, level 2.2
[libx264 @ 0x97dae40] 264 - core 132 r2310 76a5c3a - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=21 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[libfaac @ 0x97dcce0] libfaac doesn't support this output format!
Output #0, mp4, to 'out.mp4':
Metadata:
title : Media Presentation
Stream #0:0: Video: h264 (libx264), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 90k tbn, 21.92 tbc
Stream #0:1: Audio: aac, 16000 Hz, mono, s16, 128 kb/s
Stream mapping:
Stream #0:0 -> #0:0 (mpeg4 -> libx264)
Stream #0:1 -> #0:1 (aac -> libfaac)
Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height


if I try some parameters:

# ffmpeg -i -s 640x360 -r 15 -t 30 rtsp://your_cam_ip:port/additional_path out.mp4
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
-s: No such file or directory


and yet all the ffmpeg docs clearly show -s as a valid parameter. I don't know what ffmpeg is asking for....
neuronetv
 
Posts: 39
Joined: Sat May 18, 2013 9:07 am

Re: converted file is jerky

Postby burek » Sat May 18, 2013 10:04 pm

Your errors are pretty simple. For your first example, your error is:
Code: Select all
[libfaac @ 0x97dcce0] libfaac doesn't support this output format!

so, simply adding a correct audio encoding options will make it work
Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path -ar 44100 -ac 2 -ab 128k out.mp4

also, you might avoid re-encoding, if all you want is just to grab the input that your IP cam is sending:
Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path -c copy out.mp4


Your 2nd issue is a simple typo error in your cmd line:
Code: Select all
ffmpeg -i -s 640x360 -r 15 -t 30 rtsp://your_cam_ip:port/additional_path out.mp4

(after "-i" there is no input file name) which is indicated also by this error message:
Code: Select all
-s: No such file or directory


Btw, specifying input parameters, like "-s 640x360 -r 15" will have no effect at all, because, as I told you, you need to configure your encoding options over IP cam's web panel, using your web browser. The stream that ffmpeg is receiving is already encoded, so there is no point of specifying such options before -i option, in your case.
burek
 
Posts: 867
Joined: Mon May 09, 2011 10:16 pm
Location: Serbia

Re: converted file is jerky

Postby neuronetv » Sat May 18, 2013 11:13 pm

thanks very much for your further help. That first command you gave worked well and the video file seems spot on, however there's no audio in the recording. I tried changing some parameters in the command but no joy. The audio is enabled in the cam and the settings are:
enacoding AAC, (the only alternatives are G711 ulaw and G726)
sample rate 16 kHz
Bit rate 16 kbits/s

with that command you gave that works, here is the console scroll:

# ffmpeg -t 10 -i rtsp://your_cam_ip:port/additional_path -ar 16000 -ac 1 -ab 16k out.mp4g
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Input #0, rtsp, from 'rtsp://your_cam_ip:port/additional_path':
Metadata:
title : Media Presentation
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: mpeg4 (Advanced Simple Profile), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 21.92 tbr, 90k tbn, 1k tbc
Stream #0:1: Audio: aac, 16000 Hz, mono, fltp
-t is not an input option, keeping it for the next output; consider fixing your command line.
[libx264 @ 0x959c3a0] using SAR=1/1
[libx264 @ 0x959c3a0] using cpu capabilities: MMX2 SSE2Fast SSEMisalign LZCNT
[libx264 @ 0x959c3a0] profile High, level 2.2
[libx264 @ 0x959c3a0] 264 - core 132 r2310 76a5c3a - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=21 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'out.mp4':
Metadata:
title : Media Presentation
encoder : Lavf55.7.100
Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 16832 tbn, 21.92 tbc
Stream #0:1: Audio: aac (libfaac) ([64][0][0][0] / 0x0040), 16000 Hz, mono, s16, 16 kb/s
Stream mapping:
Stream #0:0 -> #0:0 (mpeg4 -> libx264)
Stream #0:1 -> #0:1 (aac -> libfaac)
Press [q] to stop, [?] for help
frame= 220 fps= 52 q=28.0 Lsize= 401kB time=00:00:09.94 bitrate= 329.9kbits/s dup=5026 drop=0
video:397kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.854777%
[libx264 @ 0x959c3a0] frame I:1 Avg QP:22.30 size: 57873
[libx264 @ 0x959c3a0] frame P:56 Avg QP:20.68 size: 5789
[libx264 @ 0x959c3a0] frame B:163 Avg QP:31.84 size: 146
[libx264 @ 0x959c3a0] consecutive B-frames: 0.5% 0.9% 4.1% 94.5%
[libx264 @ 0x959c3a0] mb I I16..4: 1.6% 85.3% 13.0%
[libx264 @ 0x959c3a0] mb P I16..4: 0.2% 0.3% 0.1% P16..4: 20.5% 4.2% 6.1% 0.0% 0.0% skip:68.6%
[libx264 @ 0x959c3a0] mb B I16..4: 0.0% 0.0% 0.0% B16..8: 7.6% 0.1% 0.1% direct: 0.1% skip:92.0% L0:33.3% L1:62.4% BI: 4.3%
[libx264 @ 0x959c3a0] 8x8 transform intra:78.9% inter:69.6%
[libx264 @ 0x959c3a0] coded y,uvDC,uvAC intra: 81.7% 79.1% 52.4% inter: 5.8% 6.5% 2.8%
[libx264 @ 0x959c3a0] i16 v,h,dc,p: 8% 17% 70% 4%
[libx264 @ 0x959c3a0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 10% 39% 5% 6% 4% 8% 8% 8%
[libx264 @ 0x959c3a0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 12% 15% 8% 11% 6% 14% 8% 8%
[libx264 @ 0x959c3a0] i8c dc,h,v,p: 54% 26% 12% 8%
[libx264 @ 0x959c3a0] Weighted P-Frames: Y:0.0% UV:0.0%
[libx264 @ 0x959c3a0] ref P L0: 46.0% 5.5% 41.4% 7.1%
[libx264 @ 0x959c3a0] ref B L0: 82.7% 15.4% 1.9%
[libx264 @ 0x959c3a0] ref B L1: 93.5% 6.5%
[libx264 @ 0x959c3a0] kb/s:323.51
[libfaac @ 0x959e080] 1 frames left in the queue on closing
neuronetv
 
Posts: 39
Joined: Sat May 18, 2013 9:07 am

Re: converted file is jerky

Postby burek » Sun May 19, 2013 6:08 am

Did you try just saving your stream to the output file, using:
Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path -c copy out.mp4

That way you'll avoid re-compressing your stream, which will save the cpu of the machine where you are running your ffmpeg and it will also keep the original visual image quality.


Anyway, first thing to do is to check your input audio, to make sure the volume is not very low:
Code: Select all
ffplay -i rtsp://your_cam_ip:port/additional_path



Also, check your out.mp4 file using:
Code: Select all
ffmpeg -i out.mp4

to see if there is an audio stream inside your mp4 container.


One suggestion though. Always check your output log to see if there are some hints/warnings that you could fix. For example in your last example, you had a warning:
Code: Select all
-t is not an input option, keeping it for the next output; consider fixing your command line.

which means you should move your "-t" option to the output options, like this:
Code: Select all
ffmpeg -i rtsp://your_cam_ip:port/additional_path -ar 16000 -ac 1 -ab 16k -t 10 out.mp4
burek
 
Posts: 867
Joined: Mon May 09, 2011 10:16 pm
Location: Serbia

Re: converted file is jerky

Postby neuronetv » Sun May 19, 2013 4:13 pm

hi yes I did try your first command:
ffmpeg -i rtsp://your_cam_ip:port/additional_path -c copy out.mp4
but I got this:
# ffmpeg -i rtsp://your_cam_ip:port/additional_path -c copy out.mp4
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx - -enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvi d --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Input #0, rtsp, from 'rtsp://your_cam_ip:port/additional_path':
Metadata:
title : Media Presentation
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: mpeg4 (Advanced Simple Profile), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 21.92 tbr, 9 0k tbn, 1k tbc
Stream #0:1: Audio: aac, 16000 Hz, mono, fltp
[mp4 @ 0xa49bc60] track 1: codec frame size is not set
Output #0, mp4, to 'out.mp4':
Metadata:
title : Media Presentation
encoder : Lavf55.7.100
Stream #0:0: Video: mpeg4 ( [0][0][0] / 0x0020), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=2-31, 90k tbn, 90k tbc
Stream #0:1: Audio: aac ([64][0][0][0] / 0x0040), 16000 Hz, mono
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
Non-monotonous DTS in output stream 0:1; previous: 362255235, current: 45297; changing to 362255236. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255236, current: 46321; changing t o 362255237. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255237, current: 47344; changing t o 362255238. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255238, current: 48368; changing t o 362255239. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255239, current: 49392; changing t o 362255240. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255240, current: 50416; changing t o 362255241. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255241, current: 51440; changing t o 362255242. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255242, current: 52464; changing t o 362255243. This may result in incorrect timestamps in the output file.
Non-monotonous DTS in output stream 0:1; previous: 362255243, current: 53488; changing to 362255244. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255244, current: 54512; changing t o 362255245. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255245, current: 55536; changing t o 362255246. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255246, current: 56560; changing t o 362255247. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255247, current: 57583; changing t o 362255248. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255248, current: 58607; changing t o 362255249. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255249, current: 59631; changing t o 362255250. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255250, current: 60655; changing t o 362255251. This may result in incorrect timestamps in the output file.
Non-monotonous DTS in output stream 0:1; previous: 362255251, current: 61679; changing to 362255252. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255252, current: 62703; changing t o 362255253. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255253, current: 63727; changing t o 362255254. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255254, current: 64751; changing t o 362255255. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255255, current: 65774; changing t o 362255256. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255256, current: 66799; changing t o 362255257. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255257, current: 67822; changing t o 362255258. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255258, current: 68846; changing t o 362255259. This may result in incorrect timestamps in the output file.
Non-monotonous DTS in output stream 0:1; previous: 362255259, current: 69870; changing to 362255260. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255260, current: 70894; changing t o 362255261. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255261, current: 71918; changing t o 362255262. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255262, current: 72942; changing t o 362255263. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255263, current: 73966; changing t o 362255264. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255264, current: 74989; changing t o 362255265. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255265, current: 76013; changing t o 362255266. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255266, current: 77037; changing t o 362255267. This may result in incorrect timestamps in the output file.
Non-monotonous DTS in output stream 0:1; previous: 362255267, current: 78061; changing to 362255268. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255268, current: 79085; changing t o 362255269. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255269, current: 80109; changing t o 362255270. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255270, current: 81133; changing t o 362255271. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255271, current: 82157; changing t o 362255272. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255272, current: 83181; changing t o 362255273. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255273, current: 84205; changing t o 362255274. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255274, current: 85228; changing t o 362255275. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255275, current: 86252; changing t o 362255276. This may result in incorrect timestamps in the output file.
Non-monotonous DTS in output stream 0:1; previous: 362255276, current: 87276; changing to 362255277. This may result in incorrect timestamps in the output file.
[mp4 @ 0xa49bc60] Non-monotonous DTS in output stream 0:1; previous: 362255277, current: 88300; changing t o 362255278. This may result in incorrect timestamps in the output file.
frame= 88 fps= 20 q=-1.0 Lsize= 1676kB time=06:17:20.95 bitrate= 0.6kbits/s
video:1663kB audio:11kB subtitle:0 global headers:0kB muxing overhead 0.164479%

and this carried on until I pressed 'q'. It did produce a video file with audio however it was choppy and out of sync with the audio.

as for the next commands I got:
# ffplay -i rtsp://your_cam_ip:port/additional_path
-bash: ffplay: command not found


# ffmpeg -i out.mp4
ffmpeg version N-53206-gebe8c7f Copyright (c) 2000-2013 the FFmpeg developers
built on May 17 2013 16:03:45 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54)
configuration: --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvpx --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-gpl --enable-postproc --enable-nonfree
libavutil 52. 33.100 / 52. 33.100
libavcodec 55. 10.100 / 55. 10.100
libavformat 55. 7.100 / 55. 7.100
libavdevice 55. 0.100 / 55. 0.100
libavfilter 3. 68.101 / 3. 68.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0xa572dc0] max_analyze_duration 5000000 reached at 5006659 microseconds
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2mp41
title : Media Presentation
encoder : Lavf55.7.100
Duration: 00:00:06.89, start: 0.000000, bitrate: 3015 kb/s
Stream #0:0(und): Video: mpeg4 (Advanced Simple Profile) (mp4v / 0x7634706D), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 2996 kb/s, 15.98 fps, 21.92 tbr, 90k tbn, 1k tbc
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 16000 Hz, mono, fltp, 57 kb/s
Metadata:
handler_name : SoundHandler
At least one output file must be specified

I think the above does show audio with the line Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 16000 Hz, mono, fltp, 57 kb/s

and yes moving the -t did solve that last bug.
neuronetv
 
Posts: 39
Joined: Sat May 18, 2013 9:07 am

Re: converted file is jerky

Postby burek » Tue May 28, 2013 10:57 pm

Try using .mkv instead of .mp4. Those are just warnings, but judging by the choppy output, it seems those warnings are meaningful. It might appear that your camera is producing a non-standard output or that ffmpeg does not quite understand it. For more help on that issue, it would be good if you could submit a bug report on our bug tracker.
burek
 
Posts: 867
Joined: Mon May 09, 2011 10:16 pm
Location: Serbia


Return to ffmpeg

Who is online

Users browsing this forum: No registered users and 2 guests