Sad news is that its there for me too on R5F1

Sad news indeed. I have been putting this error to the back of my mind while fighting another problem for the past couple of weeks (stutter with OSD up), I was about to try the new build to see if it helped with that problem.
I wonder what is different with the hardware that the guys posting on the mythtv forum is, I rarely see mention of this error on that forum. I wonder what build of MythTV R5F1 is now based on, and if it includes any of the latest patches/fixes,

Kevin

post your hardware details for comparison, but no common hardware seen in the thread thus far

I can confirm this with R5f1. this is the first time I have had this problem. I set all resolutions to 720x480 and turned off VBI recording. Nothing helps.

My hardware details:

KnoppMyth release: R5E50 (straight R5E50, I have not installed any of the mythtv patches/fixes)
Motherboard: ASUS M2NPV-VM (mATX GE6150-NF430)
CPU: AMD AM2 Athlon 64 3500+
Video: Nvidia 6150 (on the motherboard) Nvidia driver: 9755
Capture card1: Hauppauge PVR-500 (with Philips tuners)
Capture card2: Airstar HD-5000-PCI
RAM: 1G (2x512MB OCZ PC2-5400 Gold)
Hard drive: Maxtor 80GB 7200RPM ATA133S
DVD: Samsung SH-S182 IDE DVDRW with Lightscribe
Network: Dlink DWL-G122 Rev C1 USB dongle (wireless-G), Ralink RT73 driver

I am using OpenGL vsyc at the moment as XvMC gives me worse stuttering problems when the OSD is up.

In the next couple of days I will be updating to the new release and at the same time I will switch to a new 320G SATA drive,

Kevin

Interesting Wiki entry on this error, dated Aug 2006, so not sure if it is still current ..

http://www.mythtv.org/wiki/index.php?ti ... ntable=yes

Also, a long discussing in the MythTV forums, this via gossamer-threads ..

http://www.gossamer-threads.com/lists/m ... ded#216823


Seems a common theme might by that it is usually a system with a DVB card, although one poster pointed out that this would often be HD content so the amount of data and system load would be much higher. Another post I read discussed hard drive speed being a factor. Will be interesting to see if I still have the problem when I switch tom my new 300GB SATA2 drive,

Kevin

Unfortunately this seems to have been around for a while....
It looks like


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.
12) Its still present in R5F1

I personally dont believe its a lack of processing power or HD bankwidth, more likely its a mythtv bug that only manifests itself with particular cirumstances.

I dont think its a memory issue, esp if people with 1Gb in their boxes are experenicng this.

EDIT
ive also tried the suggestion here
http://svn.mythtv.org/trac/ticket/2335 that running the backend with upnp disabled might help. Unfortunately (for me at least) it made no difference.

Hi All,

I to was plaged with the this video can not be displayed problem, I applied the changes to the mysql database which improved things.

I had started to get the problem again with my dvds not recording the correct sound track again (from dvb sorce). My origonal fix was a patch to mythburn which identified the largest sound file and deleted the other one before a remplex. Later i discovered that if you went into the input cards > recording options for a given card there was an option called "Use Hardware MPEG Decoder"?? which i think was badly named. What this did was to only record the first audio track in the recording.
Any how back to the story when the problem started to reoccure i decided to check out the input cards > recording options again and low and behold this option has gone. So back too the problem in this thred I only had a problem with "video can not be displayed " since the dvb recording options changed ( I figure and i could be wrong; that there was some other changes in this section to also make the dvb interactive work) . Anyhow i noticed the first option in the dvb recording settings setings setting was wait for SEQ Header, this was checked i unchecked it on both my cards and have only had a problem once in the past week. I may be looking at this too simplisticaly but i figure that if a TV program ends and myth then restarts a recording if it has to wait for a SEQ header before it starts recording aain there is bound to be a delay ?? if this delay is too long you then get the error.

To be honest i cant see why myth cant record by channel & time of even better complete MUX & Time. That way after the recording ends a job could be run to convert / each program into a seperate file. Playing back live tv would just meen the frontend would need to playback the appropriet stream from within the file. This would give all sorts of advantages.

Firstly; you would not nave the above problem with live tv.

Secondly; you would be able to record Two / Three ... channels/programs at the same time using one card as long as they were on the same Mux.

Thirdly; I and I think others use the start recording early / late opions. if you have back to back recording on the same channel / MUX. Currently i find these recordings have to be done on alternate tuners to get the 2min early and the 2min late not to clash. If they were recorded as one file and split later not only could the recording be done using one tuner but both recording could overlap (ie the file could be extracted with an overlap of 2 min early/late).

Anyhow thats my thoughts

so the fix for me

Go into the mythtv setup (Alt-s From X frontend)

Select input cards

Select your input card

Select recording options

Uncheck "Wait for SEQ Header"

It has helped a lot for me (not fixed completely) hope it works for you all.

SimonF

_________________
Running:-
Intel 930 3GHz dual Core
Thermaltake Fanless CPU Cooler
Asus P5GS
Samsung 750G Sata HDD
8400 512m Video Card
2 * jetway DVB-t
1 * Haupage DVB-S2 Card
Samsung Sata 16x DVDRW
2048M Ram
1 * Netop Ion 330

ok i tried simonfs suggestion of Uncheck "Wait for SEQ Header"

Ive tested it for about 2 days now. in that time ive seen 1 lockup of the playback - a freeze and 1 "error occurred whilst displaying video" problem.

The transition is more sudden and agressive and possibly the problem is eased by this but its not eliminated it for me.

Has anyone made any more progress tracking down a fix for this bug?

I have got R5F1 up and running, it fixed a number of problems for me, including the video stuttering when OSD is up

Unfortunately it has not fixed the 'Error was encountered whilst displaying video' problem

R5F1 was going so well, it looked I was finally going to get a setup I could actually sit down and use.

If anyone can suggest anything I can do to gather data points to help track this down, please let me know,

Kevin

This seems to be an ATSC HDTV problem. I have two R5F1's running ATSC with Kworld & Air2PC cards, and they both do this.
OTOH I have an NTSC box (running F1) that never does it...
YMMV strikes again ...??

I got this problem last night watching a PAL SDTV.

_________________
Girkers

My box went down last night, looks like my new SATA drive got corrupted for some reason. Will be a few days before I get it back up and can start looking for the ''error was encountered while displaying video" problem. One step forwards, two steps back.

Interesting Girkers that you see the problem with SDTV,

Kevin

Here is the log output from when it happened.

_________________
Girkers

Hi Guys

Have had this issue only on last 3 releases, have been unable to find a resolve. I can confirm it happens on SD as well as HD content with no noticeable differences. I have 3 machines running as below all with dual cards of different brands etc all clean installs no updates or images.

AMD XP 2800 1 gig ram Albatron board wd hdd 2 x twinhan cards 1 x pvr-500
AMD Sempron 3200 1 gig ram ASUS board wd hdd 2 x Dvico cards
P4 2.8 1 gig ram Gigabyte board wd hdd 2 x forgot what they are.

I have had this setup running on around 10 to 15 different setups (own a computer shop so no shortage of stuff to test it on) with the same result everytime. Have installed using

Debian clean build
Ubuntu Clean build
Mythdora 4
Last 3 releases of knoppmyth

All exhibit the problem from a 5 min time period to 3 days with out the error. If more info required please let me know. All are running PAL as im in Australia.

Ghost