Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

PVR-350 and MythTV support

 

 

ivtv devel RSS feed   Index | Next | Previous | View Threaded


hverkuil at xs4all

Feb 1, 2007, 3:21 PM

Post #1 of 24 (3523 views)
Permalink
PVR-350 and MythTV support

Hi all,

Recently I've seen several comments that PVR350 support would not work
or would be removed from MythTV. While it is true that there is no
current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't
mean that it doesn't work. The ivtv API is still unchanged and as long
as the code remains in MythTV it should work just fine.

The support of the ivtv Xdriver is more problematic since the official
maintainer of that code (John Harvey) is very busy with other things
and hasn't had the opportunity to update this package to newer X11
versions.

Hopefully he will have more time to do this in the near future. If not,
then I'll try to find someone else to do the job or I'll do it myself.

At the moment I'm working hard to get a new ivtv release finished: this
release is substantially redesigned/cleaned up and should be much more
stable. At the same time I'm also working on moving the ivtv-specific
ioctl calls (i.e. the driver API) to new well-designed ioctls that will
be included in the linux V4L2 specification. When that is finished I
will ensure that the MythTV code is updated to the new (standardized)
API and this will include the PVR350 code.

Hopefully this clarifies the current situation.

Should the PVR350 support in MythTV break for whatever reason, then
please post a report to ivtv-devel [at] ivtvdriver I'll try my best to
fix it.

Regards,

Hans Verkuil
ivtv maintainer

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mrsam at courier-mta

Feb 1, 2007, 3:53 PM

Post #2 of 24 (3473 views)
Permalink
Re: [mythtv] PVR-350 and MythTV support [In reply to]

Hans Verkuil writes:

> The support of the ivtv Xdriver is more problematic since the official
> maintainer of that code (John Harvey) is very busy with other things
> and hasn't had the opportunity to update this package to newer X11
> versions.

Well, Ian Campbell's version of the ivtv_xdriver compiles, builds, and runs
just fine for me. The problem I have is with the ivtv_fb.ko module. It
loads without any errors, but TV-Out remains a blue screen in 0.9; unlike
in 0.8 where upon loading ivtv_fb.ko, which happens long before starting X
and loading ivtv_xdriver, the TV-Out signal drops from blue to green to
black. That does not happen with 0.9's ivtv_fb.ko, it remains at its
initial power-up state of solid blue. I can see from Xorg's logs that it
starts up and apparently continues to run fine, thinking that there's
nothing wrong with the framebuffer, except that nothing actually appears on
TV-Out.

> Should the PVR350 support in MythTV break for whatever reason, then
> please post a report to ivtv-devel [at] ivtvdriver I'll try my best to
> fix it.

See http://www.gossamer-threads.com/lists/ivtv/devel/34107?#34107

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.9.1 (tagged release) loading
ivtv: Linux version: 2.6.19-1.2895.fc6 SMP mod_unload 686 REGPARM 4KSTACKS
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge card (cx23415 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
tveeprom 3-0050: Hauppauge model 48132, rev K268, serial# 8289359
tveeprom 3-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47)
tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 3-0050: audio processor is MSP4448 (idx 27)
tveeprom 3-0050: decoder processor is SAA7115 (idx 19)
tveeprom 3-0050: has radio, has IR remote
ivtv0: Autodetected Hauppauge WinTV PVR-350
tuner 0-0043: chip found @ 0x86 (I2C Voodoo3/Banshee adapter)
tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 0-0060: All bytes are equal. It is not a TEA5767
tuner 0-0060: chip found @ 0xc0 (I2C Voodoo3/Banshee adapter)
tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115 3-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
msp3400 0-0040: MSP3430G-A4 found @ 0x80 (I2C Voodoo3/Banshee adapter)
msp3400 0-0040: MSP3430G-A4 supports radio, mode is autodetect and
autoselect
i2c_adapter i2c-0: sendbytes: error - bailout.
msp3400 0-0044: chip reset failed
i2c_adapter i2c-0: Client creation failed at 0x44 (-1)
msp3400 3-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
msp3400 3-0040: MSP4448G-A2 supports radio, mode is autodetect and
autoselect
i2c_adapter i2c-3: Client creation failed at 0x44 (-1)
ivtv0: Encoder revision: 0x02050032
ivtv0: Decoder revision: 0x02020023
ivtv0: Registered device video0 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi0 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPEG
ivtv0: Registered device vbi8 for decoder VBI
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV
ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
tuner 3-0061: type set to 47 (LG NTSC (TAPE series))
ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
ivtv: ==================== END INIT IVTV ====================
ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0)
ivtv0-osd: screen coords: [0 0] → [720 480]
ivtv0-osd: original global alpha = 208
ivtv0-osd: current OSD state = 39
ivtv0-osd: new global alpha = 208 (1 255 0)
ivtv0-osd: framebuffer at 0xe9510000, mapped to 0xd2010000, size 1665k
ivtv0-osd: mode is 720x480x32, linelength=2880
ivtv0-osd: fb1: cx23415 TV out frame buffer device


bolek-mythtv at curl

Feb 1, 2007, 3:59 PM

Post #3 of 24 (3458 views)
Permalink
Re: PVR-350 and MythTV support [In reply to]

