hi
i am getting different behaviours with same GEM patch under linux and windows. The patch is rendering a webcam image with pix_video and then a basic rectangle with no texture on top of the webcam (using pix_blob to analyse the camera and move the rectangle around). Each has its own gemhead and they are separated in different abstractions.
While in windows all is rendered fine, linux does not like it the rectangle was rendered but the webcam image wasnt. The only way to get it to work was to put some render argument of the rectangle like 2. So I decided to set that value to $0 on loadbang, this should give different numbers to each instance of the abstractions. (Note that i dont have a clue if this is bad idea). Both the camera image and the rectagle are included in abstractions.
The result was kind of ok, now linux was more happy with it but still sometimes the webcam image goes off again. This happens for example when I move the gem window or after ~10 to ~20 secs. Also if i open a PD subpatch.
When I switch rendering off on the rectangle's gemhead and then the webcam goes live again... When I switch on the rectangle it takes some secs to go off again... If I dont turn on the rectangle the webcam stays alive.
The webcam gemhead gets set to 1004 and the rectangle to 1005 from the $0 arg of the abstractions they live in.
I guess this must be some problem with having two gemheads but i am not sure why this problem is not happening at all under windows, so it looks like a linux issue. Anything i can do to avoid this problem?
Sorry if the explanation is not very clear...
thanks!
enrike
altern wrote:
hi
[...]
While in windows all is rendered fine, linux does not like it the rectangle was rendered but the webcam image wasnt. The only way to get it to work was to put some render argument of the rectangle like 2. So I decided to set that value to $0 on loadbang, this should give different numbers to each instance of the abstractions. (Note that i dont have a clue if this is bad idea). Both the camera image and the rectagle are included in abstractions.
i would say that this is generally a rather bad idea. you are deliberately randomizing the render-order.
why don't you just manually specify the rendering order the way it should be? if the rectangle is to be drawn on top of the textured geo, you would want to render it later, thus it should have a higher number than the white rectangle.
The result was kind of ok, now linux was more happy with it but still sometimes the webcam image goes off again. This happens for example when I move the gem window or after ~10 to ~20 secs. Also if i open a PD subpatch.
for me this seems to be a problem with the driver (texture memory). which gfx-care do you use? which driver?
I guess this must be some problem with having two gemheads but i am not
i don't think so.
sure why this problem is not happening at all under windows, so it looks like a linux issue. Anything i can do to avoid this problem?
is this the same computer (same hardware) running both w32 and linux? which (exact) versions of Gem are you using?
what do you mean by "the image goes off"? does the geo you render it onto goes black? white? green? invisible?
does the camera work stable on linux? with Gem? (for long-term?) is anything printed to either the pd-console or the terminal-console? (watch both - a lot of messages in the capture code are not written to the pd-console!)
fmgasdr. IOhannes
hi again
another issue i am getting with GEM on linux. When I run a patch that uses GEM that uses the webcam while the VGA output of the laptop is connected to an external monitor the X crashes , like if I press CTRL+ALT+Backspace.
I guess it has more to do with the system configuration than with GEM but I am not sure...
enrike
IOhannes m zmoelnig(e)k dio:
altern wrote:
hi
[...]
While in windows all is rendered fine, linux does not like it the rectangle was rendered but the webcam image wasnt. The only way to get it to work was to put some render argument of the rectangle like 2. So I decided to set that value to $0 on loadbang, this should give different numbers to each instance of the abstractions. (Note that i dont have a clue if this is bad idea). Both the camera image and the rectagle are included in abstractions.
i would say that this is generally a rather bad idea. you are deliberately randomizing the render-order.
why don't you just manually specify the rendering order the way it should be? if the rectangle is to be drawn on top of the textured geo, you would want to render it later, thus it should have a higher number than the white rectangle.
The result was kind of ok, now linux was more happy with it but still sometimes the webcam image goes off again. This happens for example when I move the gem window or after ~10 to ~20 secs. Also if i open a PD subpatch.
for me this seems to be a problem with the driver (texture memory). which gfx-care do you use? which driver?
I guess this must be some problem with having two gemheads but i am not
i don't think so.
sure why this problem is not happening at all under windows, so it looks like a linux issue. Anything i can do to avoid this problem?
is this the same computer (same hardware) running both w32 and linux? which (exact) versions of Gem are you using?
what do you mean by "the image goes off"? does the geo you render it onto goes black? white? green? invisible?
does the camera work stable on linux? with Gem? (for long-term?) is anything printed to either the pd-console or the terminal-console? (watch both - a lot of messages in the capture code are not written to the pd-console!)
fmgasdr. IOhannes
-
altern -
IOhannes m zmoelnig