GEM-dev March 2006

gem-dev@lists.iem.at

15 participants
34 discussions

pf/pdp/3dp in Gem
by Tom Schouten 11 Aug '06

11 Aug '06

hi gemmers, just talking with jamie here in bergen and it's pretty clear to me how to write the bridge between libpdp and Gem. practicly, for me it is the build system. i'd like to add 5 objects. 3 of them are already in the pf/pd bridge. * [gem.get <thing>] : forks off one gemstate object as pdp packet * [gem.set <thing>] : inserts one pdp object in gem state * [pdp <thing>] : generic pdp processors (functional maps) * [3dp <thing] : 3d drawing objects (draw to current gl context) * [pf <script>] : any pf script the last 3 i have C code for and they don't depend on gem, but if pf/pdp/3dp is running inside Gem they need to be included. the first 2 need to be written from scratch as gem objects, possibly just derived from GemBase. i suggest someone helps me with setting this up, by adding templates for the gem.get and gem.set objects in the source tree and add them to the build process. the names are of course open to discussion. anything sane and short. the rest i need is just an init callback. this callback will: * initialize the forth and pdp memory manager * create the pf/pdp/3dp pd objects maybe it is best to keep this optional, since it introduces a library dependency. so, who is motivated to help me out here by adding the templates? i don't have time to learn the build and init process. cheers tom

10 62

Re: [PD] PD on Mac-Intel
by IOhannes m zmoelnig 11 Jul '06

11 Jul '06