Sam Varshavchik wrote:
> The problem I have is with the ivtv_fb.ko
> module. It loads without any errors, but TV-Out remains a blue screen
> in 0.9; unlike in 0.8 where upon loading ivtv_fb.ko, which happens long
> before starting X and loading ivtv_xdriver, the TV-Out signal drops from
> blue to green to black. That does not happen with 0.9's ivtv_fb.ko, it
> remains at its initial power-up state of solid blue. I can see from
> Xorg's logs that it starts up and apparently continues to run fine,
> thinking that there's nothing wrong with the framebuffer, except that
> nothing actually appears on TV-Out.

Forgive me if it's already been covered, but are you sure that you don't
have the missing saa7127 problem?

Bolek


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mrsam at courier-mta

Feb 1, 2007, 4:56 PM

Post #4 of 24 (3454 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

Boleslaw Ciesielski writes:

> Sam Varshavchik wrote:
>> The problem I have is with the ivtv_fb.ko
>> module. It loads without any errors, but TV-Out remains a blue screen
>> in 0.9; unlike in 0.8 where upon loading ivtv_fb.ko, which happens long
>> before starting X and loading ivtv_xdriver, the TV-Out signal drops from
>> blue to green to black. That does not happen with 0.9's ivtv_fb.ko, it
>> remains at its initial power-up state of solid blue. I can see from
>> Xorg's logs that it starts up and apparently continues to run fine,
>> thinking that there's nothing wrong with the framebuffer, except that
>> nothing actually appears on TV-Out.
>
> Forgive me if it's already been covered, but are you sure that you don't
> have the missing saa7127 problem?

That's the next thing I'm going to look into. I wasn't aware of this issue
until yesterday, when I trawled Google again. There's nothing in
/var/log/messages that complains about any missing module. If something
yelled loud and hard, at me, about some missing module, I would've picked it
up right away. grepping for saa7127 in /var/log/messages comes up empty,
but I'm going to try building it.


lists at l8r

Feb 1, 2007, 5:40 PM

Post #5 of 24 (3467 views)
Permalink
Re: PVR-350 and MythTV support [In reply to]

On Fri, 2 Feb 2007 00:21:57 +0100
Hans Verkuil <hverkuil [at] xs4all> wrote:

> Hi all,
>
> Recently I've seen several comments that PVR350 support would not work
> or would be removed from MythTV. While it is true that there is no
> current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't
> mean that it doesn't work. The ivtv API is still unchanged and as long
> as the code remains in MythTV it should work just fine.

Well, working is relative. It's quite buggy at times. I spent weeks
working on patches with some maintainers, but they unfortunately didn't
have cards handy to test anything at their end.

0.19 had several bugs in the on screen menu and PIP, that could cause
crashes or outright lockups. Menus could cause lockups. I saw
nothing in 0.20 release notes to indicate that there had been other
changes to fix such things.

FF, REW and other live tv controls had issues, were fixed, but remained
buggy at times. Realistically, the code is broken, but it will work if
you only do specific things, and never move outside of a specific
framework.

I can understand any maintainer's point of view. The IVTV X driver
isn't really that much of a burn on CPU cycles, compared to the
framebuffer driver. Considering the sad state of the IVTV framebuffer
code in Myth right now, it would probably make everyone's life easier if
it was just removed.

Of course, that doesn't mean it _will_ be removed. :P


>
> The support of the ivtv Xdriver is more problematic since the official
> maintainer of that code (John Harvey) is very busy with other things
> and hasn't had the opportunity to update this package to newer X11
> versions.
>
> Hopefully he will have more time to do this in the near future. If not,
> then I'll try to find someone else to do the job or I'll do it myself.
>
> At the moment I'm working hard to get a new ivtv release finished: this
> release is substantially redesigned/cleaned up and should be much more
> stable. At the same time I'm also working on moving the ivtv-specific
> ioctl calls (i.e. the driver API) to new well-designed ioctls that will
> be included in the linux V4L2 specification. When that is finished I
> will ensure that the MythTV code is updated to the new (standardized)
> API and this will include the PVR350 code.
>
> Hopefully this clarifies the current situation.
>
> Should the PVR350 support in MythTV break for whatever reason, then
> please post a report to ivtv-devel [at] ivtvdriver I'll try my best to
> fix it.
>

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Feb 2, 2007, 1:38 AM

Post #6 of 24 (3448 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Friday 02 February 2007 01:56, Sam Varshavchik wrote:
> Boleslaw Ciesielski writes:
> > Sam Varshavchik wrote:
> >> The problem I have is with the ivtv_fb.ko
> >> module. It loads without any errors, but TV-Out remains a blue
> >> screen in 0.9; unlike in 0.8 where upon loading ivtv_fb.ko, which
> >> happens long before starting X and loading ivtv_xdriver, the
> >> TV-Out signal drops from blue to green to black. That does not
> >> happen with 0.9's ivtv_fb.ko, it remains at its initial power-up
> >> state of solid blue. I can see from Xorg's logs that it starts up
> >> and apparently continues to run fine, thinking that there's
> >> nothing wrong with the framebuffer, except that nothing actually
> >> appears on TV-Out.
> >
> > Forgive me if it's already been covered, but are you sure that you
> > don't have the missing saa7127 problem?
>
> That's the next thing I'm going to look into. I wasn't aware of this
> issue until yesterday, when I trawled Google again. There's nothing
> in /var/log/messages that complains about any missing module. If
> something yelled loud and hard, at me, about some missing module, I
> would've picked it up right away. grepping for saa7127 in
> /var/log/messages comes up empty, but I'm going to try building it.

