Some question and problem
Hi all !
I got some problems (just 2 don't worry )
First : I'm trying to use [pix_multiblob] , but everytime I try to link it to [pix_texture] (linked to [pix_video] with my webcam in input ) pd crash litterally (so for the moment i use [pix_blob] but there is some more function in [pix_multiblob] I would like to use)
Second : I'm trying to map different color aera in a videostream, so to do it I link [pix_contrast] to [pix_texture] to clean and saturate a bit my videostream, then I link [pix_colorreduce] to create clear color aeras (and it work pretty good ) but I would like know if it's possible to mask some colors (to turn them to black) to let just one color appearing (for exemple to let just red appear)?
If anyone know something about these stuff, please share with me ^^
GEM: flipping the video images
Hi,
is possible flipping the video images (pix_movie) in the same way as with [pix_flip] (this serves to flip the still images) ??
Even i have just tried to use other objects like [pix_2grey] or [pix_aging] and they neither work with [pix_movie].
any idea?
Seeking Sompatible Video Capture Card - Composite Video on Linux
hi all.
for a project we're working on at the moment, we've been looking for a usb video composite capture card that would work with pd/GEM on Linux OS. we bought a Pinnacle PCTV USB2 that works fine on Linux with the usbvision driver, but somehow crashes GEM. we've posted the error log on the pd and gem-dev list, with no luck until now. so here it is again in case someone around here can help :
we want to use [pix_video] with a USB video capture device (Pinnacle PCTV USB2). But when we send [1( to [pix_video], pd says :
GEM: Start rendering
pix_videoNEW: starting transfer
cap: name Pinnacle PCTV USB 2 type 3 channels 3 maxw 720 maxh 576 minw 48 minh 32
picture: brightness 32896 depth 21571 palette 8
channel 0 name Television type 1 flags 1
channel 1 name Composite1 type 2 flags 0
channel 2 name S-Video type 2 flags 0
setting to channel 1
closing video
pix_texture: not using client storage
and all that we can see is a white rectangle.
XTerm is saying : VIDIOCGMBUF: Invalid argument
When we stop rendering with [0(, pd crashes.
we're on Ubuntu 6.06 LTS with Pd 0.39-2 / GEM 0.90. The USB video capture device is a Pinnacle PCTV Analog USB2
we had no trouble for getting the box to work with the video4linux drivers.
It works well with TVTime, but not with GEM. It seems everything goes well (using pix_videoNEW, listing the video channels, choosing the good one), and then this message "closing video". Why ?
we've tried the patch on Windows XP and have no problems with [pix_video] with this video capture device.
Any ideas ?
Scanning through pixel values of an image
Hi.
I am having trouble with getting pix_data to scan though the image values of the picture.
I am open for suggestions if there is another way to do this.
Can anyone help me?
mvh.
evemgr
here`s my code
#N canvas 637 81 628 488 12;
#X obj 190 159 pix_resize 10 10;
#X obj 171 238 pix_data;
#X floatatom 200 337 5 0 0 0 - - -;
#X floatatom 245 337 5 0 0 0 - - -;
#X floatatom 291 337 5 0 0 0 - - -;
#X floatatom 289 258 5 0 0 0 - - -;
#X obj 200 290 unpack 0 0 0;
#X obj 171 418 pix_draw;
#N canvas 0 0 466 316 image 0;
#X obj 77 48 inlet;
#X obj 77 344 outlet;
#X obj 223 55 inlet;
#X msg 223 123 open \$1;
#X obj 223 100 openpanel;
#X obj 77 205 pix_image c:/lyder/lyd.jpg;
#X connect 0 0 5 0;
#X connect 2 0 4 0;
#X connect 3 0 5 0;
#X connect 4 0 3 0;
#X connect 5 0 1 0;
#X restore 190 115 pd image;
#X obj 190 67 gemhead;
#N canvas 0 0 454 304 gemwin 0;
#X obj 130 159 gemwin;
#X obj 67 125 outlet;
#X obj 67 10 inlet;
#X obj 67 41 route create;
#X msg 67 74 set destroy;
#X msg 204 65 set create;
#X msg 132 112 create \, 1;
#X msg 246 111 destroy;
#X connect 2 0 3 0;
#X connect 3 0 4 0;
#X connect 3 0 6 0;
#X connect 3 1 5 0;
#X connect 3 1 7 0;
#X connect 4 0 1 0;
#X connect 5 0 1 0;
#X connect 6 0 0 0;
#X connect 7 0 0 0;
#X restore 422 273 pd gemwin;
#X msg 422 232 destroy;
#X obj 460 53 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1
-1;
#N canvas 0 0 474 324 counterx 1;
#X obj 194 13 loadbang;
#X obj 194 58 trigger bang bang;
#X msg 81 90 stop;
#X obj 194 146 float;
#X obj 194 181 + 1;
#X msg 325 126 0;
#X floatatom 194 230 5 0 0 0 - - -;
#X obj 194 272 outlet;
#X msg 143 20 bang;
#X obj 81 58 select 11;
#X obj 273 272 outlet;
#X obj 195 110 metro 11000;
#X connect 0 0 1 0;
#X connect 1 0 11 0;
#X connect 1 1 5 0;
#X connect 2 0 11 0;
#X connect 3 0 4 0;
#X connect 3 0 10 0;
#X connect 4 0 6 0;
#X connect 4 0 3 1;
#X connect 4 0 9 0;
#X connect 5 0 3 1;
#X connect 6 0 7 0;
#X connect 8 0 1 0;
#X connect 9 0 2 0;
#X connect 11 0 3 0;
#X restore 210 186 pd counterx;
#N canvas 542 0 478 328 countery 0;
#X obj 192 270 outlet;
#X obj 194 13 loadbang;
#X obj 194 58 trigger bang bang;
#X msg 81 90 stop;
#X obj 194 146 float;
#X obj 194 181 + 1;
#X msg 325 126 0;
#X floatatom 194 230 5 0 0 0 - - -;
#X obj 81 58 select 11;
#X obj 131 15 inlet;
#X obj 194 110 metro 1000;
#X connect 1 0 2 0;
#X connect 2 0 10 0;
#X connect 2 1 6 0;
#X connect 3 0 10 0;
#X connect 4 0 5 0;
#X connect 5 0 7 0;
#X connect 5 0 4 1;
#X connect 5 0 8 0;
#X connect 6 0 4 1;
#X connect 7 0 0 0;
#X connect 8 0 3 0;
#X connect 9 0 2 0;
#X connect 10 0 4 0;
#X restore 230 211 pd countery;
#X obj 422 191 loadbang;
#N canvas 661 149 482 332 maincounter 0;
#X obj 194 13 loadbang;
#X msg 148 12 bang;
#X obj 194 58 trigger bang bang;
#X obj 81 58 select 101;
#X msg 81 90 stop;
#X obj 194 146 float;
#X obj 194 181 + 1;
#X msg 325 126 0;
#X floatatom 194 230 5 0 0 0 - - -;
#X obj 265 224 outlet;
#X obj 194 110 metro 1001;
#X connect 0 0 2 0;
#X connect 1 0 2 0;
#X connect 2 0 10 0;
#X connect 2 1 7 0;
#X connect 3 0 4 0;
#X connect 4 0 10 0;
#X connect 5 0 6 0;
#X connect 6 0 8 0;
#X connect 6 0 5 1;
#X connect 6 0 3 0;
#X connect 7 0 5 1;
#X connect 10 0 5 0;
#X connect 10 0 9 0;
#X restore 171 19 pd maincounter;
#X msg 89 176 bang;
#X msg 369 192 bang;
#X obj 263 84 loadbang;
#X connect 0 0 1 1;
#X connect 1 0 7 0;
#X connect 1 1 6 0;
#X connect 1 2 5 0;
#X connect 6 0 2 0;
#X connect 6 1 3 0;
#X connect 6 2 4 0;
#X connect 8 0 0 0;
#X connect 9 0 8 0;
#X connect 10 0 11 0;
#X connect 11 0 10 0;
#X connect 13 0 1 2;
#X connect 13 1 14 0;
#X connect 14 0 1 3;
#X connect 15 0 11 0;
#X connect 16 0 1 0;
#X connect 17 0 1 0;
#X connect 18 0 11 0;
Multiple pix loading
I don't have all of your answers in me at this moment though i'll startup a few. The length of this response is due to its super-thorough nature. Alright, so you can make a [pix_image] object that receives a [gemhead]'s outlet in its inlet. You can add the directory as an attribute, for example [pix_image /Users/Person/Folder/Folder/Picturename.psd], or alternatively make an [open( message with the same attribute. For example: [open /Users/Person/Folder/Folder/Picturename.psd(. This [open( message's outlet goes to [pix_image]'s inlet, even if [pix_image] already has attributes. To find you picture's directory, you can first figure out how PD reads and writes various files to your system. If you save any patch, in PD's console, it will say "saved to: /Users/person/folder/folder/Patchname.pd". It helps to have folder and file names without spaces though there are many ways around this in different scenarios. If you would like some advice on matching up your 40 keys with these [pix_image] picture loaders, i will if you let me know. I can show you ways to hide your already open pictures and you can move them around with [translateXYZ]. For your upside pictures, the object [rotateXYZ] should do this, though I have not tested it. You can use [rotateXYZ] by sending [pix_image]'s outlet to its inlet and [rotateXYZ]'s outlet to [pix_draw]. For the three [rotateXYZ] inlets from right to left, you can add number boxes. Creating this layout should give you an interface similar to the one in the pd help patch. Ill respond if you have any more questions or can share anything else in similar subject areas.
Pix\_mix vertical flip problem
hello
I'm using pd from the installer (version 0.39.2-extended-test5)
gem 0.91-cvs
qt 6.5
winXP
when I'm using pix-mix, pix_add or pix_composite
everytime, the right-inlet video image is vertical flipped
if I put before a vertical pix_flip object, the flip alterning on/off
strange problem not ?
the only solution that I've found for the moment, is to do the composite in 3D
but the openGL window is not recordable in QT (with pix_record)
so, it's that I want to do
does anybody get the same problem? or , better, a solution ?
(not a fancy iSight) But a normal webcam
tx Megale for your answer, im under OSX and using Pd-0.39.2-extended-test1.app and that's why i pose the question since in linux i know how to locate the webcam, simply /dev/video0..but under os x im simply lost.. i did search what you said an got some patches to play with and see but so far i get this when trying to load [pix_videoDS]
... couldn't create
If i take away the DS part it comes up
pix_videoDarwin: height 320 width 240
pix_videoDarwin: could not make new SG channnel
pix_videoDarwin: could not set SG ChannelBounds
pix_videoDarwin: could not set SG ChannelUsage
pix_videoDarwin: set SG NormalQuality
pix_videoDarwin: Using YUV
but when trying to access any help file or documentation i get this:
sorry, couldn't find help patch for "Gem/pix_videoDarwin.pd"
what means that so far the learning curve, withouth dokumentantion, gets really steep..
thanks for you answer, it opened a way..but please if possible (if you are under OS X) could you share a llittle example patch?
tx,
/kad
Using RAM for multiple videos ?
From http://gem.iem.at/manual/ListObjects.html
pix_film - use a movie file as a pix source for image-processing
pix_movie - use a movie file as a pix source and load it immediately into the texture-buffer
I don't use Gem myself, but reading that it seems pix_movie would load the whole video file into RAM, and probably into the video RAM on the graphics card. Not knowing much about Gem, there may be a difference between "pix for image processing" and "pix for texture", which may or may not be important.
GEM render order & tansparencies
hey cheers,
although i just remembered why i did not use [pix_film} but rather [pix_movie} in first place. i found that the resolution/colourdepth/etc with [pix_film} was horrible. so using [pix_movie] would make a good image, but crash.
does anyone have a suggestion how to get high quality image with [pix_film]?
cu, flo
btw: the use of crappy encoding compression is not the problem. the video is excellent on other video-players.