zapping-misc — General discussion

Re: [Zapping-misc] zapping MPEG recording?

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

Luke Q Campagnola wrote:
>=20
> The Zapping website has brief mentions of MPEG recording
> capabilities/plugins, however I have been unable to locate any such
> things.. any clue for me?

When you installed a Zapping binary the plugins are in
/usr/local/lib/zapping/plugins or wherever your distro likes to put misc
stuff. Zapping loads all plugins a startup, the mpeg plugin needs the
rte library to function. When you compiled Zapping yourself the mpeg
plugin will be compiled as well, if the rte library is installed. When
you have everything, it should be listed under Settings/Plugins or you
should get some error message.=20

Marcel Hild wrote:
>
> AFAIK you have to compile mp1e to encode into mpeg streams.
> I havent played with the plugins and the 'goto capturing' isnt
> supported in the debian package, right now.

Isn't supported? Astounding.

FYI the rte library is our interface to video codecs, similar to libjpeg
or libpng. Its relation to mp1e is this: I wrote mp1e as a command line
tool in 99, I=F1aki wanted an MPEG recording plugin for Zapping and wrote
a library front end. We agreed more formats would be nice, so mp1e
became just one backend, ffmpeg another (in the works), more to follow.
Until rte matured enough I didn't want to break up mp1e, hence the mp1e
standalone (which I didn't really requested to be re-published :-) and
the rte library including mp1e, compiling standalone mp1e as well.
Future versions of rte will only contain the codecs, and if still needed
mp1e will shrink to a small command line front end to librte.

Michael

Re: [Zapping-misc] audio recording problem

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

WANG Xuewen wrote:
> 
> The viewer works very well, so the teletexte. I can record to mpeg file
> but this is no sound. When I chosed ESD, it will say:' Warning: ESD
> select time out."
> When I chose OSS, no warning but still no sound recorded. I've chosen
> the default options for  audio recording.

As has been mentioned already, the audio output of your TV card must be
connected to LineIn of your sound card. The kernel comes with a library
of sound drivers: Open Sound System (OSS). I presume it's already
configured for your hardware? If so, you should be able to play and
record audio with other applications.

Enlightened Sound Daemon (ESD) allows Gnome applications to share the
sound hardware, it runs on top of the kernel drivers and will
automatically start when Zapping tries to access ESD. To use OSS
directly, you must enter the audio sampling device name: /dev/dsp0,
/dev/dsp1, ... but usually /dev/dsp which is a symbolic link to
/dev/dsp0.

Finally you must open a mixer application, set the desired recording
volume of LineIn and select LineIn as recording source. It may default
to CD, Mic or Synth.

Michael

(RFC: Should we add a mixer GUI and/or option to remember, set & restore
mixer? What's the ESD philosophy, a system wide sound config I suppose?
A whatsitsname to show the actual audio levels may be nice too.)

Re: [Zapping-misc] deinterlace?

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

Hi Marcel,

>  After some (re)search through the web, it seems to me that mp1e produces
>  the 'best' mpeg1 quality.
>  In comparison to hardware encoded streams (like with DC10), how good is
>  the quality? I mean, would you say, dont spend money on such a card, you
>  wont get better looking movies?

You better ask someone actually using hw compression.

Generally speaking sw compression can very well achieve and surpass hw
quality, but not present mp1e or ffmpeg. On the other hand, hw will not
improve, and beauty, contact lenses and compression quality are in the
eye of the beholder.

>  Would you recommend mpeg1 video?

I recommend you take the best available for the job. When you want to
play back CDs or DVDs on hardware players you have no choice but MPEG-1
or -2. For archiving I would really spend the few extra bucks on more
disk space, record [near] lossless, edit, and then encode with a decent
offline compression tool. Programs like mp1e or ffmpeg may be
convenient, but it comes at a cost.

>  Can you give me some hints on the options of mp1e? Especially the filter.
>  This seems to work good:
> 
> mp1e -m 1 -s 768x576 -v -b 3.0 -F 3.125 -R 16,16 > test.mpg

Sorry, typo in the man page. Should read -f3.125. However you want
something different: -F5 averaging of top & bottom field.

I'm well aware that's a pity excuse for real deinterlacing (pulldown,
inter-field motion compensation, whatnot kind of filters), but I'd
rather add MPEG-2, that would compress better and preserve the spatial
and temporal resolution of interlaced video.

Michael

Re: [Zapping-misc] deinterlace?

[Marcel H. <hi...@b4...>]

On Don, Nov 15, 2001 at 08:49:07 +0100, Heiko Bachmann wrote:
> >  so I started with 768x576. That works fine, but are there any tools to=
 deinterlace
> >  the recorded  stream?
>=20
> Try  ffmeg -deinterlace, results are very good. But you might get those A=
/V
> sync problems.  And it's not possible to use it together with zapping
> without further work. Plug-In writing time :)

maybe i'll look into that later.

