On Thu, Jul 08, 2004 at 03:01:42PM +0200, Jose Alberto Reguero wrote:
Sometimes Vdr problem with AverTV BVB-T 771 cvs drivers and vdr 1.3.11
...
I get similiar problems with my skystar2.6B: after a while of heavy use,
it stops providing any data.
The frontend is fine at that moment: I can tune
That's true. It seems to happen with almost any driver/kernel/card type
combination. What stands out somewhat is a combination of VDR and a 2+
card setup with budget cards.
Maybe that my problem is related to that. My setup is vdr-sever with
2 dvb-s budget cards. I allways had problems
El Domingo, 11 de Julio de 2004 21:48, Frank Oppel escribió:
I fix my problem as suggested in:
http://www.linuxtv.org/mailinglists/vdr/2004/06-2004/msg00057.html
I set Setup/DVB/Update channels to no, and at the moment no more video
data
stream broken.
Jose Alberto Reguero
Hello Jose,
Hello Johannes
Because I cannot reproduce it. Maybe I haven't tried hard enough,
but then I don't have the time to do that.
That shouldn't be the problem, because to reproduce it I haven't to try it
hard.
If you want to take a look at a machine where the error reliable occurs
and you have the
Wolfgang Fritz wrote:
Johannes Stezenbach wrote:
Frank Oppel wrote:
it would be interesting for us, what the developers from Convergence
or the other gurus think about the video data stream broken-error,
wouldn't it?
Why the don't join the discussion about this problem?
Because
Andreas Share wrote:
Hmm, my skystar2 rev 2.6c/stv0299 dies within 2-3h, but my nova (like
budget-ci) and my ff rev 1.5 sometimes run for ~12h...
i have seen the skystar2 irq_handler calls dvb_dmx_swfilter_packets()
more
often than the other cards
if (adapter-capturing != 0) {
Andreas Share wrote:
Hi,
I have around 1600-1800 interrupts per second, with the ss2 as secondary
device during epgscan.
OK, That is not excessive - an idle 2.6 machine has 1000 from the timer
interrupt alone.
One other thing: The Dbox2 related Tuxbox Project share the Api3 and the
most of
- Original Message -
From: Jon Burgess [EMAIL PROTECTED]
To: Andreas Share [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, July 10, 2004 10:26 PM
Subject: [linux-dvb] Re: Vdr video data stream broken
Andreas Share wrote:
Hi,
I have around 1600-1800 interrupts per second
Can we say that everytime the stv0299 is involved ?
In my opinion, definitively yes!
Whenever the stv0299 is involved it comes to the video data stream
broken-error, except you have a single nexus running.
On Thursday 08 July 2004 23:03, Frank Oppel wrote:
One more datapoint for you, in my setup I have VDR running with 4 DVB-T
PCI cards and it works fine.
I regularly have timers recording programmes on 2 or 3 cards
simultaneously and have never seen the error you describe.
Perhaps
Can we say that everytime the stv0299 is involved ?
In my opinion, definitively yes!
Whenever the stv0299 is involved it comes to the video data stream
broken-error, except you have a single nexus running.
Also it comes with to AverTV BVB-T 771 cards(mt352 frontend).
No, because older skystar2 rev 2.3 with mt312 also involved.
Ok, now we have the skystar 2 rev 2.3 with the mt312 frontend,
the AverTV BVB-T 771 cards with mt352 frontend, and finally the
nova, skystar2 (rev. ?) and the tt budget cards with the stv0299 frontend.
Which similarities have the
On Friday 09 July 2004 10:11, Andreas Share wrote:
Can we say that everytime the stv0299 is involved ?
Steffen
No, because older skystar2 rev 2.3 with mt312 also involved.
Andreas
I have both cards and my impression is, that the nova/stv0229 triggers this
bug more often than the
I have both cards and my impression is, that the nova/stv0229 triggers
this
bug more often than the skystar2/mt312.
Well I think so, because I can reproduce this bug (with Kernel 2.6.5) in
less than 10 sec, with my tt budget card which uses the stv0299.
Always when a recording starts, the vdr
OoO En cette matinée pluvieuse du vendredi 09 juillet 2004, vers
10:41, Christian Schuld [EMAIL PROTECTED] disait:
I have both cards and my impression is, that the nova/stv0229 triggers this
bug more often than the skystar2/mt312. May be because it has no hardware
filters?
Do you
On Friday 09 July 2004 10:11, Andreas Share wrote:
Can we say that everytime the stv0299 is involved ?
Steffen
No, because older skystar2 rev 2.3 with mt312 also involved.
Andreas
I have both cards and my impression is, that the nova/stv0229 triggers
this
bug more often than the
Hi,
you can add the Hauppauge DVB-S rev2.1 and and a DVB-S rev1.3 to the list.
I had that problem on both boards, but more often on the rev2.1 (secondary
device), rev. 1.3 (primary) produced it very seldom.
I do not have this problem any more since I turned off VDR's EPG scan, at
least its not
On Friday 09 July 2004 12:29, Andreas Mair wrote:
Hi,
you can add the Hauppauge DVB-S rev2.1 and and a DVB-S rev1.3 to the list.
I had that problem on both boards, but more often on the rev2.1 (secondary
device), rev. 1.3 (primary) produced it very seldom.
I do not have this problem any more
On Thursday 08 July 2004 15:01, Jose Alberto Reguero wrote:
Sometimes Vdr problem with AverTV BVB-T 771 cvs drivers and vdr 1.3.11
Jul 7 19:35:00 jar vdr[2235]: timer 2 (5 1935-1830 'TELECINCO') start
Jul 7 19:35:04 jar vdr[2235]:
record /video/TELECINCO/2004-07-07.19:35.50.99.rec
Jul 7
Hi,
On Thursday 08 July 2004 15:27, Steffen Barszus wrote:
On Thursday 08 July 2004 15:01, Jose Alberto Reguero wrote:
Sometimes Vdr problem with AverTV BVB-T 771 cvs drivers and vdr 1.3.11
Jul 7 19:35:00 jar vdr[2235]: timer 2 (5 1935-1830 'TELECINCO') start
Jul 7 19:35:04 jar
On Thursday 08 July 2004 16:23, Andreas Share wrote:
On Thursday 08 July 2004 15:51, Christian Schuld wrote:
I suppose
none of the driver developers actually use such a setup with VDR
regulary,
because then it would have gotten more attention - simply because it is
really annoying
On Thursday 08 July 2004 15:29, Steffen Barszus wrote:
Does klaus know about this ? Can something changed inside vdr to avoid this
? This is what i understood from what you have said :D, am I right ? I have
this problem since months no matter which vdr version and this sucks.
From memory,
On Thursday 08 July 2004 16:34, Gavin Hamill wrote:
On Thursday 08 July 2004 15:29, Steffen Barszus wrote:
Does klaus know about this ? Can something changed inside vdr to avoid
this ? This is what i understood from what you have said :D, am I right ?
I have this problem since months no
On Thursday 08 July 2004 16:23, Andreas Share wrote:
On Thursday 08 July 2004 15:51, Christian Schuld wrote:
I suppose
none of the driver developers actually use such a setup with VDR
regulary,
because then it would have gotten more attention - simply because it
is
really
On Thursday 08 July 2004 16:56, Andreas Share wrote:
Maybe the driver should close all filters, tune and then restart the
filters...
Agreed, especially when it is known, that some frontends deliver garbage, when
they are not locked.
I have also tested epg-scanning without any section filter
On Thursday 08 July 2004 16:34, Gavin Hamill wrote:
On Thursday 08 July 2004 15:29, Steffen Barszus wrote:
Does klaus know about this ? Can something changed inside vdr to avoid
this ? This is what i understood from what you have said :D, am I
right ?
I have this problem since months
On Thursday 08 July 2004 16:56, Andreas Share wrote:
Maybe the driver should close all filters, tune and then restart the
filters...
Agreed, especially when it is known, that some frontends deliver garbage,
when
they are not locked.
Hmm, the ves1893yes...but my brand new rev 1.5 with
OoO Lors de la soirée naissante du jeudi 08 juillet 2004, vers 17:06,
[EMAIL PROTECTED] (Andreas Share) disait:
I also think the right place to fix this is the driver, but i could live
with a workaround in vdr if this is possible. At the moment i could not
understand why some people have this
Christian Schuld wrote:
Normally ERROR: video data stream broken indicates, that VDR doesn't get any
data out of the DVB-card. The reason might be a tuning failiure or this
mysterios bug, which happens only with VDR in a multi card setups. I suppose
none of the driver developers actually use
29 matches
Mail list logo