hi i moved this to gem-dev. Cefn Hoile wrote: > Thanks, IOhannes > > Now building from latest cvs source of the Gem module from > cvs.gem.iem.at:/cvsroot/pd-gem > > Have to change both CFLAGS, CPPFLAGS and CXXFLAGS to include the > pd-39_2 source folder, else you get... > > configure: WARNING: m_pd.h: accepted by the compiler, rejected by the > preprocessor! > > ...or... > > error: m_pd.h: No such file or directory configure expects m_pd.h to be in the default search paths. this should probably be handled by the "-with-pd" flag to configure (but it is not). it might work if you set the INCLUDES when running configure: %> INCLUDES="-I/Users/cefn/Documents/curiosity/pdplay/pd-intel/" ./configure ... (this is one line!) this should save you from the following: > > So for me it was > export CFLAGS=-I/Users/cefn/Documents/curiosity/pdplay/pd-intel/ > pd-0.39-2/src/ > export CPPFLAGS=-I/Users/cefn/Documents/curiosity/pdplay/pd-intel/ > pd-0.39-2/src/ > export CXXFLAGS=-I/Users/cefn/Documents/curiosity/pdplay/pd-intel/ > pd-0.39-2/src/ > > But I run into exactly the same error as before, even with the CVS > version. > > If I run ./configure --disable-SIMD > I get the same what is the output of configure? how do Make.config and Base/configDarwin.h look like? (that is: after configure) is there any mention of "mmx" somewhere? > > I am now building the latest source from the Gem CVS repository. Anyone > any ideas what options I could throw at GCC version 4 to make it more > forgiving of these errors, or alternatively, what the error means (I'm > not an experienced C coder)... > > g++ -c -fPIC -I/Users/cefn/Documents/curiosity/pdplay/pd-intel/ > pd-0.39-2/src/ -I.. pix_coloralpha.cpp -o pix_coloralpha.o > pix_chroma_key.cpp: In member function 'virtual void > pix_chroma_key::processRGBA_MMX(imageStruct&, imageStruct&)': > pix_chroma_key.cpp:277: error: expected unqualified-id before numeric > constant > pix_chroma_key.cpp:288: error: cannot convert 'int' to 'int __vector__' > for argument '2' to 'int __vector__ _mm_cmpeq_pi32(int __vector__, int > __vector__)' it seems to be a problem with MMX. however, looking at the code again, it might be that there is a problem with variable name "nil" (as defined in line277 of pix_chroma_key.cpp) you could try to replace all occurences of "nil" with "null64". probably that's all. (if so, you might have to change it in a couple of other files too) if you still get the same errors, then there IS an issue with MMX. you might try to add "-U__MMX__" to the gcc-flags. or add a a "#undef __MMX__" somewhere at the beginning of Base/GemSIMD.h (line 30 seems to be fine) mfg.ads IOhannes

4 9

new win32 build
by chris clepper 12 May '06

12 May '06

I put a build up that fixes the crash when QT load, has some of my more recent pix_ objects and does ARB_ shaders. I also moved the QT init code into the GemMan init and added a fps output to gemwin (not checked into CVs yet). The biggest problem I have is that pix_film runs at like 2 seconds per frame when the first clip is loaded, but starting and stopping rendering fixes it. pix_video does the same. Also, texturing performance is really bad on the FireGL here. Anyone still attempting GEM on Windows want to test it? http://taproot.dyndns.org/~cgc/downloads/Gem.dll cgc

7 39

Re: [GEM-dev] stencil
by cyrille henry 04 May '06

04 May '06

hello, copiing your modifications, i've change lines 33 and 34 of the GemWinCreateXWin.cpp file to this : static int snglBuf24[] = {GLX_RGBA, GLX_RED_SIZE, 8, GLX_GREEN_SIZE, 8, GLX_BLUE_SIZE, 8, GLX_DEPTH_SIZE, 16, GLX_STENCIL_SIZE, 8, None}; static int dblBuf24[] = {GLX_RGBA, GLX_RED_SIZE, 4, GLX_GREEN_SIZE, 4, GLX_BLUE_SIZE, 4, GLX_DEPTH_SIZE, 16, GLX_STENCIL_SIZE, 8, GLX_DOUBLEBUFFER, None}; the buffer is now active, and the red square of the example is not draw when the test is active. now, i'm tryng to clear the stencil buffer in order to be able to draw a shape in this buffer. this exemple patch does not work. any ideas? thanks Cyrille james tittle a Ã©crit : >> hey cyrille, >> >> On Mar 3, 2006, at 8:54 AM, cyrille henry wrote: >> >>> does anyone have succefully used stencil buffer with GEM? >>> >>> here is what i'm trying to do, without succes... >> >> >> >> ...this is easy: it's not working because the gemwindow creation >> doesn't request a stencil buffer (at least on osx and linux)! >> However, I just committed a small change to the osx code that indeed >> does enable the stencil buffer, and it should be just as easy to do >> for linux and windows...after doing so, the patch works as expected... >> >> ...this does bring up an issue: should we always create the >> additional buffers (ie. depth, stencil, accumulation, aux), or should >> we create a message for gemwin to selectively enable/disable these >> before window creation? Currently on osx, 24bit depth and 8bit >> stencil buffers are created, and on linux it just creates a 16bit >> depth buffer... >> >> time to go out, >> jamie >> >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev(a)iem.at >> http://lists.puredata.info/listinfo/gem-dev >> >> > > > ------------------------------------------------------------------------ > > #N canvas 0 0 1198 875 10; > #X obj 54 112 gemhead 44; > #X obj 54 403 translateXYZ 0 0 -1; > #X obj 54 90 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1 > ; > #X obj 54 374 GEMglStencilOp; > #X obj 54 295 GEMglStencilFunc; > #X floatatom 194 367 5 0 0 0 - - -; > #X obj 147 340 GLdefine GL_KEEP; > #X obj 148 319 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X floatatom 196 236 5 0 0 0 - - -; > #X obj 188 191 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X obj 188 212 GLdefine GL_NEVER; > #X msg 161 269 1; > #X obj 54 230 GEMglEnable; > #X floatatom 137 184 5 0 0 0 - - -; > #X obj 126 140 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X obj 126 163 GLdefine GL_STENCIL_TEST; > #X obj 316 189 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X obj 316 212 GLdefine GL_ALWAYS; > #X obj 732 155 gemhead 31; > #X obj 732 131 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 > 1; > #X obj 732 281 GEMglClear; > #X obj 797 240 GLdefine GL_STENCIL_BUFFER_BIT; > #X obj 797 219 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X floatatom 806 262 5 0 0 0 - - -; > #X obj 822 217 loadbang; > #X obj 188 132 loadbang; > #X obj 54 454 square 3; > #X obj 54 428 color 1 0 0; > #X text 219 282 enable the stencil buffer; > #X obj 520 95 gemwin; > #X msg 520 47 create \, 1; > #X msg 528 72 0 \, destroy; > #X obj 732 191 GEMglClearStencil 0; > #X text 220 303 the red square should not be seen \, unless setting > the StencilFunc to "GL_ALWAYS". This work as expected.; > #X obj 454 473 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 > 1; > #X obj 454 543 GEMglStencilMask; > #X msg 561 520 1; > #X obj 454 643 GEMglStencilFunc; > #X msg 561 618 1; > #X floatatom 503 609 5 0 0 0 - - -; > #X obj 489 563 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X obj 489 586 GLdefine GL_ALWAYS; > #X obj 582 406 loadbang; > #X obj 454 744 square 1; > #X obj 454 497 gemhead 32; > #X msg 453 450 0; > #X text 459 766 to draw in the stencil buffer. this does not work because > the buffer is full of 1; > #X obj 454 722 GEMglStencilOp; > #X floatatom 594 715 5 0 0 0 - - -; > #X obj 548 667 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 > -1; > #X obj 547 688 GLdefine GL_REPLACE; > #X text 732 307 to clear the stencil buffer. this should make the stencil > test always be inactive. did not work...; > #X connect 0 0 12 0; > #X connect 1 0 27 0; > #X connect 2 0 0 0; > #X connect 3 0 1 0; > #X connect 4 0 3 0; > #X connect 6 0 5 0; > #X connect 6 0 3 1; > #X connect 6 0 3 2; > #X connect 6 0 3 3; > #X connect 7 0 6 0; > #X connect 9 0 10 0; > #X connect 10 0 8 0; > #X connect 10 0 4 1; > #X connect 11 0 4 3; > #X connect 11 0 4 2; > #X connect 12 0 4 0; > #X connect 14 0 15 0; > #X connect 15 0 13 0; > #X connect 15 0 12 1; > #X connect 16 0 17 0; > #X connect 17 0 4 1; > #X connect 18 0 32 0; > #X connect 19 0 18 0; > #X connect 21 0 20 1; > #X connect 21 0 23 0; > #X connect 22 0 21 0; > #X connect 24 0 21 0; > #X connect 25 0 10 0; > #X connect 25 0 15 0; > #X connect 25 0 6 0; > #X connect 25 0 11 0; > #X connect 27 0 26 0; > #X connect 30 0 29 0; > #X connect 31 0 29 0; > #X connect 32 0 20 0; > #X connect 34 0 44 0; > #X connect 35 0 37 0; > #X connect 36 0 35 1; > #X connect 37 0 47 0; > #X connect 38 0 37 3; > #X connect 38 0 37 2; > #X connect 40 0 41 0; > #X connect 41 0 39 0; > #X connect 41 0 37 1; > #X connect 42 0 36 0; > #X connect 42 0 41 0; > #X connect 42 0 38 0; > #X connect 42 0 45 0; > #X connect 44 0 35 0; > #X connect 45 0 34 0; > #X connect 47 0 43 0; > #X connect 49 0 50 0; > #X connect 50 0 48 0; > #X connect 50 0 47 1; > #X connect 50 0 47 2; > #X connect 50 0 47 3; >

4 8

rstp video in GEM
by Adrien Mondot 01 Apr '06

01 Apr '06

Hi here, I'm working on a live stage performance mixing juggling and computer arts, I've already worked a little bit with gem. For a project using a 100 fps IP-camera (check http://www2.elphel.com/index.html) , I'm looking for a way to use a streamed video in gem. Although I know it would be better to use pdp for this kind of stuff, most of the patch is already done in GEM (with a 25 fps DV cam), and it would be a pain in the ass to make it from scratch in pdp. The problem is : I can encapsulate the stream in a .mov file in order to make QT think it is a local file, but the pix_film object is unable to load the frame in it (while QT, Quartz Composer or other QT-based application can do it). any ideas of a solution ? I'm using a PowerBook G4 with OS 10.4.5, Pd-0.39-2 from Miller and GEM-CVS (11/05) To give an idea of what we are looking to do, here is a video of the patch with the DV-Cam http://video.adrienm.net/LaboReTime.avi PS : excuse for my poor english... _________________ www.adrienm.net "Et avec quelle quantité d'illusions ai-je dû naitre pour pouvoir en perdre une chaque jour ?" Cioran

5 11

commit access for help files
by Hans-Christoph Steiner 01 Apr '06

01 Apr '06

I am working on the 5 part intro to Pd workshop outlined here: http://puredata.org/dev/pddp/IntroWorkshopSeries As I am doing that, I am going to be going thru the Gem docs a lot. A lot of the Gem help patches are quite nice, like cube-help.pd with the [pd gemwin] subpatch, and the clear format. I'd like to fix some of the others, like gemwin-help.pd, which are still quite raw. Should I just send updated versions to y'all, or commit them directly (in which case I would need commit access)? A lot of the time, it'll be minor changes, like typos, small changes in working, etc. Also, I was thinking that [pd gemwin] should be an object rather than a subpatch. Its handy for normal Gem use. .hc ________________________________________________________________________ ____ If you are not part of the solution, you are part of the problem. - Eldridge Cleaver

2 2

gemwin "view" message
by B. Bogart 31 Mar '06

31 Mar '06

Hey all, So I'm using the "view" message to set the camera to correspond to three physical screens. The question I have is that the perspective seems off. Does the distance between the viewpoint position and the target position matter, or just the vector from one to the other? Any way to tweak the perspective? (perspec seems to just change clipping planes) Thanks! .b.

1 1

clearing the contents of a pix_buffer
by B. Bogart 30 Mar '06

30 Mar '06

Hey all, Is there a way to clear the frames in a pix_buffer? Basically reseting it to its initial state... I could dynamically reinit the pix_buffer object, but I'd rather do it through a message... Thanks! .b.

1 0

Re: Fwd: [GEM-dev] about splash-screen
by IOhannes m zmoelnig 29 Mar '06

29 Mar '06

james tittle wrote: > ...don't know if ya got this during your email probs yesterday: no i didn't get it, thanks for the forward i split my answers in several mails... > > Begin forwarded message: > >> From: james tittle <tigital(a)mac.com> >> Date: March 27, 2006 11:06:58 AM EST >> To: IOhannes m zmoelnig <zmoelnig(a)iem.at> >> Cc: gem-dev <gem-dev(a)iem.at> >> Subject: Re: [GEM-dev] Re: [GEM-cvs] Gem/src/Base GemSIMD.cpp, NONE, >> 1.1 GemSIMD.h, 1.3, 1.4 >> >> On Mar 24, 2006, at 4:32 PM, IOhannes m zmoelnig wrote: >> >>> usually only one single instance of GemSIMD will be created during the >>> life-cycle of Gem, serving as an initialization of the cpu-check. >>> this instantiation is done in GemMan (right after the splash-screen). >> >> >> ...splash screen? I saw this committed, but what's the idea of it? >> Is this something to come up when Gem is loaded? Or when a gemwin is >> opened? oh, by "splash-screen" i mean the lines displayed on the pd-console when you have sucessfully loaded Gem: the one with "GEM: Graphics Environment for Multimedia" and all the authors. however, i have recently committed a (yet empty) Geo-object "GemSplash". the reasoning behind this is, that it would be nice to to make an object [Gem] which you can put somewhere in your patch in order to load the library "Gem". of course you can do that (loading Gem via an object [Gem]) already, but the object creation will fail, because there is no such object within the library. this can be fixed in various ways, e.g. create an object with no inlets and outlets (just like the iemlib does it). then i thought it would be good to use the existing framework to include this object; however, you cannot just create an object "Geos/Gem.cpp" because you will get naming conflicts with the auto-registering macro magic. so i thought there i would just make another object which has an alias "Gem". furthermore i thought, it would be nice if this object could do something. the first idea that came to my mind was a Geo that would display some info on Gem (in the gem-window), kind of a "splash-screen" with more or less the same information as is given on the console when loading. i don't like the idea of a "real" splash-screen (something that pops up and that you cannot disable), but if the user is given the choice to include it (who would want that, i wonder) it would be nice. so i created a (still empty) Geo-object "GemSplash" (to avoid the name problem) and aliased it to "Gem". now you could just connect a [gemhead] to the [Gem] and it should (in future times) display something cool. however, i haven't found the time to actually put something in there, esp. as this object should - must - not rely on anything installed on the computer apart from pd/Gem, which makes text display a bit wearisome. a continuative (what a word...) idea was, that we could do community based competitions for this splash screen, which would change for each release (considering a release cycle of 2 years we should be able to find at least _one_ person who would create such object for each release ;-)) of course this is a bit weird, as this object would have to be coded directly in C++ which somehow contradicts the paradigm of using objects... what do you think? mfg.ads.r IOhannes

2 1

Re: Fwd: [GEM-dev] Re: [GEM-cvs] GemSIMD
by IOhannes m zmoelnig 29 Mar '06

29 Mar '06

ack, this went to the list-admin instead of the list... james tittle wrote: >> >> >> ...this sounds fine, but the GemSIMD::getCPU() static variable in >> GemPixUtil.cpp isn't working for me: it always remains 0, whereas >> GemSIMD::cpuid does show "3"...perhaps we should just make it defined >> in GemMan like most things, then "extern static int m_simd;" in >> source files when needed? well, "m_" is a bad naming scheme, since (i think) it means "member variable" which is definitely not an "extern static". however, it is very weird that the getCPU() does not work. >> >> >> ...ok, I'm all for doing it if it buys us more flexibility at no >> cost, even if we rarely use it... >> >>> ... >> >> >> ...I don't know what the function overhead would be, but isn't it >> minimal when dealing with a basic accessor function to a c++ class >> member variable? Would this be a candidate for inline-ing? is it possible to use an inlined function from an another class? however, probably the simplest way to go would be to skip the getCPU() alltogether and just directly _read_ the GemSIMD::cpuid. it is not really necessary to start using access control mechanisms now, as such mechanism isn't used throughout the code anyhow; esp. when it causes problems. i guess we can just trust ourselves, that we shouldn't _write_ GemSIMD::cpuid. however, i would rather use the variable from GemSIMD than to mirror it in GemMan: speed is the same and we should (start to) try to leave member variables where they belong. and then it might be best to just skip the local "m_simd" alltogether and always directly use GemSIMD::cpuid. mfg.asd.rt IOhannes

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev March 2006