so, you encode with mp1e ? can you give me some sample commandline args, for
e.g. recording from tv, recording from VHS tape, etc ?

thanx
 marcel

--=20
GPG: http://blackhole.pca.dfn.de:11371/pks/lookup?op=3Dget&search=3D0xEDF82=
C72

Re: [Zapping-misc] audio recording problem

[WANG X. <x2w...@fr...>]

Thank  you for the reply. In fact my Tv card needs also to be connected 
to linein of my sound card.  In this case, what can I do to get audio 
recorded?
Change the device from /dev/dsp to something else?

Marcel Hild wrote:

>On Fre, Nov 16, 2001 at 12:40:52 +0100, WANG Xuewen wrote:
>
>>Hi,
>>
>>Thanks for this great TV program!
>>
>>I've problem to record to mpeg. The mpeg file recorded has no sound.
>>
>>System: Redhat7.2
>>Destop: gnome.
>>Zapping: 0.6.1
>>TV card: Miro PCTV(bt848)
>>
>>The viewer works very well, so the teletexte. I can record to mpeg file 
>>but this is no sound. When I chosed ESD, it will say:' Warning: ESD 
>>select time out."
>>When I chose OSS, no warning but still no sound recorded. I've chosen 
>>the default options for  audio recording.
>>
>>Any help? I've already searched the archive but found no answer.
>>
>
>How is sound configured with you card? My WinTV cards needs to be connected
>to LineIn or Mic of my sound card. Maybe you have to play with these...
>
>marcel
>

Re: [Zapping-misc] audio recording problem

[Marcel H. <hi...@b4...>]

On Fre, Nov 16, 2001 at 12:40:52 +0100, WANG Xuewen wrote:
> Hi,
>=20
> Thanks for this great TV program!
>=20
> I've problem to record to mpeg. The mpeg file recorded has no sound.
>=20
> System: Redhat7.2
> Destop: gnome.
> Zapping: 0.6.1
> TV card: Miro PCTV(bt848)
>=20
> The viewer works very well, so the teletexte. I can record to mpeg file=
=20
> but this is no sound. When I chosed ESD, it will say:' Warning: ESD=20
> select time out."
> When I chose OSS, no warning but still no sound recorded. I've chosen=20
> the default options for  audio recording.
>=20
> Any help? I've already searched the archive but found no answer.
>=20

How is sound configured with you card? My WinTV cards needs to be connected
to LineIn or Mic of my sound card. Maybe you have to play with these...

marcel

--=20
GPG: http://blackhole.pca.dfn.de:11371/pks/lookup?op=3Dget&search=3D0xEDF82=
C72

Re: [Zapping-misc] zapping MPEG recording?

[Marcel H. <hi...@b4...>]

On Don, Nov 15, 2001 at 06:50:45 -0700, Luke Q Campagnola wrote:
> The Zapping website has brief mentions of MPEG recording
> capabilities/plugins, however I have been unable to locate any such
> things.. any clue for me?
>=20

AFAIK you have to compile mp1e to encode into mpeg streams.
I havent played with the plugins and the 'goto capturing' isnt
supported in the debian package, right now.

marcel

--=20
GPG: http://blackhole.pca.dfn.de:11371/pks/lookup?op=3Dget&search=3D0xEDF82=
C72

[Zapping-misc] audio recording problem

[WANG X. <x2w...@fr...>]

Hi,

Thanks for this great TV program!

I've problem to record to mpeg. The mpeg file recorded has no sound.

System: Redhat7.2
Destop: gnome.
Zapping: 0.6.1
TV card: Miro PCTV(bt848)

The viewer works very well, so the teletexte. I can record to mpeg file 
but this is no sound. When I chosed ESD, it will say:' Warning: ESD 
select time out."
When I chose OSS, no warning but still no sound recorded. I've chosen 
the default options for  audio recording.

Any help? I've already searched the archive but found no answer.
 

[Zapping-misc] zapping MPEG recording?

[Luke Q C. <lca...@Mi...>]

The Zapping website has brief mentions of MPEG recording
capabilities/plugins, however I have been unable to locate any such
things.. any clue for me?

Luke

Re: [Zapping-misc] deinterlace?

[Heiko B. <Hei...@In...>]

On Thu, 15 Nov 2001, Marcel Hild wrote:
>  I just have a fast CPU and a bttv878 tv card. So, my main goal is to record
>  in realtime, with the best quality / compression ratio. Yes, I dont want to
>  record uncompressed (as always, lack of diskspace :) 

Don't forget a good A/V sync. Some tools I tried desynced already after some
seconds although enough CPU was available.


>  so I started with 768x576. That works fine, but are there any tools to deinterlace
>  the recorded  stream?

Try  ffmeg -deinterlace, results are very good. But you might get those A/V
sync problems.  And it's not possible to use it together with zapping
without further work. Plug-In writing time :)


Good luck ;)
Heiko.


