I have been using on of the most recent ivtv driver for about the last 24 hours and I have been having really good luck with it. The version I am currently using is ivtv-0.2.0-rc1j.

I just thought others would be interested.

You can find it at.... http://205.209.168.201/~ckennedy/ivtv/
******* Updated the URL 21 Dec 04 ********

Have fun!

P.S. If your not having problems... ignore this post!!!

I was wondering if these were becoming stable. before It was said that 2.0 was development code and highly unstable, but I noticed the other day that he had 2.0pr and had started 3.0 unstable branch and was wondering. good to hear that this new branch is working pretty well. I was wondering what the differences were above and beyond the 0.1.10pr code.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

from reading it sounded like they just chose a spot that seemed stable and called it .20rc sounded kinda random to me. i too am glad they will be relaseing another stable version soon. i just hope the pvr500 will be included into ivtv .30

I hadn't heard about a PVR500 so I did a little homework and found this link.

http://www.shspvr.com/forum/viewtopic.php?t=5675

I wouldn't be surprised if this card is supported very rapidly. It just looks like two pvr250s mounted on one board.

Do not expect PVR 500 support in the ivtv drivers anytime soon. Apparently both it and the PVR 150 are NOT real PVR [23]50 family members, but rather part of the unsupported blackbird family of boards.

I tried this version and it works great. I have 2 PVR250's and the PIP jerkiness is almost gone. It has a tiny bit of jerkiness, but I'd say 95% smooth. Thanks for finding that out!

_________________
ASUS A7N266 Micro-ATX Motherboard
Athlon 2200 processor
512K Kingston PC2100 Memory
MicroAtx Case
2 PVR250's w/remote
eVGA e-GeForce mx4000 (64 Ram with Tv/Out (Svideo))
Lite-on DVD cd-rw combo
120 GB Western Digital

I was hoping some of you who have migrated to the new ivtv-rc drivers might give some hints on getting them to work on the current knoppmyth distros. With all the new switches and knoppmyth's current scripts it seems to be a small mess.

I had attempted to install the new drivers at one point and had to go back and reinstall the distro to get things working normaly. Currently I have R4V4.1 installed and working except for a few machine freezes on fast forward and rewind.

Any howto's on moving to the 0.2.0 line? Or might we see it included in the next knoppmyth release?

Michael

A little research and reading of the docs will give you basically the information from this post. Just pick the part where it talks about updating ivtv. I did it many times without any problems and have even used same to reinstlal older versions. Not hard at all just takes a little reading.

_________________
ASUS A7N266 Micro-ATX Motherboard
Athlon 2200 processor
512K Kingston PC2100 Memory
MicroAtx Case
2 PVR250's w/remote
eVGA e-GeForce mx4000 (64 Ram with Tv/Out (Svideo))
Lite-on DVD cd-rw combo
120 GB Western Digital

_________________
ASUS A7N266 Micro-ATX Motherboard
Athlon 2200 processor
512K Kingston PC2100 Memory
MicroAtx Case
2 PVR250's w/remote
eVGA e-GeForce mx4000 (64 Ram with Tv/Out (Svideo))
Lite-on DVD cd-rw combo
120 GB Western Digital

FYI - I have installed ivtv-0.2.0-rc2d, and it works well for me with 0.16.

In the past, I had tried switching to some of the more recent 0.1.10xxx versions, but they were causing me real grief, especially with ff/rw.

This version has a slightly different behaviour with ff/rw (seems subjectively slower), but I really wanted to use the improved dual sound decoding and switching that is present in this release (my 0.1.9 version is stable, but often I don't get sound from the second audio channel, which annoys me).

When switching over, you have to "adapt" your ivtv module file, because a lot of autodetection is now in the driver. Here is what I did:
From 0.1.9 version:
-----------------


To 0.2.0 version:
---------------------


Summary (commands from memory, YMMV):
- Stop myth: /etc/init.d/mythbackend stop; killall frontend
- Unload ivtv: rmmod ivtv (and everything that it depends on) (is this really necessary?)
- In ivtv-0.2.0 directory: cd driver; make; make install; cd ../utils; make; make install
- depmod -ae
- Restart myth: /etc/init.d/mythbackend start; mythfrontend

http://67.18.1.101/~ckennedy/ivtv/HOWTO.ivtv-0.1.10


Is there a need to change any of the scripts that use ivtvctl instead of test_ioctl? Or did they make it backwards compatable?

From what I gather, "test_ioctl" has simply been renamed "ivtvctl".
If you don't want to change anything in your scripts, symlink test_ioctl to ivtvctl.

I updated to ivtv-0.2.0-rc1g the 17th october and edited line 4 in /etc/init.d/set_ivtv_params from:

IVTVCTL='test_ioctl' to
IVTVCTL='ivtvctl'

Until now it didn't cause any problems... works well

The link above is broken.. I found another one here:

http://ivtv.no-ip.com

That would be a bad thing. The 150 is appearing with prices that are just over half of what a 250 would cost. The 500 is going to cost what a 350 did earlier this year, but it's going to have two inputs (so hopefully less conflicts on the PCI bus.)

Considering how cheap tivos are getting, even when you add in service costs (has anyone *really* spent less than $299 for an HTPC?) price is a big deal.