Menu
▾
▴
pvrusb-user — Mailing list for Linux USB PVR driver
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(14) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(23) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2005 |
Jan
(1) |
Feb
(2) |
Mar
(8) |
Apr
(2) |
May
(12) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bret C. W. <bw...@al...> - 2006-01-18 08:16:22
|
I am using my pvrusb2 with Kubuntu Breezy on a Thinkpad T42. I'm using ATI= 's=20 8.20 accelerated driver, and mplayer for display. I can watch TV just fine. I haven't figured out how to get the remote working. I have looked over ma= ny=20 howto's, etc. Nothing quite seems to follow my experience all the way=20 through. (K)ubuntu has an inexplicable requirement to compile the lirc=20 modules by hand (I could have stayed with Gentoo if I wanted to complie=20 packages - and might return yet). But when I follow the instructions, I=20 don't get .ko files, I only get .o files. I ran make directly in the lirc-modules-source tree and got .ko files then,= =20 which I copied into place under /lib/modules/... and ran depmod -ae &&=20 update-modules. Now I can load lirc_dev and lirc_i2c. dmesg provides this: [4294798.364000] lirc_dev: no version for "struct_module" found: kernel=20 tainted [4294798.368000] lirc_dev: IR Remote Control driver registered, at major 61 [4294798.389000] bttv: driver version 0.9.15 loaded [4294798.389000] bttv: using 8 buffers with 2080k (520 pages) each for capt= ure [4294798.426000] lirc_i2c: chip found @ 0x18 (Hauppauge IR) [4294798.426000] pvrusb2 i2c_attach [client=3DHauppauge IR @ 0x18 id=3D0xf3] [4294798.429000] lirc_dev: lirc_register_plugin:sample_rate: 10 irw gives nothing. Am I supposed to point the remote at the pvrusb2 or at my laptop's IrDA por= t? =20 Neither works. Can anyone suggest what to do? Up until now I have been poking the 5 local= =20 channel frequencies directly into the /sys/class/pvrusb2 registers, and tha= t=20 works fine. Thanks, Bret |
|
From: Bret C. W. <bw...@al...> - 2005-07-08 23:36:38
|
I see there is Linux support for this PVR. I can get one on ebay for a goo= d=20 price. The ones advertised on ebay are all 'Model 941'. I live in New Zealand (or= =20 maybe Australia soon), both of which use PAL TV signals. Can anyone tell m= e=20 if the 941 model works with PAL TV? If not, can anyone tell me which model= I=20 do want for that? Thanks in advance, Bret =2D-=20 Given the degree to which Americans distrust politicians, it boggles the mi= nd=20 that religious leaders would consign themselves to that particular circle o= f=20 hell. =2D Alan Wolfe |
|
From: Mike I. <is...@is...> - 2005-06-01 13:31:25
|
On Tue, 31 May 2005, Joshua Cavanaugh wrote:
> Can I use the same driver for the Wintv USB2 as for the pvr usb2? I was
> trying to follow the directions from the website, but I got stuck trying
> to build the firmware files. There is no hcwusb2.sys from my extracted
> driver file. Any information on the Wintv USB2 would be appreciated.
>
> Thanks,
>
> Josh Cavanaugh
> jo...@ho...
I thought those two names corresponded to the same device - in which case
the answer is yes. But now I'm not so sure. Can you post a link showing
information about the "Wintv USB2"?
-Mike
--
| Mike Isely | PGP fingerprint
Spammers Die!! | | 03 54 43 4D 75 E5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8
| |
|
|
From: Joshua C. <jo...@jo...> - 2005-06-01 07:29:40
|
Can I use the same driver for the Wintv USB2 as for the pvr usb2? I was trying to follow the directions from the website, but I got stuck trying to build the firmware files. There is no hcwusb2.sys from my extracted driver file. Any information on the Wintv USB2 would be appreciated. Thanks, Josh Cavanaugh jo...@ho... |
|
From: Mike I. <is...@is...> - 2005-05-20 20:56:24
|
On Fri, 20 May 2005, Bruno Grieder wrote:
> Mike,
>
> Your latest version (Mai 16) compiled fine on my 2.11.8 kernel.
>
> However, I get a very strange behaviour where the norm seems to be unw=
illing to stick to SECAM - which is what I need.
There is one other person I know who is testing SECAM for me (and
reporting roughly the same level of success as everyone else). That's n=
ot
to say you won't have problems, but hopefully this should give you some
confidence that you aren't blazing a trail here. I can't test SECAM
because I'm in NTSC territory. Read on...
>
> When selecting a channel, I sometimes get the line
> =A0=A0=A0 saa7115: decoder set norm SECAM
> in the syslog. When that happens, things usually go ok and this usuall=
y happens when the reception quality is good(I am using an
> antenna).
OK.
>
> When I do not get this entry in the log and I directly get
> =A0=A0=A0 /*--TRACE_COMMIT--*/ "Tuner Frequency (Hz)" <-- 567250000 (<=
integer>)
This log message happens when the driver realizes that a new frequency
must be tuned.
> =A0=A0=A0 /*---TRACE_CTL----*/ pvr2_tuner_set_freq
This log message is telling you what action it is actually taking. The
function pvr2_tuner_set_freq() is the entry point within the driver wher=
e
it sends the new frequency over to tuner.ko.
Some types of "commits" spawn multiple actions. The idea behind these l=
og
messages is to clearly show what data has changed ("TRACE_COMMIT") and
then what actions are happening as a result ("TRACE_CTL").
> Two things happen:
> -either I get an mpeg timeeout and the only thing left to do for me is=
to unplug and replug the device
> -or I get a highly pixelized flipping image. Forcing the norm to SECAM=
using the xawtv menu will usually fix the issue.
>
OK, you are hitting problems known to exist when xawtv is involved. Jus=
t
in the past few days I've been trying to characterize these things mysel=
f.
1. The mpeg timeouts happen when xawtv asks the driver for data and the
driver doesn't respond within 3 seconds. This one has been hard to
reproduce, unfortunately. Best I can tell right now is that under some
circumstances the driver is just not generating any data.
2. The pixelated data I currently suspect as being a problem in xawtv. =
I
have not been able to find any evidence of corruption in the data stream
at the driver level, and if I use mplayer instead (e.g. "mplayer -vo xv
/dev/video0") it *NEVER* gets corrupted in this manner.
There's also a problem where sometimes xawtv issues a read request to th=
e
driver for zero bytes. In that case the driver has no choice but to rep=
ly
with zero (i.e. ask for zero bytes, get zero bytes). Unfortunately zero
also means EOF, so xawtv responds by closing the stream. The root cause
is the request for zero bytes. There is an exchange going on right now
with the xawtv maintainer to try to figure out this problem. Previous
snapshots of my driver (and possibly Aurelien's driver) responded to thi=
s
situation by returning EAGAIN - which is even worse. When that happens,
xawtv and the driver get into an infinite loop of retries, which also
causes the stream to fail.
> What seeems to happen is that the norm is constantly switching between=
SECAM and something else (looks like being PAL) and does
> not stabilize.
That's very interesting. Do you see any TRACE_COMMIT log messages that
suggest somebody is deliberately changing it? I'm very puzzled by this.
>
> Is there some (too) clever mechanism trying to guess the norm?
The only (deliberate) cleverness going on with the video standard is
*only* when the driver is initialized. At that point, the driver reads
the set of supported standards from the device's eeprom and picks an
initial standard from that list. Be advised however that you might have=
a
multi-standard tuner (the other SECAM tester I know has this issue), and
in that case it might be initializing itself to a PAL variant. However
none of that matters because the app is supposed to set the video
standard, a.k.a. "norm" as part of its initialization. If there's any
additional magic going on, it's happening there.
I can certainly see a scenario where the driver somehow gets set to the
wrong standard, can't tune anything, and thus won't emit any video strea=
m
- which then causes the mpeg timeout. That *might* be what is happening
to you. The driver at least shouldn't be doing anything behind your bac=
k
with respect to the standard, once it has initialized. I can't vouch fo=
r
what xawtv might be doing (but if xawtv is doing anything there should b=
e
TRACE_COMMIT log messages revealing that evidence).
One thing that might help you: Use the sysfs control interface. At any
time you can access / change any control in the driver by accessing the
appropriate file under "/sys/class/pvrusb2/sn-XXXX". You can do this at
*any* time, even while somebody else is using the device. So you could
for example query the current video standard if you suspect it's getting
messed up. Look at my web page for more information on using sysfs.
By the way, there will be a new driver snapshot probably this weekend
which is going to fix a few instability corner cases. I figured out the
solution(s) last night. However the issues you hit above are not relate=
d
to the upcoming fixes, at least not yet.
-Mike
--
| Mike Isely | PGP fingerpr=
int
Spammers Die!! | | 03 54 43 4D 75 E=
5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F=
5 C1 E8
| |
|
|
From: Bruno G. <bgr...@fr...> - 2005-05-20 20:27:16
|
Correction. The kernel version is obviously 2.6.11.8 Bruno Grieder wrote: > Mike, > > Your latest version (Mai 16) compiled fine on my 2.11.8 kernel. > > However, I get a very strange behaviour where the norm seems to be > unwilling to stick to SECAM - which is what I need. > > When selecting a channel, I sometimes get the line > saa7115: decoder set norm SECAM > in the syslog. When that happens, things usually go ok and this > usually happens when the reception quality is good(I am using an antenna). > > When I do not get this entry in the log and I directly get > /*--TRACE_COMMIT--*/ "Tuner Frequency (Hz)" <-- 567250000 (<integer>) > /*---TRACE_CTL----*/ pvr2_tuner_set_freq > Two things happen: > -either I get an mpeg timeeout and the only thing left to do for me is > to unplug and replug the device > -or I get a highly pixelized flipping image. Forcing the norm to SECAM > using the xawtv menu will usually fix the issue. > > What seeems to happen is that the norm is constantly switching between > SECAM and something else (looks like being PAL) and does not stabilize. > > Is there some (too) clever mechanism trying to guess the norm? > > Bruno > > > > Mike Isely wrote: > >>On Tue, 17 May 2005, Bruno Grieder wrote: >> >> >> >>>Hi Mike, >>> >>>Actually it was a tuner issue. The scanner could not find any channels. >>>To be fair, I cannot remember if I tried your driver before or after I upgraded my kernel. >>>As soon as I have some bandwidth, I will do some more testing with your driver. >>> >>> >> >>Bruno: >> >>If you still have log output from your tests with my update of the driver >>(look for "tveeprom" lines), I can tell you if you hit the "type 58" >>problem that was in that driver. Ironically enough, Aurelien's driver >>only works with about 3 tuner types (hardcoded into the driver itself); my >>changes include the ability to work with essentially any tuner type >>supported by v4l. However a problem in v4l's tveeprom.ko caused hauppauge >>tuner type 58 not to function. Possibly you could have encountered that. >> >>The latest snapshot on the web site includes a solution for that problem, >>so I'd love to hear if it works for you and I can then rule out any new >>unknown problem that you might have hit. >> >> -Mike >> >> >> > |
|
From: Bruno G. <bgr...@fr...> - 2005-05-20 20:25:08
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Mike,<br>
<br>
Your latest version (Mai 16) compiled fine on my 2.11.8 kernel.<br>
<br>
However, I get a very strange behaviour where the norm seems to be
unwilling to stick to SECAM - which is what I need.<br>
<br>
When selecting a channel, I sometimes get the line <br>
saa7115: decoder set norm SECAM<br>
in the syslog. When that happens, things usually go ok and this usually
happens when the reception quality is good(I am using an antenna).<br>
<br>
When I do not get this entry in the log and I directly get<br>
/*--TRACE_COMMIT--*/ "Tuner Frequency (Hz)" <-- 567250000
(<integer>)<br>
/*---TRACE_CTL----*/ pvr2_tuner_set_freq<br>
Two things happen:<br>
-either I get an mpeg timeeout and the only thing left to do for me is
to unplug and replug the device<br>
-or I get a highly pixelized flipping image. Forcing the norm to SECAM
using the xawtv menu will usually fix the issue.<br>
<br>
What seeems to happen is that the norm is constantly switching between
SECAM and something else (looks like being PAL) and does not stabilize.<br>
<br>
Is there some (too) clever mechanism trying to guess the norm?<br>
<br>
Bruno<br>
<br>
<br>
<br>
Mike Isely wrote:
<blockquote cite="mid...@cn..."
type="cite">
<pre wrap="">On Tue, 17 May 2005, Bruno Grieder wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Mike,
Actually it was a tuner issue. The scanner could not find any channels.
To be fair, I cannot remember if I tried your driver before or after I upgraded my kernel.
As soon as I have some bandwidth, I will do some more testing with your driver.
</pre>
</blockquote>
<pre wrap=""><!---->
Bruno:
If you still have log output from your tests with my update of the driver
(look for "tveeprom" lines), I can tell you if you hit the "type 58"
problem that was in that driver. Ironically enough, Aurelien's driver
only works with about 3 tuner types (hardcoded into the driver itself); my
changes include the ability to work with essentially any tuner type
supported by v4l. However a problem in v4l's tveeprom.ko caused hauppauge
tuner type 58 not to function. Possibly you could have encountered that.
The latest snapshot on the web site includes a solution for that problem,
so I'd love to hear if it works for you and I can then rule out any new
unknown problem that you might have hit.
-Mike
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: Mike I. <is...@is...> - 2005-05-18 17:58:16
|
The error you are seeing is because Aurelien's driver is not recognizing
the type of tuner you have. This is a limitation in that driver. Try out
my version and you should be able to get past that problem. Note: You
will likely need a kernel later than 2.6.8. My driver relies on
functionality built into video4linux that is not likely to be present in
2.6.8 - I suppose if you patched it up with the latest video4linux changes
you might have a chance. But frankly 2.6.11.something is a more stable
kernel anyway and I suggest you update to it.
-Mike
> > friedhelm serwane wrote:
> >
> >> Hello,
> >> i tried to get my new pvrusb2 working with my suse 9.2 system.
> >>
> >>
> >> pvrusb2-dev-07112004
> >> kernel-default-2.6.8-24.11
> >> in my syslog, there is the line:
> >> unknown tuner 60. Please contact developer
> >>
> >> I get the mpeg-stream on /dev/video but it's snow and i cant change
> >> chanels via xawtv4.
> >>
> >> has anyone an idea?
> >>
--
| Mike Isely | PGP fingerprint
Spammers Die!! | | 03 54 43 4D 75 E5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8
| |
|
|
From: friedhelm s. <fre...@we...> - 2005-05-18 16:47:59
|
hi, thanks for your quick answer. There is already a symlink from /dev/video0 to /dev/video here is some more information from /var/log/messages: May 18 18:41:21 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-main.c: pvr_init May 18 18:41:21 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-main.c: endpoints : 6 May 18 18:41:21 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-remote.c: pvr_input_init May 18 18:41:21 localhost kernel: No class name for input device usb IR (pvrusb2) at usb<7>evdev_connect: evdev cdfe4680 handle cdfe469c name event3 May 18 18:41:21 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-eeprom.c: pvr_analyse_eeprom May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-eeprom.c: audio processor idx : 6 May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-eeprom.c: tuner idx : 60 May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-tuner.c: unknow tuner 60. Please contact developper. May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-eeprom.c: radio present : 1 May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-remote.c: pvr_input_start May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-stream.c: pvr_stream_alloc May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-stream.c: registered video device with minor 0 May 18 18:41:22 localhost kernel: usbcore: registered new driver pvrusb2 May 18 18:41:22 localhost kernel: /root/pvrusb2-dev-07112004/pvrusb2-main.c: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : 0.6(08/09/2004) does this help? thanks friedhelm NABAWI Jad wrote: > perhaps you have to make a link > ln -s /dev/video0 /dev/video > because xawtv4 look at /dev/video0 > > > > friedhelm serwane wrote: > >> Hello, >> i tried to get my new pvrusb2 working with my suse 9.2 system. >> >> >> pvrusb2-dev-07112004 >> kernel-default-2.6.8-24.11 >> in my syslog, there is the line: >> unknown tuner 60. Please contact developer >> >> I get the mpeg-stream on /dev/video but it's snow and i cant change >> chanels via xawtv4. >> >> has anyone an idea? >> >> PS:Could you cc to me since i am not on the mailing list. >> >> Thanks >> >> Friedhelm >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by Oracle Space Sweepstakes >> Want to be the first software developer in space? >> Enter now for the Oracle Space Sweepstakes! >> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >> _______________________________________________ >> Pvrusb-user mailing list >> Pvr...@li... >> https://lists.sourceforge.net/lists/listinfo/pvrusb-user >> > > > |
|
From: Mike I. <is...@is...> - 2005-05-17 20:57:33
|
On Tue, 17 May 2005, Bruno Grieder wrote:
> Hi Mike,
>
> Actually it was a tuner issue. The scanner could not find any channels.
> To be fair, I cannot remember if I tried your driver before or after I upgraded my kernel.
> As soon as I have some bandwidth, I will do some more testing with your driver.
Bruno:
If you still have log output from your tests with my update of the driver
(look for "tveeprom" lines), I can tell you if you hit the "type 58"
problem that was in that driver. Ironically enough, Aurelien's driver
only works with about 3 tuner types (hardcoded into the driver itself); my
changes include the ability to work with essentially any tuner type
supported by v4l. However a problem in v4l's tveeprom.ko caused hauppauge
tuner type 58 not to function. Possibly you could have encountered that.
The latest snapshot on the web site includes a solution for that problem,
so I'd love to hear if it works for you and I can then rule out any new
unknown problem that you might have hit.
-Mike
--
| Mike Isely | PGP fingerprint
Spammers Die!! | | 03 54 43 4D 75 E5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8
| |
|
|
From: Bruno G. <bgr...@fr...> - 2005-05-17 19:54:09
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Mike,<br>
<br>
Actually it was a tuner issue. The scanner could not find any channels.<br>
To be fair, I cannot remember if I tried your driver before or after I
upgraded my kernel.<br>
As soon as I have some bandwidth, I will do some more testing with your
driver.<br>
<br>
Cheers<br>
<br>
Mike Isely wrote:
<blockquote cite="mid...@cn..."
type="cite">
<pre wrap="">This morning I came across Bruno Grieder's post about pvrusb2. One
paragraph in particular is:
</pre>
<blockquote type="cite">
<pre wrap="">The pvrusb2 drive I use is that of Aurélien Allleaume
pvrusb2-dev-07112004.tar.bz2
<a class="moz-txt-link-rfc2396E" href="http://justiceforall.free.fr/pvrusb2-dev-07112004.tar.bz2"><http://justiceforall.free.fr/pvrusb2-dev-07112004.tar.bz2></a>
Mike Isely (<a class="moz-txt-link-freetext" href="http://www.isely.net/pvrusb2.html">http://www.isely.net/pvrusb2.html</a>) picked up hiw work and
made a more recent version but it never worked for me.
</pre>
</blockquote>
<pre wrap=""><!---->
I am in the middle of a large restructuring of the pvrusb2 driver, but I'd
certainly hope that it continues to work as well as it has in earlier
versions. I'd therefore like very much to know the nature of the problem
here so that I can correct it in newer snapshots of the driver. Bruno:
I can't contact you directly since the mailing list archive does not show
full e-mail addresses. So please contact me. Use the e-mail address
showing at <a class="moz-txt-link-freetext" href="http://www.isely.net/pvrusb2.html">http://www.isely.net/pvrusb2.html</a> (top of the page). Or send
to my sourceforge username "mcisely" and I should see the message.
For others here - The Hauppauge "PVR USB2" device is a different animal
than the device that this sourceforge project is aimed at. So I imagine
this isn't the appropriate place to eat bandwidth discussing it. If there
is enough demand, I can set up an alternate list elsewhere. In any case,
if anyone has questions - don't hesitate to contact me via the address on
my web page. The more feedback I get, the better I can make this driver
and its associated documentation.
-Mike
p.s.
There was also an earlier post here about lack of audio with this driver
(subject = "msp34x5g.c: pvr_audio_setvolume: mute=on v=0x00 b=0x00").
Cat'ing /dev/video0 to a file normally will work perfectly well. The
problem is that the driver might have the audio muted. My snapshot of the
driver starts off with the audio UNmuted so that normally isn't an issue.
HOWEVER, xawtv will mute the audio upon exit, so if you run xawtv first
then you won't have any audio when you then try to capture the stream. I
imagine there's probably a way with v4lctl to correct it manually.
Alternatively, my more recent driver snapshots also include a sysfs
interface, which you can manipulate at the shell to query / set any
control in the driver (including of course mute).
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: Mike I. <is...@is...> - 2005-05-17 13:47:43
|
That driver doesn't handle different tuner types very well. Try this one instead: http://www.isely.net/pvrusb2.html -Mike On Tue, 17 May 2005, friedhelm serwane wrote: > Hello, > i tried to get my new pvrusb2 working with my suse 9.2 system. > > > pvrusb2-dev-07112004 > kernel-default-2.6.8-24.11 > in my syslog, there is the line: > unknown tuner 60. Please contact developer > > I get the mpeg-stream on /dev/video but it's snow and i cant change > chanels via xawtv4. > > has anyone an idea? > > PS:Could you cc to me since i am not on the mailing list. > > Thanks > > Friedhelm > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Pvrusb-user mailing list > Pvr...@li... > https://lists.sourceforge.net/lists/listinfo/pvrusb-user > > -- | Mike Isely | PGP fingerprint Spammers Die!! | | 03 54 43 4D 75 E5 CC 92 | isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8 | | |
|
From: friedhelm s. <fre...@we...> - 2005-05-17 12:17:31
|
Hello, i tried to get my new pvrusb2 working with my suse 9.2 system. pvrusb2-dev-07112004 kernel-default-2.6.8-24.11 in my syslog, there is the line: unknown tuner 60. Please contact developer I get the mpeg-stream on /dev/video but it's snow and i cant change chanels via xawtv4. has anyone an idea? PS:Could you cc to me since i am not on the mailing list. Thanks Friedhelm |
|
From: Mike I. <is...@is...> - 2005-05-15 00:23:22
|
This morning I came across Bruno Grieder's post about pvrusb2. One paragraph in particular is: > The pvrusb2 drive I use is that of Aur=E9lien Allleaume > pvrusb2-dev-07112004.tar.bz2 > <http://justiceforall.free.fr/pvrusb2-dev-07112004.tar.bz2> > Mike Isely (http://www.isely.net/pvrusb2.html) picked up hiw work and > made a more recent version but it never worked for me. I am in the middle of a large restructuring of the pvrusb2 driver, but I= 'd certainly hope that it continues to work as well as it has in earlier versions. I'd therefore like very much to know the nature of the proble= m here so that I can correct it in newer snapshots of the driver. Bruno: I can't contact you directly since the mailing list archive does not sho= w full e-mail addresses. So please contact me. Use the e-mail address showing at http://www.isely.net/pvrusb2.html (top of the page). Or send to my sourceforge username "mcisely" and I should see the message. For others here - The Hauppauge "PVR USB2" device is a different animal than the device that this sourceforge project is aimed at. So I imagine this isn't the appropriate place to eat bandwidth discussing it. If the= re is enough demand, I can set up an alternate list elsewhere. In any case= , if anyone has questions - don't hesitate to contact me via the address o= n my web page. The more feedback I get, the better I can make this driver and its associated documentation. -Mike p.s. There was also an earlier post here about lack of audio with this driver (subject =3D "msp34x5g.c: pvr_audio_setvolume: mute=3Don v=3D0x00 b=3D0x= 00"). Cat'ing /dev/video0 to a file normally will work perfectly well. The problem is that the driver might have the audio muted. My snapshot of t= he driver starts off with the audio UNmuted so that normally isn't an issue= . HOWEVER, xawtv will mute the audio upon exit, so if you run xawtv first then you won't have any audio when you then try to capture the stream. = I imagine there's probably a way with v4lctl to correct it manually. Alternatively, my more recent driver snapshots also include a sysfs interface, which you can manipulate at the shell to query / set any control in the driver (including of course mute). -- | Mike Isely | PGP fingerpr= int Spammers Die!! | | 03 54 43 4D 75 E= 5 CC 92 | isely @ pobox (dot) com | 71 16 01 E2 B5 F= 5 C1 E8 | | |
|
From: Bruno G. <bgr...@fr...> - 2005-05-10 06:47:17
|
Hi, It took me a while so I figured I would share my experience. I started with a Mandrake 10.1. The first thing was to make a kernel upgrade to 2.6.11.8 (I believe=20 anything below a 2.6.10 is unlikely to work well with the latest v4l=20 drivers). Then I got the latest xawtv-4 cvs snapshot (I never got it to work with=20 the 3.94 version supplied) which I built and compiled. (make sure to=20 urpme all xawtv packages instaled by your distro first) I also go the latest v4l driver (from the same site) which I built and=20 install to replace the ones supplied by the Kernel. Watch out, the=20 modules are installed in a different directory that those supplied by=20 the kernel. The smart way is probably to build the kernel without v4l=20 support, then install these (or even better, patch the kerenel sources=20 upfront). I used the dangerous quick way: change the directory name of=20 the new install to _v4l so the modues would be picked up by depmod=20 before those of the kernel. I did not have to patch the kernel sources=20 to get xawtv4 built - only install the modules. Other users report=20 having all this work with the "old" driver. The pvrusb2 drive I use is that of Aur=E9lien Allleaume=20 pvrusb2-dev-07112004.tar.bz2=20 <http://justiceforall.free.fr/pvrusb2-dev-07112004.tar.bz2> Mike Isely (http://www.isely.net/pvrusb2.html) picked up hiw work and=20 made a more recent version but it never worked for me. The driver loaded nicely into the kernel after installing it following=20 the instructions provided by Aur=E9lien. Then scantv provided by xawtv4 then found some channels (e.g. the tuner=20 works) To get xawtv running properly, the last thing required was to remove the=20 loading of the DRI module in Xorg. Unplugging the device causes the usb driver to crash and a kernel dump.=20 The pvrusb2 driver should be unloaded first. Happy xawtving Bruno Grieder |
|
From: Bruno G. <bgr...@fr...> - 2005-05-10 05:11:34
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi,<br> <br> It took me a while so I figured I would share my experience.<br> <br> I started with a Mandrake 10.1.<br> The first thing was to make a kernel upgrade to 2.6.11.8 (I believe anything below a 2.6.10 is unlikely to work well with the latest v4l drivers).<br> <br> Then I got the latest xawtv-4 cvs snapshot (I never got it to work with the 3.94 version supplied) which I built and compiled. (make sure to urpme all xawtv packages instaled by your distro first)<br> <br> I also go the latest v4l driver (from the same site) which I built and install to replace the ones supplied by the Kernel. Watch out, the modules are installed in a different directory that those supplied by the kernel. The smart way is probably to build the kernel without v4l support, then install these (or even better, patch the kerenel sources upfront). I used the dangerous quick way: change the directory name of the new install to _v4l so the modues would be picked up by depmod before those of the kernel. I did not have to patch the kernel sources to get xawtv4 built - only install the modules.<br> <br> The pvrusb2 drive I use is that of Aurélien Allleaume <a href="http://justiceforall.free.fr/pvrusb2-dev-07112004.tar.bz2">pvrusb2-dev-07112004.tar.bz2</a><br> Mike Isely (<a class="moz-txt-link-freetext" href="http://www.isely.net/pvrusb2.html">http://www.isely.net/pvrusb2.html</a>) picked up hiw work and made a more recent version but it never worked for me.<br> <br> The driver loaded nicely into the kernel after installing it following the instructions provided by Aurélien.<br> <br> Then scantv provided by xawtv4 then found some channels (e.g. the tuner works)<br> <br> To get xawtv running properly, the last thing required was to remove the loading of the DRI module in Xorg.<br> <br> Happy xawtving<br> <br> Bruno Grieder<br> </body> </html> |
|
From: Matthias K. <mat...@t-...> - 2005-04-10 18:50:48
|
With using the pvrusb2-0.6 (first pvrusb2-dev-07112004) Version of=20 http://justiceforall.free.fr/pvrusb2.htm and changing the lines in pvrusb2-tuner.c to #define PVR_NTUNER 1 static struct pvr_tuner pvr_tuners[] =3D { { "Philips PAL/SECAM multi (FM1216ME MK3)", 0 /* PAL-BGDKI SECAM */, 16*160.00, 16*442.00, 0x01, 0x02, 0x04, 0x8e, 623 },=20 }; The format of the pvrusb2-tuner.c are different in this two versions!! I have audio now on my recorded files with cat /dev/video0 > file.mpg Unchanged: 1. No videotext mtt4 starts now with "stderr messages": "vbi: open failed [/dev/video0]" 2. Changing the channel with xawtv4 it seems there is a timeout in the pvrusb2-driver. With this version (0.6) the timeout seems is a little shorter set, so I need more attempts to get the next program. 3. One time I can start mplayer with option "-vo xv" and the cpu needs only 55%. Now I have 48% for mplayer and 35% for X What make I wrong? Starting playback... VDec: vo config request - 720 x 576 (preferred csp: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1,33:1 - prescaling to correct movie aspect. VO: [xv] 720x576 =3D> 768x576 Planar YV12=20 A: 53,5 V: 53,3 A-V: 0,151 ct: -0,359 1311/1311 43% 40% 7,0% 160 0 = =20 ************************************************ **** Your system is too SLOW to play this! **** ************************************************ Thanks for all Infos and tips Matthias Am Donnerstag, 31. M=E4rz 2005 16:57 schrieb Matthias Kindtner: > Hello, >=20 > I'm using the pvrusb2-dev-07112004 from=20 > http://justiceforall.free.fr/pvrusb2.html on > Suse 9.2=20 > kernel-default-2.6.8-24.11 > pwlib-plugins-v4l-1.8.0-3 > v4l-tools-3.94-2 > v4l-conf-3.94-2 > xawtv4-20050121-1.1 >=20 > With xawtv4 I'm able to view TV and have a audio too. > Now I tried to record some film to disk. > xawtv4 I think doesn't support it in the devel state?! > So I take "cat /dev/video0 > film.mpg" but in this mpg-File > there is the audio-signal zero or mute on. >=20 > In the syslog I find the following lines after start xawtv4 : > pvrusb2-msp34x5g.c: pvr_audio_setvolume: mute=3Doff v=3D0x7e b=3D0x00 >=20 > and stop it: >=20 > pvrusb2-msp34x5g.c: pvr_audio_setvolume: mute=3Don v=3D0x00 b=3D0x00 >=20 > When I start with my "cat" command the mute is "on" I think. >=20 > How I can set it manually to off and trottle the volume to a middle > so the recorded file has audio too? >=20 > Thanks fort every help >=20 > Matthias=20 >=20 >=20 |
|
From: Matthias K. <mat...@t-...> - 2005-04-03 15:22:33
|
>hello, >i buy a Hauppauge WinTV-USB2(model 1020), and i install all things for the >pvrusb2 driver but stay don"t have any thing working, i"m under Fedora >core3 (2.6.10-760), that"s 3 week that i have this card and i won"t use it >under windows, if you can help me it will be realy great, thank you a lot >.. >(i"install usbvison too but no way, i modprobe all the modules but i still >don"t have any stream, and when booting or pluging my card it"s known as >a sound card, and automaticaly the module snd-usb is attached to it) >Help I don't know fedora and I'm no expert in Linux or pvrusb2. Read the following links carefully: http://pvrusb2.dax.nu/ http://justiceforall.free.fr/pvrusb2.html http://www.eskimo.com/~roger/programming/ http://sourceforge.net/mailarchive/forum.php?thread_id=6826286&forum_id=36602 For analyses what chips are in your card you can download from hauppauge http://hauppauge.lightpath.net/software/utils/prodinfo.exe I hope this will help you with Good luck Matthias |
|
From: NABAWI J. <na...@en...> - 2005-03-31 15:17:42
|
hello, i buy a Hauppauge WinTV-USB2(model 1020), and i install all things for the pvrusb2 driver but stay don't have any thing working, i'm under Fedora core3 (2.6.10-760), that's 3 week that i have this card and i won't use it under windows, if you can help me it will be realy great, thank you a lot .. (i'install usbvison too but no way, i modprobe all the modules but i still don't have any stream, and when booting or pluging my card it's known as a sound card, and automaticaly the module snd-usb is attached to it) Help (yes i'm not very good in english) :) Jad Nabawi Eleve ingenieur 2ieme annee ENSEIRB. |
|
From: Matthias K. <mat...@t-...> - 2005-03-31 14:57:19
|
Hello, I'm using the pvrusb2-dev-07112004 from http://justiceforall.free.fr/pvrusb2.html on Suse 9.2 kernel-default-2.6.8-24.11 pwlib-plugins-v4l-1.8.0-3 v4l-tools-3.94-2 v4l-conf-3.94-2 xawtv4-20050121-1.1 With xawtv4 I'm able to view TV and have a audio too. Now I tried to record some film to disk. xawtv4 I think doesn't support it in the devel state?! So I take "cat /dev/video0 > film.mpg" but in this mpg-File there is the audio-signal zero or mute on. In the syslog I find the following lines after start xawtv4 : pvrusb2-msp34x5g.c: pvr_audio_setvolume: mute=off v=0x7e b=0x00 and stop it: pvrusb2-msp34x5g.c: pvr_audio_setvolume: mute=on v=0x00 b=0x00 When I start with my "cat" command the mute is "on" I think. How I can set it manually to off and trottle the volume to a middle so the recorded file has audio too? Thanks fort every help Matthias |
|
From: Matthias K. <mat...@t-...> - 2005-03-26 22:03:21
|
Am Freitag, 25. M=E4rz 2005 12:25 schrieb Bjorn Danielsson:
> Matthias Kindtner <mat...@t-...> wrote:
> >=20
> > 1. My CPU (PIII/1100) is between 75% - 100% and the movie have
> > sometimes "little timeout" I feel.
>=20
> Do you get the same CPU load with mplayer?
> I get 55-60% CPU load when watching TV with mplayer on a
> 700 MHz Celeron (my Xbox), with 6 Mbit/s 720x576 video.
> Motion is perfectly smooth except when a lot of disk
> activity happens at the same time.
>=20
A cat /dev/video0 > film.mpg uses only 10-15 % CPU, but a start
of mplayer film.mpg uses 52%, when operating with "top")
Under xawtv4 I have 45% xawtv and 35% for X.
So xawtv4 uses X11 for output or software is scalling?
How can I operate and change this?
Where do you get the information for the video?
If I start mplayer I get the following output, but it was playback.
Under xawtv I don't find information about the video.
It was fullscreen both.
I've set manually rtc max_user_freq=3D1024 but mplayer
isn't lucky.=20
MPlayer 1.0pre6-3.3.4 (C) 2000-2004 MPlayer Team
CPU: Intel Celeron 2/Pentium III Coppermine,Geyserville (Family: 6, Steppin=
g:=20
10)
Detected cache-line size is 32 bytes
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 0
Compiled with runtime CPU detection - WARNING - this is not optimal!
To get best performance, recompile MPlayer with=20
=2D-disable-runtime-cpudetection.
Linux RTC init error in ioctl (rtc_irqp_set 1024): Unpassender IOCTL=20
(I/O-Control) f=FCr das Ger=E4t
Try adding "echo 1024 > /proc/sys/dev/rtc/max-user-freq" to your system=20
startup scripts.
Opening joystick device /dev/input/js0
Can't open joystick device /dev/input/js0 : Kein passendes Ger=E4t gefunden
Can't init input joystick
Setting up LIRC support...
mplayer: could not connect to socket
mplayer: Keine Berechtigung
=46ailed to open LIRC support.
You will not be able to use your remote control.
Playing /sounds/film.mpg.
MPEG-PS file format detected.
VIDEO: MPEG2 720x576 (aspect 2) 25,000 fps 6000,0 kbps (750,0 kbyte/s)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 48000 Hz, 2 ch, 16 bit (0x10), ratio: 28000->192000 (224,0 kbit)
Selected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
vo: X11 running at 1024x768 with depth 16 and 16 bpp (":0.0" =3D> local dis=
play)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough
VDec: vo config request - 720 x 576 (preferred csp: Mpeg PES)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
The selected video_out device is incompatible with this codec.
VDecoder init failed :(
Opening video decoder: [libmpeg2] MPEG 1/2 Video decoder libmpeg2-v0.4.0b
Selected video codec: [mpeg12] vfm:libmpeg2 (MPEG 1 or 2 (libmpeg2))
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Checking audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
AF_pre: af format: 2 bps, 2 ch, 48000 hz, little endian signed int=20
AF_pre: 48000Hz 2ch Signed 16-bit (Little-Endian)
AO: [oss] 48000Hz 2ch Signed 16-bit (Little-Endian) (2 bps)
Building audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/16bit...
Starting playback...
VDec: vo config request - 720 x 576 (preferred csp: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1,33:1 - prescaling to correct movie aspect.
VO: [xv] 720x576 =3D> 768x576 Planar YV12=20
> Make sure that hardware scaling is used, or that the screen
> is in 720x576 mode (720x480 for NTSC). Otherwise software
> scaling is used to produce square pixels. With mplayer on
> a slow CPU, use -vo xv or something equivalent, not -vo x11.
>
I think mplayer don't use X11 (VDec: using Planar YV12 as output csp (no 0)=
),
but the line "Movie-Aspect is 1,33:1 - prescaling to correct movie aspect."
seems as software correction was done?
=20
So mplayer seems to work normal (cpu-%) but where do I get audio?
Why do xawtv4 uses X11 for output and where can I change this?
How do I use videotext, mtt4 also didn't work. (blank-screen)
Thanks=20
Matthias
|
|
From: Robert G. <gi...@op...> - 2005-03-26 18:24:09
|
Bjorn, Have you been able to make v4l compatible drivers for the Win TV PVR USB2? Would I be able to record programs with MythTV? Regards, Rob |
|
From: Bjorn D. <sf...@da...> - 2005-03-25 11:26:03
|
Matthias Kindtner <mat...@t-...> wrote: > > 1. My CPU (PIII/1100) is between 75% - 100% and the movie have > sometimes "little timeout" I feel. Do you get the same CPU load with mplayer? I get 55-60% CPU load when watching TV with mplayer on a 700 MHz Celeron (my Xbox), with 6 Mbit/s 720x576 video. Motion is perfectly smooth except when a lot of disk activity happens at the same time. Make sure that hardware scaling is used, or that the screen is in 720x576 mode (720x480 for NTSC). Otherwise software scaling is used to produce square pixels. With mplayer on a slow CPU, use -vo xv or something equivalent, not -vo x11. -- Bjorn Danielsson <sf...@da...> |
|
From: Matthias K. <mat...@t-...> - 2005-03-23 23:30:24
|
Am Donnerstag, 17. M=E4rz 2005 20:44 schrieb Matthias Kindtner:
> First, I'm no member of the mailinglist, so please set me to CC: when pos=
t=20
an=20
> answer. Thanks!
>=20
> I'm try to get my new PVR USB 2 to work with my SUSE 9.2=20
>=20
> kernel-default-2.6.8-24.11
> pwlib-plugins-v4l-1.8.0-3
> v4l-tools-3.94-2
> v4l-conf-3.94-2
> xawtv4-20050121-1.1
> pvrusb2-dev-07112004
>=20
> But I get only snow-falling with xawtv4, mplayer, now station with scantv4
>=20
> In my syslog, there is a line "Please contact developper"
> I hope this is the problem while I failed.
> In pvrusb2-tuner.c there is no tuner 57 in section "#define PVR_NTUNER 4
>=20
In a ivtv-mailing-list I've found a log entry=20
Nov 16 11:44:43 localhost kernel: tveeprom: tuner =3D Philips FM1216 ME
MK3 (idx =3D 57, type =3D 38)
Nov 16 11:44:43 localhost kernel: tveeprom: tuner fmt =3D PAL(D/K)
(eeprom =3D 0x74, v4l2 =3D 0x00400e17)
Nov 16 11:44:43 localhost kernel: tveeprom: audio_processor =3D CS5331 (typ=
e =3D=20
9)
So, I've a card with idx=3D57 and number=3D38
The lines fron the tuner.c of the kernel I copy to pvrusb2-tuner.c
{ "Philips PAL/SECAM multi (FM1216ME MK3)", Philips, PAL,
=A0 =A0 =A0 =A0 =A0 16*160.00,16*442.00,0x01,0x02,0x04,0x8e,623 },
but the format of the lines are not equal with the others.
So I changed to:
{ "Philips PAL/SECAM multi (FM1216ME MK3)", 57,
=A0 =A0 =A0 16*160, 16*442, 0x01, 0x02, 0x04, 0xce, 0xc8, 623 },
With "0xce, 0xc8," I'm not sure what this means,
but all other entries have it too.
Now my card works, but there a 2 problems open:
1. My CPU (PIII/1100) is between 75% - 100% and the movie have
sometimes "little timeout" I feel.
2. With scantv4 I can't change the channel without trouble.
Sometimes it needs a lot if "clicks" until the channel select.
Most activity ends in "mpeg: select: timeout (3 sec)" dialog-box.
the syslog only says:=20
pvrusb2-dev-07112004/pvrusb2-tuner.c: pvr_set_freq_tv : 2692
May be a bug in the xawtv4-cvs or my change in the pvrusb2-tuner.c??
Thanks again for every help
Matthias
|
|
From: Charlie N. <cp...@ca...> - 2005-03-18 15:41:38
|
I have a quick question about this wonderful wintv pvr v4l2 driver. Can you switch mpeg encoding off on the device? and say read the YUV420 data on/dev/video? If anyone knows an answer to this question I would appreciate it if you could email me. Thanks Charlie |
