Simon Koch wrote:
> On 2/7/06, *Simon Koch* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
> On 2/5/06, *Simon Koch* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> On 12/4/05, *Hans Verkuil* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> On Sunday 04 December 2005 05:17, Simon Koch wrote:
>> On 12/2/05, Bryan Mayland <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>> > Keith C wrote:
>> > > Wow, I finally was able to play back your clip (VLC
> didn't seem
>> > > to do it and Safari on Mac mangled the file, but
> mplayer from a
>> > > firefox download worked). Thats a very strange
> flash. I got a
>> > > screen grab of it. Its a partially shifted (or
> interlaced) frame
>> > > that only occurs for a single frame. This needs
> someone from the
>> > > dev list to look at it, so I'm cross posting it to
> that list.
>> > >
>> > > Here's the screen grab (its a tiff, and its 776 Kb) :
>> > > http://allesys.com/images/flash.tiff
>> >
>> > Thanks for the tiff, I couldn't play the file either.
>> >
>> > Zot! I've got the same issue on a PVR-250, one frame
> every so
>> > often (anywhere between 10secs and a couple minutes)
> has as the
>> > bottom of its frame shifted horizontally off *just*
> like that. I
>> > just assumed my card was crapping out, since my PVR-150
> didn't do
>> > it. Now I'm going to have to investigate. Running
> Kubuntu 5.10
>> > and ivtv branches/0.4 and lirc-0.7.2 .
>> >
>> > _______________________________________________
>> > ivtv-devel mailing list
>> > [email protected]
> <mailto:[email protected]>
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>>
>> I'm also having this problem on a PVR-250. However, I
> find that I
>> only get it with 0.4.0. The version I used before 0.4.0
> was 0.3.7c,
>> and I don't see this with 0.3.7c and firmware 0x02040011 or
>> 0x02040024. I see it on 0.4.0with both of those
> firmwares and with
>> 0x02050032. I'm using the S-Video in
>> on my 250. The PVR-500 in the same system using its
> tuners does not
>> exhibit this problem. I always record at 640x480.
>>
>> Simon
>
> As is usual in these cases: try to determine the exact
> version where you
> see this for the first time. Then I can see what changed
> and possibly
> broke something.
>
> Hans
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected] <mailto:[email protected]>
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
> <http://ivtvdriver.org/mailman/listinfo/ivtv-devel>
>
>
> I finally tracked down the change that caused this: #2704, in
> ivtv-streams.c. When I back out that change, the flashes go
> away but the ghosting that change fixed is back. Hopefully,
> both problems can be fixed, but that's beyond my expertise.
> If we're stuck with one or the other, I vote for the
> ghosting. It's much less noticable than the flashes.
>
> Simon
>
>
> No, I take that back. The flashes are back again today. Odd that
> none appeared when I watched video after changing the driver.
> Maybe they don't happen right after loading the driver? I'll
> study it some more.
>
> Simon
>
>
> Ok, this time I think I've really got it. About a week ago, I undid
> the change from revision 2690. I haven't seen any of the flashes
> since. I haven't noticed any jitter like the commit message says, but
> I'm not really sure what I should be looking for.
>
> Here's my 250's portion of the ivtv init messages, in the hopes that
> it will help identify a way to discern which cards need ivtv_vapi(itv,
> 0xdc, 2, 3, 1) and which need ivtv_vapi(itv, 0xdc, 2, 3, 0):
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.4.2 (tagged release) loading
> ivtv: Linux version: 2.6.15.1 <http://2.6.15.1> SMP PENTIUMIII gcc-3.4
> 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: User specified WinTV PVR 250 card (detected cx23416 based chip)
> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
> msp3400 1-0040: chip=MSP4448G-A2 +nicam +simple +simpler +radio
> mode=simpler
> msp3400 1-0040: msp34xxg daemon started
> ivtv0: i2c attach to card #0 ok [client=MSP4448G-A2, addr=40]
> tveeprom 1-0050: Hauppauge model 32032, rev B326, serial# 7155146
> tveeprom 1-0050: tuner model is Temic 4036FY5 (idx 26, type 8)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is MSP4448 (idx 27)
> tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
> tveeprom 1-0050: has no radio, has IR remote
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB
> total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers
> (2048KB total)
> tuner 1-0061: type set to 8 (Temic NTSC (4036 FY5))
> ivtv0: Initialized WinTV PVR 250, card #0
>
>
> Simon
I reverted the changes from 2690 am running ivtv 0.4.0 with
kernel-2.6.14-1.1656_FC4.
I initially looked at modifying 0.4.3 but am unfamiliar and there were
many changes from 0.4.0, so it was easier to revert the changes in
0.4.0. I got several compile time errors when I tried using 0.4.0 and
2.6.15-1.1831_FC4. So I rolled back to kernel-2.6.14.
I typically see the flashes immediatly but have not seen any thus far.
I'll keep running this for the next week or so. I wonder what
*Jitter* refers to in the comment as I don't see anything obvious (yet).
Great work Simon!
Al
My info:
01:09.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
Subsystem: Hauppauge computer works Inc. WinTV PVR 250
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at d4000000 (32-bit, prefetchable) [size=64M]
Capabilities: [44] Power Management version 2
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.14-1.1656_FC4 686 REGPARM 4KSTACKS gcc-4.0
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 250 card (iTVC16 based)
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
lirc_dev: lirc_register_plugin: sample_rate: 10
tveeprom: ivtv version
tveeprom: Hauppauge: model = 32062, rev = B185, serial# = 2868847
tveeprom: tuner = TCL 2002N 6A (idx = 85, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP3445 (type = c)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
msp3400 2-0040: ivtv driver
msp3400 2-0040: chip=MSP3445G-B8 +nicam +simple +simpler +radio mode=simpler
ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40]
msp3400 2-0040: msp34xxg daemon started
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 250, card #0
ivtv: ==================== END INIT IVTV ====================
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
