Re: [linux-dvb] stv0297: improvement for qam256 modulated channels

2007-10-28 Thread e9hack
Johann Friedrichs schrieb:

 I get no lock on any QAM-256 channel with my C-2300 after applying that
 patch.

I've seen two different values for the carrier offset on Windows XP for a 
TT-C2300. Registers 20/21h
are programmed with 3c0a or 3ba4 (carrier offset 6763 or 6718). The value 
depends on the driver
revision. On a TT-C1500, this value is 4000 (carrier offset 7209). It may be 
possible, that the
value is calculated from some other values. I know, that the patch has no 
effect for some testers.
This is the first report with a failure. So it isn't possible to add the patch.

In my case, I've some channels in the UHF range with a poor signal strength. 
Without the patch, I
got ber ~3500h and unc 10h. With the patch, I get ber ~b00h and unc 0.

- Hartmut

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] stv0297: improvement for qam256 modulated channels

2007-10-28 Thread e9hack
2007/10/28, e9hack [EMAIL PROTECTED]:

 I've seen two different values for the carrier offset on Windows XP for a
 TT-C2300. Registers 20/21h
 are programmed with 3c0a or 3ba4 (carrier offset 6763 or 6718). The value
 depends on the driver
 revision. On a TT-C1500, this value is 4000 (carrier offset 7209). It may
 be possible, that the
 value is calculated from some other values. I know, that the patch has no
 effect for some testers.
 This is the first report with a failure. So it isn't possible to add the
 patch.

 In my case, I've some channels in the UHF range with a poor signal
 strength. Without the patch, I
 got ber ~3500h and unc 10h. With the patch, I get ber ~b00h and unc 0.



Sorry, 'carrier offset' should be 'initial demodulation frequency'.

- Hartmut
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Poor reception with tuners but fine on regular DTV??

2007-10-28 Thread Dom H
Dual pci Nova-T's, Ubuntu Gutsy.

Just moved house recently, set my machine up and reception was very
poor on a particular multiplex (the itv ch4 one) I assumed I'd need to
rescan as maybe I need to be tuning to a different transmitter now.
Did a full scan with MythTV but still poor reception and ITV missing.
Tried a scan with dvb-utils 'scan uk-Mendip' and got the same result.

I assumed the reception in this area was poor but I took the aerial
out of the pc and plugged it into my lcd dtv and the reception was
fine and it found all channels with a full signal strength (mythtv
reports 20-25% strength)

I was on mendip transmitter previously, moved further north to Bristol
area and it still seems to be tuning to mendip(same freqs) and not the
closer but weaker Kings Weston transmitter. I assume doing a full scan
in myth would just choose the strongest signals or do I need to
specify I want some mplexs from one transmitter and the others from
another?

Any advice greatly appreciated as I'm a bit stuck. Obviously it's not
my aerial feed as my regular tv is fine.


Thanks