I was wondering myself why the yell was missing: turns out to be a
driver bug. It will yell if the saa7127 driver was compiled as a kernel
module and the kernel module was missing, but it would say nothing if
it wasn't in the kernel at all! This is now fixed and will be in the
next ivtv release.

Thanks,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mouw at nl

Feb 2, 2007, 4:34 AM

Post #7 of 24 (3443 views)
Permalink
Re: [mythtv] PVR-350 and MythTV support [In reply to]

On Fri, Feb 02, 2007 at 12:21:57AM +0100, Hans Verkuil wrote:
> Recently I've seen several comments that PVR350 support would not work
> or would be removed from MythTV. While it is true that there is no
> current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't
> mean that it doesn't work. The ivtv API is still unchanged and as long
> as the code remains in MythTV it should work just fine.

FWIW, it works just fine with myth 0.20. I'm using a PVR 350 in both
head ends.


Erik

--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachments: signature.asc (0.18 KB)


jeffsimpson at alum

Feb 6, 2007, 7:04 AM

Post #8 of 24 (3437 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On 2/1/07, Hans Verkuil <hverkuil [at] xs4all> wrote:
> Hi all,
>
> Recently I've seen several comments that PVR350 support would not work
> or would be removed from MythTV. While it is true that there is no
> current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't
> mean that it doesn't work. The ivtv API is still unchanged and as long
> as the code remains in MythTV it should work just fine.

As I was probably a person who made some of those comments, I feel I
should back them up:

#1, MPEG Output on the PVR-350 is working, but mostly unsupported by
advanced features. Things like fast forward and rewind don't work,
frequency scaling doesn't work, things like that. It does technically
still play video, but only native MPEG2 (no mpeg4, no alternate
formats, etc). The only way to play anything that isn't a native
recording is to use the framebuffer or xdriver, whose faults are
described later.

#2, Myth is moving to OpenGL for menus. It now supports OpenGL and qt
and you can switch between them. I can't imagine they will continue to
provide both options for much longer. The PVR-350 doesn't support
OpenGL and never will.

#3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
machine, but the menus are still slow. I often find the X session
using 50 or 60% of my cpu, just SITTING there. Forget trying to run it
at the same time as another X session, it jumps to a full 100%.
Playing anything that isn't a native mpeg2 video makes the system
crawl.

#3 XDriver is a great project, but it's always been buggy at best, and
difficult to compile (with each version of X, the driver has needed
another patch or hack just to compile). I think now that it's in some
repositories (gentoo), it's better? (I've still had to patch it, but
maybe by now it's better).

So in summary, the PVR-350 *does* work, it just isn't as fully
supported as say, any nvidia or ati tv out card made in the last 5
years for 1/4 of the cost. The video encoding is well supported, just
like the 150/250/500, it's just the output that's flaky. In my own
personal opinion, having owned a PVR-350, I would say that I'd be
better off owning a 150 and an nvidia geforce card with TV Out.

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mouw at nl

Feb 6, 2007, 9:06 AM

Post #9 of 24 (3415 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Tue, Feb 06, 2007 at 10:04:56AM -0500, Jeff Simpson wrote:
> On 2/1/07, Hans Verkuil <hverkuil [at] xs4all> wrote:
> > Hi all,
> >
> > Recently I've seen several comments that PVR350 support would not work
> > or would be removed from MythTV. While it is true that there is no
> > current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't
> > mean that it doesn't work. The ivtv API is still unchanged and as long
> > as the code remains in MythTV it should work just fine.
>
> As I was probably a person who made some of those comments, I feel I
> should back them up:
>
> #1, MPEG Output on the PVR-350 is working, but mostly unsupported by
> advanced features. Things like fast forward and rewind don't work,
> frequency scaling doesn't work, things like that. It does technically
> still play video, but only native MPEG2 (no mpeg4, no alternate
> formats, etc). The only way to play anything that isn't a native
> recording is to use the framebuffer or xdriver, whose faults are
> described later.

However, the PVR350 allows you to use rather moderate hardware for a
front- and backend (i.e.: my old P3 850 as combined front+backend and
a PII 300 as a second frontend).

> #2, Myth is moving to OpenGL for menus. It now supports OpenGL and qt
> and you can switch between them. I can't imagine they will continue to
> provide both options for much longer. The PVR-350 doesn't support
> OpenGL and never will.

I don't know the reason for switching to OpenGL, the Qt engine still
works fine. One way to support OpenGL on the 350 would be to use Mesa,
but that would be another layer of indirection that will slow down the
system.

> #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
> machine, but the menus are still slow. I often find the X session
> using 50 or 60% of my cpu, just SITTING there.

Never seen that. An idle machine is just idle over here. Occasionally
Xorg tends to eat 100% CPU time, but that seems to be unrelated to Myth
cause the same happens occasionally on my desktop.

> Forget trying to run it
> at the same time as another X session, it jumps to a full 100%.
> Playing anything that isn't a native mpeg2 video makes the system
> crawl.

If you only use PVR x50 cards to record the problem doesn't exist.

> #3 XDriver is a great project, but it's always been buggy at best, and
> difficult to compile (with each version of X, the driver has needed
> another patch or hack just to compile). I think now that it's in some
> repositories (gentoo), it's better? (I've still had to patch it, but
> maybe by now it's better).

