Re: [ivtv-devel] Invalid PGM index

On Friday 16 February 2007 06:57, Ricardo Lugo wrote: Hans, I've been using the trunk r3799, and keep getting the following warnings in my dmesg. Feb 15 20:40:59 tube kernel: ivtv0 warning: Invalid PGM index 178891420 (= 400) Feb 15 20:41:43 tube kernel: ivtv0 warning: Invalid PGM index

Re: [ivtv-devel] System (practically) non-responsi ve after several hours...no clues

Rich, Thanks for the report, I've been able to reproduce this and I'm now investigating. Regards, Hans On Friday 16 February 2007 02:11, Rich Kadel wrote: OK... Some more data for you, based on your questions: 1. It is sliced. I am reading it from /dev/vbi[x]. 2. I tried some

[ivtv-devel] [linux-dvb] Re: RFC: MPEG encoding and decoding V4L2 API additions

Mauro Carvalho Chehab writes: manufactured by a plethora of vendors (Technotrend, Hauppauge, Galaxis and many others ) making it very popular. These cards are popularly knowns as the AV7110 based Full Fledged (FF) cards. If the mpeg implementation on DVB API is generic enough to

Re: [ivtv-devel] System (practically) non-responsive after several hours...no clues

Hans, OK. Thanks. Those messages are gone. However, now it's exposing something new that wasn't a problem with 0.10.0rc1. I started losing a lot of data, and getting another LARGE set of log messages. I restarted my app, started reading in VBI from 8 tuners (no problem there), and then I

Re: [ivtv-devel] System (practically) non-responsi ve after several hours...no clues

On Friday 16 February 2007 19:03, Rich Kadel wrote: Hans, OK. Thanks. Those messages are gone. However, now it's exposing something new that wasn't a problem with 0.10.0rc1. I started losing a lot of data, and getting another LARGE set of log messages. I restarted my app, started reading

Re: [ivtv-devel] System (practically) non-responsive after several hours...no clues

Feb 16 09:07:35 server2 kernel: ivtv0: All encoder VBI stream buffers are full. Dropping data. Feb 16 09:07:35 server2 kernel: ivtv0: Cause: the application is not reading fast enough. Note that these messages are from different cards (ivtv0 and ivtv1)! Those were just examples. These

Re: [ivtv-devel] RFC: MPEG encoding and decoding V4L2 API additions

On 2/17/07, hermann pitton [EMAIL PROTECTED] wrote: Am Freitag, den 16.02.2007, 22:51 +0100 schrieb hermann pitton: Hi, Am Freitag, den 16.02.2007, 19:55 +0400 schrieb Manu Abraham: On 2/16/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: ... API 's are meant to be hardware

Re: [ivtv-devel] RFC: MPEG encoding and decoding V4L2 API additions

Hi, Am Freitag, den 16.02.2007, 19:55 +0400 schrieb Manu Abraham: On 2/16/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: If the mpeg implementation on DVB API is generic enough to work with non-av7110 hardware, API 's are meant to be hardware independant. Probably rjkm has

Re: [ivtv-devel] RFC: MPEG encoding and decoding V4L2 API additions

Am Freitag, den 16.02.2007, 22:51 +0100 schrieb hermann pitton: Hi, Am Freitag, den 16.02.2007, 19:55 +0400 schrieb Manu Abraham: On 2/16/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: ... API 's are meant to be hardware independant. Probably rjkm has cleared the rest of your

Re: [ivtv-devel] RFC: MPEG encoding and decoding V4L2 API additions

On 2/17/07, hermann pitton [EMAIL PROTECTED] wrote: Am Samstag, den 17.02.2007, 02:58 +0400 schrieb Manu Abraham: On 2/17/07, hermann pitton [EMAIL PROTECTED] wrote: Am Freitag, den 16.02.2007, 22:51 +0100 schrieb hermann pitton: Hi, Am Freitag, den 16.02.2007, 19:55 +0400

Re: [ivtv-devel] RFC: MPEG encoding and decoding V4L2 API additions

Am Samstag, den 17.02.2007, 02:58 +0400 schrieb Manu Abraham: On 2/17/07, hermann pitton [EMAIL PROTECTED] wrote: Am Freitag, den 16.02.2007, 22:51 +0100 schrieb hermann pitton: Hi, Am Freitag, den 16.02.2007, 19:55 +0400 schrieb Manu Abraham: On 2/16/07, Mauro Carvalho Chehab