Opened 13 years ago
Closed 13 years ago
#4761 closed defect (invalid)
Rotor counting up percentage when it is already in position
Reported by: | anonymous | Owned by: | danielk |
---|---|---|---|
Priority: | minor | Milestone: | 0.22 |
Component: | mythtv | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
The rotor movement has been altered in the last few weeks and extremely slows channel tuning when moving from one position to another. Instead of allowing a channel lock as soon as the channel is found, a channel will not tune until the seemingly arbitrary movement percentage counter has reach 100%. This is particularly annoying with sat positions that are very close to each other where movement and tuning should take only a few seconds now can take a minute or more.
Change History (3)
comment:1 Changed 13 years ago by
Milestone: | 0.21 → 0.22 |
---|---|
Owner: | changed from Isaac Richards to danielk |
Status: | new → assigned |
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
This has been reported to still work correctly by Mark Buechler. My assumption is that this happened on the first tune, when we don't know where the rotor is. In which case MythTV will report the incorrect rotor position.
Can you provide the "mythbackend -v record,channel" logs changing to the initial channel and then to the second and third channels, along with the "mythfronted -v playback,channel" logs of the same?