Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Whats 'the pylon software' ? How does it control the camera without a /dev/video?
pix_video requires normal video interfaces
On Sun, Aug 5, 2018 at 3:35 PM, Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
I guess the producer calls its software pylon. Anyway maybe I have to do something with the udev rulers, loos like it can not write into it.
On Sun, Aug 5, 2018 at 4:32 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
Whats 'the pylon software' ? How does it control the camera without a /dev/video?
pix_video requires normal video interfaces
On Sun, Aug 5, 2018 at 3:35 PM, Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
From what i see from that camera, it doesnt use video4linux , and thus, is
-not- supported to use in PureData
On Sun, Aug 5, 2018 at 5:04 PM, Csaba Láng langcsaba@gmail.com wrote:
I guess the producer calls its software pylon. Anyway maybe I have to do something with the udev rulers, loos like it can not write into it.
On Sun, Aug 5, 2018 at 4:32 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
Whats 'the pylon software' ? How does it control the camera without a /dev/video?
pix_video requires normal video interfaces
On Sun, Aug 5, 2018 at 3:35 PM, Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Bast,
how did you check it? do you know any other high speed camera around 150fps and above which is puredata compatible? Thanks for your answer anyway.
On Sun, Aug 5, 2018 at 6:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
From what i see from that camera, it doesnt use video4linux , and thus, is -not- supported to use in PureData
On Sun, Aug 5, 2018 at 5:04 PM, Csaba Láng langcsaba@gmail.com wrote:
I guess the producer calls its software pylon. Anyway maybe I have to do something with the udev rulers, loos like it can not write into it.
On Sun, Aug 5, 2018 at 4:32 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
Whats 'the pylon software' ? How does it control the camera without a /dev/video?
pix_video requires normal video interfaces
On Sun, Aug 5, 2018 at 3:35 PM, Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
By the way I found out that this camera uses HALCON, and there is a plugin to pix_video: https://github.com/rfabbri/Gem/tree/master/plugins/videoHALCON Should it work?
On Sun, Aug 5, 2018 at 9:24 PM Csaba Láng langcsaba@gmail.com wrote:
Bast,
how did you check it? do you know any other high speed camera around 150fps and above which is puredata compatible? Thanks for your answer anyway.
On Sun, Aug 5, 2018 at 6:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
From what i see from that camera, it doesnt use video4linux , and thus, is -not- supported to use in PureData
On Sun, Aug 5, 2018 at 5:04 PM, Csaba Láng langcsaba@gmail.com wrote:
I guess the producer calls its software pylon. Anyway maybe I have to do something with the udev rulers, loos like it can not write into it.
On Sun, Aug 5, 2018 at 4:32 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
Whats 'the pylon software' ? How does it control the camera without a /dev/video?
pix_video requires normal video interfaces
On Sun, Aug 5, 2018 at 3:35 PM, Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg < buzz@spacedout.nl> wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
> Dear list, > > I use special 227fps usb cameras. > lsusb shows the id and the bus. > Bus 006 Device 002: ID 2676:ba02 Basler AG ace > How can I find the path to it and use with pix_video? > Test software shows device input. > device0-7 can not find it as /dev/video* does not exist. > Best, > > Popesz > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > > _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 08/05/2018 10:15 PM, Csaba Láng wrote:
By the way I found out that this camera uses HALCON, and there is a plugin to pix_video: https://github.com/rfabbri/Gem/tree/master/plugins/videoHALCON Should it work?
yes, it should work. there's also a PYLON backend, which you should be able to use as an alternative.
however, you must compile both videoHALCON and videoPYLON yourself (that is: they are not included in e.g. the Debian packages because of licensing reasons)
fgamrds IOhannes
Thanks Iohannes, just now I found the PYLON backend and this is exactly what I need. I see you already explained how to compile it but not sure if I can manage :) By the way, do I have to compile GEM too or the deken version should be OK
On Sun, Aug 5, 2018 at 10:38 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/05/2018 10:15 PM, Csaba Láng wrote:
By the way I found out that this camera uses HALCON, and there is a
plugin
to pix_video: https://github.com/rfabbri/Gem/tree/master/plugins/videoHALCON Should it work?
yes, it should work. there's also a PYLON backend, which you should be able to use as an alternative.
however, you must compile both videoHALCON and videoPYLON yourself (that is: they are not included in e.g. the Debian packages because of licensing reasons)
fgamrds IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Iohannes,
the new version of pylon5 is installed in /opt/pylon5 folders like: bin lib64 I tried to export instead of
$ export PYLON_ROOT=${HOME}/lib/pylon $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PATH=${PYLON_ROOT}/bin/:${PATH} $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib $ PylonViewerApp
like this:
$ export PYLON_ROOT=${HOME}/opt/pylon5 $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PYLON_ROOT=${HOME}/opt/pylon5 $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib64 $ PylonViewerApp PylonViewerApp: command not found
What is the right way with the new version of PYLON?
Can you advice?
Popesz
On Sun, Aug 5, 2018 at 10:42 PM Csaba Láng langcsaba@gmail.com wrote:
Thanks Iohannes, just now I found the PYLON backend and this is exactly what I need. I see you already explained how to compile it but not sure if I can manage :) By the way, do I have to compile GEM too or the deken version should be OK
On Sun, Aug 5, 2018 at 10:38 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/05/2018 10:15 PM, Csaba Láng wrote:
By the way I found out that this camera uses HALCON, and there is a
plugin
to pix_video: https://github.com/rfabbri/Gem/tree/master/plugins/videoHALCON Should it work?
yes, it should work. there's also a PYLON backend, which you should be able to use as an alternative.
however, you must compile both videoHALCON and videoPYLON yourself (that is: they are not included in e.g. the Debian packages because of licensing reasons)
fgamrds IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 08/05/2018 10:54 PM, Csaba Láng wrote:
Iohannes,
the new version of pylon5 is installed in /opt/pylon5 folders like: bin lib64 I tried to export instead of
$ export PYLON_ROOT=${HOME}/lib/pylon $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PATH=${PYLON_ROOT}/bin/:${PATH} $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib $ PylonViewerApp
like this:
$ export PYLON_ROOT=${HOME}/opt/pylon5 $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PYLON_ROOT=${HOME}/opt/pylon5 $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib64 $ PylonViewerApp PylonViewerApp: command not found
What is the right way with the new version of PYLON?
no idea (i haven't touched any GiGE related stuff for some time)
however, the part about running PylonViewerApp is just a simplistic test to see whether the rest is correctly set up. it depends on an application PylonViewerApp, which apparently is no longer shipped with Pylon5. the good news is, that you can simply ignore it.
just proceed with the build instruction and see where it gets you.
gfmdsar IOhannes
PylonViewerApp is in the /opt/pylon5/bin folder and works fine. But I do not have lib/pylon folder instead /opt/pylon5 and lib folder is called lib64. Should I continue with the original PATH? Sorry for the newbie question By the way it is not a GigE camera but USB3, but from this point of view I guess does not matter
On Sun, Aug 5, 2018 at 11:02 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/05/2018 10:54 PM, Csaba Láng wrote:
Iohannes,
the new version of pylon5 is installed in /opt/pylon5 folders like: bin lib64 I tried to export instead of
$ export PYLON_ROOT=${HOME}/lib/pylon $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PATH=${PYLON_ROOT}/bin/:${PATH} $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib $ PylonViewerApp
like this:
$ export PYLON_ROOT=${HOME}/opt/pylon5 $ export GENICAM_ROOT_V1_1=${PYLON_ROOT} $ export PYLON_ROOT=${HOME}/opt/pylon5 $ export LD_LIBRARY_PATH=${PYLON_ROOT}/lib64 $ PylonViewerApp PylonViewerApp: command not found
What is the right way with the new version of PYLON?
no idea (i haven't touched any GiGE related stuff for some time)
however, the part about running PylonViewerApp is just a simplistic test to see whether the rest is correctly set up. it depends on an application PylonViewerApp, which apparently is no longer shipped with Pylon5. the good news is, that you can simply ignore it.
just proceed with the build instruction and see where it gets you.
gfmdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 08/05/2018 11:07 PM, Csaba Láng wrote:
PylonViewerApp is in the /opt/pylon5/bin folder and works fine. But I do not have lib/pylon folder instead /opt/pylon5 and lib folder is called lib64. Should I continue with the original PATH?
you should use paths that exist on your system.
Sorry for the newbie question By the way it is not a GigE camera but USB3, but from this point of view I guess does not matter
right.
gfdsar IOhannes
Iohannes,
I tried to compile from Gem/Plugin/videoHALCON folder. This is the output
in terminal
$ ./configure ./configure --with-pylon=${HOME}/opt/pylon5
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: ./configure
configure: WARNING: unrecognized options: --with-pylon
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for ./configure-g++... no
checking for ./configure-c++... no
checking for ./configure-gpp... no
checking for ./configure-aCC... no
checking for ./configure-CC... no
checking for ./configure-cxx... no
checking for ./configure-cc++... no
checking for ./configure-cl.exe... no
checking for ./configure-FCC... no
checking for ./configure-KCC... no
checking for ./configure-RCC... no
checking for ./configure-xlC_r... no
checking for ./configure-xlC... no
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking build system type... Invalid configuration ./configure': machine./configure' not recognized
configure: error: /bin/bash ./config.sub ./configure failed
is@is:~/Downloads/Gem/plugins/videoHALCON$ make
make all-am
make[1]: Entering directory '/home/is/Downloads/Gem/plugins/videoHALCON'
make[1]: Leaving directory '/home/is/Downloads/Gem/plugins/videoHALCON'
is@is:~/Downloads/Gem/plugins/videoHALCON$ make install
make[1]: Entering directory '/home/is/Downloads/Gem/plugins/videoHALCON'
make[1]: Nothing to be done for 'install-exec-am'.
make[1]: Leaving directory '/home/is/Downloads/Gem/plugins/videoHALCON'
can you advise where it goes wrong?
On Sun, Aug 5, 2018 at 11:13 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/05/2018 11:07 PM, Csaba Láng wrote:
PylonViewerApp is in the /opt/pylon5/bin folder and works fine. But I do not have lib/pylon folder instead /opt/pylon5 and lib folder is called lib64. Should I continue with the original PATH?
you should use paths that exist on your system.
Sorry for the newbie question By the way it is not a GigE camera but USB3, but from this point of view
I
guess does not matter
right.
gfdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 08/06/2018 12:29 AM, Csaba Láng wrote:
Iohannes, I tried to compile from Gem/Plugin/videoHALCON folder. This is the output in terminal $ ./configure ./configure --with-pylon=${HOME}/opt/pylon5
that's certainly a typo. the line should read (without the leading "$"): $ ./configure --with-pylon=${HOME}/opt/pylon5
mgfsard IOhannes
Iohannes,
in the attachment I send you the errors from terminal. Looks like the path is already ok, checking for PYLON...yes at the end of configure. I need to have this work.
Thanks in advance.
Popesz
On Mon, Aug 6, 2018 at 9:02 AM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/06/2018 12:29 AM, Csaba Láng wrote:
Iohannes, I tried to compile from Gem/Plugin/videoHALCON folder. This is the output in terminal $ ./configure ./configure --with-pylon=${HOME}/opt/pylon5
that's certainly a typo. the line should read (without the leading "$"): $ ./configure --with-pylon=${HOME}/opt/pylon5
mgfsard IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
What would be the ultimate prefix to configure Gem with videoPYLON plugin? I just compiled from the source 0.93.3 (hope this is the latest as it is always hard to find it) and pix_video did not find any backend not only pylon.
On Mon, Aug 6, 2018 at 9:39 AM Csaba Láng langcsaba@gmail.com wrote:
Iohannes,
in the attachment I send you the errors from terminal. Looks like the path is already ok, checking for PYLON...yes at the end of configure. I need to have this work.
Thanks in advance.
Popesz
On Mon, Aug 6, 2018 at 9:02 AM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/06/2018 12:29 AM, Csaba Láng wrote:
Iohannes, I tried to compile from Gem/Plugin/videoHALCON folder. This is the
output
in terminal $ ./configure ./configure --with-pylon=${HOME}/opt/pylon5
that's certainly a typo. the line should read (without the leading "$"): $ ./configure --with-pylon=${HOME}/opt/pylon5
mgfsard IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
and the same for pix_film, no backend found: [pix_video]: no video backends found! [pix_film]: no movie decoding backends found!
How to fix it?
On Mon, Aug 6, 2018 at 12:39 PM Csaba Láng langcsaba@gmail.com wrote:
What would be the ultimate prefix to configure Gem with videoPYLON plugin? I just compiled from the source 0.93.3 (hope this is the latest as it is always hard to find it) and pix_video did not find any backend not only pylon.
On Mon, Aug 6, 2018 at 9:39 AM Csaba Láng langcsaba@gmail.com wrote:
Iohannes,
in the attachment I send you the errors from terminal. Looks like the path is already ok, checking for PYLON...yes at the end of configure. I need to have this work.
Thanks in advance.
Popesz
On Mon, Aug 6, 2018 at 9:02 AM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 08/06/2018 12:29 AM, Csaba Láng wrote:
Iohannes, I tried to compile from Gem/Plugin/videoHALCON folder. This is the
output
in terminal $ ./configure ./configure --with-pylon=${HOME}/opt/pylon5
that's certainly a typo. the line should read (without the leading "$"): $ ./configure --with-pylon=${HOME}/opt/pylon5
mgfsard IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2018-08-06 13:31, Csaba Láng wrote:
and the same for pix_film, no backend found: [pix_video]: no video backends found! [pix_film]: no movie decoding backends found!
How to fix it?
On Mon, Aug 6, 2018 at 12:39 PM Csaba Láng langcsaba@gmail.com wrote:
What would be the ultimate prefix to configure Gem with videoPYLON plugin? I just compiled from the source 0.93.3 (hope this is the latest as it is always hard to find it) and pix_video did not find any backend not only pylon.
i'm not exactly sure what you mean, but:
- the backends *must* live besides the Gem-binary that you load.
so if you use /home/csaba/.local/lib/pd/extra/Gem/Gem.pd_linux then you must also have a /home/csaba/.local/lib/pd/extra/Gem/videoPYLON.so
- if instead you use /usr/lib/pd/extra/Gem/Gem.pd_linux, then the
videoPYLON.so in ~/.local/ will *not* be used
- the backend plugin probably should have the same version as the Gem
version, and it might be required that both have been compiled with the same compiler (there was a breaking change between g++-4 and g++-5 making binaries incompatible). if you've already compiled videoPYLON, you should also compile Gem itself.
fgamsdr IOhannes
unfortunately, I have only Gem compiled, videoPYLON plugin was impossible to compile even with an old version of Pylon v2.1. Anyway it was for GigE, but USB is needed.
GEM: Graphics Environment for Multimedia GEM: ver: 0.93.git 03e8d06a GEM: compiled on Aug 6 2018
[pix_video]: backend #0='v4l2' : v4l2 analog [pix_video]: backend #1='v4l' : v4l analog [pix_video]: backend #2='dv4l' : dv4l dv [pix_video]: backend #3='dc1394' : dc1394 iidc [pix_video]: backend #4='unicap' : unicap analog libv4l2cpi [pix_video]: backend #5='vlc' <--- DISABLED
Popesz
On Mon, Aug 13, 2018 at 2:02 PM IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2018-08-06 13:31, Csaba Láng wrote:
and the same for pix_film, no backend found: [pix_video]: no video backends found! [pix_film]: no movie decoding backends found!
How to fix it?
On Mon, Aug 6, 2018 at 12:39 PM Csaba Láng langcsaba@gmail.com wrote:
What would be the ultimate prefix to configure Gem with videoPYLON
plugin?
I just compiled from the source 0.93.3 (hope this is the latest as it is always hard to find it) and pix_video did not find any backend not only pylon.
i'm not exactly sure what you mean, but:
- the backends *must* live besides the Gem-binary that you load.
so if you use /home/csaba/.local/lib/pd/extra/Gem/Gem.pd_linux then you must also have a /home/csaba/.local/lib/pd/extra/Gem/videoPYLON.so
- if instead you use /usr/lib/pd/extra/Gem/Gem.pd_linux, then the
videoPYLON.so in ~/.local/ will *not* be used
- the backend plugin probably should have the same version as the Gem
version, and it might be required that both have been compiled with the same compiler (there was a breaking change between g++-4 and g++-5 making binaries incompatible). if you've already compiled videoPYLON, you should also compile Gem itself.
fgamsdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2018-08-13 14:08, Csaba Láng wrote:
Anyway it was for GigE, but USB is needed.
PYLON is a transport agnostic API for accessing industrial type cameras. whether this is about GigE or USB4 doesn't really matter at all.
what does matter is that their API seems to be unstable, so Gem's videoPYLON can no longer compile...
fgamsdr IOhannes
I am a step closer to what find the devices. Looks like they appear in /dev/bus/usb/busnumbers and when I click on the [device /dev/bus/usb/006/002( for example, this is what pd prints out:
videoctl: device /dev/bus/usb/006/002 Cannot open '/dev/bus/usb/006/002': 25, Inappropriate ioctl for device
What does it mean exactly? The device works on 227fps
Best, Popesz
On Sun, Aug 5, 2018 at 3:35 PM Csaba Láng langcsaba@gmail.com wrote:
no /dev/video at all. If I connect a usb2 webcam, that works, /dev/video0 appears. user has access to the camera as the pylon software from the producer can see it immediately, could change the parameters such as the device name or resolution. But I need it in pd :)
On Sun, Aug 5, 2018 at 3:26 PM Bastiaan van den Berg buzz@spacedout.nl wrote:
- do you see /dev/video* when you plug it in
- does your user have access to that
just like any other camera?
On Sun, Aug 5, 2018 at 2:59 PM, Csaba Láng langcsaba@gmail.com wrote:
Dear list,
I use special 227fps usb cameras. lsusb shows the id and the bus. Bus 006 Device 002: ID 2676:ba02 Basler AG ace How can I find the path to it and use with pix_video? Test software shows device input. device0-7 can not find it as /dev/video* does not exist. Best,
Popesz
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Bastiaan van den Berg -
Csaba Láng -
IOhannes m zmoelnig -
IOhannes m zmölnig