Bug #4369
Bug #4336: New PCR code issue (was: Parser very verbose?)
"tsdemux - PCR fix for ffmpeg input" looks not be fixed
100%
Description
Hello perexg,
I looked very intresting if the "PTS and PCR diff" will be fixed and compile the latest version but....
2017-05-12 21:20:31.798 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (271800)
#257: PTS and PCR diff is very big (270359)
2017-05-12 21:20:31.822 parser: IPTV/BBC1/Service01: AAC-LATM
2017-05-12 21:20:33.756 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (660600)
#257: PTS and PCR diff is very big (650519)
2017-05-12 21:20:33.777 parser: IPTV/BBC1/Service01: AAC-LATM
2017-05-12 21:20:37.957 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (1099800)
#257: PTS and PCR diff is very big (1094039)
2017-05-12 21:20:37.958 parser: IPTV/BBC1/Service01: AAC-LATM
2017-05-12 21:20:42.387 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (1445400)
#257: PTS and PCR diff is very big (1433879)
2017-05-12 21:20:42.388 parser: IPTV/BBC1/Service01: AAC-LATM
2017-05-12 21:20:46.270 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (1791000)
#257: PTS and PCR diff is very big (1777559)
2017-05-12 21:20:46.271 parser: IPTV/BBC1/Service01: AAC-LATM
2017-05-12 21:20:49.563 parser: IPTV/BBC1/Service01: H264 #256: PTS and PCR diff is very big (2136600)
#257: PTS and PCR diff is very big (2132759)
2017-05-12 21:20:49.565 parser: IPTV/BBC1/Service01: AAC-LATM
I have this problem since you upgraded to version 4.3 (roundabout the cersion jump)
Thanks for your good work on this project
Frank
Files
History
Updated by Jaroslav Kysela over 7 years ago
Could you attach cca 20 seconds of the original mpegts stream? Just use 'wget -O file.ts MUX_URL' + Ctrl+C. Grab MUX_URL from the play link in the mux grid.
Updated by Frank Baier over 7 years ago
- File tvh_test.ts tvh_test.ts added
Hello Jaroslav,
i want to do this but this is not possible becaus this is a HLS/DASH Stream. To show the channel via TVh i use the following command:
pipe:///usr/bin/ffmpeg -loglevel fatal -user-agent Kodi/16 -i http://a.files.bbci.co.uk/media/live/manifesto/audio_video/simulcast/hls/uk/abr_hdtv/ak/bbc_one_hd.m3u8 -codec copy -bsf:v h264_mp4toannexb,dump_extra -tune zerolatency -f mpegts pipe:1
This worked good in the last month and i got the problem first with 4.3
In the attachemant you can find an 30sec example which i generate with this command line:
/usr/bin/ffmpeg -loglevel fatal -user-agent Kodi/16 -i http://a.files.bbci.co.uk/media/live/manifesto/audio_video/simulcast/hls/uk/abr_hdtv/ak/bbc_one_hd.m3u8 -codec copy -bsf:v h264_mp4toannexb,dump_extra -tune zerolatency -f mpegts /tvh_test.ts
I use tvh on debian stretch with
ffmpeg version 3.2.4-1 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 6.3.0 (Debian 6.3.0-6) 20170205
Updated by Frank Baier over 7 years ago
Hallo,
FYI
your last change from this morning would not help
Thanks for all :)
Frank
Updated by Jaroslav Kysela over 7 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|9a62ad30365926d0416eec9a5e0c6729cf0a65c3.
Updated by Jaroslav Kysela over 7 years ago
FFMPEG works really badly with PCR clocks:
$ ./support/pcr_diff.py tvh_test.ts pid: 256 pcr: 18900000 pcr delta (ms): 700.0 pid: 256 pcr: 122040000 pcr delta (ms): 3820.0 pid: 256 pcr: 225720000 pcr delta (ms): 3840.0 pid: 256 pcr: 329400000 pcr delta (ms): 3840.0 pid: 256 pcr: 433080000 pcr delta (ms): 3840.0 pid: 256 pcr: 536760000 pcr delta (ms): 3840.0 pid: 256 pcr: 640440000 pcr delta (ms): 3840.0 pid: 256 pcr: 744120000 pcr delta (ms): 3840.0 pid: 256 pcr: 847800000 pcr delta (ms): 3840.0 pid: 256 pcr: 951480000 pcr delta (ms): 3840.0
(Note that these clocks should be updated each 100ms!!!).
Increased boundary again in v4.3-71-g9a62ad3 .
Updated by Frank Baier over 7 years ago
Hello Jaroslav,
I test this version and it's working now but it stutters and in this moment i got the message again :(
I think the allowed time dff is on the border from working/nor working...
before the jump to 4.3 it's woring very well...