Bug #5027
Tvh log flooded with "parser: (null)" messages
0%
Description
After update to HTS Tvheadend 4.3-1206~g5de70b4 Tvheadend log is flooded by these two messages:
parser: (null): H264 #256: DTS and PCR diff is very big
#257: DTS and PCR diff is very big
parser: (null): AAC-LATM
Subscriptions tab does not show any errors though.
All m3u8 streams are ffmpeg piped with container copy.
Files
History
Updated by Jaroslav Kysela over 6 years ago
--trace parser : https://tvheadend.org/projects/tvheadend/wiki/Traces , use latest
Updated by Jaroslav Kysela over 6 years ago
Full trace log, one channel start .. 30 seconds .. stop.
Updated by kodiaq kodiaq over 6 years ago
I forgot to mention that this is very intermittent and for example now I do not see these messages in the tvh log. I can not even figure out if this is related to particular channel, because I do not see any related channel name or ID anywhere.
So before if I do those 30 seconds, I need to figure out when it is happening and with what channel(s), otherwise you would not see anything useful in there.
Updated by kodiaq kodiaq over 6 years ago
New observation in relation to this issue. See picture below.
1 - As you can see subscriber number 1 is not receiving any htsp data (tvh/ffmpeg not outputting anything just receiving) and tvh log shows lots of "DTS and PCR diff is very big" messages.
2 - When I open very same stream during this happening, everything works just fine. Subscription is 2 receiving htsp data properly.
If I than restart the channel (disable and re-enable channel under channels tab) both htsp clients start receiving stream without "DTS and PCR diff is very big" messages.
Updated by kodiaq kodiaq over 6 years ago
After adding "tprofile" in HTS Tvheadend 4.3-1233~g4fe0af0 this issue is occuring with much lower frequency, but still occurs time to time.
I'll monitor it and post further observations.
Updated by kodiaq kodiaq over 6 years ago
I've noticed today, that these "DTS and PCR diff is very big" messages start to occur if there is an internet connection speed reduction on the user side (client download speed).
You can easily reproduce this issue with upload bandwidth throttling.
Shouldn't be parser stability resistant or rather independent from client internet download speed fluctuations?
M3U8 streams are received by ffmpeg properly as there is no internet speed fluctuation on the reception side (server download).
Updated by Pablo R. over 6 years ago
kodiaq kodiaq wrote:
I've noticed today, that these "DTS and PCR diff is very big" messages start to occur if there is an internet connection speed reduction on the user side (client download speed).
You can easily reproduce this issue with upload bandwidth throttling.
Shouldn't be parser stability resistant or rather independent from client internet download speed fluctuations?
M3U8 streams are received by ffmpeg properly as there is no internet speed fluctuation on the reception side (server download).
I had similar problems, after a connection speed reduction in the client (tvheadend) stream is never recovered, receiving (in my case) constant continuity errors until restarting the stream.
Updated by saen acro over 6 years ago
kodiaq kodiaq wrote:
M3U8 streams are received by ffmpeg properly as there is no internet speed fluctuation on the reception side (server download).
there is no such ting as M3U8 stream
there is a HLS streams they are no so Live streams usually they are 10 seconds behind
HTTP-TS stream used by TVH is continuous stream but some players can't handle temporary "lag by speed" events and need to restart stream to synchronise
so it is problem of player not of server
Same can be seen with Infomir MAG devices
Updated by Pablo R. over 6 years ago
saen acro wrote:
kodiaq kodiaq wrote:
M3U8 streams are received by ffmpeg properly as there is no internet speed fluctuation on the reception side (server download).
there is no such ting as M3U8 stream
there is a HLS streams they are no so Live streams usually they are 10 seconds behindHTTP-TS stream used by TVH is continuous stream but some players can't handle temporary "lag by speed" events and need to restart stream to synchronise
so it is problem of player not of server
Same can be seen with Infomir MAG devices
Then, TVHEADEND as client also has this problem.
Updated by Jaroslav Kysela over 6 years ago
kodiaq kodiaq kodiaq: I think that there's lowlatency switch for ffmpeg which might help in this. It seems that ffmpeg does own buffering (thus those sines in graph).
The PCR/DTS diff around 1878356 means that there's 20 seconds diference which is obviously wrong. Again, show the parser trace logs for one channel to analyze.