Re: [GnomeMeeting-list] gnomemeeting + ATI Wonder pro TV Capture card
- From: Sanjay Darisi <sanjay_darisi leafnetworks net>
- To: GnomeMeeting mailing list <gnomemeeting-list gnome org>
- Subject: Re: [GnomeMeeting-list] gnomemeeting + ATI Wonder pro TV Capture card
- Date: Thu, 05 Jan 2006 16:48:58 -0500
Damien Sandras wrote:
Le jeudi 05 janvier 2006 à 12:37 -0500, Sanjay Darisi a écrit :
Damien Sandras wrote:
Le jeudi 05 janvier 2006 à 11:33 -0700, sanjay_darisi leafnetworks net a
OK, this is what I'm doing. When I open gnomemeeting it tries to read from the camera as it is connected but displays nothing, no video. I can open
up all the menus and close them fine (changing any of the settings freezes it too). When I hit the camera button, as you said it tries to stop the
video and freezes again (as the button is a toggle button).
So, when I start gnomemeeting, it connects to the camera but displays no video.
I would need a backtrace at this point of time, if possible in debug
symbols. But my guess would be that for some reason, the V4L plugin is
blocked at some stage, due to the driver.
Have you tried reporting the problem to the driver author?
Backtrace from gdb??
I don't see any debug statements when I give d -4 as arguement to
gnomemeeting? I've compiled it from source. Do I have to do something to
enable debug statements ?
I'm just wondering how xawtv was able play the video. I believe it uses
the V4L plugin right? I haven't reported the problem to the driver
author yet. Will do it soon.
xawtv is not using the same color formats, and it is not using our V4L
I see you built from sources, are you sure of what you have done?
Sometimes it can be due to the fact you are using old plugins with a
newer pwlib. The fact tht you have no debug output proves something else
Just now I observed something in my lsmod. I was looking at the modinfo
of the tuner card driver modules (cx88xx) and looks like they are v4l2
drivers. There was another v4l2_compat module for v41(1) compatibility
layer for v4l2 drivers. Do you think this is the problem? As the driver
is a v412 driver with v4l compatibilty layer, this would cause prbs. I
saw an option in pwlib for v4l2, does this help? Or gnomemeeting wont'
be able to read from the v4l2 drivers?
] [Thread Prev