Digital TV tuner drivers for Puppy 2.12 up

What works, and doesn't, for you. Be specific, and please include Puppy version.
Message
Author
tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#16 Post by tempestuous »

The http://linuxtv.org/hg/~hverkuil/v4l-dvb ... 61b30f3e35
link provides the full v4l/ivtv source code patched for AverMedia MCE116, not just the patch itself.
So I have compiled the patched ivtv modules, and attached the package to the 3rd post in this thread.

modesto
Posts: 7
Joined: Sat 28 Jul 2007, 17:41

#17 Post by modesto »

Thanks very much indeed.

I have not tried it yet as I am still using Puppy 2.14 and was dragging my feet on upgrading as it took me so long to get Nvidia TV out and DVB-S working properly, and have so many dot pets.

Seems like there is a good reason now.

Thanks

Phil

shenen
Posts: 37
Joined: Sun 03 Dec 2006, 18:19

#18 Post by shenen »

Hi tempestuous,
The ivtv module for the PVR250 is fine, however, the encoded video quality is not as good as that of the one recorded in Windows.

When I zoom it to full screen, I can see a kind of mesh in the video quality, I doubt it's a resolution issue, if it's a video resolution, usually you can see kind of mosaic effect when you zoom it.

Do you know what is that, or if there are parameters to fine tune the video encoding quality?
(VCR output to PVR input)

Thanks.
Shenen

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#19 Post by tempestuous »

First, make sure the comparison is equitable. I suggest you save the Linux video recording to a FAT32 partition or USB flash drive, then play it in Windows.
If the recordings made in Linux and Windows look identical (they should) then the "mesh" appearance is a problem with the media player application in
Linux.

But if the Linux recording definitely looks worse, that will be strange, because the PVR series cards have HARDWARE encoding chips, so the encoding is not done in software, and the process should be independent of the operating system.

Your problem then requires expertise from the IVTV developers. I suggest you submit your query to the ivtv-users mailinglist -
http://ivtvdriver.org/mailman/listinfo/ivtv-users

shenen
Posts: 37
Joined: Sun 03 Dec 2006, 18:19

#20 Post by shenen »

Based on what I have read, it seems to me the encoding and decoding are done through firmware, which is taken from windows driver.

http://ivtvdriver.org/index.php/Firmware

I played using Windows media player, it shows the same effect.

Theoretically the result should be the same. I don't know why, but I will look for more information.

Thanks.
Shenen

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#21 Post by tempestuous »

I provided the "standard" firmware recommended by the IVTV project. It's in /lib/firmware.
You could try replacing this with the firmware from your Windows driver.

modesto
Posts: 7
Joined: Sat 28 Jul 2007, 17:41

#22 Post by modesto »

Shenen,

Is the file size per unit of time the same for Linux and windows? If it was not the same it would suggest different levels of compression, IE different Bitrates. In linux I think the only bitrate is 6000K/s. I get about 2.6GByte/hr in Linux. If I want to get a lower bitrate I use ffmeg to process the saved file, which takes a long time, but it works, and it can be done via a script overnight

Different Bitrates could explain what you see. I think in Windows it can be changed.

Phil

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#23 Post by tempestuous »

October 6 2007
IVTV module package for Puppy 3.00 attached to 3rd post.

modesto
Posts: 7
Joined: Sat 28 Jul 2007, 17:41

#24 Post by modesto »

I installed Puppy 2.17 and the enhanced drivers, but still no sound.

I used cardtype 21 which seems to be the right card except it has no tuner support, but cardtype 16 does work with its tuner. Anyhow the goal is sound via the RCA sockets and the enhanced drivers seem to the right direction. So I do appreciate all the help, I am getting somewhere.

I think the problem this time may be that looking in the card initialization using dmesg, it has a line

IVTV: Failed to load module wm8739

When I try modprobe wm8739 I get Fatal wm8739 not found and indeed there is no wm8739.ko file in the applicable folder.

the odd thing is that I did have wm8739.ko in my Puppy 2.14. I am not not sure which package installed it.

From where could I get a wm8739 module for puppy 2.17?

Is it worth trying installing 3.0 and see what I get?

Thanks very much.

Phil
PS the wm8739 is the audio mixer, so I am not shooting in the dark, it makes some sense to need it

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#25 Post by tempestuous »

OK, I just added the wm8739 module to both the Puppy 2.17 and 3.00 ivtv packages. Both packages are now called "patched".
As well as the wm8739 module, I also discovered that the revised source provides several other new modules, so I added these as well;

cs53132a
saa7127
saa7191
tlv320aic23b
upd64031a
upd64083
v4l-int-device
vivi
vp27smpx
zr364xx

modesto
Posts: 7
Joined: Sat 28 Jul 2007, 17:41

#26 Post by modesto »

It works!!!

Thank you very much indeed.

Puppy makes a very good Home Theatre PC. The Nvidia drivers (6600 cards and up) are very good picture quality for DVDs etc and have good de-interlacing etc. Add a cheap video capture card and you are set to watch TV, convert tapes to DVD, Record and Burn DVDs of TV programs, watch TV semi-live tiVo style with replay and fast forward. Add a DVB-S card and get interesting satellite channels. This is on a PIII last generation computer. All thanks to people like you who help us with the details.

Phil

Post Reply