zapping-misc — General discussion

[Zapping-misc] crush on debian

[slav0nic0 <sla...@gm...>]

i try run zapping from debian  unstable repo (from testing too), it 
crushed after i select "channels", or "Parametrs" from menu with error:


(zapping:13546): Gtk-CRITICAL **: gtk_list_store_get_value: assertion 
`VALID_ITER (iter, GTK_LIST_STORE(tree_model))' failed

(zapping:13546): GLib-GObject-WARNING **: gtype.c:3337: type id `0' is 
invalid

(zapping:13546): GLib-GObject-WARNING **: can't peek value table for 
type `<invalid>' which is not currently referenced

wtf?=\

Re: [Zapping-misc] Watching VHS with Zapping.

[Steve <bef...@ya...>]

Works now.  The RFC modulator was in a bad outlet.  I also needed to
set the input to "television" and type to "NTSC".

The sound was very bad.  It sounded screecy, like an amp turned to high
no matter how I adjusted the volume, bass, and trebile on my speakers.

I switched to kdetv and I did not have this problem.  I'm not saying
that to flame, just to bring a potential issue to your attention and if
I can find out how I can get rid of that problem.

I like zapping better and would prefer to use it if I could ditch that
problem.

Thanks in advance

Steve


--- Steve <bef...@ya...> wrote:

> Hi;
> 
> About two years ago I used a knoppix linux install with kwintv and an
> RFC modulator to hook up an ancient salvaged VCR directly to my
> computer and watch some old VHS tapes I had.   The old VCR died.  I
> have recently bought a new one and I would like to watch some VHS
> tapes
> again on my computer.  I think I forgot some of the things I did as I
> am not getting results.

[Zapping-misc] NVidia

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

Hey Group;

I know that "Nvidia" current.run is causing the problem with Zapping 
failing.  Is there any CVS or otherwise effort to use the lost direct 
memory problem in zapping or any other Xwindows based TV app?
-- 
73 de Donn Washburn
307 Savoy Street     Email: " n5...@ha... "
Sugar Land, TX 77478 LL# 1.281.242.3256
Ham Callsign N5XWB   HAMs : " n5...@ar... "
VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg
BMW MOA #: 4146 - Ambassador
       " http://counter.li.org " #279316

[Zapping-misc] Watching VHS with Zapping.

[Steve <bef...@ya...>]

Hi;

About two years ago I used a knoppix linux install with kwintv and an
RFC modulator to hook up an ancient salvaged VCR directly to my
computer and watch some old VHS tapes I had.   The old VCR died.  I
have recently bought a new one and I would like to watch some VHS tapes
again on my computer.  I think I forgot some of the things I did as I
am not getting results.

Currently I have:

1. Ubuntu 6.10 ( Edgy )
2. Zapping 0.10cvs6

This HaugePauge TV card ( about 3 -4 years old ):

----------------------------------------------------------------------

TV/Radio Card ( Hauge Pauge )
lspci -vv
----------------------------------------------------------------------

02:02.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
Capture (rev 11)
	Subsystem: Hauppauge computer works Inc. WinTV Series
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (4000ns min, 10000ns max)
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at f47fe000 (32-bit, prefetchable) [size=4K]
	Capabilities: <available only to root>
------------------------------------------------------------------------

I am in the United States so I set the video standard as NTSC and I set
the video input as s-video.

I then turned my VCR on, set it to channel 3, put a tape in, pressed
play, and told zapping to automatically scan for channels.  If found
none.

I get nothing but a blue screen.

Any ideas what I might need to do to play the tape?

Thanks much in advance for any information

Steve

[Zapping-misc] thanks

[Thomas S. <sch...@gm...>]

im using latest cvs build (zapping in ubuntu edgy is broken)
with latest v4l-dvb sources (supporting my hauppauge wintv go2 model).

I've no problems with watching tv or tuning in a station, but teletext
allways crash.
I've also some trouble with recording, sometimes sound is crappy,
sometimes it's out off sync (especialy if i try to record large movies ~
>=1GB.

Is this zapping releaded or is this common with my card?

Best Regards
Tom

Re: [Zapping-misc] libzvbi issues during compilation

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

Hi,

> I have compiled and installed libzvbi.  The libraries are installed in
> /usr/local/lib.  And yet here is the error message from autogen.sh:
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for PACKAGE... yes
> checking for gdk-pixbuf-csource... /usr/bin/gdk-pixbuf-csource
> checking for ZVBI... no
> *** Could not find libzvbi >= 0.2.9.  The library is required
> *** for Teletext, caption/subtitles and OSD.  The latest version
> *** is available from http://zapping.sourceforge.net.  To compile
> *** Zapping without libzvbi run ./configure --without-zvbi
> 
> Any ideas how to get around this?  I've tried setting my ZVBI_LIBS
> environment variable to point to the libzvbi library files, but that
> has no effect.

Perhaps /usr/local is not in the pkg-config search path?
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure ... may help.

Michael

[Zapping-misc] libzvbi issues during compilation

[Robert D. <rdi...@gm...>]

Hi.

I'm trying to compile zapping with zvbi support and the autogen.sh and
configure.sh scripts keep complaining about not finding zvbi.

I have compiled and installed libzvbi.  The libraries are installed in
/usr/local/lib.  And yet here is the error message from autogen.sh:
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PACKAGE... yes
checking for gdk-pixbuf-csource... /usr/bin/gdk-pixbuf-csource
checking for ZVBI... no
*** Could not find libzvbi >= 0.2.9.  The library is required
*** for Teletext, caption/subtitles and OSD.  The latest version
*** is available from http://zapping.sourceforge.net.  To compile
*** Zapping without libzvbi run ./configure --without-zvbi

Any ideas how to get around this?  I've tried setting my ZVBI_LIBS
environment variable to point to the libzvbi library files, but that
has no effect.

-Rob

[Zapping-misc] Zapping crashes

[k_f <k_...@16...>]

Hello,

 I just compiled and installed Zapping 0.10 (cvs6), but the error window pops up after start. I got this by running it in terminal: 

** (zapping:8198): WARNING **: GConf key '/apps/zapping/plugins/deinterlace/method' is unset and has no default. Zapping schemas incomplete or not installed?

Here is the entry I found in /usr/gconf/etc/schemas/zapping.schemas: 

  <schema>
   <key>/schemas/apps/zapping/plugins/deinterlace/method</key>
   <applyto>/apps/zapping/plugins/deinterlace/method</applyto>
   <owner>Zapping</owner>
   <type>string</type>
   <default>disabled</default>
  </schema>

I think the error is caused by this. Any idea how to fix it?
 
By the way if I run it with "Zapping -p", no error pops but the video screen is messed.


regards, 

Fei.K

Re: [Zapping-misc] spanglish cc-text on msnbc

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

On Wed, 2006-09-27 at 16:30 -0400, Karol Zapolski wrote:
> This time I've some problems with mixed cc-text
> While capturing cctext from msnbc - sometime I got spanish captions...

Please send me a sample for my curiosity collection:
./capture --sliced >file

> How to isolate chanels using zvbi?

Try CVS: ./zvbi-ntsc-cc -c -l1

It's a quick hack but maybe it works.

http://zapping.sourceforge.net/ZVBI/Download.html#Anonymous_CVS_Access

> plus last field after 
> ./capture --sliced -d /dev/vbi0 | ./decode -c
> command is not always giving correct text...

Sorry I don't understand.

Michael

[Zapping-misc] spanglish cc-text on msnbc

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

Hello again...
This time I've some problems with mixed cc-text
While capturing cctext from msnbc - sometime I got spanish captions...
How to isolate chanels using zvbi?

I tried change following parameters in
/contrib/ntsc-cc.c
int     ccmode=1;               //cc1 or cc2

and

test/decode.c
ch = (c1 >> 3) & 1; /* channel (language) */

but without result...
plus last field after 
./capture --sliced -d /dev/vbi0 | ./decode -c
command is not always giving correct text...
or maybe I need something else to decode this...

btw. it looks that msnbc uses all features for cc-text - it is a good
testing example.. :)

Best regards
Karol Zapolski

Re: [Zapping-misc] XDS

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

On Sun, 2006-09-24 at 20:27 -0700, David Liontooth wrote: 
> I'm using libzvbi 0.2.22-1 and will run some tests. The first one (here
> I grep % an hour of captured text) shows a lot of "% LENGTH" lines that
> are probably triggered by advertising -- they're not really informative.
> Would it make sense to skip these too?

Try CVS: zvbi-ntsc-cc -x=TITLE[,etc]

> There are also a number of "%" blank lines.

That's fixed now.

> Additional tests this morning don't show this pattern with any
> consistency -- there are only occasional "LENGTH" entries, few blank
> lines, and several new blank TITLE lines:

Do you get blank call signs, program and network names with test/capture
--sliced | test/decode --xds as well?

> NBC doesn't seem to show much on XDS -- by coincidence, they broadcast a
> sequence from FOX news, and embedded in the clip was apparently XDS
> information. Aside from that the file shows no useful XDS about the
> actual show, but I take it this is KNBC's problem, not libzvbi's:
...
> The odd thing is that FOX in LA seem to have misconfigured their XDS
> too, cf. http://www.evertz.com/support#faq1 --

Yeah it seems so. Also the XDS inserter at KNBC should drop channel
info packets and insert its own call sign and network name.

Michael

Re: [Zapping-misc] teletext - particular page...

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

On Sun, 2006-09-24 at 12:45 -0400, Karol Zapolski wrote:
> Hamming error in pmag
> 
> Whats are these errors?

Uncorrectable errors in the packet/magazine byte of a Teletext packet.
Is your signal noisy?

> It is possible that because of loop, I'll miss some subtitles?

Subtitles must not change too quickly to be readable. If your loop can
restart ./capture and ./export before the page is transmitted again you
won't miss any. Of course it would be much more efficient to loop and
print timestamps in ./export itself.

Michael

Re: [Zapping-misc] XDS

[David L. <lio...@co...>]

David Liontooth wrote:
> Michael Schimek wrote:
>   
>> On Mon, 2006-09-11 at 04:05 -0700, David Liontooth wrote:
>>   
>>     
>>> I'm recording some news programs from tv on a regular schedule, and 
>>> would like to use zvbi-ntsc-cc's -x parameter to capture XDS 
>>> information. My problem is that my recordings are scheduled on the hour, 
>>> and programs often run over a bit, so that the new program doesn't start 
>>> until a few minutes later. The result is that the XDS information that 
>>> gets recorded is for the program that is ending rather than the program 
>>> I'm recording.
>>>
>>> I haven't experimented a lot with this, but it looks like XDS 
>>> information is recorded only once, and only at the beginning of the 
>>> capture session. Would it be possible to pass a parameter (something 
>>> like -x 10) to indicate when or how often the XDS information should be 
>>> captured? Or is there a way to do something like this in the existing code?
>>>     
>>>       
>> The app skips repeated XDS packets (source code line 233 or thereabouts),
>> so it should print the XDS info every time it changes.
>>
>> How's the version in CVS? Works for me, after a few tweaks to properly
>> decode my test stream.
>>   
>>     
> I'm using libzvbi 0.2.22-1 and will run some tests. The first one (here
> I grep % an hour of captured text) shows a lot of "% LENGTH" lines that
> are probably triggered by advertising -- they're not really informative.
> Would it make sense to skip these too? There are also a number of "%"
> blank lines.
>
> The only thing I really want is the title ("60 Minutes" below) -- it
> would be very useful to be able to pass a parameter and request only
> some fields.
>
> Dave
>
>
>
> %     CALL: NET6
> %   RATING: (NOT RATED) (72)
> %  NETWORK:
> %    TITLE:
> %
> % TIMECODE: 0/00 0:32
> %   LENGTH: 0:00:00 of 1:00:00
> % TIMECODE: 9/24 19:00
> %    TITLE: 60 Minutes "A"
> %   LENGTH: 0:01:20 of 1:00:00
> %
> %
> %   LENGTH: 0:02:21 of 1:00:00
> %   LENGTH: 0:03:21 of 1:00:00
> %   LENGTH: 0:04:21 of 1:00:00
> %
> %   LENGTH: 0:05:21 of 1:00:00
> %
> %
> %   LENGTH: 0:06:21 of 1:00:00
>   
Additional tests this morning don't show this pattern with any
consistency -- there are only occasional "LENGTH" entries, few blank
lines, and several new blank TITLE lines:

$ grep % *.txt

NBC doesn't seem to show much on XDS -- by coincidence, they broadcast a
sequence from FOX news, and embedded in the clip was apparently XDS
information. Aside from that the file shows no useful XDS about the
actual show, but I take it this is KNBC's problem, not libzvbi's:

2006-09-25_0430_KNBC_Channel_4_News.txt:%     CALL:  FOX
2006-09-25_0430_KNBC_Channel_4_News.txt:%    TITLE: FOX NEWS SUNDAY
2006-09-25_0430_KNBC_Channel_4_News.txt:%   RATING: (NOT RATED) (72)
2006-09-25_0430_KNBC_Channel_4_News.txt:%  NETWORK:  FOX
2006-09-25_0430_KNBC_Channel_4_News.txt:%    TITLE:
2006-09-25_0430_KNBC_Channel_4_News.txt:%   RATING: (NOT RATED) (88)
2006-09-25_0430_KNBC_Channel_4_News.txt:%

The odd thing is that FOX in LA seem to have misconfigured their XDS
too, cf. http://www.evertz.com/support#faq1 --

2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%   RATING: (NOT RATED) (72)
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%  NETWORK: Evertz
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE: Evertz
Broadcasting
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%     CALL: WEVE
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:% TIMEZONE: UTC-5
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE:
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:% CUR.TIME: 18:15
8/11/2005 UTC
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE: Evertz
Broadcasting
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:% CUR.TIME: 18:16
8/11/2005 UTC
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE:
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:% CUR.TIME: 18:19
8/11/2005 UTC
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE: Evertz
Broadcasting
2006-09-25_0430_KTTV-FOX_A_Current_Affair.txt:%    TITLE:

This one's good -- though the Call, Rating, and Length fields would be
better skipped:

2006-09-25_0500_KABC_Eyewitness_News.txt:%  NETWORK: ABC
2006-09-25_0500_KABC_Eyewitness_News.txt:%     CALL:
2006-09-25_0500_KABC_Eyewitness_News.txt:%    TITLE: ABC'S WORLD NEWS
THIS MORNING
2006-09-25_0500_KABC_Eyewitness_News.txt:%    TITLE:
2006-09-25_0500_KABC_Eyewitness_News.txt:%  NETWORK:
2006-09-25_0500_KABC_Eyewitness_News.txt:%  NETWORK: ABC
2006-09-25_0500_KABC_Eyewitness_News.txt:%   RATING: (NOT RATED) (72)
2006-09-25_0500_KABC_Eyewitness_News.txt:%   LENGTH: 0:02:00 of 3:09:00
2006-09-25_0500_KABC_Eyewitness_News.txt:%   LENGTH: 0:03:00 of 3:09:00
2006-09-25_0500_KABC_Eyewitness_News.txt:%   LENGTH: 0:04:00 of 3:09:00
2006-09-25_0500_KABC_Eyewitness_News.txt:%  NETWORK:
2006-09-25_0500_KABC_Eyewitness_News.txt:%    TITLE: Live with Regis and
Kelly
2006-09-25_0500_KABC_Eyewitness_News.txt:%

Looks like KTTV hasn't configured their XDS properly; I've sent them a note:

2006-09-25_0500_KTTV-FOX_Morning_News_at_5.txt:%
2006-09-25_0600_KTTV-FOX_Morning_News_at_6.txt:%
2006-09-25_0700_KTTV-FOX_Morning_News_at_7.txt:%
2006-09-25_0700_KTTV-FOX_Morning_News_at_7.txt:%   RATING: (NOT RATED) (88)

In brief, it would still be useful to be able to select a particular
field through a zvbi-ntsc-cc parameter. In the meantime, I'll prod the
stations to get their XDS act together.

Cheers,
Dave

> %   LENGTH: 0:07:20 of 1:00:00
> %   LENGTH: 0:08:20 of 1:00:00
> %   LENGTH: 0:09:21 of 1:00:00
> %   LENGTH: 0:10:21 of 1:00:00
> %   LENGTH: 0:11:21 of 1:00:00
> %   LENGTH: 0:11:20 of 1:00:00
> %
> %   LENGTH: 0:12:20 of 1:00:00
> %   LENGTH: 0:13:20 of 1:00:00
> %
> %   LENGTH: 0:14:21 of 1:00:00
> %
> %   LENGTH: 0:15:21 of 1:00:00
> %   LENGTH: 0:16:21 of 1:00:00
> %
> %   LENGTH: 0:17:21 of 1:00:00
> %   LENGTH: 0:18:21 of 1:00:00
> %   LENGTH: 0:19:21 of 1:00:00
> %   LENGTH: 0:20:21 of 1:00:00
> %   LENGTH: 0:21:21 of 1:00:00
> %
> %   LENGTH: 0:22:21 of 1:00:00
> %
> %   LENGTH: 0:23:21 of 1:00:00
> %   LENGTH: 0:24:21 of 1:00:00
> %
> %   LENGTH: 0:25:21 of 1:00:00
> %
> %   LENGTH: 0:26:20 of 1:00:00
> %   LENGTH: 0:27:20 of 1:00:00
> %
> %   LENGTH: 0:28:20 of 1:00:00
> %   LENGTH: 0:29:21 of 1:00:00
> %
> %   LENGTH: 0:30:21 of 1:00:00
> %
> %   LENGTH: 0:31:21 of 1:00:00
> %
> %   LENGTH: 0:32:21 of 1:00:00
> %
> %   LENGTH: 0:33:21 of 1:00:00
> %
> %   LENGTH: 0:34:21 of 1:00:00
> %   LENGTH: 0:35:21 of 1:00:00
> %   LENGTH: 0:36:21 of 1:00:00
> %   LENGTH: 0:37:21 of 1:00:00
> %   LENGTH: 0:38:21 of 1:00:00
> %
> %   LENGTH: 0:39:21 of 1:00:00
> %
> %   LENGTH: 0:40:20 of 1:00:00
> %
> %   LENGTH: 0:41:21 of 1:00:00
> %
> %   LENGTH: 0:42:21 of 1:00:00
> %
> %   LENGTH: 0:43:21 of 1:00:00
> %   LENGTH: 0:44:20 of 1:00:00
> %
> %   LENGTH: 0:45:21 of 1:00:00
> %   LENGTH: 0:46:20 of 1:00:00
> %
> %   LENGTH: 0:47:21 of 1:00:00
> %   LENGTH: 0:48:21 of 1:00:00
> %   LENGTH: 0:49:20 of 1:00:00
> %
> %   LENGTH: 0:50:21 of 1:00:00
> %
> %   LENGTH: 0:51:21 of 1:00:00
> %   LENGTH: 0:52:21 of 1:00:00
> %   LENGTH: 0:53:21 of 1:00:00
> %   LENGTH: 0:54:21 of 1:00:00
> %
> %   LENGTH: 0:55:21 of 1:00:00
> %
> %   LENGTH: 0:56:21 of 1:00:00
> %
> %   LENGTH: 0:57:21 of 1:00:00
> %
> %   LENGTH: 0:58:21 of 1:00:00
> %   LENGTH: 0:59:21 of 1:00:00
>
>
>
>   

Re: [Zapping-misc] XDS

[David L. <lio...@co...>]

Michael Schimek wrote:
> On Mon, 2006-09-11 at 04:05 -0700, David Liontooth wrote:
>   
>> I'm recording some news programs from tv on a regular schedule, and 
>> would like to use zvbi-ntsc-cc's -x parameter to capture XDS 
>> information. My problem is that my recordings are scheduled on the hour, 
>> and programs often run over a bit, so that the new program doesn't start 
>> until a few minutes later. The result is that the XDS information that 
>> gets recorded is for the program that is ending rather than the program 
>> I'm recording.
>>
>> I haven't experimented a lot with this, but it looks like XDS 
>> information is recorded only once, and only at the beginning of the 
>> capture session. Would it be possible to pass a parameter (something 
>> like -x 10) to indicate when or how often the XDS information should be 
>> captured? Or is there a way to do something like this in the existing code?
>>     
>
> The app skips repeated XDS packets (source code line 233 or thereabouts),
> so it should print the XDS info every time it changes.
>
> How's the version in CVS? Works for me, after a few tweaks to properly
> decode my test stream.
>   
I'm using libzvbi 0.2.22-1 and will run some tests. The first one (here
I grep % an hour of captured text) shows a lot of "% LENGTH" lines that
are probably triggered by advertising -- they're not really informative.
Would it make sense to skip these too? There are also a number of "%"
blank lines.

The only thing I really want is the title ("60 Minutes" below) -- it
would be very useful to be able to pass a parameter and request only
some fields.

Dave



%     CALL: NET6
%   RATING: (NOT RATED) (72)
%  NETWORK:
%    TITLE:
%
% TIMECODE: 0/00 0:32
%   LENGTH: 0:00:00 of 1:00:00
% TIMECODE: 9/24 19:00
%    TITLE: 60 Minutes "A"
%   LENGTH: 0:01:20 of 1:00:00
%
%
%   LENGTH: 0:02:21 of 1:00:00
%   LENGTH: 0:03:21 of 1:00:00
%   LENGTH: 0:04:21 of 1:00:00
%
%   LENGTH: 0:05:21 of 1:00:00
%
%
%   LENGTH: 0:06:21 of 1:00:00
%   LENGTH: 0:07:20 of 1:00:00
%   LENGTH: 0:08:20 of 1:00:00
%   LENGTH: 0:09:21 of 1:00:00
%   LENGTH: 0:10:21 of 1:00:00
%   LENGTH: 0:11:21 of 1:00:00
%   LENGTH: 0:11:20 of 1:00:00
%
%   LENGTH: 0:12:20 of 1:00:00
%   LENGTH: 0:13:20 of 1:00:00
%
%   LENGTH: 0:14:21 of 1:00:00
%
%   LENGTH: 0:15:21 of 1:00:00
%   LENGTH: 0:16:21 of 1:00:00
%
%   LENGTH: 0:17:21 of 1:00:00
%   LENGTH: 0:18:21 of 1:00:00
%   LENGTH: 0:19:21 of 1:00:00
%   LENGTH: 0:20:21 of 1:00:00
%   LENGTH: 0:21:21 of 1:00:00
%
%   LENGTH: 0:22:21 of 1:00:00
%
%   LENGTH: 0:23:21 of 1:00:00
%   LENGTH: 0:24:21 of 1:00:00
%
%   LENGTH: 0:25:21 of 1:00:00
%
%   LENGTH: 0:26:20 of 1:00:00
%   LENGTH: 0:27:20 of 1:00:00
%
%   LENGTH: 0:28:20 of 1:00:00
%   LENGTH: 0:29:21 of 1:00:00
%
%   LENGTH: 0:30:21 of 1:00:00
%
%   LENGTH: 0:31:21 of 1:00:00
%
%   LENGTH: 0:32:21 of 1:00:00
%
%   LENGTH: 0:33:21 of 1:00:00
%
%   LENGTH: 0:34:21 of 1:00:00
%   LENGTH: 0:35:21 of 1:00:00
%   LENGTH: 0:36:21 of 1:00:00
%   LENGTH: 0:37:21 of 1:00:00
%   LENGTH: 0:38:21 of 1:00:00
%
%   LENGTH: 0:39:21 of 1:00:00
%
%   LENGTH: 0:40:20 of 1:00:00
%
%   LENGTH: 0:41:21 of 1:00:00
%
%   LENGTH: 0:42:21 of 1:00:00
%
%   LENGTH: 0:43:21 of 1:00:00
%   LENGTH: 0:44:20 of 1:00:00
%
%   LENGTH: 0:45:21 of 1:00:00
%   LENGTH: 0:46:20 of 1:00:00
%
%   LENGTH: 0:47:21 of 1:00:00
%   LENGTH: 0:48:21 of 1:00:00
%   LENGTH: 0:49:20 of 1:00:00
%
%   LENGTH: 0:50:21 of 1:00:00
%
%   LENGTH: 0:51:21 of 1:00:00
%   LENGTH: 0:52:21 of 1:00:00
%   LENGTH: 0:53:21 of 1:00:00
%   LENGTH: 0:54:21 of 1:00:00
%
%   LENGTH: 0:55:21 of 1:00:00
%
%   LENGTH: 0:56:21 of 1:00:00
%
%   LENGTH: 0:57:21 of 1:00:00
%
%   LENGTH: 0:58:21 of 1:00:00
%   LENGTH: 0:59:21 of 1:00:00

Re: [Zapping-misc] teletext - particular page...

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

Thanx a lot - I tried:
./capture --sliced | ./ttxfilter 777 | ./decode -a 
and I got following:

Teletext line=323 7/ 0 >/.//...P..777.01/01.TG1.ndz.24.09.18:42:16<
Teletext line=  7 7/27 >j6.s^j/j...j/j.jjjjj^jjjjj^jjjjj^jjjjj^j.O<
Teletext line=  8 7/26 >/6.f...yA...AIOB...IOt..t..t..t..t..t..t..<
Teletext line=  9 7/ 1 >j.                     .....STRONA 777... <
Teletext line= 10 7/21 >j......n.,,, .NAPISY DLA NIES]YSZACYCH... <
Teletext line= 11 7/22 >/......j.zw.  .                       ... <
Teletext line= 12 7/23 >j......(,,,/.WYKAZ PROGRAMOW - STR.335... <
Teletext line= 13 7/24 >/!...WYKAZ PROGRAMOW  ...  PROGRAM TVP  . <
Teletext line= 14 1/ 0 >...8....d.160.01/01.TG1.ndz.24.09.18:42:16<
Hamming error in pmag
Hamming error in pmag
Hamming error in pmag
Hamming error in pmag
Hamming error in pmag

Whats are these errors?

In the mean time I'm using 2 scripts:
and I get output like :
[2006-09-24 18:23:57] Swoje zbiory zanosz@ do gniazda
[2006-09-24 18:24:23] i tam magazynuj@ je...

It is possible that because of loop, I'll miss some subtitles?
here come these simple scripts :

<export_subtitles.sh (bash)>
#!/bin/bash
   COUNTER=0
   while [  $COUNTER -lt 1 ]; do
	./capture --sliced | ./export "text;charset=UTF8" 777 | ./space_strip
   done
</export_subtitles>

<space_strip (freepascal)>
uses strutils,strutils;
var
     ch1,ch2:char;
     st:string;
const
     st1='<unwanted strings>';

procedure parse_string(var s:string);
begin
     s:=AnsiReplaceStr(s,st1,'');
     s:='['+formatdatetime('YYYY-MM-DD hh:nn:ss',Now)+']';
end;
begin
     repeat
        read(ch1);
        read(ch2);
        if (((ch1=' ') or (ch1=chr(10))) and ((ch2=' ') or
(ch2=chr(10)))) then begin
          repeat
                read(ch2);
          until ((ch2<>' ') and (ch2<>chr(10)));
        end;
        if (ch1=chr(26)) then begin
parse_string(st);writeln(st);exit;end else
        if (ch2=chr(26)) then begin
parse_string(st);writeln(st);exit;end else
        st:=st+ch1+ch2;
     until (true=false);
end.
</space_strip>


Thank you for your help
Regards
Karol Zapolski


On Sun, 2006-09-24 at 07:30 +0200, Michael Schimek wrote:
> Hi Karol,
> 
> > How can I capture particular page ie. 777 (it's subtitle page)...
> > I've tried :
> > capture --sliced | decode --a
> 
> ./capture --sliced | ./ttxfilter 777 | ./decode -a
> 
> If you need plain text
>   ./capture --sliced | ./export text 777
> would work too, but currently ./export quits after saving one page.
> 
> Michael
> 

Re: [Zapping-misc] XDS

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

On Mon, 2006-09-11 at 04:05 -0700, David Liontooth wrote:
> I'm recording some news programs from tv on a regular schedule, and 
> would like to use zvbi-ntsc-cc's -x parameter to capture XDS 
> information. My problem is that my recordings are scheduled on the hour, 
> and programs often run over a bit, so that the new program doesn't start 
> until a few minutes later. The result is that the XDS information that 
> gets recorded is for the program that is ending rather than the program 
> I'm recording.
> 
> I haven't experimented a lot with this, but it looks like XDS 
> information is recorded only once, and only at the beginning of the 
> capture session. Would it be possible to pass a parameter (something 
> like -x 10) to indicate when or how often the XDS information should be 
> captured? Or is there a way to do something like this in the existing code?

The app skips repeated XDS packets (source code line 233 or thereabouts),
so it should print the XDS info every time it changes.

How's the version in CVS? Works for me, after a few tweaks to properly
decode my test stream.

Michael

Re: [Zapping-misc] HELP FOR ZAPPING

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

On Thu, 2006-09-14 at 01:42 +0200, Michele Ponziano wrote:
> Hi, 
> my name is Michele and i'm a nb of linux.
> On suse 10.0, after installing nvidia driver running zapping i have
> this message :
> (zapping:24329): GnomeUI-WARNING **: While connecting to session
> manager:
...
> The error was 'XF86DGANoDirectVideoMode'.

That's fixed in Zapping 0.10. Sorry I can't offer SuSE binaries, but if
you want to compile the application yourself the source code is
available at:
http://sourceforge.net/project/showfiles.php?group_id=2599

Michael

Re: [Zapping-misc] zapping crashes after the start

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

Hi Lukas,

Thanks for the info. When you start
  zapping --no-overlay
from a terminal window it works?

Michael

Re: [Zapping-misc] teletext - particular page...

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

Hi Karol,

> How can I capture particular page ie. 777 (it's subtitle page)...
> I've tried :
> capture --sliced | decode --a

./capture --sliced | ./ttxfilter 777 | ./decode -a

If you need plain text
  ./capture --sliced | ./export text 777
would work too, but currently ./export quits after saving one page.

Michael

[Zapping-misc] Zapping - KDE 3.5.4 - Nvidia

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

Zapping error - Is there any future hopes on the DGA issue being solved?

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 159 request_code 138 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.)

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

[Zapping-misc] teletext - particular page...

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

Hello everybody!

How can I capture particular page ie. 777 (it's subtitle page)...

I've tried :
capture --sliced | decode --a

but how can I isolate pages from this output...

Regards
Karol Zapolski

[Zapping-misc] Zapping News wrong year

[David L. <lio...@co...>]

The Zapping News at http://zapping.sourceforge.net/Zapping/News.html
shows 2005 instead of 2006 for the last four entries -- makes it seem
the project is a lot more out of date than it actually is! Could someone
with write access fix it?

The release notes show the correct dates.

David


Zapping News

Tip! Release notification
by Sourceforge: Zapping, libzvbi, librte
by Freshmeat: Zapping, libzvbi.

2005-05-10 Libzvbi 0.2.21 released
    Oops. WSS capturing from video images didn't work anymore. Release
notes.

2005-05-08 Libzvbi 0.2.20 released
    Minor improvements. Release notes.

2005-02-23 Libzvbi 0.2.19 released

2005-02-11 Libzvbi 0.2.18 released

2005-10-08 Libzvbi 0.2.17 released
    Updates the XDS demultiplexer, the CNI table, and installs a
customized version of ntsc-cc. Release notes

[Zapping-misc] HELP FOR ZAPPING

[Michele P. <pon...@ya...>]

Hi, 
 my name is Michele and i'm a nb of linux.
 On suse 10.0, after installing nvidia driver running zapping i have this message :
 (zapping:24329): GnomeUI-WARNING **: While connecting to session manager:
 Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
 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 159 request_code 138 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.)
 Please help me.Thanks.
 Bye
 
 
 __________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 

[Zapping-misc] XDS

[David L. <lio...@co...>]

I'm recording some news programs from tv on a regular schedule, and 
would like to use zvbi-ntsc-cc's -x parameter to capture XDS 
information. My problem is that my recordings are scheduled on the hour, 
and programs often run over a bit, so that the new program doesn't start 
until a few minutes later. The result is that the XDS information that 
gets recorded is for the program that is ending rather than the program 
I'm recording.

I haven't experimented a lot with this, but it looks like XDS 
information is recorded only once, and only at the beginning of the 
capture session. Would it be possible to pass a parameter (something 
like -x 10) to indicate when or how often the XDS information should be 
captured? Or is there a way to do something like this in the existing code?

David

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

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

Thank you!  That did the trick!

Let me know if that's going to make it into a release.

Thanks,
Rich

--

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 10:13 PM
To: Rich Kadel
Cc: zap...@li...
Subject: RE: [Zapping-misc] VBI parity errors on NTSC channel 56 -
knowntowork elsewhere

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