FWIW, it never crashed on me.

> So in summary, the PVR-350 *does* work, it just isn't as fully
> supported as say, any nvidia or ati tv out card made in the last 5
> years for 1/4 of the cost. The video encoding is well supported, just
> like the 150/250/500, it's just the output that's flaky. In my own
> personal opinion, having owned a PVR-350, I would say that I'd be
> better off owning a 150 and an nvidia geforce card with TV Out.

I diagree. A PVR 150 is about 85 EUR, for 140 EUR you have a 350. That
difference does buy you a ati or nvidia card with tv out (cheapest is
around 40 EUR), but doesn't buy you a CPU fast enough to do the
decoding, especially when you have some old hardware lying around.


Erik

--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachments: signature.asc (0.18 KB)


punka at cfl

Feb 7, 2007, 7:07 AM

Post #10 of 24 (3417 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Feb 6, 2007, at 10:04 AM, Jeff Simpson wrote:

> #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
> machine, but the menus are still slow. I often find the X session
> using 50 or 60% of my cpu, just SITTING there. Forget trying to run it
> at the same time as another X session, it jumps to a full 100%.
> Playing anything that isn't a native mpeg2 video makes the system
> crawl.

Yup, writing directly to the framebuffer is slow. And yes, it is the
main source of problems with the OSD in Myth.

That's why the 350 framebuffer support should be taken out of Myth,
not the entire support for the PVR-350.

> #3 XDriver is a great project, but it's always been buggy at best, and
> difficult to compile (with each version of X, the driver has needed
> another patch or hack just to compile). I think now that it's in some
> repositories (gentoo), it's better? (I've still had to patch it, but
> maybe by now it's better).

Patching != buggy.
And yes, a modular X will need a patched Xdriver. Most other
hwdrivers in X probably needed patches, too.

With XV support in the Xdriver, the PVR-350 HAS become a full-fledged
video card, just like your onboard video. There is no need to write
directly to the framebuffer anymore. It can play MPEG-2 with little
to no CPU footprint, and play that downloaded XviD or transcoded
MPEG-4 on my dual 500MHz celeron at about ~30% CPU utilization. Not
bad for a machine that's > 7 years old.

No, it does not have OpenGL support, but someone will hopefully
maintain the QT side of mythtv for those using old/embedded hardware.

- Rick



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mouw at nl

Feb 7, 2007, 9:46 AM

Post #11 of 24 (3420 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Wed, Feb 07, 2007 at 10:07:28AM -0500, Ricardo Lugo wrote:
> On Feb 6, 2007, at 10:04 AM, Jeff Simpson wrote:
>
> > #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
> > machine, but the menus are still slow. I often find the X session
> > using 50 or 60% of my cpu, just SITTING there. Forget trying to run it
> > at the same time as another X session, it jumps to a full 100%.
> > Playing anything that isn't a native mpeg2 video makes the system
> > crawl.
>
> Yup, writing directly to the framebuffer is slow. And yes, it is the
> main source of problems with the OSD in Myth.

What OSD problems? Curious, cause I haven't had any so far.

> That's why the 350 framebuffer support should be taken out of Myth,
> not the entire support for the PVR-350.

If that means that you can't use a PVR-350 to display both menu and
video, I don't agree. It's one of the major advantages of the 350: one
card does all.


Erik

--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachments: signature.asc (0.18 KB)


jeffsimpson at alum

Feb 7, 2007, 12:02 PM

Post #12 of 24 (3411 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

> > #1, MPEG Output on the PVR-350 is working, but mostly unsupported by
> > advanced features. Things like fast forward and rewind don't work,
> > frequency scaling doesn't work, things like that. It does technically
> > still play video, but only native MPEG2 (no mpeg4, no alternate
> > formats, etc). The only way to play anything that isn't a native
> > recording is to use the framebuffer or xdriver, whose faults are
> > described later.
>
> However, the PVR350 allows you to use rather moderate hardware for a
> front- and backend (i.e.: my old P3 850 as combined front+backend and
> a PII 300 as a second frontend).

Only if you want a limited-use frontend. You can only play mpeg2 on
it, which means no automatic transcoding, no dvds, etc. It is a good
way to breathe life into older hardware, but I can't recommend this
card to anyone with a fast machine.

> > #2, Myth is moving to OpenGL for menus. It now supports OpenGL and qt
> > and you can switch between them. I can't imagine they will continue to
> > provide both options for much longer. The PVR-350 doesn't support
> > OpenGL and never will.
>
> I don't know the reason for switching to OpenGL, the Qt engine still
> works fine. One way to support OpenGL on the 350 would be to use Mesa,
> but that would be another layer of indirection that will slow down the
> system.

exactly. I did try that, but mesa made the framebuffer output on the
350 even slower than it already is. It was unbearable and took all my
CPU.

> > #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
> > machine, but the menus are still slow. I often find the X session
> > using 50 or 60% of my cpu, just SITTING there.
>
> Never seen that. An idle machine is just idle over here. Occasionally
> Xorg tends to eat 100% CPU time, but that seems to be unrelated to Myth
> cause the same happens occasionally on my desktop.

I see it often if I leave it in the list of recordings where it shows
a small preview, that alone will eat up 30-40% of cpu. actually using
it to display something eats more. The hacks to let you play a DVD or
other format of video through XV on the PVR output are just that -
hacks. They eat a LOT of CPU that a normal accelerated card would not
have to.

