Unfortunately I've still got dropouts. Will provide logs soon.
How often is tsreader comparing timestamp and clock?
Is the initial buffer time needed for this version to work? Because meanwhile I set this to 0 again...
Just saw that @Snoopy87 is having similar problems when accessing the timeshift files via UNC:
https://forum.team-mediaportal.com/...ezes-with-rtsp-unc.127225/page-3#post-1099939
I answered in the other thread. Since I am experiencing the same behaviour with Server 2012E + Win 7, it does not appear to be related to any new code that Microsoft may have introduced in Win 8 / Server 2012 R2.Yes, it seems to be a new Windows 8/WS2012 R2 SMB 'feature'
Hhm, sounds much like a head-in-the-sands approach. Yesterday I was watching a 1080i stream and after some time (ca. 30 min) there were massive stream interruptions with major difficulties to recover from, which coincided with prolonged occurences of said read failures (unfortunatly the log is gone).It's not a 'terminal' problem since TsReader will just keep re-trying the file read until it gets the data, so I might just suppress those messages in the log.
Unfortunately the entry in the registry isn't there...Yes, it is needed.