Reply to thread

Message

<blockquote data-quote="HTPCSourcer" data-source="post: 1107388" data-attributes="member: 74879">No problem, it's just a message.The GOP that I implemented yesterday has to do with the signature process and is reported to increase server speed by suppressing the need for signing, which creates a 10-15% overhead. I was quite surprised that after having done this, instead of having occasional invalid signature messages in tsreader.log, the log was virtually flooded with these messages. I am really interested what kind of SMB registry setting leads to these errors being reported by Windows. Could you imagine to provide a registry setting for switching the reporting on and off in tsreader? This way I could continue to investigate. But certainly just a nice-to-have only.This was just a 10 min watch number and I would need to monitor this over a longer time for different channels to assess if the 1080i in combination with CI decrypting vs. 780p HD and/or SD TV makes a difference. Will report again.</blockquote>

[QUOTE="HTPCSourcer, post: 1107388, member: 74879"] No problem, it's just a message. The GOP that I implemented yesterday has to do with the signature process and is reported to increase server speed by suppressing the need for signing, which creates a 10-15% overhead. I was quite surprised that after having done this, instead of having occasional invalid signature messages in tsreader.log, the log was virtually flooded with these messages. I am really interested what kind of SMB registry setting leads to these errors being reported by Windows. Could you imagine to provide a registry setting for switching the reporting on and off in tsreader? This way I could continue to investigate. But certainly just a nice-to-have only. This was just a 10 min watch number and I would need to monitor this over a longer time for different channels to assess if the 1080i in combination with CI decrypting vs. 780p HD and/or SD TV makes a difference. Will report again. [/QUOTE]

Verification