GEM-dev January 2006

gem-dev@lists.iem.at

8 participants
19 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

V4L2
by B. Bogart 16 Feb '06

16 Feb '06

Hi Johannes, So now I would very much like to be able to use two of my video capture devices to work in Gem. Right now only the wintv works fine, though a little buggy, but I can't get anything out of the cx878 boards. xawtv works on both cards equally. I have a hunch this may be due to an imcompatibility with the v4l wrapper v4l_compat around v4l2 drivers. (I'm using 2.6.13-ck5) How about pix_video using v4l2 proper rather than v4l? .b..

2 2

building gem CVS (anonymous from right now)
by B. Bogart 04 Feb '06

04 Feb '06

Hi all, I'm trying to recompile Gem with v4l2 stuff, but the compile bails with this: g++ -c -fPIC -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -mmmx -I/usr/X11R6/include -I/usr/include/ffmpeg -I/usr/include/quicktime -I/usr/include/avifile-0.7 -I/usr/include/freetype2 -I.. -I/usr/include/FTGL -I/usr/include/freetype2 GemGLUtil.cpp -o GemGLUtil.o In file included from GemGLUtil.cpp:18: GemGLUtil.h:25: error: declaration of C function `int getGLdefine(t_symbol*)' conflicts with GemGLUtil.h:24: error: previous declaration `int getGLdefine(char*)' here GemGLUtil.h:26: error: declaration of C function `int getGLdefine(t_atom*)' conflicts with GemGLUtil.h:25: error: previous declaration `int getGLdefine(t_symbol*)' here GemBase.cpp:138: error: parse error at end of input make[1]: *** [GemBase.o] Error 1 make[1]: *** Waiting for unfinished jobs.... GemGLUtil.cpp: In function `int getGLdefine(t_atom*)': GemGLUtil.cpp:78: error: cannot convert `t_symbol*' to `t_atom*' for argument ` 1' to `int getGLdefine(t_atom*)' GemGLUtil.cpp: In function `int getGLdefine(t_symbol*)': GemGLUtil.cpp:84: error: declaration of C function `int getGLdefine(t_symbol*)' conflicts with GemGLUtil.cpp:76: error: previous declaration `int getGLdefine(t_atom*)' here GemGLUtil.cpp: In function `int getGLdefine(t_atom*)': GemGLUtil.cpp:85: error: cannot convert `char*' to `t_symbol*' for argument `1' to `int getGLdefine(t_symbol*)' GemGLUtil.cpp: In function `int getGLdefine(char*)': GemGLUtil.cpp:90: error: declaration of C function `int getGLdefine(char*)' conflicts with GemGLUtil.cpp:84: error: previous declaration `int getGLdefine(t_symbol*)' here GemGLUtil.cpp: At global scope: GemGLUtil.cpp:5636: error: parse error at end of input make[1]: *** [GemGLUtil.o] Error 1 make: *** [Base] Error 2 I'll just hack the v4l2 stuff into my local copy for the time being. b.

3 13

new binaries for Windows and OSX
by chris clepper 03 Feb '06

03 Feb '06

As the recent requests indicate, it's probably about time for some updated binaries for Windows and OSX. Jamie will be in Chicago later this week which might be a good time to wrap up the OSX end. I have been working on parts of the Windows code and have a few bug fixes and features added (mainly QT stuff). The main lack of functionality on Windows is the shader code. I tried GLEW but the resultant binary always crashes during window creation. I think it might require more reworking of the windows code than just replacing a few of the includes, so my question is whether we try to move to GLEW with Windows (and also Mac and Linux?) or just hack in the calls for ARB_fragment/vertex/etc and go? cgc

4 8

HaveValidContext + AGL
by IOhannes m zmoelnig 30 Jan '06

30 Jan '06

hi all. i am currently skipping through the code and trying to replace pre-processor checks by runtime checks. i see a lot of references to HaveValidContext() in __APPLE__. i think some of them are obsolete or leftovers. what bothers me a bit is, that whenver HaveValidContext is used, there is also an include for <AGL/agl.h>. is this necessary or is it just a copy'n'paste leftover? (i think there is nothing special in most of these files which would require AGL) also i noticed that <Carbon/Carbon.h> and <AGL/agl.h> are included using the #import directive, which i think is ugly. are these 2 files save to include more than once? mf.asdr IOhannes

3 3

adding line drawing to [model]
by james tittle 27 Jan '06

27 Jan '06

...for some reason I was playing around a [model] the other day, and realized that it didn't respond to [draw line<, or [draw anything< ! A little investigation showed that glmDraw() is called with a mode flag (bitwise OR values), usually with (GLM_SMOOTH | GLM_TEXTURE)...this ignores the other two possibilities: GLM_NONE (for drawing only vertices, ie. lines) GLM_FLAT (for drawing facet normals; used instead of GLM_SMOOTH, which renders vertex normals) ...GLM_MATERIAL is switchable via the [material $1 < , but I don't think this would be the best place to put the option for vertex-only drawing... ...so, anyone against me putting in either a [mode $1 < or [draw $1 < ? As I see it, it'd have 4 states: GLM_NONE | GLM_FLAT GLM_NONE | GLM_SMOOTH GLM_FLAT | GLM_TEXTURE GLM_SMOOTH | GLM_TEXTURE ...any ideas on a way to make this better, or rather more informative, than [mode 0|1|2|3< ? ...also, I noticed some of unfinished code for .3ds loading: IOhannes, did you ever get any further with your try? I suppose that these kind of messages should also have meaning for other model types... jamie

1 0

pix_buffer_write and copy2Image()
by chris clepper 27 Jan '06

27 Jan '06

I just had a crash from trying to put a 720x480 image into a 640x480 pix_buffer. I can't find any sort of check against that condition in the pix_buffer code nor in copy2Image. I think there needs to be one, so where does it make sense? I think copy2Image probably needs to do such a check before the memcpy(), but that would make it identical to refreshImage - so what purpose does each serve? Should the copy2Image be changed to refreshImage in pix_buffer and other places if the check is needed? cgc

2 1

[GEM-dev] Re: [GEM-cvs] Gem/src importGLEW.sh, NONE, 1.1 README.glew, 1.1, 1.2
by IOhannes m zmoelnig 26 Jan '06

26 Jan '06

IOhannes m zmÃ¶lnig wrote: > Update of /cvsroot/pd-gem/Gem/src > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3642 > > Modified Files: > README.glew > Added Files: > importGLEW.sh > Log Message: > made a script (which will hopefully hardly ever be needed) to import glew > mention it in the README.glew > so i've imported the most uptodate glew-files and made a little script that should ease the importing in future times. this of course is no glewifying of Gem yet, but at least it is a start... mf.asdr. IOhannes

1 0

GLEW and pix_texture
by chris clepper 25 Jan '06

25 Jan '06

I seem to have GEM built with GLEW on Windows however the pix_texture object was crashing. It took a little time to trace the crash, but I finally figured out that it died on GL_APPLE_texture_range. Now, let's look at that again in slow-motion: Windows box, Apple specific extension, crash. GLEW apparently says 'YES!' to every extension under the sun, which means we need to clean up some code based on platform assumptions in order to make it work. cgc

2 11

Re: Gem on osx 10.4.4
by IOhannes m zmoelnig 24 Jan '06

24 Jan '06

Giulio Fregni wrote: > Hi > > I was wondering if I am missing something > I'm running PD 0.9.3 on os x 10.4.4, and placed the 18mb gem 0.90 wow, where did you get pd-0.9.3...? > compiled for g4 into the folder "extra". > While other lib are running, Gem is not running. > Can U help me? What am I doing wrong? you have to load Gem explicitly. either create an object [Gem] in your patch OR start pd with "-lib Gem" (if you are running pd from the command-line) OR put "Gem" into one of the library-entries within the "Startup..."-menu. when Gem is loaded, you will see a notice in pd's console. mfga.sd.r IOhannes > Thanks! > > Giulio Fregni

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 January 2006