Thread: beginner's problem with dvgrab
Brought to you by:
aeb,
bencollins
From: Steve S. <st...@cs...> - 2000-04-25 03:48:10
|
Hello, I hate to trouble you, but I am having problems getting dvgrab to work. I have installed the ieee1394-2.2.14-20000318 patch in a 2.2.14 kernel and that seems to work just fine. At boot time I see: ieee1394: registered ohci1394 driver, initializing now ohci1394: looking for Ohci1394 cards ohci1394_0: allocated interrupt 10 ohci1394_0: remapped memory spaces reg 0xc8013000 ohci1394_0: soft reset finished ohci1394_0: max packet size = 2048 bytes ohci1394_0: 4 iso contexts available ohci1394_0: Receive DMA ctx=2 initialized ohci1394_0: Receive DMA ctx=0 initialized ohci1394_0: Receive DMA ctx=1 initialized ohci1394_0: AT dma ctx=0 initialized ohci1394_0: AT dma ctx=1 initialized ohci1394_0: resetting bus on request and attempting to become root ieee1394: detected 1 ohci1394 adapter ieee1394: 1 host adapter initialized I have built your dvgrab 0.7 with the libraw1394-0.6 library. I am trying to capture the raw DV so I can decode it with playdv (the libDV package from OGI). I have a SIIG card with a TI TSB12LV23 chip on it. If I run your dvgrab like this: dvgrab --ntsc --raw --frames 200 raw.dv without a camera connected I see these messages in the log file: ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: listening enabled on channel 63 That seems okay to me. If I hook up a camera (a Canon Optura, or a Panasonic Palmsight - I tried two different cameras) I get zillions of these messages: ieee1394: received packet during reset; ignoring There are huge numbers sent per second - causing klogd to use up 20% of my 533MHz CPU just throwing them away (I must not have the syslog.conf set to store them away, thankfully). If I unplug the DV connector from the camera the reset messages stop with one additional message: ieee1394: received packet during reset; ignoring ieee1394: received packet during reset; ignoring ohci1394_0: Got phy packet ctx=0 ... discarded The file "raw.dv" does not receive any data (i.e. it is always empty). If I terminate the dvgrab program then this message is logged: ohci1394_0: listening disabled on iso channel 63 which also makes sense to me. If I plug in the camera when the program is not running I see these log messages: ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded (there are 3 of them with a single plugging in operation, and one more when I unplug). Any idea what I am doing wrong? I am not totally unfamiliar with UNIX kernels (I have been dabbling with them since 1973), but IEEE1394 and DV are new to me (I have done some background reading, but not enough). Can you start me in the right direction? Do I need to supply more information? Thank you, it looks like a nice little package, once I get over the initial problems. st...@cs... |
From: Alastair M. <ala...@aj...> - 2000-04-25 15:52:45
|
Steve Sutphen wrote: > > Hello, > I hate to trouble you, but I am having problems getting dvgrab > to work. I have installed the ieee1394-2.2.14-20000318 patch in > a 2.2.14 kernel and that seems to work just fine. At > boot time I see: [snip] For some reason the OCHI driver doesn't always seem to 'take' when first loaded, particularly when devices are plugged in later. My routine now is to wait until everything has booted up, make sure my devices are plugged in/powered on, and then insmod the driver modules. Then I run testlibraw or gscanbus to make sure I'm really seeing everything. (And if not, unload/reload the modules.) > I have built your dvgrab 0.7 with the libraw1394-0.6 library. > I am trying to capture the raw DV so I can decode it with playdv > (the libDV package from OGI). > > I have a SIIG card with a TI TSB12LV23 chip on it. > > If I run your dvgrab like this: > dvgrab --ntsc --raw --frames 200 raw.dv > without a camera connected I see these messages in the log file: > ohci1394_0: Got phy packet ctx=0 ... discarded > ohci1394_0: listening enabled on channel 63 Note, the "--raw" option to dvgrab isn't very helpful for further playback: it writes *every* packet, including the short (16-byte) ones, and prepends a 4-byte length field to each one. Also, the "--frames" count in this case is really a packet count, you have to grab a lot of those to make a real video frame. I submitted a patch yesterday that adds a "--dv" option that strips short packets and extraneous header info, "playdv" understands the output from that. [snip] > > Can you start me in the right direction? Do I need to supply more > information? > I found 'testlibraw' (in the libraw package) and 'gscanbus' (downloadable from ftp://ftp.fokus.gmd.de/pub/cc/cats/usr/ami/ ) to be helpful in getting my setup running. If you can control your camera's functions (ie with the camera in VTR mode) from the gscanbus GUI then all is communicating properly async, so iso grabs with dvgrab should then be okay. Hope this helps. -- Alastair |