Re: [Icewing-user] Problems intializing v4l-device in iceWing
Brought to you by:
floemker
From: Frank L. <floemker@TechFak.Uni-Bielefeld.DE> - 2006-10-09 15:37:24
|
Hello, On Mon, Oct 09, 2006 at 05:05:51PM +0200, Frank Loemker wrote: > Hello, > > On Mon, Oct 09, 2006 at 01:36:48PM +0200, Axel Haasch wrote: > > I am trying to get iceWing cooperating with my Pinnacle Studio > > DC10plus video capture board, but unfortuanetly I wasn't successful so far. > > Maybe you've got an idea? > > > >... > > > > That wasn't successful either. So, what can I do next? > > Are there any messages in the file /var/log/messages concerning the capture > board? > > It might be necessary to increase the verbosity level of the syslog > system. If you have syslog-ng, something like > > destination messages { file("/var/log/messages"); }; > log { source(src); destination(messages); }; > > in the file > > /etc/syslog-ng/syslog-ng.conf > > might work (or something similar). Don't forget to restart the / send > a HUP to the syslog daemon. > > > Does it make sense to > > fetch a recent devel-version from the iceWing repository? > > To fix the problem -- no, nothing concerning the grabber interaction has > changed there. To see the latest and greatest features and help enhancing > iceWing -- yes of course :) And a second possibility / try: What happens if you try to load the zoran kernel module with the option "v4l_bufsize=700"? It seems, that the default buffer size is set to 128k, which, if this is really right, is quite small. Or, alternatively, set the Downsampling in iceWing to 3 BEFORE iceWing accesses the grabber for example by starting iceWing with -rc "Other.Downsampling=3" Bye, -- Frank Loemker |