Dennis Noordsij wrote:
Yes I did try that :-) 2 (coincidentally) identical PC's, swap cards, problem follows card. It really is in the card, not in other hardware.
OK very good to know.
Can you try vdr 1.1.13 and the 0.9.4 driver with the crashing card and see how long that is stable when you use just replaying? I've had 0.9.4 running stable for weeks with a card that later crashed with 1.0.0 drivers within hours or minutes.
Can I do that while running 2.6.4?
I don't think so I'm afraid - but worth a try. 2.4.x should work however.
And then the streamdev-client probably doesn't work in 1.1.13, etc.True 1.1.13 won't support that I think. But you can try provoking the bug by playing back a file over and over again. This is probably easier done with mplayer built against 0.9.4 drivers.
I've tried something similar by calling that on every channel change (vdr might do this on channel change anyway I think) - but it made no difference. Possibly worth a try to do this more often, but I don't think this resolves the problem. Question is - can you reproduce that 0.9.4 is stable over a day or so on your otherwise crashy card and if you can, why is that so. What do later drivers do differently that makes it crash. I've had no luck trying to figure this out last year for a couple of months.I'm still not too sure about this - but maybe this has something to do with the rest of the system rather than the cards itself. Sometimes people have reported outcom errors are even caused by things like heat etc. but obviously in the same setup both cards ought to work.
Wasn't there a remark on the DVB list about calling SetPIDS(0,0,0,0,0) periodically (interrupts video stream though) to keep things working?