Opened 9 years ago

Closed 8 years ago

Last modified 3 years ago

#5367 closed defect (fixed)

ffmpeg muxing error, no video packets muxed: cur_dts is invalid (this is harmless if it occurs once at the start per stream)

Reported by: leo.z Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords: h264 mpegts
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Hi all

I'm using ffmpeg to recode a live mpegts stream, but no video packets muxed, the debug log keep saying: cur_dts is invalid (this is harmless if it occurs once at the start per stream).
the source file recoded using others tools: http://203.118.245.62/hd_spts.ts.
the ffmpeg report file: http://203.118.245.62/ffmpeg-20160323-065632.log

Attachments (4)

ffmpeg-20160627-160404.log (108.2 KB ) - added by Alexander V. Lukyanov 8 years ago.
iptv-raw conversion log
ffmpeg-20160627-160955.log (654.3 KB ) - added by Alexander V. Lukyanov 8 years ago.
iptv-raw conversion log from ffmpeg git d693392886b8454c818e384c816b9ede53c570d8
hd_spts_cut.ts (2.4 MB ) - added by Carl Eugen Hoyos 8 years ago.
iptv-raw_cut (2.4 MB ) - added by Carl Eugen Hoyos 8 years ago.

Change History (10)

comment:1 by Carl Eugen Hoyos, 9 years ago

Keywords: cur_dts is invalid removed

Please provide the command line that allows to reproduce the issue together with the complete, uncut console output here on the bug tracker to make this a valid ticket: External resources may disappear.

comment:2 by leo.z, 9 years ago

I'm using command "ffmpeg -y -i hd_spts.ts -c copy 1.ts -report", just try to remux it.
I had uploaded the source video, report log file and the dts/pts analyze form:
source video: http://203.118.245.62/hd_spts.ts
report log: http://203.118.245.62/ffmpeg-20160323-065632.log
pts/dts: http://203.118.245.62/hd_spts.xlsx

Input #0, mpegts, from 'hd_spts.ts':

Duration: 00:01:43.30, start: 16966.364000, bitrate: 8120 kb/s
Program 352

Metadata:

service_name : FIGHT SPORTS HD
service_provider:

Stream #0:0[0xc0], 255, 1/90000: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
Stream #0:1[0x124], 211, 1/90000: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s

Successfully opened the file.
Parsing a group of options: output file 1.ts.
Applying option c (codec name) with argument copy.
Successfully parsed a group of options.
Opening an output file: 1.ts.
[file @ 0xb4945a0] Setting default whitelist 'file'
Successfully opened the file.
[mpegts @ 0xb493fe0] muxrate VBR, pcr every 9000 pkts, sdt every 200, pat/pmt every 40 pkts
Output #0, mpegts, to '1.ts':

Metadata:

encoder : Lavf57.25.100
Stream #0:0, 0, 1/90000: Video: h264 ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 25 tbr, 90k tbn, 90k tbc
Stream #0:1, 0, 1/90000: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, 192 kb/s

Stream mapping:

Stream #0:0 -> #0:0 (copy)
Stream #0:1 -> #0:1 (copy)

Press [q] to stop, ? for help
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
...
[mpegts @ 0xb493fe0] Delay between the first packet and last packet in the muxing queue is 10008000 > 10000000: forcing output
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
[mpegts @ 0xb493fe0] Delay between the first packet and last packet in the muxing queue is 10008000 > 10000000: forcing output
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
[mpegts @ 0xb493fe0] Delay between the first packet and last packet in the muxing queue is 10008000 > 10000000: forcing output
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
cur_dts is invalid (this is harmless if it occurs once at the start per stream)
No more output streams to write to, finishing.
frame= 0 fps=0.0 q=-1.0 Lsize= 2657kB time=00:01:42.91 bitrate= 211.5kbits/s speed= 150x
video:0kB audio:2411kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 10.197172%
Input file #0 (hd_spts.ts):

Input stream #0:0 (video): 5148 packets read (97738708 bytes);
Input stream #0:1 (audio): 4287 packets read (2469312 bytes);
Total: 9435 packets (100208020 bytes) demuxed

Output file #0 (1.ts):

Output stream #0:0 (video): 0 packets muxed (0 bytes);
Output stream #0:1 (audio): 4287 packets muxed (2469312 bytes);
Total: 4287 packets (2469312 bytes) muxed

0 frames successfully decoded, 0 decoding errors
[AVIOContext @ 0xb45df20] Statistics: 0 seeks, 858 writeouts
[AVIOContext @ 0xb460e60] Statistics: 110383212 bytes read, 3 seeks

Version 0, edited 9 years ago by leo.z (next)

comment:3 by Carl Eugen Hoyos, 9 years ago

Resolution: needs_more_info
Status: newclosed

Feel free to reopen this ticket if you can provide the command line that allows to reproduce this issue together with the complete, uncut console output.

comment:4 by Alexander V. Lukyanov, 8 years ago

Resolution: needs_more_info
Status: closedreopened

Please look at this iptv sample:
https://drive.google.com/file/d/0B0laIcbq4vKRV1g0c1B4NGREZ1E/view?usp=sharing

ffplay can show the video, but ffmpeg cannot copy it using this command line:

ffmpeg -report -y -ss 5 -i iptv-raw -t 30 -c copy /tmp/a.avi

The diagnostics looks very similar to the report of the topic starter.

by Alexander V. Lukyanov, 8 years ago

Attachment: ffmpeg-20160627-160404.log added

iptv-raw conversion log

by Alexander V. Lukyanov, 8 years ago

Attachment: ffmpeg-20160627-160955.log added

iptv-raw conversion log from ffmpeg git d693392886b8454c818e384c816b9ede53c570d8

comment:5 by Carl Eugen Hoyos, 8 years ago

Keywords: h264 mpegts added
Resolution: duplicate
Status: reopenedclosed

I believe this is a duplicate of ticket #5088.

by Carl Eugen Hoyos, 8 years ago

Attachment: hd_spts_cut.ts added

by Carl Eugen Hoyos, 8 years ago

Attachment: iptv-raw_cut added

comment:6 by aalku, 3 years ago

Resolution: duplicatefixed

Errors are different than in #5088 so i'll mark it as fixed rather than duplicated.
I think "cur_dts is invalid" is an important difference.
I started with a prepared "ffmpeg version n4.2.2" package stripped from almost all modules and got that "cur_dts is invalid" error and getting no video trying to read some input file until I recompiled enabling this two parsers when calling configure:

  --enable-parser=h264
  --enable-parser=acc

In other cases this might be the problem or else it may have been fixed in this years.

Maybe this can help someone anyway.

Note: See TracTickets for help on using tickets.