Custom Query (13624 matches)

There are a number of conditions where the frontend is unable to start watching LiveTV due to the channel that the backend is currently tuned to.

1) Backend starts up using channel cardinput.startchan but the channel is no longer on air.
2) Backend still running, but the currently tuned channel has gone off air since the frontend last watched LiveTV.
3) As with (2) except the channel may have come back on air, but the state information the backend is holding is no longer current

Case 1: I have a patch for.
Case 3: I suspect is out of date pid/pmt information.

Case 2 & Case 3 are TODO

This patch just changes some "#if USING_DVB" to "#if USING_DVB_STATUS" to get rid of the empty "DVB Signal Information" from the myth backend status (mythweb, and port 6544).

If bob deinterlacing is turned on, current Mythfrontend turns it off if the playback speed is not 1x (such as when fast-forward/rewinding or using timestretch). This was done because otherwise panning motions can be quite unsmooth, particularly with timestretch. Unfortunately turning off all deinterlacing results in the usual ugly interlaced artifacts, particularly if the output is scaled (e.g. 1080i material being displayed at 1280x720).

This patch uses the onefield deinterlacer instead for non 1x. I chose onefield because it's the lowest resource-consumption deinterlacer, and if you're fast forwarding you could be processing frames much faster than usual.