Dom

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread Dominik Kuhlen
On Wednesday 24 October 2007 16:41, Daniel Golle wrote:
  For info I've spotted a newer repo over here http://jusst.de/hg/multiproto/ 
  (spotted in one of manu's mails about multiproto)
  but I think the older driver could be better at the moment as with the 
  newer driver the device doesn't appear to initialize for the stb0899
  
  also I hope you don't mind
  but I took some of the changes and combined it with the driver I've been 
  working with
  http://homepage.ntlworld.com/garlicbread/Projects/452e/patches/
  
  1. lnbp22.patch -  this is from the patch above, it's better than the one 
  I'd setup so I've left this as is
  2. pctv452e_initreg.patch - separate header file containing the registers 
  to be sent to the device on init
  I think this is more up to date because it's based off the usbsnoop logs 
  with the win driver
  but I need to give it one more final sanity check to be sure
  3. stb0899_tstrs3.patch - minor change to one of the registers I've spotted 
  while trailing through the usb logs
  4. stb0899_misc.patch - changes you've made to the stb0899 driver 
  (originally part of the above patch)
  
  3. pctv452e_main.patch - a combination of the above driver and some code 
  I've been working with
  it's basically a slightly changed version of the more recent ttusb driver
  with bits of code from the above patch (remote control especially, this 
  does work with evtest)
  the newer budget driver in manu's tree (another func added for the stb6100) 
  with some other bits
  
  at this point the results are the same (meter lights up but not much else)
  so I can't say if this is better or worse at this point
  although I've noticed the LED is staying at orange when it should be going 
  green in both cases, which suggests the GPIO register isn't being set when 
  it should
  
  quick question has anyone managed to get any kind of visible video output 
  from the device at this point?
  I'm wondering if the mpeg stream settings (for the iso transfer) need 
  tweaking (I'm not sure if the endpoint or some other setting is set correct)
 Hi all!
 I got the same results here. Tried both your and Dominik's patches. The
 card in both cases seems to at least switch polarization and 22kHz but
 ends up with an error during tuning, so no data is received.
 
 --- szap ---
 reading channels from file '/home/daniel/channels.conf'
 zapping to 25 'DAS VIERTE,D VIERTE;BetaDigital':
 sat 0, frequency = 12460 MHz H, symbolrate 2750, vpid = 0x07ff, apid
 = 0x0800 sid = 0x0024
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 status 00 | signal  99% | snr  99% | ber -2 | unc -2 | 
 FE_READ_STATUS failed: Invalid argument
 status 00 | signal  99% | snr  99% | ber -2 | unc -2 | 
 FE_READ_STATUS failed: Invalid argument
 status 00 | signal  99% | snr  99% | ber -2 | unc -2 | 
 
 
 
 --- kern.log 
 Oct 24 16:37:22 bart stb0899_read_signal_strength: Unsupported delivery
 system
 Oct 24 16:37:22 bart _stb0899_read_reg: Reg=[0xf50d], data=00
 Oct 24 16:37:22 bart stb0899_read_snr: Unsupported delivery system
 Oct 24 16:37:22 bart stb0899_read_ber: Unsupported delivery system
 Oct 24 16:37:22 bart pctv452e_streaming_ctrl: onoff=0
 Oct 24 16:37:29 bart lnbp22_set_voltage: 2 (18V=1 13V=0)
 Oct 24 16:37:29 bart lnbp22_set_voltage: 0x60)
 Oct 24 16:37:29 bart _stb0899_read_reg: Reg=[0xf12a], data=5c
 Oct 24 16:37:29 bart stb0899_sleep: Going to Sleep .. (Really
 tired .. :-))
 ---

Are you sure you have used the DVB-S2 enabled szap?
Manu posted a link a few days/weeks ago
Currently only the new tuning API does work.


Dominik


pgpQjHHDWS5JE.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread Dominik Kuhlen
On Wednesday 24 October 2007 01:42, [EMAIL PROTECTED] wrote:
 
 at this point the results are the same (meter lights up but not much else)
 so I can't say if this is better or worse at this point
 although I've noticed the LED is staying at orange when it should be going 
 green in both cases, which suggests the GPIO register isn't being set when it 
 should
 
You can change the GPIO1 initialisation to 0x02 instead of 0x82. 
this will switch the led to green when the frontend gets open()'ed.
To switch it back to orange insert
 stb0899_write_reg(state, STB0899_GPIO01CFG, 0x82);
in the stb0899_sleep() function.
(this should be somehow limited to the pctv452e as the GPIOs might 
have different meanings on other devices)

Dominik


pgpg3kmyC8iiz.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] dvbstream: Not able to lock to the signal

2007-10-28 Thread Nico Sabbi
Il Thursday 25 October 2007 04:07:19 Hong Yin Lim ha scritto:
 Hi,

 I've tried to use the following command to capture the TS from a
 DVB-C card:

 $ dvbstream -f 594000 -s 6875 -0 8192  test.ts

 However, I get the follwoing result:

 *dvbstream v0.7 - (C) Dave Chapman 2001-2004
 **Released under the GPL.
 **Latest version available from http://www.linuxstb.org/
 Adding whole transport stream to map n . 0
 **Open file test.ts
 **Tuning to 594000 Hz
 **Using DVB card ST STV0297 DVB-C, freq=594000
 **tuning DVB-C to 59400, srate=6875000
 **Getting frontend status
 **Not able to lock to the signal on the given frequency
 **MAP 0, file test.ts: From -1 secs, To -1 secs, 2 PIDs - 0 8192
 **dvbstream will stop after -1 seconds (71582788 minutes)
 **Streaming 1 stream*


 Where did I went wrong?

 I've tried using czap to lock into the channels,  it works..


 Thank you.


 Regards,
 hy


try to raise the timeout value in tune.c

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] solved problem with nova-TD hangs, usb related

2007-10-28 Thread Henrik Beckman
Hi,

