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