As this thread is getting rather long I have updated the first post with the story so far
It seems the error "Error Was encountered while displaying video" happens during LiveTV watching in knoppmyth r5e50 and some previous versions

1) its been around for at least a year
2) there does not seem to be any commonality as to what hardware config it manifests itself in - a random collection of AMD/Intel processors and variety of motherboard
3) Its reported mainly here with DVB and HDTV recording but thats not definitive
4) It seems to happen at the program boundary when the backend wants to take a new 'LiveTV recording' file and the front end attempts to open it
5) There is a suggestion that it may be that the frontend is trying to open the new recording file before its been created
6) There is a suggestion that it could be related to Mysql DB performance problems
7) Some tweaks to my.cnf were applied and seemed to help a bit but the problem is still present
8 ) Mythtv has a ticket for this http://svn.mythtv.org/trac/ticket/2335
9) Ive tried various other distros and mythtv and its happening with mythdora and ubuntu + myth - so its unlikely to be a knoppmyth issue
10) mythtv .20 changes have been applied to r5e50 with no success
11) I seems that pressing the pause button during livetv can alleviate the problem as it gives the frontend more time to open the new file - this is not a solution for the channel surfer tho.




Original posting is below this line
---------------------------------------------------------------
I think ive got this problem, and searching the forums/google it looks like others have it too.
When watching live TV it seems that *sometimes* not 100% of the time playback will crash with the above error when the backend decides to "take a new file" as a result of the schedule change. note that its just playback not the whole frontend that crashes....

Ive had this happen 4 times now in 1 night, each time on a program scheduling boundary.

Worryingly i dont seem to be able to find anyone else thats had it and solved it (there was a rumour that the noapic option in lilo.conf would help for nforce boards but i dont have an nforce board)
here is the backend log from around the time of the last playback crash
at 4am


Does anyone have a quick fix for this , or should i take r5e50 back to the workbench and reinstate my r5a16 box which did not exhibit this problem, and be prepared for a long troubleshooting session

Ive posted thie following in a thread about the EIT data causing stuttering but I think its more correctly put in here so im reposting

I think I have now come to the conclusion that its not EIT data thats causing the stutter its the switch to an new recording file at each change in the recording schedule.

I ran the frontend interactively from an xterm and was able to watch its logging to the terminal....
it shows


Im drawing the conclusion here that the front end is trying to open the new backend recording file too fast (before its created) and failing....

anyone else seen this and can think of a work around ?

Links to some more info on this

http://svn.mythtv.org/trac/ticket/1153
http://svn.mythtv.org/trac/ticket/2335
even tho the first ticket is closed if you read the history its still clearly a problem 2 months ago

it seems that pausing live tv for a few seconds can stop this error(not tried that yet so cant verify), but my wife watches livetv all the time and I dont think she'll wear this

Wish I had a solution, because I am having the same problem, with a similar error.

I agree that when it does occur, its always happen when the schedule starts a new recording for a new program.




In my case it may happen as many as two or three times in one evening, and other times not at all.

I will have to try the pause idea, and see if that makes a difference.

What type of hardware do you have - to see if there is any overlap

I have
MSI socket 478 mobo
Pentium 4 1.7Ghz
512mb ram
3 Hauppauge wintv nova-t DVB digital terrestrial card (2 new model 1 old model)

Ive tried it with just 1 card an it still happens

Going to try it on a ubuntu build if i cant find a fix to see if its an knoppix issue or a mythtv issue

ps - still dont know if the pausing livetv prevents the issue, not really that fussed if it does as i dont want to be forced into rememebering to pause livetv every time i channel change - this is too clumsy a work around for the problem.

I'm running

KnoppMyth R5D1 - with Cecil's Myth 2.0 update
ASUS P4P800-E
XFX Geforce FX5200 Version 4.0
Intel Pentium 4

I see the same thing. Sometimes it happens, mostly no problem. I'm running R5D1, no .20 updates.

which tuner cards do you have ?

I have the following tuner cards installed:

Two - HD3000
PVR350
PVR150

I usually only watch live TV with the HD3000 cards so have only seen the problem there.

ok that rules out my tuner cards as being a specific compatibility problem..

so if its hardware it must be my motherboard or HD controller....

My motherboard (and CPU) was a pretty cheap ebay purchase so I could be persuaded to dump them if i was certain they were the issue... but given that its appearing on a variety of combinations I'm struggling to see what the commonality is

I believe the problem is related to Myth and not your hardware.

When I was running R5C7, I rarely if ever had this problem. (Myth v19)

Mine started when I went to R5D1 and Myth (v20)

Agreed, it does point to a myth issue. However given that we are in the minority and it seems that most people dont have the issue it makes me think the issue could lie with myth (0.20) and some other (hardware possibly?) factor.

Like I mentioned earlier, I might try the route of testing a ubuntu +mythtv install on the same hardware to see if the problem is still there with a different distro. But I more comfortable with KnoppMyth and dont really want to go that way in the long term because of 1) better "out of the box" functionality in knoppmyth and 2) this excellent forum for support.

Just to let you know that I too have encountered this problem and it &*^%s the wife no end. Fortunately there is a ban on TV in my house at the moment so this is no longer an issue. I am using a current test version of KnoppMyth and it is still present.

_________________
Girkers

Yep, I cant sell any benefits in R5e50 to my wife if it crashes out of livetv multiple times/night. My main myth box is still on r5a16 and its still working well, i just wanted the latest features and a quieter box with 3 tuners this time. My other option im considering is upgrading to an historic version of knoppmyth based on myth 0.19 (ie newer than my current version but not based on 0.20 where the problem might lie). Are the old versions still avail for download - eg r5c7 ?

I'm looking for an answer too! I have searched and searched and searched for an answer, but nada!

From what I gather its the frontend getting ahead of itself, so when the show times change over it creates a new file, so it needs to start the new file, but the file hasn't quite been created when it goes to play it and drops out.

How to resolve that issue... is a bridge that i'm not quite sure how to cross!!

_________________
DRM 'manages access' in the same way that jail 'manages freedom.'
_________________
Intel P4 2.6
Intel Desktop Board
2GB DDR400
nVidia 6600GT
Dvico HDTV+
Dvico Dual 4
200GB WD for Swap /boot & /
2x 500GB WD with LVM & XFS for /myth/tv