-- 
[ Mail ....................... hei...@in...  ]
[ Homepage ...................... http://www-user.tu-chemnitz.de/~heba/  ]
[ Second hand CD list .... http://www.tu-chemnitz.de/~heba/cd-list.html  ]
[ B&W photography ................................ http://www.septem.de  ]

Re: [Zapping-misc] Aspect ratio support not working

[E. <ga...@eu...>]

> I can only discuss the decoding part, GUI's not my domain.
Last time i looked the gui part worked. But we all know that untouched
code tends to rot :-), so drop me a line if you find something broken in
there.

> In the future, should v4l(2) define an API to access hw VBI decoders of
> TV cards (which aren't subject to a capture window limitation), or
> perhaps after extending Zapping to access DVB cards (depends if the
> transmission is encrypted or aspect ratio information in some
> proprietary format), we'd have a more reliable source of WSS data. But
> to my best knowledge that's about all one can do right now.
amen.

I=F1aki

[Zapping-misc] [Fwd: Re: nl translation, prefs]

[E. <ga...@eu...>]

I cannot reach Reinout directly, so sending to the list, let's hope that
Reinout, Ime or anybody else willing to help with nl.po will read this.

Regards,
I=F1aki

Re: [Zapping-misc] sintonizacion

[E. <ga...@eu...>]

Hi,

I'll translate and answer this one:

> mis disculpas por escribir en castella=F1o, solo leo en ingl=E9s.
[ Sorry about writing in Spanish, I can only read English.]

> Vivo en Argentina, aqui en Uruguay, brasil, y=20
> Bolivia utilizamos Pal N, el
> pal NC funcional perfectamente, solo que
> sintoniza los primeros 13 canales
> y ademas lo hace informando que se trata de=20
> us-broadcast, =BFc=F3mo puedo
> sintonizar los 65 canales? el proceso de=20
> autodetecci=F3n no lo hace.
[I live in Argentina, here and in Uruguay, Brasil and Bolivia we use Pal
N. Pal NC works perfectly but it only tunes the first 13 channels and
also it tells that it's us-broadcast. How can I tune the 65 channels?
The autodetect process doesn't do it.]

Sorry about the confusing GUI for this, we have tried to improve this
for the next release. First you need to select the frequency table
according to the region you're in, then click 'Search available
channels'. If search doesn't find all channels, you can still add them
manually:
-> Tune to the desired frequency (select entries in the frequency list
and fine tune).
-> Add a name for the channel
-> Hit 'Add'

Hopefully this will be clearer in the next release.

If you really need Pal-N, then you need to apply this patch to tveng1.c
(patch -p0 < patch_contents)
***************** cut here ***************
Index: tveng1.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/zapping/zapping/src/tveng1.c,v
retrieving revision 1.68
diff -u -r1.68 tveng1.c
--- tveng1.c    2001/11/12 22:38:40     1.68
+++ tveng1.c    2001/11/15 18:49:04
@@ -90,7 +90,7 @@
 /*
   If this is enabled, pal_n mode is enabled ( it can crash my system )
 */
-/* #define TVENG1_PAL_N 1 */
+#define TVENG1_PAL_N 1
=20
 /* Private, builds the controls structure */
 static int
******************* cut here ***************

I disabled Pal-N some time ago because some buggy bttv driver would
cause the system to hard lock when setting this standard. It appears to
be fixed in bttv 0.8.x, so i'll enable this mode again.

>    Felicitaciones por el programa realmente es una maravilla, para
cuando
> una traducci=F3n al castella=F1o?
[ Thanks for the program, it's truly a marvel. When will be a Spanish
translation?].
It's already translated, i do the translation myself :-)
Make sure you've installed correctly, you have the locale correctly set,
etc.

Regards,
I=F1aki

[Zapping-misc] deinterlace?

[Marcel H. <hi...@b4...>]

Hi,
 I am relatively new to mpeg encoding.
 Maybe some experts can answer me some questions. :)

 What I basically want to do is, archive my VHS video tapes on CDs and 
 maybe record TV broadcasts.

 I just have a fast CPU and a bttv878 tv card. So, my main goal is to record
 in realtime, with the best quality / compression ratio. Yes, I dont want to
 record uncompressed (as always, lack of diskspace :) 

 I had those questions:

 After some (re)search through the web, it seems to me that mp1e produces 
 the 'best' mpeg1 quality.
 In comparison to hardware encoded streams (like with DC10), how good is 
 the quality? I mean, would you say, dont spend money on such a card, you
 wont get better looking movies?
 Would you recommend mpeg1 video? 
 As I want to archive the video, I dont want to record on a lower resolution, 
 so I started with 768x576. That works fine, but are there any tools to deinterlace
 the recorded  stream?

 Can you give me some hints on the options of mp1e? Especially the filter.
 This seems to work good:

mp1e -m 1 -s 768x576 -v -b 3.0 -F 3.125 -R 16,16 > test.mpg

 But the result seems to have to be deinterlaced. Are there any tools for 
 linux to do this? Or am i just wrong with some filter settings?

 
Thanks for any hints or pointers to resources...

marcel
-- 
GPG: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xEDF82C72

[Zapping-misc] sintonizacion

[jtreper <jt...@fi...>]

mis disculpas por escribir en castella=F1o, solo leo en ingl=E9s.
Vivo en Argentina, aqui en Uruguay, brasil, y Bolivia utilizamos Pal N, el
pal NC funcional perfectamente, solo que sintoniza los primeros 13 canales
y ademas lo hace informando que se trata de us-broadcast, =BFc=F3mo puedo
sintonizar los 65 canales? el proceso de autodetecci=F3n no lo hace. Estoy
tomando como fuente Television ya que las otras dos solo muestran una
pantalla azul.=20
   Felicitaciones por el programa realmente es una maravilla, para cuando
una traducci=F3n al castella=F1o?

			Gracia

					Jaime Trepper

Re: [Zapping-misc] prefs go bad after reboot

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

I=F1aki Garc=EDa Etxebarria wrote:
> > > NTSC composite inputs are a problem under V4L1, since the api doesn=
't
> > > allow for changing the standard in tunerless modes.
> > Could Zapping try the input tuner, Standard/x, old input workaround
> > automagically?
> Sure, i'll write this code. Just one question: which standard should it
> switch to?
> I've though about emulating a v4l2-style api with v4l (when possible)
> and remembering standards for each input, would this work?

Dunno, but I think for consistency tveng should always remember
standards for each input, moreover standard menus should list only the
standards (or better yet, disable those not) applicable to the current
input.

The rationale is not all inputs may support the same set of standards,
typically the tuner supports only a subset of those allowed by the video
decoder, ie. available for composite or s-video.

Given a global standard Zapping had to pick a reasonable replacement
when switching to an input not supporting the current standard, or spit
out frustrating error messages. Also arguing there's some advantage
implies many users have multi-standard equipment connected to all RF and
baseband inputs. In contrast the majority probably wants RF at the same
standard all the time (or switch at channel granularity), while eg. a
multi-standard VCR is connected to a single baseband input.

Michael

Re: [Zapping-misc] Aspect ratio support not working

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

Hi James,

> I have a digital cable box which talks to my video card over the
> motherboard, and gets overlayed to screen using Xvideo.
> 
> When I switch programmes and notice one is in 4:3, and one is in 16:9
> modes, zapping does not alter the window to compensate.
> 
> According to the bug above, which I filed, it should.
>
> I am using GNOME+E. Any ideas?

I can only discuss the decoding part, GUI's not my domain. In brief:
Zapping tries hard to get hands on the aspect ratio information, but
odds are against it.

A set-top box can switch the TV aspect ratio in two ways I'm aware of:
using a dedicated line at the connector or by inserting a signal in the
VBI. The connector line is inaccessible but our libvbi decodes three
different a/r signals, the European standard's named Wide Screen
Signalling.

Unfortunately this signal is encoded on the first half of video scan
line 23, immediately before active video starts. The video capture
driver may be unable to extend the VBI capture window down to line 23,
notably bttv 0.7 or older will not, bttv 0.8 or bttv-v4l2 may. By
definition PAL active video has 575 lines, i.e. scan line 23.5 to 311.0
and 336.0 to 623.5. Drivers usually capture 576 lines, ranging from 23.0
to 624.0.

Specifically for this case I've added RGB data sampling as a last
resort. All common pixel formats are supported, and for WSS the captured
image must be at least 320 pixels wide and still contain all the data
from line 23, despite scaling or other processing. In preview mode or
using XVideo the driver writes the images directly into video ram,
Zapping has no function to read it back from there, should this be
possible at all. So RGB sampling works only in capture mode, however I
must add at the moment the sw interface (capture.c 420) is temporarily
disconnected.

In the future, should v4l(2) define an API to access hw VBI decoders of
TV cards (which aren't subject to a capture window limitation), or
perhaps after extending Zapping to access DVB cards (depends if the
transmission is encrypted or aspect ratio information in some
proprietary format), we'd have a more reliable source of WSS data. But
to my best knowledge that's about all one can do right now.

Michael

[Zapping-misc] [ zapping-Bugs-481143 ] Gtk-CRITICAL

[<no...@so...>]

Bugs item #481143, was opened at 2001-11-12 18:31
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=481143&group_id=2599

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Gtk-CRITICAL

Initial Comment:
[bruceg@linux bruceg]$ zapping

Gtk-CRITICAL **: file gtkmain.c: line 582
(gtk_main_quit): assertion `main_loops != NULL' failed.

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

>Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-11-14 10:46

Message:
Logged In: YES 
user_id=7928

looks like the infamous consolehelper bug.
Try running "zapping -z"

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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=481143&group_id=2599

[Zapping-misc] [ zapping-Bugs-463534 ] preferences segfault

[<no...@so...>]

Bugs item #463534, was opened at 2001-09-21 04:46
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=463534&group_id=2599

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Tilmann Bitterberg (tibit)
Assigned to: Nobody/Anonymous (nobody)
Summary: preferences segfault

Initial Comment:
Hi

I am using zapping-0.6.1 and when I click on 
1) preferences 
2) OK
3) preferences (again)
I get a segmentation fault
here is the gdb backtrace

Tilmann

Gtk-CRITICAL **: file gtkaccelgroup.c: line 148
(gtk_accel_group_unref): assertion
on `accel_group->ref_count > 0' failed.

Program received signal SIGSEGV, Segmentation fault.
g_mem_chunk_alloc (mem_chunk=0x81478a0) at gmem.c:575
575     gmem.c: No such file or directory.
(gdb) bt
#0  g_mem_chunk_alloc (mem_chunk=0x81478a0) at
gmem.c:575
#1  0x401607ba in gtk_accel_group_new () at
gtkaccelgroup.c:115
#2  0x4006837d in gnome_dialog_init (dialog=0x40f016d0)
at gnome-dialog.c:181
#3  0x40222367 in gtk_type_new (type=56597) at
gtktypeutils.c:391
#4  0x4009c869 in gnome_property_box_new () at
gnome-propertybox.c:232
#5  0x404db2c1 in propbox_new (xml=0x40f02158,
info=0x8169598)
    at glade-gnome.c:1889
#6  0x404eae36 in glade_xml_build_widget
(self=0x40f02158, info=0x8169598, 
    parent_long=0x0) at glade-xml.c:1241
#7  0x404eabaf in glade_xml_build_interface
(self=0x40f02158, tree=0x81485a8, 
    root=0x80c9b00 "zapping_properties") at
glade-xml.c:1105
#8  0x404e99c8 in glade_xml_construct (self=0x40f02158, 
    fname=0x80c9ac0
"/opt/zapping/share/zapping/zapping.glade", 
    root=0x80c9b00 "zapping_properties", domain=0x0) at
glade-xml.c:205
#9  0x404e9819 in glade_xml_new (
    fname=0x80c9ac0
"/opt/zapping/share/zapping/zapping.glade", 
    root=0x80c9b00 "zapping_properties") at
glade-xml.c:136
#10 0x806a651 in build_widget (name=0x80c9b00
"zapping_properties", 
    glade_file=0x80c9ac0
"/opt/zapping/share/zapping/zapping.glade")
    at interface.c:88
