hi, am i alone in finding GEM really not intuitive? it doesnt really have a "dataflow" feeling to it.
For example [cylinder] outputs an cylinder to graphics window,
but it isnt connected to the [gemwin] block.
What if i wanted to multiply the pixels of 2 different cylinders and
then output it to the graphics window?
Normally i would think:
[cylinder] [cylinder]
\ /
[pix_multiply]
|
[gemwin]
maybe it would be more fun if there was more a flow to it, like with pd sound. dont shoot me down if im wrong, it's just an impression :)
hi, am i alone in finding GEM really not intuitive? it doesnt really have a "dataflow" feeling to it.
For example [cylinder] outputs an cylinder to graphics window, but it isnt connected to the [gemwin] block. What if i wanted to multiply the pixels of 2 different cylinders and then output it to the graphics window? Normally i would think: [cylinder] [cylinder] \ / [pix_multiply] | [gemwin]
The problem here is that you are trying to use the pix_ image and video objects with an OpenGL 3D object. The pix_ prefix is the clue that all the pix_ objects work together, maybe the 3D objects should have been named 3D_cylinder or geo_cylinder but it's a little late to do that now.
Also, what would you expect to happen when you multiply these two objects? The cylinder object only sends a set of vertices as a description of the cylinder to the video card, so what would multiplying those vertices actually do? Make the cylinder larger? If the cylinders were textured there is a way to multiply the textures together using a shader, but GEM is not capable of doing that just yet.
You could use pix_snap to grab the area of the output window with a each cylinder then use pix_multiply on the captured areas.
maybe it would be more fun if there was more a flow to it, like with pd sound. dont shoot me down if im wrong, it's just an impression :)
I think it might be more 'fun' once the tutorials are more complete and integrated with the distributions. Until then you might want to learn about OpenGL, 3D, video processing in general to figure out why your patch doesn't work.
cgc
t208898:
hi, am i alone in finding GEM really not intuitive? it doesnt really have a "dataflow" feeling to it.
Thats because OpenGL rendering is not about dataflow. It uses a different paradigm. It is impossible to understand this at first sight, without any background in 3D modelling.
We hope the tutorial will solve this "first time" problem.
Guenter
For example [cylinder] outputs an cylinder to graphics window, but it isnt connected to the [gemwin] block. What if i wanted to multiply the pixels of 2 different cylinders and then output it to the graphics window? Normally i would think: [cylinder] [cylinder] \ / [pix_multiply] | [gemwin]
The problem here is that you are trying to use the pix_ image and video objects with an OpenGL 3D object. The pix_ prefix is the clue that all the pix_ objects work together, maybe the 3D objects should have been named 3D_cylinder or geo_cylinder but it's a little late to do that now.
Also, what would you expect to happen when you multiply these two objects? The cylinder object only sends a set of vertices as a description of the cylinder to the video card, so what would multiplying those vertices actually do? Make the cylinder larger? If the cylinders were textured there is a way to multiply the textures together using a shader, but GEM is not capable of doing that just yet.
You could use pix_snap to grab the area of the output window with a each cylinder then use pix_multiply on the captured areas.
maybe it would be more fun if there was more a flow to it, like with pd sound. dont shoot me down if im wrong, it's just an impression :)
I think it might be more 'fun' once the tutorials are more complete and integrated with the distributions. Until then you might want to learn about OpenGL, 3D, video processing in general to figure out why your patch doesn't work.
cgc
hello all,
i'm experiencing rare problems with pix_video object, the captured image is not so good: there is some dropped frames and sometimes image is cutted in horizontal lines... i'm not shure but i think that it works with very good quality in the same computer before some changes with my packages.
any idea?
i'm using GEM+cvs version: GEM: Graphics Environment for Multimedia GEM: ver: 0.87+cvs GEM: compiled: Apr 11 2003
i obtain this error: (VIDIOCSYNC: Invalid argument)
cap: name BT848A( *** UNKNOWN/GENERIC **) type 235 channels 4 maxw 924 maxh 576 minw 48 minh 32
picture: brightness 32768 depth 32 palette 5
vcap.channels 4 channel 0 name Television type 1 flags 3 channel 1 name Composite1 type 2 flags 2 channel 2 name S-Video type 2 flags 2 channel 3 name Composite3 type 2 flags 2 buffer size 4259840, frames 2, offset 0 2129920
frame 0 0, format 4, width 512, height 512
GEM: pix_video: Opened video connection B vmmap 81108D8 starting thread! VIDIOCSYNC: Invalid argument
i don't know if it's useful but here is some data about my Xfree configuration:
xfree86 4.2.1-6 NVIDIA driver
and in XF86Config-4 i'm loading this modules: Load "bitmap" Load "dbe" Load "ddc" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "pex5" Load "record" Load "speedo" Load "type1" Load "vbe" Load "xie" Load "v4l"
thank's
_
(o< -! lluis gómez i bigordà lgomez@pangea.org
//\ +34.650.91.94.35
V_/_ www.pangea.org/~lgomez
__________________________________________________________________________
-
chris clepper -
guenter geiger -
lluis gomez i bigorda -
t208898