Reply to thread

Message

<blockquote data-quote="TesterBoy" data-source="post: 103768" data-attributes="member: 22382">I assume you're talking about the Australian Daylight Saving update?&nbsp; If so, I hope not - I'm in New Zealand&nbsp; B-)Further info - the problem appears to go away after rebooting the htpc, but then progressively gets worse over time...Compressing fixes the problem for a particular recording (since the header is then gone), but the problem also affects the timeshifting - obviously we can't compress the timeshift buffer.&nbsp; This makes the shuttle almost useless for watching live TV (Note that on my htpc at least, I can't turn timeshifting off since the picture and sound degrade very quickly until it stops completely).Edit: Actually, I'm not sure it gets worse - I rebooted last night and the recorded time was correct (0:01:00), but this morning I'm getting a 0:03:44 time on a 0:01:00 recording.&nbsp; The 35-minute scheduled recording I made this morning thinks it's 45 minutes long, though...</blockquote>

[QUOTE="TesterBoy, post: 103768, member: 22382"] I assume you're talking about the Australian Daylight Saving update? If so, I hope not - I'm in New Zealand B-) Further info - the problem appears to go away after rebooting the htpc, but then progressively gets worse over time... Compressing fixes the problem for a particular recording (since the header is then gone), but the problem also affects the timeshifting - obviously we can't compress the timeshift buffer. This makes the shuttle almost useless for watching live TV (Note that on my htpc at least, I can't turn timeshifting off since the picture and sound degrade very quickly until it stops completely). Edit: Actually, I'm not sure it gets worse - I rebooted last night and the recorded time was correct (0:01:00), but this morning I'm getting a 0:03:44 time on a 0:01:00 recording. The 35-minute scheduled recording I made this morning thinks it's 45 minutes long, though... [/QUOTE]

Verification