On Wed, Apr 16, 2008 at 8:54 PM, Douglas Kosovic <<a href="mailto:douglask@itee.uq.edu.au">douglask@itee.uq.edu.au</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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.</blockquote><div><br>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.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Have you tried using DV4Linux so that your Camcorder can be seen as a V4L device? I haven't tried it myself.</blockquote>
<div> <br>Interesting, I'll have to try that out. Would vic theoretically be able to transmit 640 (or 720)x480 video from a V4L device?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As for the flashing verticle line artifacts on Windows, I don't seem them, but I was using a quad-core 2.6GHz Xeon.</blockquote><div><br>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?<br>
<br>--Andrew<br></div></div>