#11 0x806a798 in create_zapping_properties () at
interface.c:133
#12 0x807529a in on_propiedades1_activate
(menuitem=0x81665e8, user_data=0x0)
    at properties.c:63
#13 0x401cd7b1 in gtk_marshal_NONE__NONE
(object=0x81665e8, 
    func=0x807528c <on_propiedades1_activate>,
func_data=0x0, args=0xbfffeb6c)
    at gtkmarshal.c:312
#14 0x401fc01c in gtk_handlers_run (handlers=0x8107058,
signal=0xbfffeb18, 
    object=0x81665e8, params=0xbfffeb6c, after=0) at
gtksignal.c:1917
#15 0x401fb485 in gtk_signal_real_emit
(object=0x81665e8, signal_id=75, 
    params=0xbfffeb6c) at gtksignal.c:1477
#16 0x401f9563 in gtk_signal_emit (object=0x81665e8,
signal_id=75)
    at gtksignal.c:552
#17 0x4022fa4e in gtk_widget_activate
(widget=0x81665e8) at gtkwidget.c:2886
#18 0x401d5154 in gtk_menu_shell_activate_item
(menu_shell=0x81664d8, 
    menu_item=0x81665e8, force_deactivate=1) at
gtkmenushell.c:849
#19 0x401d43fa in gtk_menu_shell_button_release
(widget=0x81664d8, 
    event=0x81f36f8) at gtkmenushell.c:485