Added a VIA usb controller card and attached my TD stick to that instead of
the nforce 430 controller and since it has been 100% stable.
If it´s a bug in any driver or if it´s my hardware that´s bad I don´t know.

/Henrik
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Fwd: [mythtv-users] Nova-T 500 musings...

2007-10-28 Thread Henrik Beckman
-- Forwarded message --
From: James Fidell [EMAIL PROTECTED]
Date: Oct 28, 2007 12:44 AM
Subject: [mythtv-users] Nova-T 500 musings...
To: Discussion about mythtv [EMAIL PROTECTED]

Anyone else have a Nova-T500 tuner and still getting mt2060 I2C write
errors?

I'm running CentOS5 (2.6.18 kernel + RedHat updates) with new v4l-dvb
drivers taken from linuxtv.org a couple of weeks ago and the latest
firmware.  I still get mt2060 I2C read and write errors.  As far as I
can tell the read errors don't seem that serious, but the write errors
seem to break tuning somehow so that I end up with a failed recording.
Thus far I've resolved this by stopping mythbackend and unloading and
reloading all the dvb modules whenever I've seen a writer error.  This
seems to work ok, but it's a pita.

Yesterday, more out of irritation than any real understanding of the
code, I changed the mt2060 driver code that calls write_regs to retry
if the first attempt fails.  Thus far I've had a couple of fails that
have worked ok on the second attempt and I've had no failed recordings.

I'll be watching things over the next few days to see what happens.
What I've done is without doubt a hack rather than a genuine fix, but
if it mostly resolves the problem for me, I think I can live with that
until such time as someone who understands the problem properly can
do the job right.

James
___
mythtv-users mailing list
[EMAIL PROTECTED]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Unable to load em2880-dvb

2007-10-28 Thread Menion
Hi, I compile d the official repository  http://linuxtv.org/hg/v4l-dvb/  on
Ubuntu amd64
em28xx seems to load fine but em2880-dvb won't:

dmesg output is:

[  951.511747] em28xx v4l2 driver version 0.0.1 loaded
[  951.511944] usbcore: registered new interface driver em28xx
[  955.263862] em2880_dvb: Unknown symbol em28xx_unregister_extension
[  955.263925] em2880_dvb: disagrees about version of symbol
dvb_frontend_detach
[  955.263929] em2880_dvb: Unknown symbol dvb_frontend_detach
[  955.263949] em2880_dvb: Unknown symbol em28xx_register_extension
[  955.263964] em2880_dvb: disagrees about version of symbol
dvb_unregister_frontend
[  955.263966] em2880_dvb: Unknown symbol dvb_unregister_frontend
[  955.264020] em2880_dvb: disagrees about version of symbol
dvb_register_frontend
[  955.264022] em2880_dvb: Unknown symbol dvb_register_frontend

I have the proper firmware for my device (Terratec HybribT USB) installed
Any suggestions? Bye!!!
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] stv0297: improvement for qam256 modulated channels

2007-10-28 Thread Johann Friedrichs
Hi Oliver, Hartmut

I have to modify my last statement concerning this patch. I forgot that
I had to use a frequency shift in av7110.c to achieve a good reception.
If I set this shift to 0 and use the new value of initial_demod_freq I
get a lock again on QAM256-channels with reception as good as before.
As this freq shift also improved reception on QAM64-channels I'm at the
moment using 6718 for QAM256 and QAM64 with resulting BERs in the same
range as with unpatched stv0297.ko and a frequency shift of -25.
Maybe this also sheds some light on the discussion about shifting
frequencies on vdr-portal.de

Oliver Endriss schrieb:
 Hi,
 
 Oliver Endriss [EMAIL PROTECTED] wrote:
 e9hack wrote:
 I did eavesdrop the i2c-bus on the TT-C2300 on windows. The
 initialization of the stv0297 is a little bit different. If I
 change the value for the initial demodulation frequency, the ber
 value is reduced to a fourths.
 @all:
 please test with QAM256 channels and report any problems.

 If nobody objects I'll commit this patch.
 
 Apparently we cannot use 6718 for all cards.
 So the patch must be modified...
 
 @TT/Hauppauge DVB-C 2300 users:
 Are there any problems with this patch?
 
 CU
 Oliver
 


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Initial DVB-H tuning files for Finland (dvb-h/fi-*)

2007-10-28 Thread Antti Palosaari