> > Forget trying to run it
> > at the same time as another X session, it jumps to a full 100%.
> > Playing anything that isn't a native mpeg2 video makes the system
> > crawl.
>
> If you only use PVR x50 cards to record the problem doesn't exist.

only if you don't auto-transcode to mpeg4, watch dvds, or use the myth
box for anything that isn't just plain old TV. Myth isn't just for
SDTV, it's supposed to be the everything box. I also can't use
mythgame on the PVR-350 at all, since it can't scale or accelerate.
Games like stepmania that would be great on a myth box can't be played
on a graphics card without openGL and acceleration.

> > #3 XDriver is a great project, but it's always been buggy at best, and
> > difficult to compile (with each version of X, the driver has needed
> > another patch or hack just to compile). I think now that it's in some
> > repositories (gentoo), it's better? (I've still had to patch it, but
> > maybe by now it's better).
>
> FWIW, it never crashed on me.

Mine doesn't crash either. But it is buggy. Switching VTs results in
garbage on one of the main screens on my other card when I use the
framebuffer, if I kill X and restart it, the screen is garbled until I
play an mpeg video, at which point it fixes it, small little bugs. And
a LOT of hacking around just to make it work in the first place. It's
not plug-and-play like a typical video card is.

> > So in summary, the PVR-350 *does* work, it just isn't as fully
> > supported as say, any nvidia or ati tv out card made in the last 5
> > years for 1/4 of the cost. The video encoding is well supported, just
> > like the 150/250/500, it's just the output that's flaky. In my own
> > personal opinion, having owned a PVR-350, I would say that I'd be
> > better off owning a 150 and an nvidia geforce card with TV Out.
>
> I diagree. A PVR 150 is about 85 EUR, for 140 EUR you have a 350. That
> difference does buy you a ati or nvidia card with tv out (cheapest is
> around 40 EUR), but doesn't buy you a CPU fast enough to do the
> decoding, especially when you have some old hardware lying around.

If you only want the bare minimum of what myth has to offer, than the
PVR-350 will do it. But if you want advanced PVR features like
"fast-forward" and "rewind", you need a supported card. It's sad but
it's true. I really like the idea of the PVR-350, the idea that the
hardware can do all the tedious decoding and save the processor for
the real work. The problem is not many people use the card, and as
such, support for it is lacking. It's the same reason I wouldn't want
to use an alpha or sparc machine. The architecture is great, but
software support is terrible.

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


Wilhelm.Eger at uni-jena

Feb 7, 2007, 12:21 PM

Post #13 of 24 (3399 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

Zitat von Jeff Simpson <jeffsimpson [at] alum>:

> I see it often if I leave it in the list of recordings where it shows
> a small preview, that alone will eat up 30-40% of cpu. actually using
> it to display something eats more. The hacks to let you play a DVD or
> other format of video through XV on the PVR output are just that -
> hacks. They eat a LOT of CPU that a normal accelerated card would not
> have to.

All I can say about this is: It works. I use to view all kind of divx/xvid
whatever non mpeg stuff through my PVR 350's TV out with the xdriver and xine
(through Mythtv). And it is smooth. First I had an Athlon 500 now a Geode NX
1750

Greetings, Wilhelm



----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


punka at cfl

Feb 7, 2007, 12:44 PM

Post #14 of 24 (3409 views)
Permalink
Re: [mythtv] [ivtv-users] PVR-350 and MythTV support [In reply to]

On Feb 7, 2007, at 12:46 PM, Erik Mouw wrote:

> On Wed, Feb 07, 2007 at 10:07:28AM -0500, Ricardo Lugo wrote:
>> On Feb 6, 2007, at 10:04 AM, Jeff Simpson wrote:
>>
>>> #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a
>>> 3ghz
>>> machine, but the menus are still slow. I often find the X session
>>> using 50 or 60% of my cpu, just SITTING there. Forget trying to
>>> run it
>>> at the same time as another X session, it jumps to a full 100%.
>>> Playing anything that isn't a native mpeg2 video makes the system
>>> crawl.
>>
>> Yup, writing directly to the framebuffer is slow. And yes, it is the
>> main source of problems with the OSD in Myth.
>
> What OSD problems? Curious, cause I haven't had any so far.

Try "Edit Recording" while watching a recording: I've never gotten it
to work. Or using the PVR-350's TV-out with MythTV on a big-endian
machine.

>
>> That's why the 350 framebuffer support should be taken out of Myth,
>> not the entire support for the PVR-350.
>
> If that means that you can't use a PVR-350 to display both menu and
> video, I don't agree. It's one of the major advantages of the 350: one
> card does all.

I'm not advocating removal of the OSD at all. I couldn't live without
it!

I'm suggesting that the OSD be accomplished through regular calls to
X through the Xdriver and XV - ie like any other video card out
there, but that the MPEG2 decoding still be done by the 350.

Currently, the OSD is drawn by MythTV writing directly to the 350's
framebuffer. This is time-consuming to maintain, and buggy: On my PPC
machine (big-endian) the OSD colors are off, and the time calculation
for the duration of the recording is also off. Commercial skipping
sometimes results in MythTV losing control of the OSD. Editing a
Recording causes MythTV to lose control of the OSD - I have to
restart X to get control again.