#20 0x401cd43b in gtk_marshal_BOOL__POINTER
(object=0x81664d8, 
    func=0x401d426c <gtk_menu_shell_button_release>,
func_data=0x0, 
    args=0xbfffef4c) at gtkmarshal.c:28
#21 0x401fb4c3 in gtk_signal_real_emit
(object=0x81664d8, signal_id=27, 
    params=0xbfffef4c) at gtksignal.c:1492
#22 0x401f9563 in gtk_signal_emit (object=0x81664d8,
signal_id=27)
    at gtksignal.c:552
#23 0x4022f90b in gtk_widget_event (widget=0x81664d8,
event=0x81f36f8)
    at gtkwidget.c:2860
#24 0x401cd3a5 in gtk_propagate_event
(widget=0x81665e8, event=0x81f36f8)
    at gtkmain.c:1313
#25 0x401cc5ce in gtk_main_do_event (event=0x81f36f8)
at gtkmain.c:770
#26 0x40279cb7 in gdk_event_dispatch (source_data=0x0, 
    current_time=0xbffff344, user_data=0x0) at
gdkevents.c:2129
#27 0x4043e2b9 in g_main_dispatch
(dispatch_time=0xbffff344) at gmain.c:656
#28 0x4043e8c3 in g_main_iterate (block=1, dispatch=1)
at gmain.c:877
#29 0x4043ea5c in g_main_run (loop=0x81583f8) at
gmain.c:935
#30 0x401cbec7 in gtk_main () at gtkmain.c:476
#31 0x805a535 in main (argc=1, argv=0xbffff764) at
main.c:742
#32 0x40570c7f in __libc_start_main (main=0x8058ba8
<main>, argc=1, 
    argv=0xbffff764, init=0x80564f4 <_init>,
