hi,
first, i would like to thank iohannes for his advices and the time he spent to explain me how to contribute to Gem development : git tuto, coding advices, and so and so... I tried to follow all the things as close as possible and I made some changes in videoV4L2 plugin to be able to choose a device with its physical bus location. I also added 3 properties : driver, card and bus_info bus_info is the device's bus location and could be used as an argument to [open( message card is the name of the device (ie : Built in I-sight) and driver is the used driver
i didn't want to put some backend specific code in pix_video.cpp so I only work on videoV4L2.cpp but to open a device with it's bus location, i'm assuming that all paths to devices start with a slash '/' it could be a limitation but i didn't find a better way... i've updated the pix_video-help.pd patch with the add of a v4l2-specific abstraction to explain what i've done
all the things are in the branch *videoV4L2* on my github repos : git://github.com/avilleret/Gem.git
hope this help and i hope i've done the things in the right way this time :-) feedbacks are welcome
best
antoine
Hi,
Do you recommend any V4L2 learning path? I'd like to do contribute on that myself in the near future.
Nice work!
Ricardo Fabbri -- Linux registered user #175401 www.lems.brown.edu/~rfabbri pt.wikipedia.org/wiki/IPRJ labmacambira.sf.net
On Sun, Feb 5, 2012 at 4:27 PM, Antoine Villeret antoine.villeret@gmail.com wrote:
hi,
first, i would like to thank iohannes for his advices and the time he spent to explain me how to contribute to Gem development : git tuto, coding advices, and so and so... I tried to follow all the things as close as possible and I made some changes in videoV4L2 plugin to be able to choose a device with its physical bus location. I also added 3 properties : driver, card and bus_info bus_info is the device's bus location and could be used as an argument to [open( message card is the name of the device (ie : Built in I-sight) and driver is the used driver
i didn't want to put some backend specific code in pix_video.cpp so I only work on videoV4L2.cpp but to open a device with it's bus location, i'm assuming that all paths to devices start with a slash '/' it could be a limitation but i didn't find a better way... i've updated the pix_video-help.pd patch with the add of a v4l2-specific abstraction to explain what i've done
all the things are in the branch videoV4L2 on my github repos : git://github.com/avilleret/Gem.git
hope this help and i hope i've done the things in the right way this time :-) feedbacks are welcome
best
antoine
do it yourself http://antoine.villeret.free.fr http://drii.ensad.fr -- Google lit ce mail... si vous refusez cela, utilisez l'adresse antoine.villeret [at] free.fr pour me contacter
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Hi,
sorry, i've just remember i never answer to your mail in fact, i don't know anything about V4L2, i've just walked through included header to find out structures definition and i learned a lot with comments too
++ a.
On 02/05/12 19:27, Antoine Villeret wrote:
i didn't want to put some backend specific code in pix_video.cpp so I only work on videoV4L2.cpp
right, that's the idea.
but to open a device with it's bus location, i'm assuming that all paths to devices start with a slash '/' it could be a limitation but i didn't find a better way...
you could check first whether the devicename is an existing (v4l2) devicefile, and if not check whether it is a valid bus-id...
all the things are in the branch *videoV4L2* on my github repos : git://github.com/avilleret/Gem.git http://github.com/avilleret/Gem.git
cool, thanks; i merged that into "master".
i've updated the pix_video-help.pd patch with the add of a v4l2-specific abstraction to explain what i've done
i rejected that, and instead tried to implement a more generic approach (allowing plugins to come with their own help-file extensions which are then dynamically displayed in the pix_video help-patch
hope this help and i hope i've done the things in the right way this time :-) feedbacks are welcome
thanks a lot.
fga,sdr IOhannes