moro,
Files attached. Is there anything else we should put DVB-H tuning files? 
Scan does not handle DVB-H files yet, although those can be used when 
changing first letter H to T in tuning file.


I put also Nokia Oulu development network to own file because it is not 
public as others. I wonder if it is wise at all to add development 
networks (network configuration can change and file is not up to date) 
to dvb-apps. Maybe it helps Nokia engineers ;)


Regards
Antti Palosaari
--
  |||
 (0-0)
-oOO--(_)--OOo-
 http://palosaari.fi/
-Kahta asiaa en ymmärrä.. C-kielen syntaksi ja naisten logiikka..

# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
H 58600 8MHz 1/2 NONE QAM16 8k 1/8 NONE

# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
H 49800 8MHz 1/2 NONE QAM16 8k 1/8 NONE

# Nokia Oulu delelopment network
# Network Name 'Nokia Oulu'
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
H 69000 8MHz 1/2 NONE QPSK 8k 1/8 NONE

# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
H 49800 8MHz 1/2 NONE QAM16 8k 1/8 NONE

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread garlicdevel
 You can change the GPIO1 initialisation to 0x02 instead of 0x82. 
 this will switch the led to green when the frontend gets open()'ed.
 To switch it back to orange insert
  stb0899_write_reg(state, STB0899_GPIO01CFG, 0x82);
 in the stb0899_sleep() function.
 (this should be somehow limited to the pctv452e as the GPIOs might 
 have different meanings on other devices)
 
 Dominik

I've recently updated perl script to get the correct reg names
and uploaded a typical output from the script for tuning to BBC1 as output.log
this shows the order in which the registers are being set typically under the 
win environment to give us some more clues

I just spotted the above in the log for GPIO01CFG
and tried this out in the driver and it now works :) I had the values the wrong 
way round for orange / green
which is a relief (I was worried there might have been a bigger problem 
somewhere with setting the registers)
I've now set the light to come on during tuning / device access (this is 
usually the same time when there is power for the LNB)

updated the patch for stb0899_reg.h with a couple more minor changes (probably 
makes no difference)
based on the output of the win driver / the order the registers are set in
pulled off a newer release of stb0899 as the Unlocking error seemed to be a bit 
random
but this check has been removed recently I think

for szap the one I've been using is located here
http://abraham.manu.googlepages.com/szap.c
this is the latest one mentioned by manu
I've put up a small tar.bz2 file containing a script and the needed files to 
compile, just to make this easier for anyone who wants to try this


at the moment I'm slowly working my way through the registers and manu's code
to try and work out how everything fits together
I think I've got diseqc figured out now at least from looking at the log
pulled the diseqc specs from here http://www.eutelsat.com/satellites/4_5_5.html
The win driver appears to probe for any diseqc devices attached to the Bus 
using E2 00 00
the 00 specifies all devices on the bus and the E2 requires a response from any 
slaves attached looking at the specs

when nothing is found, the LNB power is switched on then the following command 
is issued E0 10 38 f0
I think this means set the switcher to the first position based on szap / specs
this looks like it's always the same which makes me think the win driver is 
ignoring the diseqc setting at the moment and always
selecting the first switch option

Also I think that when we init the FIFO register at the beginning this doesn't 
output onto the bus
as it looks as if the precharge bit has to be set within DISCNTRL1 before 
anything is output
It also looks as if the win driver writes values in a slightly different way
I think with the current linux code we enable precharge set one byte then 
disable precharge to send one at a time
with the win driver it looks as if it's possible to send more than one byte at 
a time into FIFO
set precharge, send in all the bytes to FIFO, unset precharge
DISSTATUS then counts down to zero, I think using the first 4 bits (could be 
wrong on this)
the 5th bit is set to on when data is still being sent (0x13, 0x12, 0x11) then 
the 6th bit is set as well when the fifo is
marked as clear (0x30)

still if it isn't broke don't fix it, if it works as is at the moment in the 
linux driver then this is good enough for me :)
I haven't got a switch in place but I do have a motor
I'll need to experiment with different commands later on to see if I can get 
the thing to move and twirl around using vdr

--Richard

-
Email sent from www.virginmedia.com/email
Virus-checked using McAfee(R) Software and scanned for spam


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread Daniel Golle
On Sun, 28 Oct 2007 10:54:32 +0100, [EMAIL PROTECTED] wrote:
 Are you sure you have used the DVB-S2 enabled szap?
 Manu posted a link a few days/weeks ago
 Currently only the new tuning API does work. 