fini=0x80c54ac <_fini>, 
    rtld_fini=0x4000c2c0 <_dl_fini>,
stack_end=0xbffff75c)
    at ../sysdeps/generic/libc-start.c:92

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

>Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-11-14 10:45

Message:
Logged In: YES 
user_id=7928

Closing as fixed. The source of this bug could be either:
a) A glade widget destruction bug (double free) that could
cause mem corruption, fixed some days ago.
b) Something in the prefs handling - i've rewritten all of
that code, so it shouldn't happen now. Please reopen if it
still happens in the (soon to be released) 0.6.2 version.

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

Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-10-03 10:39

Message:
Logged In: YES 
user_id=7928

Then it appears to be some obscure bug in the gnome libs.
Try upgrading libglade and libgnome*

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

Comment By: Tilmann Bitterberg (tibit)
Date: 2001-09-22 05:13

Message:
Logged In: YES 
user_id=61599

Sorry, but your patch doesn't fixes it. It happens also when
I use -p

Tilmann

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

Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-09-21 13:03

Message:
Logged In: YES 
user_id=7928

There was a bug in the mpeg plugin properties handling,
perhaps this is related. If you don't get this segfault
running with
'zapping -p'
then the following patch could improve things:
Apply under plugins/mpeg [patch -p0 < patch]
<<<<<<<<< cut here >>>>>>>>>
Index: mpeg.c
===================================================================
RCS file: /cvsroot/zapping/zapping/plugins/mpeg/mpeg.c,v
retrieving revision 1.10
diff -u -r1.10 mpeg.c
--- mpeg.c	2001/09/13 12:20:14	1.10
+++ mpeg.c	2001/09/21 20:01:49
@@ -45,7 +45,7 @@
 /* The format of the version string must be
    %d[[.%d[.%d]][other_things]], where the things between
[] aren't
    needed, and if not present, 0 will be assumed */
-static const gchar str_version[] = "0.1";
+static const gchar str_version[] = "0.2";
 /* TRUE if we are running */
 static volatile gboolean active = FALSE;
 /* The context we are encoding to */
@@ -173,7 +173,6 @@
   if (!*options_p)
     return;
  
-  grte_options_unref(*options_p);
   gtk_widget_destroy(*options_p);
 
   *options_p = NULL;
@@ -1084,6 +1083,11 @@
     (mpeg_properties, "fileentry2"), state);
 }
 
+static void nullify (void **p)
+{
+  *p = NULL;
+}
+
 static void
 set_audio_codec (GtkWidget *mpeg_properties, GtkWidget *menu)
 {
@@ -1122,6 +1126,10 @@
           gtk_table_attach (GTK_TABLE (table),
audio_options, 0, 2, 3, 4,
 
		    (GtkAttachOptions) (GTK_FILL),
 
		    (GtkAttachOptions) (0), 3, 3);
+
+
  gtk_signal_connect_object (GTK_OBJECT(audio_options),
"destroy",
+
			     GTK_SIGNAL_FUNC (nullify),
+
			     (GtkObject*)(&audio_options));
 	}
 
       g_free (zc_domain);
Index: mpeg.h
===================================================================
RCS file: /cvsroot/zapping/zapping/plugins/mpeg/mpeg.h,v
retrieving revision 1.1
diff -u -r1.1 mpeg.h
--- mpeg.h	2001/09/14 14:22:18	1.1
+++ mpeg.h	2001/09/21 20:01:49
@@ -19,4 +19,3 @@
 /* $Id: mpeg.h,v 1.1 2001/09/14 14:22:18 mschimek Exp $ */
 
 extern GtkWidget *grte_options_create (rte_context
*context, rte_codec *codec, gchar *zc_domain);
-extern void grte_options_unref (GtkWidget *);
Index: options.c
===================================================================
RCS file: /cvsroot/zapping/zapping/plugins/mpeg/options.c,v
retrieving revision 1.1
diff -u -r1.1 options.c
--- options.c	2001/09/14 14:22:18	1.1
+++ options.c	2001/09/21 20:01:49
@@ -321,28 +321,7 @@
 
   gtk_container_add (GTK_CONTAINER (frame), opts->table);
 
