Opened 18 years ago
Closed 17 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)
Change History (10)
by , 18 years ago
| Attachment: | mythtv_tsreset.1.patch added |
|---|
by , 18 years ago
| Attachment: | mythtv_tsreset.2.patch added |
|---|
comment:1 by , 18 years ago
by , 18 years ago
| Attachment: | mythtv_tsreset.3.patch added |
|---|
comment:2 by , 18 years ago
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.
by , 18 years ago
| Attachment: | mythtv_tsreset.4.patch added |
|---|
comment:3 by , 18 years ago
minimal change to cater for timestretch catchup when viewing recording in progress.
comment:4 by , 17 years ago
| Milestone: | unknown → 0.22 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:5 by , 17 years ago
| Type: | defect → patch |
|---|
updated patch which fixes catchup on recordings in progress being watched (not livetv mode). one of my biggest issues now works well.