zapping-misc — General discussion

Re: [Zapping-misc] VBI parity errors on NTSC channel 56 - known towork elsewhere

[Michael S. <msc...@us...>]

On Thu, 2006-07-20 at 16:12 -0700, Rich Kadel wrote:
> I have tried to decipher the zvbi code where it is doing
> the slicing, but the huge macros, and my lack of knowledge
> in signal processing has made it pretty much impossible.
> If you can read the embedded images below, you see the bad
> waveform on top (channel 56) and a good waveform on the
> bottom (channel 56).

Yeah they transmit an incorrect signal with the clock run-in
shifted by 1/2 cycle. Please try this change:

diff -Nurdp src/raw_decoder.c src/raw_decoder.c
--- src/raw_decoder.c       Fri Jul 21 06:17:38 2006
+++ src/raw_decoder.c       Fri Jul 21 06:17:44 2006
@@ -202,7 +202,7 @@ _vbi_service_table [] = {
                { 21, 0 },
                { 21, 0 },
                10500, 1006976, 503488, /* 32 x FH */
-               0x00005551, 0x7FF, 14, 2, 2 * 8, VBI_MODULATION_NRZ_LSB,
+               0x03, 0x0F, 4, 0, 2 * 8, VBI_MODULATION_NRZ_LSB,
                /* I've seen CC signals on other lines and there's no
                   way to distinguish from the transmitted data. */
                _VBI_SP_FIELD_NUM | _VBI_SP_LINE_NUM,
@@ -213,7 +213,7 @@ _vbi_service_table [] = {
                { 0, 284 },
                { 0, 284 },
                10500, 1006976, 503488, /* 32 x FH */
-               0x00005551, 0x7FF, 14, 2, 2 * 8, VBI_MODULATION_NRZ_LSB,
+               0x03, 0x0F, 4, 0, 2 * 8, VBI_MODULATION_NRZ_LSB,
                _VBI_SP_FIELD_NUM | _VBI_SP_LINE_NUM,
        }, {
                VBI_SLICED_2xCAPTION_525, /* NOT CONFIRMED */ 

I thought comparing CRI and start bits was a good idea to identify
caption signals more reliably, but testing only the start bits
should work as well.

Michael

Re: [Zapping-misc] VBI parity errors on NTSC channel 56 - known towork elsewhere

[Rich K. <ric...@kn...>]

Michael - I managed a kludge. I still don't know how zvbi is decoding the
waveform, but I managed to modify the waveform before the slicing with the
following code in v4l2_read_frame (io-v4l2k.c):

 

        r = read(v->fd, raw->data, raw->size);

 

int row=11; // line 21

int src_w=1440;

int rowstart=row*src_w;

int offset=25;

memcpy(raw->data+rowstart, raw->data+rowstart+offset, 450);

 

row=23; // line 284

rowstart=row*src_w;

memcpy(raw->data+rowstart, raw->data+rowstart+offset, 450);

 

This shifts the clock run-in signal on lines 21 and 284 to the left by 25
samples.  Once I did this, the Closed Caption and XDS data came through
cleanly for the first time!

 

I don't know if there is a clean fix for this issue that can be done.  I
definitely don't know how to do it.  I'll add a parameter in a one-off
version for my own purposes until there is a better solution.

 

Let me know what you think.

 

Thanks,

Rich

 

--

 

Rich Kadel

Know'bout, Inc.

(858) 433-1747

www.knowbout.com

 

Do you know about Know'bout?

 

  _____  

From: Rich Kadel [mailto:ric...@kn...] 
Sent: Thursday, July 20, 2006 4:12 PM
To: 'Michael Schimek'
Cc: 'zap...@li...'
Subject: RE: [Zapping-misc] VBI parity errors on NTSC channel 56 - known
towork elsewhere

 

Michael,

 

I have tried to decipher the zvbi code where it is doing the slicing, but
the huge macros, and my lack of knowledge in signal processing has made it
pretty much impossible.  If you can read the embedded images below, you see
the bad waveform on top (channel 56) and a good waveform on the bottom
(channel 56).

 

I'm not sure the significance of the yellow line, but all of my other
channels look like this channel 57 example.  On Channel 56, as you see, the
first yellow line goes through the top of the third and seventh sine waves.

 

More importantly, it looks like the "one" start bit (square wave) is in the
correct position.  So it is only the clock bits that appear to be shifted to
the right (by about 25 pixels).  The clock bits are encroaching on the "001"
start bits, bleeding into S1.

 

Again, any suggestion, even a kludge, that would help me fix the waveform or
the processing to allow it to read CC on Channel 56 would be greatly
appreciated.  Thanks. 

 

[pictures removed]

 

--

 

Rich Kadel

Know'bout, Inc.

(858) 433-1747

www.knowbout.com

 

Do you know about Know'bout?

 

 

-----Original Message-----
From: Michael Schimek [mailto:msc...@us...] 
Sent: Thursday, July 20, 2006 1:19 AM
To: Rich Kadel
Cc: zap...@li...
Subject: Re: [Zapping-misc] VBI parity errors on NTSC channel 56 - known
towork elsewhere

 

On Sun, 2006-07-16 at 20:10 -0700, Rich Kadel wrote:

> I recently started using zvbi to extract CC data from my

> PVR-150, 250, and 500 cards.  Generally, it works pretty

> well.  There are a few channels where I get occasional

> parity errors (originally I assumed it was just a low

> signal), but one channel (NTSC 56 - The History Channel)

> just does not work. [...]

 

It's probably the waveform. When you run the osc tool what's

different on channel 56?

 

> One of the ivtv developers suggested the problem might be

> with using hardware conversion of raw VBI to sliced.  The

> ivtv developer thought I could switch zvbi to software

> decoding by using --cc-dump, but that option no longer

> works.  I'm a developer myself, but not a driver or

> low-level IO expert, so a lot of the code is over my head

> at this point, and I'm not in a position to try to become

> an expert right now.  But from stepping through zvbi in a

> debugger, it APPEARS to be doing software decode/slicing.

> In any case, if there is a way to try an alternative solution

> (hardware if I'm doing software, or software if I'm doing

> hardware), I can't find the option to switch it.

 

You're right, currently zvbi supports only software conversion. Perhaps

the hardware conversion on the SAA 7115 works better, and that's

certainly something I want to support in zvbi, but I'm too busy now.

 

The capture --cc-dump option was replaced by decode --cc which gives

more useful data.

 

Michael

 

 

Re: [Zapping-misc] changing cc page...

[Karol Z. <kza...@cr...>]

basically what I need is to get clear english cc text and if it possible
get spanish at the same time... I was trying to hack decode.c and
ntsc-cc.c, but without satisfied results... I'm not a C programmer :(...

I'm using libzvbi-0.2.22

Regards
Karol Zapolski

On Thu, 2006-07-20 at 11:54 +0200, Michael Schimek wrote:
> On Wed, 2006-07-19 at 16:21 -0400, Karol Zapolski wrote: 
> > How can I change page number in zvbi-ntsc-cc?
> > 
> > While I capture cc text on msnbc, sometimes I get spanish cc text...
> > and the second question is :
> > How can I capture both english and spanish cc text at the same time?
> 
> Is this zvbi-ntsc-cc from libzvbi-0.2.18? The current version should
> drop all caption from the second field.
> 
> (zvbi-)ntsc-cc doesn't properly demultiplex the caption channels, much
> less record them all. It's just a stopgap until my own decoder is up to
> the task. When it's really urgent I could hack something.
> 
> > On Wed, 2006-07-19 at 14:00 -0700, Rich Kadel wrote:
> > I'm not an expert on this, but I may be able to answer your question since
> > it sounds similar to experiments I've performed with zvbi.
> > 
> > If you use decode.c as an example, the "caption_command" method has a
> > variable "ch".  This variable is the "Channel".  You may also need to know
> > the "Field", which is Field 1 for line 21 and Field 2 for line 284.  (There
> > is an "f" variable in the same caption_command() method, but I don't know if
> > that variable is referring to the same field.
> > 
> > The captioning data channels are:
> > 
> > CC1 - field 1, channel 1
> > CC2 - field 1, channel 2
> > CC3 - field 2 (line 284), channel 1
> > CC4 - field 2, channel 2
> >
> > Your English captions are probably on CC1 and Spanish on CC2.
> 
> I think CC1 and CC3.
> 
> > You can write some simple code to demux them by branching on
> > the "ch" variable, when processing line 21, and you can probably
> > ignore line 284 data if this is all you want to do.
> 
> It should be trivial to choose between f1 and f2 in ntsc-cc.c, but the
> code doesn't look like it can separate CC3 from XDS data, which is also
> transmitted on f2.
> 
> Michael
> 

Re: [Zapping-misc] VBI parity errors on NTSC channel 56 - known to work elsewhere

[Michael S. <msc...@us...>]

On Sun, 2006-07-16 at 20:10 -0700, Rich Kadel wrote:
> I recently started using zvbi to extract CC data from my
> PVR-150, 250, and 500 cards.  Generally, it works pretty
> well.  There are a few channels where I get occasional
> parity errors (originally I assumed it was just a low
> signal), but one channel (NTSC 56 =E2=80=93 The History Channel)
> just does not work. [...]

It's probably the waveform. When you run the osc tool what's
different on channel 56?

> One of the ivtv developers suggested the problem might be
> with using hardware conversion of raw VBI to sliced.  The
> ivtv developer thought I could switch zvbi to software
> decoding by using --cc-dump, but that option no longer
> works.  I=E2=80=99m a developer myself, but not a driver or
> low-level IO expert, so a lot of the code is over my head
> at this point, and I=E2=80=99m not in a position to try to become
> an expert right now.  But from stepping through zvbi in a
> debugger, it APPEARS to be doing software decode/slicing.
> In any case, if there is a way to try an alternative solution
> (hardware if I=E2=80=99m doing software, or software if I=E2=80=99m doing
> hardware), I can=E2=80=99t find the option to switch it.

You're right, currently zvbi supports only software conversion. Perhaps
the hardware conversion on the SAA 7115 works better, and that's
certainly something I want to support in zvbi, but I'm too busy now.

The capture --cc-dump option was replaced by decode --cc which gives
more useful data.

Michael

Re: [Zapping-misc] changing cc page...

[Michael S. <msc...@us...>]

On Wed, 2006-07-19 at 16:21 -0400, Karol Zapolski wrote: 
> How can I change page number in zvbi-ntsc-cc?
> 
> While I capture cc text on msnbc, sometimes I get spanish cc text...
> and the second question is :
> How can I capture both english and spanish cc text at the same time?

Is this zvbi-ntsc-cc from libzvbi-0.2.18? The current version should
drop all caption from the second field.

(zvbi-)ntsc-cc doesn't properly demultiplex the caption channels, much
less record them all. It's just a stopgap until my own decoder is up to
the task. When it's really urgent I could hack something.

> On Wed, 2006-07-19 at 14:00 -0700, Rich Kadel wrote:
> I'm not an expert on this, but I may be able to answer your question since
> it sounds similar to experiments I've performed with zvbi.
> 
> If you use decode.c as an example, the "caption_command" method has a
> variable "ch".  This variable is the "Channel".  You may also need to know
> the "Field", which is Field 1 for line 21 and Field 2 for line 284.  (There
> is an "f" variable in the same caption_command() method, but I don't know if
> that variable is referring to the same field.
> 
> The captioning data channels are:
> 
> CC1 - field 1, channel 1
> CC2 - field 1, channel 2
> CC3 - field 2 (line 284), channel 1
> CC4 - field 2, channel 2
>
> Your English captions are probably on CC1 and Spanish on CC2.

I think CC1 and CC3.

> You can write some simple code to demux them by branching on
> the "ch" variable, when processing line 21, and you can probably
> ignore line 284 data if this is all you want to do.

It should be trivial to choose between f1 and f2 in ntsc-cc.c, but the
code doesn't look like it can separate CC3 from XDS data, which is also
transmitted on f2.

Michael

Re: [Zapping-misc] changing cc page...

[Rich K. <ric...@kn...>]

Karol,

I'm not an expert on this, but I may be able to answer your question since
it sounds similar to experiments I've performed with zvbi.

If you use decode.c as an example, the "caption_command" method has a
variable "ch".  This variable is the "Channel".  You may also need to know
the "Field", which is Field 1 for line 21 and Field 2 for line 284.  (There
is an "f" variable in the same caption_command() method, but I don't know if
that variable is referring to the same field.

The captioning data channels are:

CC1 - field 1, channel 1
CC2 - field 1, channel 2
CC3 - field 2 (line 284), channel 1
CC4 - field 2, channel 2

Your English captions are probably on CC1 and Spanish on CC2.  You can write
some simple code to demux them by branching on the "ch" variable, when
processing line 21, and you can probably ignore line 284 data if this is all
you want to do.

Rich

--

Rich Kadel
Know'bout, Inc.
(858) 433-1747
www.knowbout.com

Do you know about Know'bout?

-----Original Message-----
From: zap...@li...
[mailto:zap...@li...] On Behalf Of Karol
Zapolski
Sent: Wednesday, July 19, 2006 1:22 PM
To: zap...@li...
Subject: [Zapping-misc] changing cc page...

Hello,

How can I change page number in zvbi-ntsc-cc?

While I capture cc text on msnbc, sometimes I get spanish cc text...
and the second question is :
How can I capture both english and spanish cc text at the same time?

Best regards
Karol Zapolski



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Zapping-misc mailing list
Zap...@li...
https://lists.sourceforge.net/lists/listinfo/zapping-misc

[Zapping-misc] changing cc page...

[Karol Z. <kza...@cr...>]

Hello,

How can I change page number in zvbi-ntsc-cc?

While I capture cc text on msnbc, sometimes I get spanish cc text...
and the second question is :
How can I capture both english and spanish cc text at the same time?

Best regards
Karol Zapolski

[Zapping-misc] VBI parity errors on NTSC channel 56 - known to work elsewhere

[Rich K. <ric...@kn...>]

Hello,

 

I recently started using zvbi to extract CC data from my PVR-150, 250, and
500 cards.  Generally, it works pretty well.  There are a few channels where
I get occasional parity errors (originally I assumed it was just a low
signal), but one channel (NTSC 56 - The History Channel) just does not work.
For example:

 

[kadel@knowbout2 test]$ ivtv-tune -d/dev/video4 -c56

/dev/video4: 415.250 MHz  (Signal Detected)

[kadel@knowbout2 test]$ capture -d /dev/vbi4 --sliced | decode --cc --xds CC
line= 21 cmd 0x00 0x00 null CC line=284 text 0x6c 0x75 'lu'

Parity error in CC line=21  >0xc0 0x40.

CC line=284 text 0x77 0x67 'wg'

CC line= 21 cmd 0x00 0x00 null

Parity error in CC line=21  0x40 >0xc0.

Parity error in CC line=21  >0xc0 >0xc0.

Parity error in CC line=21  >0xc0 >0x00.

CC line= 21 cmd 0x00 0x00 null

Parity error in XDS data.

Parity error in CC line=284  0xc4 >0x63.

CC line= 21 cmd 0x14 0x26 roll-up caption ch=0 f=0 rows=3 CC line=284 cmd
0x03 0x01 XDS packet start/continue Parity error in XDS data.

Parity error in CC line=284  >0x63 0xec.

Parity error in CC line=21  >0x5c 0xec.

Parity error in CC line=21  >0x27 >0x30.

Parity error in XDS data.

Parity error in CC line=284  0xc7 >0x3f.

CC line= 21 cmd 0x00 0x00 null

Parity error in CC line=21  0x80 >0xc0.

CC line=284 text 0x73 0x74 'st'

Parity error in XDS data.

Parity error in CC line=284  >0xf9 0x43.

 

I am using the IVTV driver, and have been actively discussing this problem
on the IVTV mailing list.  The belief is that IVTV is not the problem.  The
card seems to be fine too because I can put it in a Windows Media Center
box, and the CC data from Channel 56 works fine there.

 

So that brings me back to zvbi.

 

One of the ivtv developers suggested the problem might be with using
hardware conversion of raw VBI to sliced.  The ivtv developer thought I
could switch zvbi to software decoding by using --cc-dump, but that option
no longer works.  I'm a developer myself, but not a driver or low-level IO
expert, so a lot of the code is over my head at this point, and I'm not in a
position to try to become an expert right now.  But from stepping through
zvbi in a debugger, it APPEARS to be doing software decode/slicing.  In any
case, if there is a way to try an alternative solution (hardware if I'm
doing software, or software if I'm doing hardware), I can't find the option
to switch it.

 

If the problem is that zvbi may not be tolerant to some variations in the
waveform, is there a developer out there that would be willing to look into
this problem if I provide some samples of the raw data?

 

Let me know the best way to provide it.  Would I just run "capture >
capture.raw"?  

 

Thanks,

Rich

 

 

--

 

Rich Kadel

Know'bout, Inc.

(858) 433-1747

www.knowbout.com

 

Do you know about Know'bout?

 

[Zapping-misc] XF86DGANoDirectVideoMode error

[<nun...@ne...>]

Hi there.

First of all, I'm sorry if this question was posted before. I didn't 
not find the search feature in this mailing list.

I'm looking for a hand with zapping (0.9.2-2) in Debian Sarge.

I have a nVidia card (GeForce4 MX 4000 AGP) and a TV tuner PCTV 
Pinnacle (Philips Semiconductors SAA7133 Audio+video broadcast decoder 
- PCI).

When I attempt to run zapping, I get msg saying:
The program zapping received an X Window System error. This probably 
reflects a bug in the program. The error was:  
'XF86DGANoDirectVideoMode'.

I fussed a bit in google and it seems to be related to a dga module 
that nvidia driver doesn't carry.

Is there a way to resolve this?

Thanks

Re: [Zapping-misc] Xpert DVB-T and FC5 Woes

[Michael S. <msc...@us...>]

Hi Gordon,

> I have an Xpert DVB-T card under Fedora Core 5 and I cannot get zapping, 
> xawtv or tvtime to work at all.

Zapping and TVtime do not support DVB-only devices. If this card is one,
the nice folks on the linux-dvb mailing list may be able to help you:
http://www.linuxtv.org/cgi-bin/mailman/listinfo

> When I do the channel scan in zapping, the program just crashes.

Which version of Zapping did you try? What must I do to reproduce this,
open the channel editor, click on the scan button, wave a dead
chicken? :-)

Michael

[Zapping-misc] Xpert DVB-T and FC5 Woes

[Gordon M. <gor...@bt...>]

Hi

I have an Xpert DVB-T card under Fedora Core 5 and I cannot get zapping, 
xawtv or tvtime to work at all.

It looks like the modules are loaded OK and this is part of the dmesg 
output :

CORE cx88[0]: subsystem: 17de:08a6, board: KWorld/VStream XPert DVB-T 
[card=14,autodetected]
TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
input: cx88 IR (KWorld/VStream XPert D as /class/input/input2
cx88[0]/0: found at 0000:00:0d.0, rev: 5, irq: 19, latency: 64, mmio: 
0xf9000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0


When I do the channel scan in zapping, the program just crashes.

Help !

Re: [Zapping-misc] zapping and kde3.5

[Michael S. <msc...@us...>]

Hi Donn,

> I have been using zapping for several years headache free.
> This system is SuSE10.1 and Nvidia's current file.run
> 
> Zapping has started a strange problem.  That is it will not run and in a 
> xterm it give an error.
> 
> donn@m1l:~> zapping --sync
> 
> ERROR:
> The program 'zapping' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'XF86DGANoDirectVideoMode'.

The nvidia drivers do not support DGA anymore. It isn't required but
older versions of Zapping didn't catch the error. 0.10 should work.

Michael

[Zapping-misc] zapping and kde3.5

[Donn W. <n5...@ha...>]

Hy Group;

I have been using zapping for several years headache free.
This system is SuSE10.1 and Nvidia's current file.run

Zapping has started a strange problem.  That is it will not run and in a 
xterm it give an error.

donn@m1l:~> zapping --sync

ERROR:
The program 'zapping' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XF86DGANoDirectVideoMode'.
   (Details: serial 15 error_code 158 request_code 137 minor_code 1)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() 
function.)

Anyone grasp the cause?

I believe it is a KDE problem more that zapping because in fvwm2 it 
seems not to happen

-- 
73 de Donn Washburn
Ham Callsign N5XWB   Email: " n5...@ha... "
307 Savoy St.        HAMs : " n5...@ar... "
Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador
LL# 1.281.242.3256   VoIP via Skype: n5xwbg
       " http://counter.li.org " #279316

[Zapping-misc] Pinnacle PCTV USB 2.0

[k0zi of G. <th...@gm...>]

hi
I have pinnacle pctv usb 2.0 pal, it is working with tvtime, but when i
start zapping only get audio no video only black screen :(
And in the record settings, there are no codecs :\
System:
fedora core 5 x86-64
David Kozma

Re: [Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Michael S. <msc...@us...>]

On Fri, 2006-05-19 at 02:05 +0200, Leon Woestenberg wrote:
> I am not familiar with exact VBI standards yet, but I assume that VBI
> lies *within* vertical blanking (duh) but *fully outside* the horizontal
> blanking.

The PAL line period is 64 =C2=B5s, the blanking interval 12 =C2=B5s. Nomina=
lly the
first cycle of the Teletext and CC clock run-in reaches into the back
porch. But Teletext, VPS, CC and WSS will all fit within 52 =C2=B5s, and
decoders should tolerate a small offset or even a missing CRI pulse.

720 pixels/line (ITU BT.601, 13.5 MHz) cover 53.3 =C2=B5s, no problems here=
.
768 pixels/line (square pixels, 14.75 MHz) cover 52 =C2=B5s, that's a littl=
e
tight but should also work.

>  Does your osc application put the luminance waveform samples
> back without horizontal compression? (i.e. to keep further away from the
> edges?)

It simulates a capture device conforming to BT.601 like the SAA 71xx
chips. The sampling parameters can change to simulate other devices, but
the signals are supposed to look exactly as defined by the respective
standards. I did not prepare for example to shift signals relative to
each other.

> Too bad I didn't find a video encoder that has full VBI output support,
> but I would guess any TV set-top box must do DVB->VBI?

I don't know if they must. :-)  Many probably do.

Michael

Re: [Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Leon W. <le...@ma...>]

Hello Michael,

On Thu, 2006-05-18 at 18:40 +0200, Michael Schimek wrote:
> On Thu, 2006-05-18 at 14:43 +0200, Leon Woestenberg wrote:
> > I have been thinking about this a bit, I would be happy with having VBI 
> > in the active video lines instead,
> > as I think I have access to equipment to move lines around.
> > 
> > Our signal path would be raw VBI -> sliced VBI -> PES -> sliced VBI 
> > ->raw VBI.
> > 
> > Can libzvbi do the latter and generate raw VBI from the DVB VBI PES and 
> > other formats?
> 
> Sort of. The raw VBI generator is not part of the API yet, and it's not
> optimized in any way. I just used it to test my bit slicer. You can see
> the output by running ./osc --sim --pal in the test directory. Input can
> be Teletext, VPS, PAL/NTSC CC and PAL WSS. Output anything from YUV
> 4:2:0 to BGR 5:5:5:1, at any sampling frequency.

Wow, neat. Thanks for that!

> DVB PES is supported,
> other formats if you can convert them to sliced VBI.
>
Yes, I saw the osc application, didn't know then it used parts of
libzvbi not API-ized yet.

> 
> If you want I'll brush up the interface and write a little DVB-to-raw
> example.
>
It's not really my call to ask you this, but brushed up interfaces are
nice :-)

The idea is to use a TV-out card to put VBI back into a composite signal
such that it is a legal signal and can be interpreted correctly by
television sets.

I am not familiar with exact VBI standards yet, but I assume that VBI
lies *within* vertical blanking (duh) but *fully outside* the horizontal
blanking. Does your osc application put the luminance waveform samples
back without horizontal compression? (i.e. to keep further away from the
edges?)

Too bad I didn't find a video encoder that has full VBI output support,
but I would guess any TV set-top box must do DVB->VBI?

Regards,

Leon Woestenberg.

Re: [Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Michael S. <msc...@us...>]

On Thu, 2006-05-18 at 14:43 +0200, Leon Woestenberg wrote:
> I have been thinking about this a bit, I would be happy with having VBI 
> in the active video lines instead,
> as I think I have access to equipment to move lines around.
> 
> Our signal path would be raw VBI -> sliced VBI -> PES -> sliced VBI 
> ->raw VBI.
> 
> Can libzvbi do the latter and generate raw VBI from the DVB VBI PES and 
> other formats?

Sort of. The raw VBI generator is not part of the API yet, and it's not
optimized in any way. I just used it to test my bit slicer. You can see
the output by running ./osc --sim --pal in the test directory. Input can
be Teletext, VPS, PAL/NTSC CC and PAL WSS. Output anything from YUV
4:2:0 to BGR 5:5:5:1, at any sampling frequency. DVB PES is supported,
other formats if you can convert them to sliced VBI.

If you want I'll brush up the interface and write a little DVB-to-raw
example.

Michael

Re: [Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Leon W. <le...@ma...>]

Hello all,

Michael Schimek wrote:
> On Wed, 2006-05-10 at 22:31 +0200, Leon Woestenberg wrote:
>   
>> I asked this today on the V4L2 list, but might miss out on a bit of the
>> targetted audience there:
>>
>> Does anyone know of a video card that can playout (raw) VBI in the
>> blanking lines (i.e. through /dev/vout driver-wise).
>>
>> For capture VBI -> playout VBI applications?
>>     
>
> The ivtv driver http://www.ivtvdriver.org can output CC, VPS and WSS
> but no raw VBI data.
>
> The video encoder on my graphics card can also insert CC, but it doesn't
> support raw VBI, accepts only YUYV data at 13.5 MHz and I'm not sure how
> far I could raise the video start.
>   
I have been thinking about this a bit, I would be happy with having VBI 
in the active video lines instead,
as I think I have access to equipment to move lines around.

Our signal path would be raw VBI -> sliced VBI -> PES -> sliced VBI 
->raw VBI.

Can libzvbi do the latter and generate raw VBI from the DVB VBI PES and 
other formats?

Regards,

Leon Woestenberg.

Re: [Zapping-misc] Disregard the first reply RE: Zapping-misc digest, Vol 1 #622 - 1 msg

[Michael S. <msc...@us...>]

On Wed, 2006-05-17 at 03:27 -0500, max Kim wrote:
> I think I gave wrong info about the version.
> I used the version 0.10cvs4, the latest one.
> 
> When I compiled it, it told me that everything's OK. but actually, the v4l2 
> module was not loaded bu instead v4l was loaded, but my chipset, cx2388x, is 
> set up for v4l2, so that it couldn't catch video pictures.

Apart of the bug I mentioned I don't see why Zapping would use V4L when
a driver supports V4L2. (Except in overlay mode using the XVideo-V4L
wrapper, which doesn't know about V4L2.) But even then you should get
video and audio.

Please start Zapping from a terminal window:

 zapping -d --io-debug 2>log

and send me the log file.

Michael

[Zapping-misc] Disregard the first reply RE: Zapping-misc digest, Vol 1 #622 - 1 msg

[max K. <ma...@ho...>]

I think I gave wrong info about the version.
I used the version 0.10cvs4, the latest one.

When I compiled it, it told me that everything's OK. but actually, the v4l2 
module was not loaded bu instead v4l was loaded, but my chipset, cx2388x, is 
set up for v4l2, so that it couldn't catch video pictures.

When I used even the tvtime, compiled from scratch , after switching from 
v4l2 to v4l modules,  it also could not show the pictures- the same thing as 
the zapping.

What  I need to do is just make the module-v4l2 loaded, I think.

I hope it would be helpful for the diagnosis





>From: zap...@li...
>Reply-To: zap...@li...
>To: zap...@li...
>Subject: Zapping-misc digest, Vol 1 #622 - 1 msg
>Date: Sat, 13 May 2006 20:13:13 -0700
>
>Send Zapping-misc mailing list submissions to
>	zap...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/zapping-misc
>or, via email, send a message with subject or body 'help' to
>	zap...@li...
>
>You can reach the person managing the list at
>	zap...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Zapping-misc digest..."
>
>
>Today's Topics:
>
>    1. Re: so frustrated please help me !!! (Michael Schimek)
>
>--__--__--
>
>Message: 1
>Subject: Re: [Zapping-misc] so frustrated please help me !!!
>From: Michael Schimek <msc...@us...>
>To: max Kim <ma...@ho...>
>Cc: zap...@li...
>Date: Fri, 12 May 2006 12:50:14 +0200
>
>On Sun, 2006-05-07 at 14:21 -0500, max Kim wrote:
> > My device,cx2388x chipset,  has support for v4l, v4l2, xvideo etc
> > Other programs ,such as tvtime, kdetv, are working fine except for this.
> > Others also have some bugs though.
> >
> > What I figured ou is as follows:
> >
> > zapping alsway uses the driver of v4l not v4l2 but my device, cx2388x, 
>uses
> > v4l2. I tryed to chage the configuration for the controlbler but failed.
>
>This may be a bug in version 0.10cvs3. Do you use that version? (See
>Help -> About.) Do you get any error messages, video, sound?
>
>Sorry about the delay. The address and subject suggested SPAM.
>
>Michael
>
>
>
>
>--__--__--
>
>_______________________________________________
>Zapping-misc mailing list
>Zap...@li...
>https://lists.sourceforge.net/lists/listinfo/zapping-misc
>
>
>End of Zapping-misc Digest

[Zapping-misc] RE: Zapping-misc digest, Vol 1 #622 - 1 msg

[max K. <ma...@ho...>]

Thanks for your reply
Yes I used the version- 0.10cvs3

I tried previous versions too but in vain.

The zapping uses v4l so it catch motion pictures but does show clear 
pictures ans sound.
The pictures are too zigzaged to watch and listen to that.






>From: zap...@li...
>Reply-To: zap...@li...
>To: zap...@li...
>Subject: Zapping-misc digest, Vol 1 #622 - 1 msg
>Date: Sat, 13 May 2006 20:13:13 -0700
>
>Send Zapping-misc mailing list submissions to
>	zap...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/zapping-misc
>or, via email, send a message with subject or body 'help' to
>	zap...@li...
>
>You can reach the person managing the list at
>	zap...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Zapping-misc digest..."
>
>
>Today's Topics:
>
>    1. Re: so frustrated please help me !!! (Michael Schimek)
>
>--__--__--
>
>Message: 1
>Subject: Re: [Zapping-misc] so frustrated please help me !!!
>From: Michael Schimek <msc...@us...>
>To: max Kim <ma...@ho...>
>Cc: zap...@li...
>Date: Fri, 12 May 2006 12:50:14 +0200
>
>On Sun, 2006-05-07 at 14:21 -0500, max Kim wrote:
> > My device,cx2388x chipset,  has support for v4l, v4l2, xvideo etc
> > Other programs ,such as tvtime, kdetv, are working fine except for this.
> > Others also have some bugs though.
> >
> > What I figured ou is as follows:
> >
> > zapping alsway uses the driver of v4l not v4l2 but my device, cx2388x, 
>uses
> > v4l2. I tryed to chage the configuration for the controlbler but failed.
>
>This may be a bug in version 0.10cvs3. Do you use that version? (See
>Help -> About.) Do you get any error messages, video, sound?
>
>Sorry about the delay. The address and subject suggested SPAM.
>
>Michael
>
>
>
>
>--__--__--
>
>_______________________________________________
>Zapping-misc mailing list
>Zap...@li...
>https://lists.sourceforge.net/lists/listinfo/zapping-misc
>
>
>End of Zapping-misc Digest

Re: [Zapping-misc] so frustrated please help me !!!

[Michael S. <msc...@us...>]

On Sun, 2006-05-07 at 14:21 -0500, max Kim wrote:
> My device,cx2388x chipset,  has support for v4l, v4l2, xvideo etc
> Other programs ,such as tvtime, kdetv, are working fine except for this.
> Others also have some bugs though.
> 
> What I figured ou is as follows:
> 
> zapping alsway uses the driver of v4l not v4l2 but my device, cx2388x, uses 
> v4l2. I tryed to chage the configuration for the controlbler but failed.

This may be a bug in version 0.10cvs3. Do you use that version? (See
Help -> About.) Do you get any error messages, video, sound?

Sorry about the delay. The address and subject suggested SPAM.

Michael

Re: [Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Michael S. <msc...@us...>]

On Wed, 2006-05-10 at 22:31 +0200, Leon Woestenberg wrote:
> I asked this today on the V4L2 list, but might miss out on a bit of the
> targetted audience there:
> 
> Does anyone know of a video card that can playout (raw) VBI in the
> blanking lines (i.e. through /dev/vout driver-wise).
>
> For capture VBI -> playout VBI applications?

The ivtv driver http://www.ivtvdriver.org can output CC, VPS and WSS
but no raw VBI data.

The video encoder on my graphics card can also insert CC, but it doesn't
support raw VBI, accepts only YUYV data at 13.5 MHz and I'm not sure how
far I could raise the video start.

Michael

[Zapping-misc] Any device supporting /dev/vout *with* VBI?

[Leon W. <le...@ma...>]

Hello,

I asked this today on the V4L2 list, but might miss out on a bit of the
targetted audience there:

Does anyone know of a video card that can playout (raw) VBI in the
blanking lines (i.e. through /dev/vout driver-wise).

For capture VBI -> playout VBI applications?

Regards,

Leon Woestenberg.

Re: [Zapping-misc] Broken WSS

[Michael S. <msc...@us...>]

On Wed, 2006-05-10 at 11:02 +0200, Maarten van Lijden wrote:
> Tried the new 0.2.20 release and the support for wss (via v4l2 video,
> not vbi lines) does not work any more. The example wss file (old wss
> test file) doens't work. Error: "Cannot decode wss" is given, with
> 0.2.19 still works perfectly.

Ugh. A broken check. I'll release a new version.

Michael