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: 1107271" data-attributes="member: 74879"><p>Understood.</p><p></p><p></p><p>We are looking at a file that is in the process of being written (via pointer access?). I don't know your code (and I don't pretend I would immediately understand it either<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />) but how is the Windows read function operating? I assume that the file is not read byte by byte but probably in larger blocks. What would be the theoretical behavior if the same block was written by the Server and simultaneously read by the Client ? I would expect the read operation to be delayed until the server's write access to the same block is finished. Standard block size is probably 4096 (the timeshift files residing in my case on a 6G IMDISK-created RamDisk).</p><p></p><p>If the hypothesis of read/write conflict is correct then we should no longer log any of these strange error messages when watching Live TV if we went back say 60 seconds in the buffer and continued watching. I'll check this out and report here.</p></blockquote><p></p>
[QUOTE="HTPCSourcer, post: 1107271, member: 74879"] Understood. We are looking at a file that is in the process of being written (via pointer access?). I don't know your code (and I don't pretend I would immediately understand it either:confused:) but how is the Windows read function operating? I assume that the file is not read byte by byte but probably in larger blocks. What would be the theoretical behavior if the same block was written by the Server and simultaneously read by the Client ? I would expect the read operation to be delayed until the server's write access to the same block is finished. Standard block size is probably 4096 (the timeshift files residing in my case on a 6G IMDISK-created RamDisk). If the hypothesis of read/write conflict is correct then we should no longer log any of these strange error messages when watching Live TV if we went back say 60 seconds in the buffer and continued watching. I'll check this out and report here. [/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