Thanks! 
That was the missing piece of the puzzle! By using szap2 I can tune in
and receive all DVB-S channels FTA on 19.2E, 
cat dvr0 | mplayer 
works almost perfectly; got some glitches from time to time, but that
was just the same with the ttpci (with budget patch) I used before.

-Daniel


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread garlicdevel

 
 From: Daniel Golle [EMAIL PROTECTED]
 Date: 2007/10/28 Sun PM 03:14:15 GMT
 To: linux-dvb@linuxtv.org
 Subject: Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)
 
 On Sun, 28 Oct 2007 10:54:32 +0100, [EMAIL PROTECTED] wrote:
  Are you sure you have used the DVB-S2 enabled szap?
  Manu posted a link a few days/weeks ago
  Currently only the new tuning API does work. 
 Thanks! 
 That was the missing piece of the puzzle! By using szap2 I can tune in
 and receive all DVB-S channels FTA on 19.2E, 
 cat dvr0 | mplayer 
 works almost perfectly; got some glitches from time to time, but that
 was just the same with the ttpci (with budget patch) I used before.
 
 -Daniel

wow you've managed to get this working?
can you list which driver your using, and which version of stb0899
I'm still trying to get video output from mine


-
Email sent from www.virginmedia.com/email
Virus-checked using McAfee(R) Software and scanned for spam


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] [v4l-dvb-maintainer] FWD: [Patch] saa7146/budget*/dvb-ttpci: Remove V4L1 dependencies

2007-10-28 Thread Mauro Carvalho Chehab
Hi Oliver and Marco,

The patch looked good to me. 

Some comments:

IMO, instead of creating an emum for vidmode, I would instead just store
v4l2_std_id there.

 if (std-id  V4L2_STD_PAL) {
 -   av7110-vidmode = VIDEO_MODE_PAL;
 +   av7110-vidmode = AV7110_VIDEO_MODE_PAL;
 av7110_set_vidmode(av7110, av7110-vidmode);
 }
 else if (std-id  V4L2_STD_NTSC) {
 -   av7110-vidmode = VIDEO_MODE_NTSC;
 +   av7110-vidmode = AV7110_VIDEO_MODE_NTSC;
 av7110_set_vidmode(av7110, av7110-vidmode);
 }

I dunno if av7110 does support PAL/60, PAL/M or PAL/N. I did a quick
look on a datasheet I found at the net for
av7110(http://www.cdaniel.de/download/AV711x_3_1.pdfs). It seems that
the only supported PAL ones are PAL/BDGHI. If this is true, the above
code is perfect.

However, if the driver supports other PAL standards, the above code
won't work, since a few PAL standards are not marked as V4L2_STD PAL
[1]. If this the case, the above code is not correct. 

[1] On V4L2, V4L2_STD_PAL means only PAL/BGDKHI. IMHO, this is one of
the weird things at V4L2 API.

To support also PAL/60, and PAL/MN, a better coding would be:

if (std-id  V4L2_STD_SECAM) {
printk(KERN_ERR Secam is not supported\n);
else if (std-id  V4L2_STD_NTSC) {
av7110-vidmode = AV7110_VIDEO_MODE_NTSC;
av7110_set_vidmode(av7110, av7110-vidmode);
} else {
av7110-vidmode = AV7110_VIDEO_MODE_PAL;
av7110_set_vidmode(av7110, av7110-vidmode);
}

Or to use V4L2_STD_525_60 (for 60 Hz standards) and V4L2_STD_625_50 (for
50 Hz standards).
 
Also, please review the patch with scripts/checkpatch.pl.

Cheers,
Mauro


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] result of running w_scan from Abingdon, Oxfordshire UK

2007-10-28 Thread Paul Gibbons
The attached is the output of running w_scan -x. I found that the file
in /usr/share/dvb/scan/dvb-t/uk-Oxford  was incomplete.


-- 
 
# ##### 
 ##  /######
/#   /  /  #####
   //  /###   ##
   /  /  ##   ##
  ## ##  ##  /###   ##    ##
  ## ##  ## / ###  / #####  / ## [EMAIL PROTECTED]
/### ##  / /   ###/  ## ###/  ## mobile: 07972184336
   / ### ## / ####   ##  ##   ##
  ## ##/  ####   ##  ##   ##
  ## ##   ####   ##  ##   ##
  ## ##   ####   ##  ##   ##
  ## ##   ##/#   ##  /#   ##
  ## ##/ ##   ##/ ##  ### / 
 ##   ## ## ###   ##   #   ##  ##/  
###   #  /  
 ###/   
  #/
### 

Linux paul-gentoo 2.6.22-gentoo-r5 
x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD
GNU/Linux


uk-Oxford
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Deinterlacing UK DVB-T

2007-10-28 Thread Mario Rossi
  I see similar things (on dvb-t) on eg five life and five us,  e
  specially movies on five us. I assume that the transmission might be  in 540 
  horisontal pixels.

  Which channels do you see this on?

I've just uploaded an example where it is easy to see it:

http://xoomer.alice.it/enodetti/log/lines.avi

It is the beginning of Star Wars from ITV1 (5MB)
Look at the text scrolling up and you'll see the lines easily.

Cheers


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] linux-dvb Digest, Vol 33, Issue 103

