Hello All, I possess just enough knowledge of ffmpeg to be dangerous, but I'm assuming that a recent problem I've run into is most likely related to a H.264 time stamp issue, as in the following ......
----------------------------------------------------------------------------------------------------------------- ffmpeg -i test1.m2ts -vcodec copy -an -f mpegts -ps 192 copy.m2ts FFmpeg version SVN-r12191, Copyright (c) 2000-2008 Fabrice Bellard, et al. configuration: --enable-libmp3lame --enable-libvorbis --enable-libfaad --enable-libfaac --enable-pp --enable-pthreads --enable-gpl --enable-libxvid --enable-libx264 --enable-libgsm --enable-libtheora --enable-swscaler --enable-libamr-nb --enable-libamr-wb --enable-nonfree libavutil version: 49.6.0 libavcodec version: 51.50.1 libavformat version: 52.7.0 libavdevice version: 52.0.0 built on Mar 1 2008 15:02:09, gcc: 4.1.2 20070925 (Red Hat 4.1.2-33) Input #0, mpegts, from 'test1.m2ts': Duration: 24:42:03.6, start: 11.650667, bitrate: 2852 kb/s Program 1 Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 tb(r) File 'copy.m2ts' already exists. Overwrite ? [y/N] y Output #0, mpegts, to 'copy.m2ts': Stream #0.0: Video: libx264, yuv420p, 1920x1080 [PAR 0:1 DAR 0:1], q=2-31, 23.98 tb(c) Stream mapping: Stream #0.0 -> #0.0 Press [q] to stop encoding error, pts < dts av_interleaved_write_frame(): Error while opening file ----------------------------------------------------------------------------------------------------------------- Am I correct in guessing that these last two lines are time stamp related? If so, is there a work around available, or is this something that may be addressed in the future? Thanks for your help. Cheers, Bill Crowley. _______________________________________________ FFmpeg-soc mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
