home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Multiseat: A lot of stuttering, artifacts, pixelation, freezes with RTSP/UNC
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="HTPCSourcer" data-source="post: 1107198" data-attributes="member: 74879"><p>Like [USER=128461]@Snoopy87[/USER] I've been trying to eliminate this error message by trying a couple of different things, e.g. deactivating the security signing requirement settings in the registry both on the 2012 Server as well as the Win 7 client, however, without any effect. I can also confirm the observation (as much as I've seen) that the error is only occurring when MePo reads the timeshift file. What [USER=83973]@Owlsroost[/USER] is saying though is, that he doubts this to have any (or shall we say significant?) effect on audible/visible interruptions of Live TV. Notwithstanding I would also very much appreciate if we eliminated this signing error from the list of possible sources.</p><p></p><p>Snoopy's investigations seem to confirm that the event happens each time the current file writing position is reached. Independently of the signing error, would this not mean that tsreader is running out of data anyway? In light of [USER=83973]@Owlsroost[/USER] latest tsreader development where he is automatically adjusting the speed (forgive my inadequate wording <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite19" alt=":notworthy:" title="Not Worthy :notworthy:" loading="lazy" data-shortname=":notworthy:" />), would it be an option to artificially slow down the reading speed permanently by a few ppm in order to remain sustainably behind the current writing position?</p></blockquote><p></p>
[QUOTE="HTPCSourcer, post: 1107198, member: 74879"] Like [USER=128461]@Snoopy87[/USER] I've been trying to eliminate this error message by trying a couple of different things, e.g. deactivating the security signing requirement settings in the registry both on the 2012 Server as well as the Win 7 client, however, without any effect. I can also confirm the observation (as much as I've seen) that the error is only occurring when MePo reads the timeshift file. What [USER=83973]@Owlsroost[/USER] is saying though is, that he doubts this to have any (or shall we say significant?) effect on audible/visible interruptions of Live TV. Notwithstanding I would also very much appreciate if we eliminated this signing error from the list of possible sources. Snoopy's investigations seem to confirm that the event happens each time the current file writing position is reached. Independently of the signing error, would this not mean that tsreader is running out of data anyway? In light of [USER=83973]@Owlsroost[/USER] latest tsreader development where he is automatically adjusting the speed (forgive my inadequate wording :notworthy:), would it be an option to artificially slow down the reading speed permanently by a few ppm in order to remain sustainably behind the current writing position? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Multiseat: A lot of stuttering, artifacts, pixelation, freezes with RTSP/UNC
Contact us
RSS
Top
Bottom