It's jumpy actually because your using the newest firmware, there's older
firmware which is better actually.  They (Conexant) have removed byte
based DMA and force frame based DMA in the newest firmware which is pretty
sad, and frame based DMA just isn't good on heavy usage because we don't
get all the data efficiently grabbed and instead have to do lots of small
grabs.  So there's a link in the QuickSetup file and also in the Wiki where
there's recommened firmware which is much better and won't do things like
that.

Thanks,
Chris
On Mon, May 23, 2005 at 01:03:05PM +0200, Alberto L�pez Navarro wrote:
> 
>     Hi all,
> 
>         I have a system with three PVR-500 cards and they have a PCI ID which 
> is not yet in the latest driver, so here it goes. I'm not familiar with 
> submitting patches, so I'm pasting here the code I've modified:
> 
> --- ivtv-cards.c
> 
> static const struct ivtv_card_pci_info ivtv_pci_pvr150[] = {
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x8801},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x8003},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xe807},
> >>>     {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0807}, <<<<
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xe817},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xc801},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0801},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0009},
>         {0, 0, 0}
> };
> 
> 
> 
>     I'm working 0.3.4i, and it works quite well (tried 0.3.4y, but it didn't 
> tune at all, just snow). I'm using vlc for streaming from all six card 
> instances simultaneously, and additionally from one DVB-S and one DVB-T cards 
> as well. However, I notice that the image is somewhat jumpy. I've discarded 
> network and CPU load problems, as the output from DVB-T/S is perfectly 
> smooth, and there is no square pixel effect: the image just seems to freeze 
> for a while. It happens particularly during sequences with fast movements, as 
> if the card wasn't able to compress, and opted for skipping some frames. I've 
> been playing with bitrate, bitrate_peak, framerate and bitrate_mode (apropos, 
> is there some documentation about this one?) without noticeable effect. 
> 
>         Also, I get this message when initializing the cards. Can it be 
> related to the problem?
> 
> > ivtv: Encoder revision: 0x02050032
> > ivtv: Encoder Firmware may be buggy, use version 0x02040011
> 
> 
>     If someone has experienced a similar problem please tell me if there is a 
> solution for it. Or maybe that's a normal thing and I'm just being a bit too 
> picky...
> 
>     Thanks,
> 
>             Alberto
> 
> 
> -------------------------------------------------------
> 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_idt12&alloc_id344&op=click
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel

-- 
---
 Chris Kennedy / [EMAIL PROTECTED]
  Engineer KMOS-TV/KTBG-FM
  Broadcasting Services Department
  Central Missouri State University


-------------------------------------------------------
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_idt12&alloc_id344&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to