I think this bug only can be reproduced if you are using 4x1 diseqc switches. I have exact same problem on my setup and I traced it out to diseqc switches. Every time one of your cards switches one switch while other card is recording, the diseqc signal goes around LNB to another diseqc switch and moves its position too, and other card, which is recording, loses signal and you get VDSB. I don't have scope but I've put the cards in different machines and if I set one of the machines to record while I'm flipping channels on second machine, the first one would got VDSB or if I'm not recording, I'd just lose signal on first machine. If I use only one, either machine, at the time, stuff works without any problems. In my opinion, the only way to resolve this is to get diseqc-multiswitch.
Another possibility is your hardware setup, i.e. one or all of your Nexus cards are using bad PCI slots or sharing IRQ with very incompatible devices. Try moving cards to different PCI slots to resolve IRQ issues.
vshved@logistic-systems.com(Vladimir Shved) 15.02.05 10:47
To be exact: You have the same error messages ;-)
That sounds like the problem i have with my "single LNB" environment: If i enabled EPG scan, after an hour the Video stream breaks.
or if I'm not recording, I'd just lose signal on first machine.
If I use only one, either machine, at the time, stuff works without any problems.
In my opinion, the only way to resolve this is to get diseqc-multiswitch.
So only users with diseqc enabled have that problem?
And why he didn't had/don't have the problem with 1.3.17? Was diseqc handling introduced with 1.3.18ff?
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Hello,
for me the most stable version is still the poissoned 1.3.17 :-)
I really wonder why poissoned is not included (but by default not enabled) ? (I know it has already been discussed, so please don't take in accound this last phrase...).
On Wed, Feb 16, 2005 at 05:55:50PM +0100, Klaus Schmidinger wrote:
Well, then why did you say it? ;-)
Because I wanted to say it in a way that would still be "ethicaly" correct in respect with that you wrote about it :-)
That "poisoning" stuff has no actual functionality and I don't believe that it will make any difference regarding your problems.
Maybe yes, but maybe not, it's a good way to know what's safe or not, but as everyone is sure it's safe without... So as I have the most stable system with poissoned 1.3.17 I just wonder what has changed and what could be done to have new feature of 1.3.21 with stability of poissoned 1.3.21 ;-) (which is really hard as VDR is a "great" project in size and fonctionality).
Thank for this great program I use everyday !!!
Grégoire Favre wrote:
The "poisoning" is merely some "pragmas" which you should easily be able to add to the VDR 1.3.21 code.
BTW: I'm neither a native French nor English speaker, but AFAIK "poison" means some stuff that might kill you, while "poisson" means "fish" in french - I don't suppose you have implemented any "fishy" stuff into your VDR ;-)
Klaus
On Wed, Feb 16, 2005 at 06:22:14PM +0100, Klaus Schmidinger wrote:
The "poisoning" is merely some "pragmas" which you should easily be able to add to the VDR 1.3.21 code.
Yes, that's true, once shall I try, but it shouldn't be so much beatifull snow here...
Oops, and it's not the fish from the Hitchhikers Guide To The Galaxy which would make the multilanguage change in VDR useless :-)
-
Grégoire Favre -
Klaus Schmidinger -
Rainer Zocholl -
Vladimir Shved