2007-10-28 Thread Daniel Golle
On Sun, 28 Oct 2007 17:24:55 +, [EMAIL PROTECTED] wrote:
  Thanks! 
  That was the missing piece of the puzzle! By using szap2 I can tune
 in
  and receive all DVB-S channels FTA on 19.2E, 
  cat dvr0 | mplayer 
  works almost perfectly; got some glitches from time to time, but
 that
  was just the same with the ttpci (with budget patch) I used before.
  
  -Daniel
 
 wow you've managed to get this working?
 can you list which driver your using, and which version of stb0899
 I'm still trying to get video output from mine 
I use:
- Linux 2.6.22-ck1 on VIA Esther processor 1200MHz
- stb0899 from http://linuxtv.org/hg/~manu/stb0899/ (last change on
10-10-2007)
- enable_pctv452e_20071021.patch posted by Dominik Kuhlen
- I changed the initial value of register STB0899_I2CRPT to 0x58 as
suggested by Dominik some hours after publishing the patch.
- szap2 from http://dev.kewl.org/hvr4000/utils/szap2.tgz finally did the
trick... (again, big thanks to Dominik for this hint!)

szap2 -r -c /home/daniel/channels.conf -i
tunes successfully to every DVB-S (but not -S2!) channel I ask it for.
I can play the stream in /dev/dvb/adapter0/dvr0 with mplayer (actually,
I do this on my router machine, the box the pinnacle is connected to:
cat /dev/dvb/adapter0/dvr0 | nc -l -p 12345
and this on my workstation:
nc 192.168.XXX.XXX 12345 | mplayer -stop-xscreensaver -v -vo xv -vf
tfields -
).

got to restart netcat and mplayer everytime I tune to a different
channel. I guess, this is more a problem with mplayer not expecting the
TS to end/die unexpectedly...

Also, I tried to compile szap2 using the headers included in manu's
stb0899 code instead of the ones included in szap2, which did NOT work
(tuner doesn't lock to channel).

Anyway, just to mention, the LED seems to stay yellow at all times after
plugging the device, but i don't care as i cannot see it anyway ;)

btw: as dvbscan doesn't work yet with the new tuner api, I need an
up-to-date channels.conf for 19.2E. somebody, please run dvbscan 
and send me the result by email.

-Daniel


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread Daniel Golle
sorry, posted with a wrong subject before... (shame on me)
On Sun, 28 Oct 2007 17:24:55 +, [EMAIL PROTECTED] wrote:
  Thanks! 
  That was the missing piece of the puzzle! By using szap2 I can tune
 in
  and receive all DVB-S channels FTA on 19.2E, 
  cat dvr0 | mplayer 
  works almost perfectly; got some glitches from time to time, but
 that
  was just the same with the ttpci (with budget patch) I used before.
  
  -Daniel
 
 wow you've managed to get this working?
 can you list which driver your using, and which version of stb0899
 I'm still trying to get video output from mine 
I use:
- Linux 2.6.22-ck1 on VIA Esther processor 1200MHz
- stb0899 from http://linuxtv.org/hg/~manu/stb0899/ (last change on
10-10-2007)
- enable_pctv452e_20071021.patch posted by Dominik Kuhlen
- I changed the initial value of register STB0899_I2CRPT to 0x58 as
suggested by Dominik some hours after publishing the patch.
- szap2 from http://dev.kewl.org/hvr4000/utils/szap2.tgz finally did the
trick... (again, big thanks to Dominik for this hint!)

