Reply to thread

Message

<blockquote data-quote="rlevis" data-source="post: 316410" data-attributes="member: 81718">I haven't posted to this thread previously.&nbsp; A few of us in New Zealand are experiencing the same issue on some specific DVB-T SD channels, but not the HD channels.&nbsp; Different hardware and codecs but same problem.One thing I don't think has been mentioned in this thread is that in all cases, pressing pause for just a second resolves the problem.&nbsp; So when watching from the timeshift file back 1 second, all is well.&nbsp; The problem only occurs at the end of the timeshift buffer.I think this should provide all the clues the developers need to resolve this problem.&nbsp; An SD channel is writing about 4 times less data than an HD channel.&nbsp; There must be a circumstance where the reader is not able to read all the data that has just been written when dealing with smaller amounts of data with SD channels.&nbsp; Perhaps some sort of Windows cache issue, I'm not sure.I think the solution is to ensure the reader is always a few hundred milliseconds behind the writer.We are all hoping for a solution, as it gets tedious always pausing for a second after changing to SD channels.&nbsp; I hope this helps you tourettes to fix this before the 1.0 release.Regards,Ross.</blockquote>

[QUOTE="rlevis, post: 316410, member: 81718"] I haven't posted to this thread previously. A few of us in New Zealand are experiencing the same issue on some specific DVB-T SD channels, but not the HD channels. Different hardware and codecs but same problem. One thing I don't think has been mentioned in this thread is that in all cases, pressing pause for just a second resolves the problem. So when watching from the timeshift file back 1 second, all is well. The problem only occurs at the end of the timeshift buffer. I think this should provide all the clues the developers need to resolve this problem. An SD channel is writing about 4 times less data than an HD channel. There must be a circumstance where the reader is not able to read all the data that has just been written when dealing with smaller amounts of data with SD channels. Perhaps some sort of Windows cache issue, I'm not sure. I think the solution is to ensure the reader is always a few hundred milliseconds behind the writer. We are all hoping for a solution, as it gets tedious always pausing for a second after changing to SD channels. I hope this helps you tourettes to fix this before the 1.0 release. Regards, Ross. [/QUOTE]

Verification