-  gtk_widget_ref (frame); /* the returned pointer */
-
   return frame;
-}
-
-/*
- *  Disconnect options from the rte_context/codec, mandatory.
- */
-void
-grte_options_unref (GtkWidget *frame)
-{
-  grte_options *opts;
-
-  if (!frame)
-    return;
-
-  opts = (grte_options *) gtk_object_get_data (GTK_OBJECT
(frame), "opts");
-
-  opts->context = NULL;
-  opts->codec = NULL;
-
-  gtk_widget_unref (frame);
 }
 
 #endif /* HAVE_LIBRTE */


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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=463534&group_id=2599

[Zapping-misc] [ zapping-Bugs-425468 ] XFree86 inc Keyboard and Mouse Freeze

[<no...@so...>]

Bugs item #425468, was opened at 2001-05-19 10:57
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=425468&group_id=2599

Category: None
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: James Green (james)
Assigned to: Iñaki García Etxebarria (garetxe)
Summary: XFree86 inc Keyboard and Mouse Freeze

Initial Comment:
OK, I have been experiencing this randomly for some
time (months), thus I've not been using zapping very much.

My setup: bttv878 tuner, GeForce IIMX AGP video card
(VIA mobo chipset at 2X), Debian Unstable with XFree86 4.0.

Have tried:
- XF4.0.2/3
- XFree86's nv driver and NVidia's own binary drivers
(0.9 and 1.0 releases)
Kernel 2.4.x (now .4) and supplied v4l drivers

Zapping apparently runs fine. Then, at random, the
mouse freezes. I can often still see gkrellm monitors
showing CPU and network activity is still going on,
although sometimes though this freezes too.

The keyboard also freezes. Numlock, Capslock, neither
light turns off/on. Magic SysRq key does not respond
(it does respond in other s/w hangs problems).

I have no option but to hard reset the box by the
button on the case.

I am reporting this as a fault in zapping as xawtv
works flawlessly. Since it occurs with both the XFree86
supplied nv driver and NVidia's own, we can rule those
out (except for unknown shared code).

I understand that this may be a tough one to track
down, so any debugging suggestions would be useful
(although, as X/keyboard/mouse and possibly other
things die, it's going to have to be magical stuff
methinks).

I would go for the v4l2 stuff but a) seems experimental
b) seems complicated to download the right things and
install so I'm not happy about leaving v4l1 right now.

I'm running current cvs of zapping.


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

>Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-11-14 10:41

Message:
Logged In: YES 
user_id=7928

Well, closing as WontFix. Lockups aren't Z's fault, after
all, it's possibly something in some driver.
Sorry for being vague, but this isn't something I can fix or
isolate.

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

Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-07-29 09:59

Message:
Logged In: YES 
user_id=7928

Perhaps strace would help debugging:
strace zapping
Please just send the last lines, not the whole log :-)

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

Comment By: Bill Vinson (billvinson)
Date: 2001-07-07 22:02

Message:
Logged In: YES 
user_id=38100

I get a very similar freeze, but only when i enter
preferences.  This is not a random freeze for me.  It only
happens at that exact point in time.

It doesn't just lock X...It causes a solid hang where I
cannot ssh into the machine from outside.

Other than that the program is looking quite nice :)

Keep up the good work

Bill Vinson

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

Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-05-28 14:45

Message:
Logged In: YES 
user_id=7928

Actually, the statement about what v4l does isn't accurate.
v4l is an XFree module that talks to the v4l device telling
it where to put the data to be blitted (i.e., the location
of the destination window). The only difference between
using v4l and 'pure' overlay mode is that in 'pure' overlay
mode is Z who tells /dev/video where to put the data
(needing some flicker to clear the screen contents), and
with v4l is XFree (that needs no flicker). Well, and the
lockup you are seeing, of course :-)

In Zapping there are basically four modes of operation:
- TTX
- Overlay in a Window. Z does almost nothing, the HW/Xfree
takes care.
- Capture in a Window. The image is processed and blitted,
this can take some time, probably you are seeing this.
- Fullscreen. Just like Overlay, but in a big window that
uses the whole screen.

Capture can be slow if you are using, say, a 24/32 bpp,
unaccelerated XPutImage and a slow box (or a unaccelerated X
driver). There's no way to avoid the cpu usage in this case.
In my setup (Matrox G400 with accelerated YUV->RGB scaling,
PII350) 0% cpu is used.
But overlay (View/Overlay) should be faster, since Z does no
processing, just telling the HW "hey, blit that image data
from x1, y1 to x2, y2". And it gets blitted.

