Opened 12 years ago

Closed 11 years ago

#3786 closed patch (fixed)

timestretch doesnt reset on catchup for remote FEs

Reported by: anonymous Owned by: danielk
Priority: minor Milestone: 0.22
Component: mythtv Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no

Description

on (some) remote frontends, timestretch doesnt reset to x1 when it catches up to the end of a recording currently in progress or livetv. The current mechanism is not very robust. The solution I have come up with is to monitor ringbuffer starvation and pass this info back up to NVP. Shoudl work under all circumstances, though not sure about BE streaming mode without readaheadthread active as it relies on incomplete reads to detect data starvation.

It may be possibly to remove the old IsNearEnd? test and use this method exclusively.

Not extensively tested but seems to work in my scenario which uses readaheadthread and NFS (I think).

patch attached

Attachments (4)

mythtv_tsreset.1.patch (6.9 KB) - added by Mark Spieth 12 years ago.
mythtv_tsreset.2.patch (7.0 KB) - added by Mark Spieth 12 years ago.
mythtv_tsreset.3.patch (7.0 KB) - added by Mark Spieth 12 years ago.
mythtv_tsreset.4.patch (598 bytes) - added by Mark Spieth 12 years ago.

Download all attachments as: .zip

Change History (10)

Changed 12 years ago by Mark Spieth

Attachment: mythtv_tsreset.1.patch added

Changed 12 years ago by Mark Spieth

Attachment: mythtv_tsreset.2.patch added

comment:1 Changed 12 years ago by Mark Spieth

updated patch which fixes catchup on recordings in progress being watched (not livetv mode). one of my biggest issues now works well.

Changed 12 years ago by Mark Spieth

Attachment: mythtv_tsreset.3.patch added

comment:2 Changed 12 years ago by Mark Spieth

patch 3 provides a minor improvement to help with slower FE's triggerring play x1 sporadically. now uses both metrics to determine catchup so should reduce the final lag when x1 is invoked.

Changed 12 years ago by Mark Spieth

Attachment: mythtv_tsreset.4.patch added

comment:3 Changed 12 years ago by Mark Spieth

minimal change to cater for timestretch catchup when viewing recording in progress.

comment:4 Changed 11 years ago by danielk

Milestone: unknown0.22
Owner: changed from Isaac Richards to danielk
Status: newassigned

comment:5 Changed 11 years ago by danielk

Type: defectpatch

comment:6 Changed 11 years ago by danielk

Resolution: fixed
Status: assignedclosed

(In [19485]) Fixes #3786. Allow timestretch to reset to 1.0 when we catch up to a recording in progress when not in livetv.

Note: See TracTickets for help on using tickets.