We have a stable Xdriver that draws graphics for us, and does so very
efficiently through the use of XV. Why should Myth write directly to
the card, when it can just write to X and let the Xdriver handle it?
This is something that can be maintained for the PVR-350.

- Rick

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


punka at cfl

Feb 7, 2007, 12:44 PM

Post #15 of 24 (3401 views)
Permalink
Re: [mythtv] [ivtv-users] PVR-350 and MythTV support [In reply to]

On Feb 7, 2007, at 1:16 PM, eric.bosch [at] comcast wrote:

> Only issue I see with it is a problem only when XvMC is turned on,
> mythtv OSD loses color, however with XvMC enabled, it is gray-
> tones, and CPU usage drops from 25-30% down to 10% with XvMC
> enabled. You win some, you lose some!

XV = X video extension (which the Xdriver can do)

XvMC = X-Video Motion Compensation (which the Xdriver cannot do?)

>
> -------------- Original message --------------
> From: Erik Mouw <mouw [at] nl>
>
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev [at] mythtv
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> >
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


mouw at nl

Feb 8, 2007, 4:48 AM

Post #16 of 24 (3397 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Wed, Feb 07, 2007 at 03:02:12PM -0500, Jeff Simpson wrote:
> > However, the PVR350 allows you to use rather moderate hardware for a
> > front- and backend (i.e.: my old P3 850 as combined front+backend and
> > a PII 300 as a second frontend).
>
> Only if you want a limited-use frontend. You can only play mpeg2 on
> it, which means no automatic transcoding, no dvds, etc. It is a good
> way to breathe life into older hardware, but I can't recommend this
> card to anyone with a fast machine.

That's what I use it for: an advanced VCR.

> > > #3, Framebuffer is slow slow slow slow, and it EATS cpu. I have a 3ghz
> > > machine, but the menus are still slow. I often find the X session
> > > using 50 or 60% of my cpu, just SITTING there.
> >
> > Never seen that. An idle machine is just idle over here. Occasionally
> > Xorg tends to eat 100% CPU time, but that seems to be unrelated to Myth
> > cause the same happens occasionally on my desktop.
>
> I see it often if I leave it in the list of recordings where it shows
> a small preview, that alone will eat up 30-40% of cpu. actually using
> it to display something eats more. The hacks to let you play a DVD or
> other format of video through XV on the PVR output are just that -
> hacks. They eat a LOT of CPU that a normal accelerated card would not
> have to.

Ah, that must be it. I switched life preview off immediately after
install cause I didn't like it. I haven't even noticed it was eating
CPU.

> > > Forget trying to run it
> > > at the same time as another X session, it jumps to a full 100%.
> > > Playing anything that isn't a native mpeg2 video makes the system
> > > crawl.
> >
> > If you only use PVR x50 cards to record the problem doesn't exist.
>
> only if you don't auto-transcode to mpeg4, watch dvds, or use the myth
> box for anything that isn't just plain old TV. Myth isn't just for
> SDTV, it's supposed to be the everything box.

Only SDTV over here in .nl. The local cable monopolist (UPC) offers
"digital TV" but that's only SDTV resolution and only possible to
receive with their own setup box (i.e.: not DVB-C compatible).

> I also can't use
> mythgame on the PVR-350 at all, since it can't scale or accelerate.
> Games like stepmania that would be great on a myth box can't be played
> on a graphics card without openGL and acceleration.

I'm not a gamer and neither is my wife :)

> > > #3 XDriver is a great project, but it's always been buggy at best, and
> > > difficult to compile (with each version of X, the driver has needed
> > > another patch or hack just to compile). I think now that it's in some
> > > repositories (gentoo), it's better? (I've still had to patch it, but
> > > maybe by now it's better).
> >
> > FWIW, it never crashed on me.
>
> Mine doesn't crash either. But it is buggy. Switching VTs results in
> garbage on one of the main screens on my other card when I use the
> framebuffer, if I kill X and restart it, the screen is garbled until I
> play an mpeg video, at which point it fixes it, small little bugs. And
> a LOT of hacking around just to make it work in the first place. It's
> not plug-and-play like a typical video card is.

Never seen that, but I have a dedicated mythtv box (or rather: I have
two).

> > > So in summary, the PVR-350 *does* work, it just isn't as fully
> > > supported as say, any nvidia or ati tv out card made in the last 5
> > > years for 1/4 of the cost. The video encoding is well supported, just
> > > like the 150/250/500, it's just the output that's flaky. In my own
> > > personal opinion, having owned a PVR-350, I would say that I'd be
> > > better off owning a 150 and an nvidia geforce card with TV Out.
> >
> > I diagree. A PVR 150 is about 85 EUR, for 140 EUR you have a 350. That
> > difference does buy you a ati or nvidia card with tv out (cheapest is
> > around 40 EUR), but doesn't buy you a CPU fast enough to do the
> > decoding, especially when you have some old hardware lying around.
>
> If you only want the bare minimum of what myth has to offer, than the
> PVR-350 will do it. But if you want advanced PVR features like
> "fast-forward" and "rewind", you need a supported card. It's sad but
> it's true.

That's indeed all I want :)

> I really like the idea of the PVR-350, the idea that the
> hardware can do all the tedious decoding and save the processor for
> the real work. The problem is not many people use the card, and as
> such, support for it is lacking. It's the same reason I wouldn't want
> to use an alpha or sparc machine. The architecture is great, but
> software support is terrible.

