Oliver Endriss wrote:
[EMAIL PROTECTED] wrote:
[faster tuning w/o zig-zag scan]
I can confirm this for my DVB-S Nexus 2.1, too.
Perhaps this is due to my setup: DVB-S connected to a DiSEqC switch.
Tuning is faster w/o zig-zag scan. Sometimes, if zig-zag scan is
enabled, the DVB-S never
On Saturday 04 Jan 2003 00:14, you wrote:
Thanks for the help, that worked a treat, just needed to reboot as well
to removed the 'borken' modules that i had previously insmod'ed
I'm following
http://www.linuxtv.org/mailinglists/linux-dvb/2002/01-2002/msg00246.html
as it appears to be the
--On den 4 januari 2003 03:41 +0200 Jaakko Hyvätti [EMAIL PROTECTED]
wrote:
Anyway, the most important thing is that zigzag is disabled.
I had problems with the zigzaging too when trying to troubleshoot
my card. It also seemed to not want to stop when retuning, it
seemed to continue
--On den 4 januari 2003 10:42 +0100 Joerg Riechardt [EMAIL PROTECTED]
wrote:
How do you disable zig-zag scan? I would like to try it.
I #if 0-ed the line:
fe-lost_sync_count++;
in driver/dvb_frontend.c, that seems to do it.
/ragge
--
Info:
To unsubscribe send a mail to [EMAIL
Hello,
I just bought the WinTV DVB-T card and would like, of course,
to use it. Can anyone advise as to what software I need to
have it run? There was a previous post to the effect that
siemens_dvb-0.9.4, which I was going to try first, was too old.
However, a firewall seems not to let me use CVS.
Hi
I recently purchased one of those cards (last Sat) and have got it
working fine. It was not easy, I started with the debian packages, which
are so old now I didn't even get the card to be seen. I tried the CVS
which was confusing. However if I had realised I didn't need to modprobe
dvb and
Joerg Riechardt wrote:
How do you disable zig-zag scan? I would like to try it.
--- dvb-api-v3.2002-11-29/driver/dvb_frontend.c Fri Nov 29 14:16:01 2002
+++ dvb-api-v3.2002-12-05/driver/dvb_frontend.c Sat Dec 7 12:57:45 2002
@@ -390,6 +390,9 @@
{
int j =
HI Roberto,
Here's my latest patch your dvb-s modification... I'm getting
artefacts (some pixels slowly updating on random basis) at the
xawtv screen.
Seems stable in my setup.
Emard
Only in DVB/apps/av7110_loadkeys: av7110_loadkeys
Only in DVB/apps/av7110_loadkeys: av7110_loadkeys.o
Only in
Hi,
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to standard
YUV (or whatever is used on the V4L-interface).
This would allow programs like XawTV to watch TV without having a own
MPEG-TS decoder. Standard
Hello Rene,
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to standard
YUV (or whatever is used on the V4L-interface).
This would allow programs like XawTV to watch TV without having a own
MPEG-TS decoder.
Rene Bartsch writes:
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to standard
YUV (or whatever is used on the V4L-interface).
This would allow programs like XawTV to watch TV without having a own
Ralph Metzler wrote:
Rene Bartsch writes:
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to standard
YUV (or whatever is used on the V4L-interface).
This would allow programs like XawTV to watch TV
Michael Hunold wrote:
Hello Rene,
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to
standard
YUV (or whatever is used on the V4L-interface).
This would allow programs like XawTV to watch TV without having
Holger Waechtler writes:
Ralph Metzler wrote:
Rene Bartsch writes:
after reading documentation of new FFMPEG 0.4.6 I got the idea to add a
libavfomat-based V4L-device to the DVB-driver, which decodes TS to standard
YUV (or whatever is used on the V4L-interface).
This
HI
Here is my latest and greatest patch for Roberto's
patch for DVB-S.
Looking cloesly what's going on, I found out that in
his original patch there was incorrect PCI bus burst
arbitration setting that caused artefact in xawtv,
It is corrected now. The patch is for convergence DVB
cvs tree.
overclocking).
lspci -vvv shows status: Cap- 66 MHz- UDF- ...
But the bus is 33 Mhz (ten year old Fujitsu/ICL). So is there something
wrong? Can I change any settings?
Cap- 66 Mhz means that card's capability is negative for 66 MHz.
In simpler words, it means 33 MHz.
You can change
Ralph Metzler wrote:
Holger Waechtler writes:
Maybe at the end we will stay stuck with the proprietary firmware
libraries which do essentially the same, but they are 'politically more
accepted', just because there is much more black voodoo around them and
you can't get rid of them so
HI
I'd like to make autodetection of the patch at dvb-s.
There is GPIO3 pin connected at VS_B. I'd like to e.g.
set to 0 and 1 GPIO3 and check if VS_B is changing too,
or, if it's easier to program, set VS_B as output,
GPIO3 as input check if GPIO3 is changing.
Anybody knows how I can read VS_B
On Sat, 4 Jan 2003, Ragnar Sundblad wrote:
get instable. I am not sure it would be a good idea to optimize
it for your card and just hope it works for all cards on all
bands and put it in the CVS driver. I'd prefer having the driver
in the CVS do as the manufacturer says, or maybe being
HI
Here's patch with the autodetection
Only in DVB/apps/av7110_loadkeys: evtest
diff -pur /home/loader/src/DVB/apps/szap/szap.c DVB/apps/szap/szap.c
--- /home/loader/src/DVB/apps/szap/szap.c Sun Nov 17 00:36:09 2002
+++ DVB/apps/szap/szap.cSat Jan 4 21:11:50 2003
@@ -193,8
20 matches
Mail list logo