szap2 -r -c /home/daniel/channels.conf -i
tunes successfully to every DVB-S (but not -S2!) channel I ask it for.
I can play the stream in /dev/dvb/adapter0/dvr0 with mplayer (actually,
I do this on my router machine, the box the pinnacle is connected to:
cat /dev/dvb/adapter0/dvr0 | nc -l -p 12345
and this on my workstation:
nc 192.168.XXX.XXX 12345 | mplayer -stop-xscreensaver -v -vo xv -vf
tfields -
).

got to restart netcat and mplayer everytime I tune to a different
channel. I guess, this is more a problem with mplayer not expecting the
TS to end/die unexpectedly...

Also, I tried to compile szap2 using the headers included in manu's
stb0899 code instead of the ones included in szap2, which did NOT work
(tuner doesn't lock to channel).

Anyway, just to mention, the LED seems to stay yellow at all times after
plugging the device, but i don't care as i cannot see it anyway ;)

btw: as dvbscan doesn't work yet with the new tuner api, I need an
up-to-date channels.conf for 19.2E. somebody, please run dvbscan 
and send me the result by email.

-Daniel


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)

2007-10-28 Thread garlicdevel

 
 From: Daniel Golle [EMAIL PROTECTED]
 Date: 2007/10/28 Sun PM 09:36:53 GMT
 To: linux-dvb@linuxtv.org
 Subject: Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (PCTV452e)
 
 sorry, posted with a wrong subject before... (shame on me)
 On Sun, 28 Oct 2007 17:24:55 +, [EMAIL PROTECTED] wrote:
   Thanks! 
   That was the missing piece of the puzzle! By using szap2 I can tune
  in
   and receive all DVB-S channels FTA on 19.2E, 
   cat dvr0 | mplayer 
   works almost perfectly; got some glitches from time to time, but
  that
   was just the same with the ttpci (with budget patch) I used before.
   
   -Daniel
  
  wow you've managed to get this working?
  can you list which driver your using, and which version of stb0899
  I'm still trying to get video output from mine 
 I use:
 - Linux 2.6.22-ck1 on VIA Esther processor 1200MHz
 - stb0899 from http://linuxtv.org/hg/~manu/stb0899/ (last change on
 10-10-2007)
 - enable_pctv452e_20071021.patch posted by Dominik Kuhlen
 - I changed the initial value of register STB0899_I2CRPT to 0x58 as
 suggested by Dominik some hours after publishing the patch.
 - szap2 from http://dev.kewl.org/hvr4000/utils/szap2.tgz finally did the
 trick... (again, big thanks to Dominik for this hint!)
 
 szap2 -r -c /home/daniel/channels.conf -i
 tunes successfully to every DVB-S (but not -S2!) channel I ask it for.
 I can play the stream in /dev/dvb/adapter0/dvr0 with mplayer (actually,
 I do this on my router machine, the box the pinnacle is connected to:
 cat /dev/dvb/adapter0/dvr0 | nc -l -p 12345
 and this on my workstation:
 nc 192.168.XXX.XXX 12345 | mplayer -stop-xscreensaver -v -vo xv -vf
 tfields -
 ).
 
 got to restart netcat and mplayer everytime I tune to a different
 channel. I guess, this is more a problem with mplayer not expecting the
 TS to end/die unexpectedly...
 
 Also, I tried to compile szap2 using the headers included in manu's
 stb0899 code instead of the ones included in szap2, which did NOT work
 (tuner doesn't lock to channel).
 
 Anyway, just to mention, the LED seems to stay yellow at all times after
 plugging the device, but i don't care as i cannot see it anyway ;)
 
 btw: as dvbscan doesn't work yet with the new tuner api, I need an
 up-to-date channels.conf for 19.2E. somebody, please run dvbscan 
 and send me the result by email.
 
 -Daniel

thanks for the info this could save me a lot of time
I've tried the above out but I'm still getting no output from dvr0

at this point I'm not sure if it's because I'm using an amd64 system (perhaps 
non friendly 64bit code somewhere) or if the channel I'm trying to tune to is 
wrong in channels.conf

can you let me know the channel details you've used to tune on Astra 19.2E (the 
line used in channels.conf)
this way I can re-align the dish motor using an external decoder box then give 
it another go

-
Email sent from www.virginmedia.com/email
Virus-checked using McAfee(R) Software and scanned for spam


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] DViCO Dual Digital 4 and remote