If all you want is a PVR, the PVR-350 is a great card.


Erik

--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachments: signature.asc (0.18 KB)


jeffsimpson at alum

Feb 8, 2007, 6:35 AM

Post #17 of 24 (3380 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

> > Only if you want a limited-use frontend. You can only play mpeg2 on
> > it, which means no automatic transcoding, no dvds, etc. It is a good
> > way to breathe life into older hardware, but I can't recommend this
> > card to anyone with a fast machine.
>
> That's what I use it for: an advanced VCR.

VCRs can fast forward and rewind. The PVR-350 can't, it's not supported.

- Jeff

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


shieldsm at gmail

Feb 8, 2007, 7:53 AM

Post #18 of 24 (3390 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

>
>
> VCRs can fast forward and rewind. The PVR-350 can't, it's not supported.
>
>
Are you talking about the speed adjust? It can certainly skip forward and
backward in time.

The only thing I'm aware that it can't do is the "speed up/slow down" -- I
have another frontend that can use that feature (nvidia video card) but...
vcr's don't do that. I suppose a vcr "plays fast" and "plays in reverse" in
ff and rw respectively but it doesn't speed the sound up like the myth
feature does. On a vcr you "fast forward" to skip something or get somewhere
else, not to "watch something fast". I digress - for skipping forward by
seconds, minutes, etc, the pvr350 decoder out works just fine for me. My
wife would kill me if it couldn't skip commercials.

My mythbox is, I suppose, a bit more than a advanced vcr - but I have never
had any desire to auto-transcode anything, play games, or anything else that
the pvr350's out "can't do". It does "what a tivo does but skips
commercials" and that's exactly what I need. Certainly, if you want a
machine to play dvd's, games, or video files encoded with random codecs,
you're going to need more general-purpose hardware -- bigger cpu and
accelerated video out (and a dvd drive - I don't even have one of those in
any of my myth systems!). That's not, nor has it ever been, the pvr350's
niche.

I'd just say that I think mythtv + pvr350 decoder out is a great thing - it
works amazingly well on my P3-650 front/back-end and if it disappeared it
would be a great shame -- I, and I assume many others, would be stuck on old
versions of software or forced to upgrade hardware. If it's ever seriously
threatened that it'll be removed due to lack of interest or "code rot", I'll
volunteer now to step up and help maintain it.

Mike


mouw at nl

Feb 8, 2007, 12:10 PM

Post #19 of 24 (3380 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Thu, Feb 08, 2007 at 09:35:54AM -0500, Jeff Simpson wrote:
> > > Only if you want a limited-use frontend. You can only play mpeg2 on
> > > it, which means no automatic transcoding, no dvds, etc. It is a good
> > > way to breathe life into older hardware, but I can't recommend this
> > > card to anyone with a fast machine.
> >
> > That's what I use it for: an advanced VCR.
>
> VCRs can fast forward and rewind. The PVR-350 can't, it's not supported.

On VCRs you usually use fast forward or rewind to skip to an
interesting part of the recording. Because of the sequential access of
the tape, you can only do that by going through all intermediate
frames. Even a 10 second skip would take several seconds because the
tape deck would have to switch to fast forward mode, roll 10 seconds of
tape, swith back to play mode, let the PLL lock again on the video
frame and finally display the frame. That took quite some time so
manufacturers added the possibility to do fast forward with view at the
same time, but to be honest, that's only a hack because you really want
an immediate 10 second skip.

Because it is backed by a randomly accesible medium like the hard
drive, the PVR-350 can do such immediate 10 second skips without
showing any of the intermediate frames. In my opinion that is an
advantage over the traditional tape based VCR.


Erik

--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachments: signature.asc (0.18 KB)


srey0123+ivtv at gmail

Feb 8, 2007, 2:40 PM

Post #20 of 24 (3373 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Feb 8, 2007, at 8:35 AM, Jeff Simpson wrote:

>>> Only if you want a limited-use frontend. You can only play mpeg2 on
>>> it, which means no automatic transcoding, no dvds, etc. It is a good
>>> way to breathe life into older hardware, but I can't recommend this
>>> card to anyone with a fast machine.
>>
>> That's what I use it for: an advanced VCR.
>
> VCRs can fast forward and rewind. The PVR-350 can't, it's not
> supported.

Actually, I find that jump forward/backward is infinitely more useful
than fast forward and rewind. Why wait for several seconds to move
through an advertisement when a jump of +30 seconds will do? The
PVR-350 does fine in this regard. In fact, in my experience, it's
better than with XvMC on an nVidia card.

This is not to say that you don't have good points, Jeff. However,
the fact is that the PVR-350 is still quite useful even if it doesn't
(and cannot) support all that MythTV is capable of.

--scott

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Feb 9, 2007, 5:17 AM

Post #21 of 24 (3375 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Thursday 08 February 2007 15:35, Jeff Simpson wrote:
> > > Only if you want a limited-use frontend. You can only play mpeg2
> > > on it, which means no automatic transcoding, no dvds, etc. It is
> > > a good way to breathe life into older hardware, but I can't
> > > recommend this card to anyone with a fast machine.
> >
> > That's what I use it for: an advanced VCR.
>
> VCRs can fast forward and rewind. The PVR-350 can't, it's not
> supported.

