errors on status page only counting when client is htsp
Another easy one, only when client is htsp does errors on the status page update, example add a dvr a http and a htsp of the same channel, introduce some lag, and only the htsp client will get a number of errors besides it, the other 2 will have 0.
Updated by Adam Sutton almost 9 years ago
- Status changed from New to Need feedback
What is your default recording format? If its TS (passthru) then that makes sense.
Currently the subscription error field reports errors detected during parsing of the A/V packets. Which does not happen for passthru.
Updated by Adam Sutton over 8 years ago
Danny, you said close it, I closed it.
Counting errors is fine, but passthru generally doesn't see any errors since they're parsing errors (passthru doesn't parse). If it's not logging HTTP/MKV errors, then sure it could probably be changed. But I'm not in the habit of asking questions, getting no definitive answer (other than a vague statement to close) and then leaving stuff open.
Updated by danny skjodt over 8 years ago
Youre right, part of that was due to my stupidity at that time, not understanding what was going on, and im sorry for that.
Even if the client is http pass this is logged :
2014-04-09 17:48:47.138 TS: 11785H/Trace Urban HD: H264
#1353: Continuity counter error, 9 duplicate log lines suppressed #1353: Continuity counter error, 18 duplicate log lines suppressed
2014-04-09 17:48:48.227 TS: 11785H/Trace Urban HD: H264
2014-04-09 17:48:49.875 TS: 11785H/Trace Urban HD: H264
#1353: Continuity counter error, 24 duplicate log lines suppressed #1353: Continuity counter error, 27 duplicate log lines suppressed
2014-04-09 17:48:50.328 TS: 11785H/Trace Urban HD: H264
Not having considered the consequences, I would say its smarter to make the subscription error field count those, instead of from parsing the a/v packets ?