Juju stack and dvsource-firewire

[Euan de Kock]

James, have you retried the camera in an existing machine that is not using the express cards. I suspect the camera may have an issue with it's connector.

Also from previous experience with audio devices, the hardware chip on the firewire card can have a big impact on performance. For audio it's normal to only use TI cards.

regards,

Euan.


On 10/05/2012 13:30 James Bromberger wrote:

On 2/05/2012 9:04 PM, Ben Hutchings wrote:
> dvgrab and
      dvsource-firewire-rtsp use libraw1394 for Firewire I/O. This works
      with both old and new stacks and will look for the corresponding
      device nodes for both. Ben.

Thanks Ben - reread the strace and I see it accessing both device names.

Using kernel 3.2.0-2-amd64 and dvsource-firewire (not -rtsp) from 0.8.3.6-1+b2 gives:

Error: invalid source specified


Whereas dmesg shows:

*firewire_ohci: Added fw-ohci device 0000:05:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x2
firewire_core: created device fw0 GUID 0102030400000510, S400
*
And when replugging the camera:
*
firewire_core: skipped bus generation, destroying all nodes
firewire_core: rediscovered device fw0*

And the /dev/fw0 device is returned. Gscanbus doesn't show anything connected, and Kino says "No AV/C compliant cam connected or not switched on?". This was working with testing 8 weeks ago (laptop is imaged from FAI). The camera is the same (JVC GR-DV4), the firewire interface is an ExpressCard. I compiled up jujuutils (doesn't seem to be in Debian Testing), but /lsfirewirephy/ just gives output of "timeout".

Using dvgrab test says "no camera exists".

I've switched to a /second /camera (a Panasonic NV-DS65A), and now I also get :

phy config: card 0, new root = ffc1, gap_count=5
IRM is not 1394a compliant, making local node (ffc0) root.
phy config: card 0, new root = ffc0, gap_count=5


... and capture works fine. lsfirewirephy says this Panasonic camera is a Texas Instruments XIO2200A. So it seems that one of my cameras -- the JVC which we've been happily using for the last year -- is no longer working (but the bus resets when re-plugged)? Hmm. Anyone know how this would have happened? Not like the camera has had any changes to its firmware. I've also tried changing the firewire ID (1, 3, 7) although its the only device on the bus, but no dice...

  James

-- 
/Mobile:/ +61 422 166 708, /Email:/ james_AT_rcpt.to
PLUG President 2012: http://www.plug.org.au <http//www.plug.org.au>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/dvswitch-devel/attachments/20120510/a842683e/attachment.html>