Not true. The PVR350 supports it, it is just never implemented in
MythTV. I'm working with the video4linux guys to make a standardized
API available in the ivtv driver to do this. That should make it much
easier to implement. Although if anyone is interested I do have example
code available that demonstrates how to use the current ivtv API for
fast forward/rewind.

(You can get it here:
http://ivtvdriver.org/viewcvs/ivtvtv/trunk.tar.gz?view=tar, file
ivtvtv.cpp. Note that this is code for testing the pvr350, not
production code.)

Basically the PVR350 is just that: a PVR, intended to be used in
hardware recorders and things like that (and I know it is in fact used
in some HW recorders). It's not for mpeg4 playback, etc. Although you
can use a software decoder and XV to do the playback. The XV stuff is
pretty efficient as it uses DMA to get the picture to the card, but
using the framebuffer directly is really inefficient as it uses PIO to
get the data to the card, which is a notoriously slow method.

But if you want to play 3D games at 100 Hz refresh rate, then you're
using the wrong card :-)

The same is true for DVD playback: it isn't designed for that
(unfortunately). Again, you can use XV for that so you can at least
utilitize the excellent TV-out quality of the PVR350.

To summarize: the PVR350 is great when used as a PVR, if you are not
interested in that, or if it is only a small part of what you use
MythTV for, then choose another capture card. But I suspect that most
people use MythTV as a PVR first and foremost.

BTW, if anyone is interested in improving the PVR350 support in MythTV
then I'd love to help out with advice and example code. It's not
something I'm going to tackle myself though out of self-protection:
ivtv is already taking up too much of my time and I'm not going to add
another project.

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


jeffsimpson at alum

Feb 9, 2007, 7:21 AM

Post #22 of 24 (3355 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

> Basically the PVR350 is just that: a PVR, intended to be used in
> hardware recorders and things like that (and I know it is in fact used
> in some HW recorders). It's not for mpeg4 playback, etc. Although you
> can use a software decoder and XV to do the playback. The XV stuff is
> pretty efficient as it uses DMA to get the picture to the card, but
> using the framebuffer directly is really inefficient as it uses PIO to
> get the data to the card, which is a notoriously slow method.
> The same is true for DVD playback: it isn't designed for that
> (unfortunately). Again, you can use XV for that so you can at least
> utilitize the excellent TV-out quality of the PVR350.

I actually just gave dvd playback another chance with the latest
version of X, ivtv, and the xdriver, and was pleasantly surprised!

xine -V xv -f dvd://

works marvelously and doesn't seem to skip at all. I use the same
command for playing other video formats and get equally good results.
Much improved from the last time I tried it.

The downside is that the latest xdriver/ivtv version has managed to
slow the framebuffer drawing down even more. I can actually see it
drawing widgets on the screen in layers it's so slow with each screen
of options it loads. i don't suppose there's any way to fix that,
though.

- Jeff

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


nufan_wfk at yahoo

Feb 9, 2007, 8:57 AM

Post #23 of 24 (3352 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

Not sure if that's a recent 'break', but the pvr350
*can* ff/rw (like a vcr), but good support for that
hasn't been written into mythtv yet.

Mine does a 3x ff, and that's about it, but it IS
still ff'ding

And for the record, i think that the pvr cards are
really only useful when you have an old box lying
around and you want to make it a pvr. If you have even
a moderately fast box, why not buy a $30 capture card
and let it decode/encode in software?

The 350 is a special case IMHO because of the
excellent video output quality, but you're still
locked in to mpeg-2.

-tmk

--- Jeff Simpson <jeffsimpson [at] alum> wrote:

> > > Only if you want a limited-use frontend. You can
> only play mpeg2 on
> > > it, which means no automatic transcoding, no
> dvds, etc. It is a good
> > > way to breathe life into older hardware, but I
> can't recommend this
> > > card to anyone with a fast machine.
> >
> > That's what I use it for: an advanced VCR.
>
> VCRs can fast forward and rewind. The PVR-350 can't,
> it's not supported.
>
> - Jeff
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>




____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


bhoar at speakeasy

Feb 9, 2007, 11:20 AM

Post #24 of 24 (3358 views)
Permalink
Re: [ivtv-users] PVR-350 and MythTV support [In reply to]

On Fri, 9 Feb 2007, kevin thayer wrote:
> And for the record, i think that the pvr cards are
> really only useful when you have an old box lying
> around and you want to make it a pvr. If you have even
> a moderately fast box, why not buy a $30 capture card
> and let it decode/encode in software?

Because you want to use 4-5 tuners at once to record in parallel? :)

My bigger concern on the pvr/ivtv issue is that HDTV is here to stay (in
the US) and coming (elsewhere). Semi on-topic, I wonder what the plans
are in europe and asia-pac for the sdtv->hdtv transition. If it's
pretty well staggered, then the pvr cards and ivtv will continue to have
a long life.

I happen to still have analog cable (one of the last few holdouts) and
one reason is so that I can continue to add tuners as my, and my SO's
watching interests evolve over time. Avoiding conflicts is key...

...the other reason is that the local cable company is actually my
neighbor (we're on the same block two doors apart) and they gave the
adjacent businesses and 2nd floor apartments free cable in perpetuity!

This was in exchange for having completely ripped out our parking lot
for a couple of months about eight years ago in order to lay all their
shiny new digital cable. I fear moving to digital will mean they'll
forget all about that arrangement... :)

-brendan

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.