[mythtv] [mythtv-commits] Ticket #1153: Live TV : "Error was encountered while displaying video."
mark.buechler at gmail.com
Fri Aug 18 18:48:18 UTC 2006
Thanks for the well detailed explanation, Daniel. This really helps quite a
bit with understanding what's going on behind the scenes. Now knowing what
causes it I'm sure I can more easily avoid it.
On 8/17/06, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Thu, 2006-08-17 at 09:40 -0400, Mark Buechler wrote:
> > I've seen this as well. As Daniel probably already knows, this message
> > appears when the backend stops recording frames for a period of time,
> > but not in all cases. I've seen this happen when the backend tunes a
> > channel which is encrypted and can't be decrypted. I've also seen on
> > occasion the backend just stops responded entirely and has to be
> > restarted. The problem also used to exist when the backend switches
> > ringbuffers between programs. I haven't seen that particular problem
> > in many versions now, however.
> The "Error was encountered while displaying video" message is
> a catch all for a large number of different types of error
> conditions. The most common is when there is a timeout waiting
> for video to start for whatever reason. The timeout is not
> supposed to start counting until we have a good signal. This
> can fail if the recorder does not have a signal monitor, if
> the signal is encrypted, or if the signal disappears after
> the signal monitor reports that it is good. The first two need
> to be fixed, the last one can't be fixed on all hardware, but
> we've talked about fixing it with some hardware.
> This can also happen if you flip channels very quickly. Fixing that
> problem is a long term project because we don't count frames in the
> NVP, we count bytes, and this sometimes fails. Counting frames depends
> on fixing #799, and some display problems I'm working on on the
> mythtv-vid branch. A quick fix would be to just limit you to one
> channel change every two minutes, but I think that is not a good
> solution since 99% of the time for a DVB-T/DVB-C or ATSC/QAM user
> a channel change completes in 1-3 seconds.
> There was another problem in 0.19 that made the quick succession of
> channel changes especially sensitive to frame count estimation
> errors, which was the problem which the logs in ticket #1153
> showed. This problem was worked around by Issac in SVN head, and
> hence the closing of the ticket. The underlying problem with the
> estimation throwing off ring buffer switching is still there,
> but usually only triggered by aggressive channel flipping, and on
> very rare occasion when we move from one program to the next in
> -- Daniel
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-dev