So, in conclusion, I do not know how to make it run faster
for you in Capture mode (i even think it isn't possible) :-(

About the other question, bttv2 is what i use regularly. it
turns out to be *very* stable (i've never crashed it, which
i cannot say of bttv 0.7.x). And the api is nicer. And it's
well maintained. And supports the same hw as bttv does. And
works with interlaced YVU420. And has timestamping. And i
just love it (especially when i compare it to bttv :-)).
Those are my abridged impressions, but, as usual, your
mileage might vary. If bttv doesn't crash for you, you don't
care about keeping lip-sync when you record mpegs, and you
don't need to use the (imho) ugly V4L API (V4L2 is much more
elegant), then there's no problem. The only drawback when
using bttv2 is that sizes are rounded to the nearest
16-multiplus, so you might see a border around the image in
Z. Not a big deal, but doesn't look good either.

Installation is easy, just 'make && make install', btw.

Regards,
Iñaki

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

Comment By: James Green (james)
Date: 2001-05-28 09:21

Message:
Logged In: YES 
user_id=1174

OK an update:

I rebooted, stopped non-essential processes (anticipating a lockup), and edited my XFree86-4 config file to remove the line 'Load "v4l"'.

I then started X, and ran Zapping (latest cvs today).

So far, after about 1.5hrs, no hang. Touch wood. I'll keep the app open for a while longer. Usually the hang happens within a couple of hours, but at random.

Also, fullscreen now works (hooray!). Sadly, windows mode now takes up to 80% cpu time. Which _really_ sucks.

I'm told that with v4l loaded into XF4, windowed mode will use overlay, and thus no cpu; but fullscreen won't work. Removing v4l from xf4 makes the system use software scaling meaning high cpu usage but also fullscreen.

Pity we can't do what win32 does and use a combination of them both (overlay in windowed mode, scaling in fullscreen).

Also, if I have the window open quite large (640x480), lines appear on the far right, distoring the image.

I wonder if bttv2/v4l2 will do any better? Is it worth trying?


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

Comment By: Iñaki García Etxebarria (garetxe)
Date: 2001-05-22 12:56

Message:
Logged In: YES 
user_id=7928

Hi James,

thanks a lot for the interest.

If Z makes the system hang, then it's XFree's (or kernel's)
fault. It's probably just that it's triggering a bug xawtv
doesn't trigger.

To do the debugging, and if it's completely random, then the
only way to go is to populate the source with messages (each
printv should also do a flush() and usleep() to make sure
the appropiate message gets printed out). Then you run from
a console and track it down to the specific routine that
causes it to hang. Then we report the bug to XFree or
kernel, hoping that it gets fixed.

I understand that this is a huge task, and perhaps it won't
help at all (the driver just hangs somewhen, somewhere,
nothing deterministic as calling a specific routine).
Indeed, in Overlay mode Z does almost nothing, apart from
processing X events.

Perhaps it is bad interaction between some XFree modules
(DRI, DGA, GLX, ...). Try disabling all extensions in
XF86Config and go on adding one by one.

Sorry, but I doubt this is really something Z does,
Iñaki

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

Comment By: James Green (james)
Date: 2001-05-19 11:16

Message:
Logged In: YES 
user_id=1174

Attaching my XFree86 log file.


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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=425468&group_id=2599

[Zapping-misc] Aspect ratio support not working

[James G. <jg...@cy...>]

In reference to
http://sourceforge.net/tracker/index.php?func=detail&aid=423785&group_id=2599&atid=102599

I have a digital cable box which talks to my video card over the
motherboard, and gets overlayed to screen using Xvideo.

When I switch programmes and notice one is in 4:3, and one is in 16:9
modes, zapping does not alter the window to compensate.

According to the bug above, which I filed, it should.

I am using GNOME+E. Any ideas?

jg

[Zapping-misc] [ zapping-Bugs-481143 ] Gtk-CRITICAL

[<no...@so...>]

Bugs item #481143, was opened at 2001-11-12 18:31
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=481143&group_id=2599

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Gtk-CRITICAL

Initial Comment:
[bruceg@linux bruceg]$ zapping

Gtk-CRITICAL **: file gtkmain.c: line 582
(gtk_main_quit): assertion `main_loops != NULL' failed.

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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=102599&aid=481143&group_id=2599

Re: [Zapping-misc] (no subject)

[<ga...@cl...>]

> i think zapping is the best tv app 4 linux....
He, thanks :-)

> but zapping could be the best (if you add some features from this app htt=
p://deinterlace.sourceforge.net/downloads.htm )   :)
Yep, i know the app. What did you miss most?

Regards,
I=F1aki

Re: [Zapping-misc] mpeg4

[E. <ga...@eu...>]

> How about adding MPEG4IP support to zapping?
> MPEG4 compression is nice, i hear:)
Me 2 :-) We definitively want to add more compression formats, it's just
a matter of time.
If you are interested in helping, the place to look is the rte module in
cvs, take a look to:
http://zapping.sf.net/download.php
for cvs instructions.

Regards,
I=F1aki

[Zapping-misc] mpeg4

[David C. <dc...@ho...>]

How about adding MPEG4IP support to zapping?
MPEG4 compression is nice, i hear:)





_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp