Thread: [libdc1394-devel] Question regarding the dc1394_vloopback
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Ivica I. B. <ico...@gm...> - 2006-03-17 08:08:09
|
Greetings! I have a small question regarding the current development of the dc1394_vloopback program and its capabilities. Namely, I have a Canopus ADVC-100 firewire interface which simply offers S-Video I/O (among other things). My Linux system sees it ok and it works fine via dvgrab (in Kino for instance). The nodes this device generates are /dev/video1394/0 and /dev/raw1394. Considering that the stream from it is TTBOMK non-compressed, I was under the impression that it should work with the aforementioned program. I am trying to get a v4l stream from this device (I have hooked-up a regular analog camera to the ADVC's S-video input), so that I can use it in an application that is v4l compatible. However, no matter what settings = I pick, I get a response that "no cameras found :(" (i.e. dc1394_vloopback --video1394=3D/dev/video1394/0 --vloopback=3D/dev/video0). I tried using th= e app both with and without the vloopback driver without any success. For this reason, I was wondering if any of the developers had any ideas as to whethe= r what I am trying to do is even possible and if so, how? My system specs are as follows: Ubuntu Hoary (32-bit), 2.6.10 kernel, libdc1394 1.0.0.3, using eMachines m6807 (AMD64) with a 4-pin firewire port= . Thank you very much for your time and effort! Best wishes, Ico |
From: Damien D. <da...@do...> - 2006-03-20 01:24:18
|
Hi Ivica, On Fri, 2006-03-17 at 03:08 -0500, Ivica Ico Bukvic wrote: > Greetings! > > I have a small question regarding the current development of the > dc1394_vloopback program and its capabilities. Namely, I have a > Canopus ADVC-100 firewire interface which simply offers S-Video I/O > (among other things). My Linux system sees it ok and it works fine via > dvgrab (in Kino for instance). The nodes this device generates > are /dev/video1394/0 and /dev/raw1394. Considering that the stream > from it is TTBOMK non-compressed, I was under the impression that it What is TTBOMK? > should work with the aforementioned program. I am trying to get a v4l > stream from this device (I have hooked-up a regular analog camera to > the ADVC's S-video input), so that I can use it in an application that > is v4l compatible. However, no matter what settings I pick, I get a > response that "no cameras found :(" (i.e. dc1394_vloopback > --video1394=/dev/video1394/0 --vloopback=/dev/video0). I tried using > the app both with and without the vloopback driver without any > success. For this reason, I was wondering if any of the developers had > any ideas as to whether what I am trying to do is even possible and if > so, how? > > My system specs are as follows: Ubuntu Hoary (32-bit), 2.6.10 kernel, > libdc1394 1.0.0.3, using eMachines m6807 (AMD64) with a 4-pin firewire > port. If your system sees the device with dvgrab/kino then it means it's an AVC device. Those won't work with libdc1394 which is for IIDC cameras. Damien -- _ Damien 'Takahara' Douxchamps, PhD ('- Post-doctoral investigator //\ Image Processing Group, NAIST V_/_ http://chihara.aist-nara.ac.jp/ |
From: Ivica I. B. <ico...@gm...> - 2006-03-20 03:33:12
|
Thank you very much for your reply! Please see my comments below. > -----Original Message----- > From: Damien Douxchamps [mailto:da...@do...] > Sent: Sunday, March 19, 2006 8:23 PM > To: Ivica Ico Bukvic > Cc: lib...@li... > Subject: Re: [libdc1394-devel] Question regarding the dc1394_vloopback > > Hi Ivica, > > On Fri, 2006-03-17 at 03:08 -0500, Ivica Ico Bukvic wrote: > > Greetings! > > > > I have a small question regarding the current development of the > > dc1394_vloopback program and its capabilities. Namely, I have a > > Canopus ADVC-100 firewire interface which simply offers S-Video I/O > > (among other things). My Linux system sees it ok and it works fine via > > dvgrab (in Kino for instance). The nodes this device generates > > are /dev/video1394/0 and /dev/raw1394. Considering that the stream > > from it is TTBOMK non-compressed, I was under the impression that it > > What is TTBOMK? "to the best of my knowledge" > > > should work with the aforementioned program. I am trying to get a v4l > > stream from this device (I have hooked-up a regular analog camera to > > the ADVC's S-video input), so that I can use it in an application that > > is v4l compatible. However, no matter what settings I pick, I get a > > response that "no cameras found :(" (i.e. dc1394_vloopback > > --video1394=/dev/video1394/0 --vloopback=/dev/video0). I tried using > > the app both with and without the vloopback driver without any > > success. For this reason, I was wondering if any of the developers had > > any ideas as to whether what I am trying to do is even possible and if > > so, how? > > > > My system specs are as follows: Ubuntu Hoary (32-bit), 2.6.10 kernel, > > libdc1394 1.0.0.3, using eMachines m6807 (AMD64) with a 4-pin firewire > > port. > > If your system sees the device with dvgrab/kino then it means it's an > AVC device. Those won't work with libdc1394 which is for IIDC cameras. I see. In that case, I would greatly appreciate your insight in the following questions: 1) I believe that my camcorder is being registered as an AVC device (Kino offers me AVC options). Does this mean that there is no way for me to emulate v4l device out of this one? 2) Is v4l deprecated and if so, will the apps which currently rely upon v4l likely move to support dv1394 and other devices (obviously this is hypothetical question as no one knows whether the projects in question will continue to be supported and/or developed)? 3) If v4l is to continue to coexist with dv1394/raw1394, is there any other way to crossover between the two (i.e. via some kind of a virtual device/converter/plugin/whatever)? If not, is there any plans to do so? Again, thank you very much for all your assistance in the matter! Sincerely, Ico > > Damien > > -- > _ Damien 'Takahara' Douxchamps, PhD > ('- Post-doctoral investigator > //\ Image Processing Group, NAIST > V_/_ http://chihara.aist-nara.ac.jp/ |
From: Damien D. <da...@do...> - 2006-03-22 03:28:47
|
Hello Ivica, On Sun, 2006-03-19 at 22:33 -0500, Ivica Ico Bukvic wrote: > Thank you very much for your reply! Please see my comments below. > > > -----Original Message----- > > From: Damien Douxchamps [mailto:da...@do...] > > Sent: Sunday, March 19, 2006 8:23 PM > > To: Ivica Ico Bukvic > > Cc: lib...@li... > > Subject: Re: [libdc1394-devel] Question regarding the dc1394_vloopback > > > > Hi Ivica, > > > > On Fri, 2006-03-17 at 03:08 -0500, Ivica Ico Bukvic wrote: > > > Greetings! > > > > > > I have a small question regarding the current development of the > > > dc1394_vloopback program and its capabilities. Namely, I have a > > > Canopus ADVC-100 firewire interface which simply offers S-Video I/O > > > (among other things). My Linux system sees it ok and it works fine via > > > dvgrab (in Kino for instance). The nodes this device generates > > > are /dev/video1394/0 and /dev/raw1394. Considering that the stream > > > from it is TTBOMK non-compressed, I was under the impression that it > > > > What is TTBOMK? > > "to the best of my knowledge" I thought it was a weird non-compressed format ;-) Well, if it is seen by Kino it is DV compressed, TTBOMK ;-) > > > should work with the aforementioned program. I am trying to get a v4l > > > stream from this device (I have hooked-up a regular analog camera to > > > the ADVC's S-video input), so that I can use it in an application that > > > is v4l compatible. However, no matter what settings I pick, I get a > > > response that "no cameras found :(" (i.e. dc1394_vloopback > > > --video1394=/dev/video1394/0 --vloopback=/dev/video0). I tried using > > > the app both with and without the vloopback driver without any > > > success. For this reason, I was wondering if any of the developers had > > > any ideas as to whether what I am trying to do is even possible and if > > > so, how? > > > > > > My system specs are as follows: Ubuntu Hoary (32-bit), 2.6.10 kernel, > > > libdc1394 1.0.0.3, using eMachines m6807 (AMD64) with a 4-pin firewire > > > port. > > > > If your system sees the device with dvgrab/kino then it means it's an > > AVC device. Those won't work with libdc1394 which is for IIDC cameras. > > I see. In that case, I would greatly appreciate your insight in the > following questions: > > 1) I believe that my camcorder is being registered as an AVC device (Kino > offers me AVC options). Does this mean that there is no way for me to > emulate v4l device out of this one? You can do that. Just decompress the video and send it on a V4L channel with the vloopback module. Actually, Kino may already provide that feature. If not I may have time to hack this kind of thing next month. > 2) Is v4l deprecated and if so, will the apps which currently rely upon v4l > likely move to support dv1394 and other devices (obviously this is > hypothetical question as no one knows whether the projects in question will > continue to be supported and/or developed)? V4L is not deprecated. Or if it is, it's by V4L2. V4L works with many classic video devices, dv1394 is for dv only. > 3) If v4l is to continue to coexist with dv1394/raw1394, is there any other > way to crossover between the two (i.e. via some kind of a virtual > device/converter/plugin/whatever)? If not, is there any plans to do so? I think you will need to write your own code for it (unless I have time next month). A simple command line program should not be very difficult: Get the video, decompress it and send it on V4L. If you're interested in doing that you will find better answers in a dv-related mailing list. Damien -- _ Damien 'Takahara' Douxchamps, PhD ('- Post-doctoral investigator //\ Image Processing Group, NAIST V_/_ http://chihara.aist-nara.ac.jp/ |