I too am getting the svideo noise.  Popping, crackling, but also a strange
periodic (30 Hz?)  distortion, kind of like the audio dropping out.  I
have not graphically looked at the audio to see exactly what is going on.
It is almost like it is playing back a frame of audio too quickly, running
out of buffer, then waiting for the next frame of audio.
I am still working my way backwards through the drivers to determine when
this started.
I am using an NTSC WinTV-PVR-150MCE.
I can supply my modprobe.conf and dmesg dump but everything looks real
clean there.

Thanks for all of the great work.

Alan



> Hi Chris,
>
> I dropped back to 0.3.3y. VBI teletext is much worse with 0.3.4a. From
> looking at the output of osc (from zvbi-0.2.8/test) I get the impression
> VBI does not correctly sync...
>
> If I try to read teletext while watching TV (mplayer /dev/video), VBI
> seems not to be available (that is starting the teletext app mtt after
> mplayer).
> If I do it the other way round (first mtt then mplayer) the picture gets
> block artefacts and depending on the content (it seems) mplayer
> complains after a while about my system being to slow. (Duron 1600)
>
> Btw. audio on tuner is perfect while on composite and svideo it has
> noise. It's not distorted, rather like listening to a dirty LP (The old
> disks which were read by a diamod scratching the groove). Sometimes it
> mutes by itself.
>
> I've got a PAL PVR-150:
> tveeprom: Hauppauge: model = 26034, rev = C197, serial# = 7702916
> tveeprom: tuner = LG PAL (TAPE Series) (idx = 97, type = 55)
> tveeprom: tuner fmt = PAL(B/G) PAL(D/K) (eeprom = 0x44, v4l2 = 0x00000e07)
> tveeprom: audio_processor = MSP3400C (type = 4)
> I use pal=G in modprobe.conf
>
> Chris Kennedy wrote:
>> This makes the vbi line size dynamic and change depending on
>> your digitizer, seems that the saa7115 needs one size, while the
>> cx25840 needs another, and so now the driver adjusts for whichever
>> card you have (seems to miss characters in the vbi stream if the
>> size isn't right, at least for CC).  Please test in PAL for teletext
>> and NTSC for CC and let me know how it works.
>>
>> Also in utils/ there is a new program called capture, which is taken
>> from the zvbi test utils directory and modified to include vbi.c in
>> it.  This requires some defines changed to point to the zvbi source
>> (available from zapping.sf.net), and can be used to get sliced vbi
>> out of the pvr150/500 cards (though software slicing), and right now
>> will print out CC using the -O option just as nice as vbi.c will.
>> It also is good to test raw output with, and should work the same
>> consistently with any pvr card, showing raw output or sliced output
>> I think (and shows how to use zvbi to manipulate the VBI data).
>>
>>
>> #0.3.4a: http:/www.ivtv.tv/releases/ivtv-0.3/
>>
>>
>> Thanks,
>> Chris
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>
>



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to