Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
05-10-2010 21:39:38.765 RecorderPid ff , No PayLoad, Continuity Counter should be the same ! 9 ( prev 0 )
05-10-2010 21:39:51.812 RecorderPid ff , No PayLoad, Continuity Counter should be the same ! 3 ( prev 8 )
05-10-2010 21:39:56.468 RecorderPid 103 : Discontinuity header bit set!
05-10-2010 21:39:56.468 RecorderPid 103 , No PayLoad, Continuity Counter should be the same ! a ( prev 6 )
05-10-2010 21:40:02.828 RecorderPid 103 , No PayLoad, Continuity Counter should be the same ! 8 ( prev 9
Gonzo you have a lot of these errors in tswriter. Ive only ever seen them caused by a bad signal. It might be a good idea to get your dish checked out
What signal strength/quality values do you get?
Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
Only for multiseat.
Single seat installation does not use streaming server.
Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
Yes it should help on single seat setups as well if you are seeing the issue.
And, btw, is there a way to display the signal level and quality directly during llive tv in mediaportal?
Does this fix also apply to single-seat installations (all on one PC) or only when client and server are on separate machines?
Only for multiseat.
Single seat installation does not use streaming server.
Romuz does tsreader read the buffer files directly when MP client is running on the same machine? Sorry I assumed streaming server was always used. StreamingServer.log always seems to note a stream being created even when a channel is tuned locally.
If tsreader is used locally its possible there might be a similar bug in there as well