Hi,
I have tried firewire capture on windows and get similar results â I just get a kind of set of lines (see attached image).
I have a feeling that this is due to vic assuming that the camera source is a standard size (e.g. 352x288) when it isn't. It looks like it is picking up an image from the camera (it changes when I move around in front of the camera) but it is only using some of that image (I think).
This was using a Sony MiniDV camera.
Andrew :)
---------------------------------------------------------
Andrew G D Rowley
Senior Development Officer
Research Computing Services
The University of Manchester
Kilburn Building, Oxford Road
Manchester, M13 9PL
t : +44 (0) 161 275 0685
e : Andrew.Rowley@xxxxxxxxxxxxxxxx
w : www.manchester.ac.uk/researchcomputing
---------------------------------------------------------
From: owner-ag-tech@xxxxxxxxxxx [mailto:owner-ag-tech@xxxxxxxxxxx] On Behalf Of Andrew Ford
Sent: 18 April 2008 21:21
To: Douglas Kosovic
Cc: ag-tech
Subject: Re: [AG-TECH] Any more H.264 news?
On Wed, Apr 16, 2008 at 8:54 PM, Douglas Kosovic <douglask@xxxxxxxxxxxxxx> wrote:
UQ Vislab vic doesn't do any transcoding from DV (or HDV) firewire devices to other codecs, so if the codebase was merged as it stands now, it wouldn't do what you are trying to do anyway.
Well, doing raw DV without transcoding would be fine (if it were on both platforms), since we can spare the bandwidth - that's what we're already doing via the ExtendedVideo services on Windows, but we'd like to be able to move on to something more cross-platform.
Have you tried using DV4Linux so that your Camcorder can be seen as a V4L device? I haven't tried it myself.
Interesting, I'll have to try that out. Would vic theoretically be able to transmit 640 (or 720)x480 video from a V4L device?As for the flashing verticle line artifacts on Windows, I don't seem them, but I was using a quad-core 2.6GHz Xeon.
We've seen it here on a couple of different systems - a Dell w/ a dual-core + hyperthreading 3.46Ghz CPU, and Suns with 2x dual-core 2.2Ghz Opterons - so I doubt it's CPU-related. Can anyone else chime in if they've tried the firewire capture on Windows?
--Andrew