2007-10-28 Thread Bonne Eggleston
On Fri, 21 Sep 2007, Michael Krufky wrote:
 Bonne Eggleston wrote:
  Hi All,
  I just got this device and was able to get the tv section working really
  quickly thanks to all your fine efforts.
  I'd like to get the remote working, so if there is anything I can do to
  help out I'd be glad to. I'm a fairly proficient programmer so any
  pointers to get me started would be a great help.

 I'll post a new test patch for the remote within the next few weeks -- I
 know how it works now, but don't have a lot of time...

Any luck with that patch? I'm keen to help out if there's anything I can do. 

Bonne


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[linux-dvb] Support for AverMedia Super 007 DVB-T card

2007-10-28 Thread Andrew McRae
Greetings,
I have a AverMedia Super 007 DVB-T Card (because my supplier
was out of stock of the card I requested and swapped in this card
instead). I'm running Fedora 6 with MythTV, and I found the
patch to enable this card, did the kernel rebuild etc., but
there are a couple of problems:

 - The remote is flagged as TODO. I don't mind doing
   something in order to make it work, if someone could provide
   a bit of a hint how to go about this (if anyone knows).

 - It appears to scan channels and find them, but I haven't
   managed to get any video out of it yet. If anyone has
   this working under MythTV (especially with Fedora 6), let
   me know.

Cheers,
Andrew McRae.



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] [v4l-dvb-maintainer] FWD: [Patch] saa7146/budget*/dvb-ttpci: Remove V4L1 dependencies

2007-10-28 Thread Oliver Endriss
Mauro Carvalho Chehab wrote:
 Hi Oliver and Marco,
 
 The patch looked good to me. 
 
 Some comments:
 
 IMO, instead of creating an emum for vidmode, I would instead just store
 v4l2_std_id there.
 
  if (std-id  V4L2_STD_PAL) {
  -   av7110-vidmode = VIDEO_MODE_PAL;
  +   av7110-vidmode = AV7110_VIDEO_MODE_PAL;
  av7110_set_vidmode(av7110, av7110-vidmode);
  }
  else if (std-id  V4L2_STD_NTSC) {
  -   av7110-vidmode = VIDEO_MODE_NTSC;
  +   av7110-vidmode = AV7110_VIDEO_MODE_NTSC;
  av7110_set_vidmode(av7110, av7110-vidmode);
  }

Basically the enum is not required.
Everything works fine without replacing VIDEO_MODE_xxx by 
AV7110_VIDEO_MODE_xxx. (VIDEO_MODE_xxx is defined in videodev.h.)

On the other hand, I like the enum because it defines the interface
between firmware and driver in a clean way. video_tuner-mode defines
should not be used here because anything except VIDEO_MODE_PAL or
VIDEO_MODE_NTSC are not valid for the firmware. In the future the enum
might be extended to display NTSC content on a PAL TV...

 I dunno if av7110 does support PAL/60, PAL/M or PAL/N. I did a quick
 look on a datasheet I found at the net for
 av7110(http://www.cdaniel.de/download/AV711x_3_1.pdfs). It seems that
 the only supported PAL ones are PAL/BDGHI. If this is true, the above
 code is perfect.

It's ok. Currently we don't support those PAL standards in the firmware.

 However, if the driver supports other PAL standards, the above code
 won't work, since a few PAL standards are not marked as V4L2_STD PAL
 [1]. If this the case, the above code is not correct. 
 
 [1] On V4L2, V4L2_STD_PAL means only PAL/BGDKHI. IMHO, this is one of
 the weird things at V4L2 API.
 
 To support also PAL/60, and PAL/MN, a better coding would be:
 
 if (std-id  V4L2_STD_SECAM) {
   printk(KERN_ERR Secam is not supported\n);
 else if (std-id  V4L2_STD_NTSC) {
   av7110-vidmode = AV7110_VIDEO_MODE_NTSC;
   av7110_set_vidmode(av7110, av7110-vidmode);
 } else {
   av7110-vidmode = AV7110_VIDEO_MODE_PAL;
   av7110_set_vidmode(av7110, av7110-vidmode);
 }
 
 Or to use V4L2_STD_525_60 (for 60 Hz standards) and V4L2_STD_625_50 (for
 50 Hz standards).
  
 Also, please review the patch with scripts/checkpatch.pl.

Will do so.

CU
Oliver

-- 

VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb