Project

General

Profile

Bug #2423

HD channels with Dolby Digital 5.1 or 2.0 sound causes DTS discontinuity errors - working ok on DD 2.0 channels

Added by Crazy Fin about 10 years ago. Updated about 10 years ago.

Status:
Fixed
Priority:
Normal
Category:
Streaming
Target version:
-
Start date:
2014-10-26
Due date:
% Done:

100%

Estimated time:
Found in version:
3.9.1952
Affected Versions:

Description

After I upgraded to 3.9.1949 and newer I started to see DTS discontinuity errors in the tvh-log for some HD channels using Dolby Digital 5.1 or 2.0 sound:

2014-10-26 15:15:45.310 parser: transport stream DVBSUB, DTS discontinuity. DTS = 550483, last = 233287
2014-10-26 15:15:45.310 parser: transport stream DVBSUB, DTS discontinuity. DTS = 550483, last = 233287
2014-10-26 15:15:49.701 parser: transport stream DVBSUB, DTS discontinuity. DTS = 953487, last = 564523
2014-10-26 15:15:49.738 parser: transport stream DVBSUB, DTS discontinuity. DTS = 953487, last = 564523

2014-10-26 15:18:18.557 subscription: 0024: "192.168.10.10 [ xbmc-lab | XBMC Media Center ]" subscribing on "Kanal 9 HD", weight: 150, adapter: "TUNER 7", network: "THOR", mux: "10778V", provider: "Telenor", service: "Kanal 9 HD", hostname="192.168.10.10", username="xbmc-lab", client="XBMC Media Center"
2014-10-26 15:18:19.315 parser: The timediff for TELETEXT is big (805730029), using current dts

Note also the "timediff" error in the log?

switching to another HD channel:

2014-10-26 15:18:50.434 subscription: 0024: "192.168.10.10 [ xbmc-lab | XBMC Media Center ]" unsubscribing from "Kanal 9 HD", hostname="192.168.10.10", username="xbmc-lab", client="XBMC Media Center"
2014-10-26 15:18:50.440 mpegts: 10778V in THOR - tuning on TUNER 7
2014-10-26 15:18:50.701 subscription: 0025: "192.168.10.10 [ xbmc-lab | XBMC Media Center ]" subscribing on "Kanal 5 HD (S)", weight: 150, adapter: "TUNER 7", network: "THOR", mux: "10778V", provider: "Telenor", service: "Kanal 5 HD (S)", hostname="192.168.10.10", username="xbmc-lab", client="XBMC Media Center"
2014-10-26 15:18:51.495 parser: The timediff for TELETEXT is big (382800779), using current dts

and switching to a HD channel with 2.0 sound:

2014-10-26 15:19:27.711 parser: The timediff for TELETEXT is big (1221280061), using current dts
2014-10-26 15:19:30.533 subscription: 0026: "192.168.10.10 [ xbmc-lab | XBMC Media Center ]" unsubscribing from "TV4 HD", hostname="192.168.10.10", username="xbmc-lab", client="XBMC Media Center"
2014-10-26 15:19:30.543 mpegts: 11785H in THOR - tuning on TUNER 7
2014-10-26 15:19:31.067 subscription: 0027: "192.168.10.10 [ xbmc-lab | XBMC Media Center ]" subscribing on "Nat Geo Wild HD", weight: 150, adapter: "TUNER 7", network: "THOR", mux: "11785H", provider: "Telenor", service: "Nat Geo Wild HD", hostname="192.168.10.10", username="xbmc-lab", client="XBMC Media Center"
2014-10-26 15:19:40.377 parser: transport stream DVBSUB, DTS discontinuity. DTS = 730973, last = 200192
2014-10-26 15:19:40.422 parser: transport stream DVBSUB, DTS discontinuity. DTS = 730973, last = 211244
2014-10-26 15:19:40.422 parser: transport stream DVBSUB, DTS discontinuity. DTS = 732323, last = 211244
2014-10-26 15:19:40.498 parser: transport stream DVBSUB, DTS discontinuity. DTS = 740675, last = 230649
2014-10-26 15:19:44.111 parser: transport stream DVBSUB, DTS discontinuity. DTS = 1095567, last = 740675
2014-10-26 15:19:45.397 parser: transport stream DVBSUB, DTS discontinuity. DTS = 1211945, last = 730973

I initially thought this happened only HD channels with DD 5.1 sound but I have seen this on HD channels with 2.0 sound as well.

I can see that channels like TV4 HD, SVT1 HD, SVT2 HD works fine without getting DTS discontinuity erros.

I have not seen these type of errors in versions before 3.9.1949.

History

#1

Updated by Crazy Fin about 10 years ago

Pls remove the text "working ok on DD 2.0 channels" from the title. I see the same errors on most of the HD channels with DD 2.0 sound.

#2

Updated by Jaroslav Kysela about 10 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset commit:tvheadend|eea8a5a374fab1ee52834b3cb6e49c050b5b8c23.

#3

Updated by Jaroslav Kysela about 10 years ago

Note: "The timediff for TELETEXT is big (382800779), using current dts" warnings are OK.

The broadcasters might use totaly different timebase for teletext which does not match with other streams (audio/video), so tvh tries to use dts provided in the teletext stream as zero time..

#4

Updated by Crazy Fin about 10 years ago

Aaahhh! Can it be the fact that we now have changed from summertime to wintertime here in Sweden during the night from this Saturday to today Sunday?

I am trying to pull your latest revision that is supposed to fix this but when I try to run

"./configure --enable-trace"

I get the error message

"ERROR: Failed to fetch dvb-scan data (use --disable-dvbscan)"

#5

Updated by Crazy Fin about 10 years ago

I did

"./configure --enable-trace --disable-dvbscan"

and then compiled and started TVH and the DTS continuity errors as well the timediff error messages seems to be gone now! :-)

Case closed! (still do not understand why I get the error message "ERROR: Failed to fetch dvb-scan data (use --disable-dvbscan")

#6

Updated by Crazy Fin about 10 years ago

Yepp, must be the switch from summer time to winter time last night.

I still see the "parser: The timediff for TELETEXT is big (805730029), using current dts" messages but only for a few of the channels I am testing on. Most of the channels do not show this error message.

#7

Updated by Jaroslav Kysela about 10 years ago

Crazy Fin wrote:

Case closed! (still do not understand why I get the error message "ERROR: Failed to fetch dvb-scan data (use --disable-dvbscan")

Perhaps, something wrong with git in the data/dvb-scan subtree.... You may try to remove this directory..

#8

Updated by Crazy Fin about 10 years ago

This error message "ERROR: Failed to fetch dvb-scan data (use --disable-dvbscan" is so strange.

If I do "sudo ./configure" then it works fine but if I do just "./configure" I get the error.

It seems as if the data/dvb-scan subtree has been taken over by "root" in the ownership?

I´ll delete the data/dvb-scan subtree as you suggested and see if the problem disappears.

Also available in: Atom PDF