GEM-dev March 2008

gem-dev@lists.iem.at

12 participants
16 discussions

[ pd-gem-Feature Requests-1908191 ] optionally disable direct rendering at runtime
by SourceForge.net 05 Mar '08

05 Mar '08

Feature Requests item #1908191, was opened at 2008-03-05 18:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507082&aid=1908191&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: ClaudiusMaximus (claudiusmaximus) Assigned to: Nobody/Anonymous (nobody) Summary: optionally disable direct rendering at runtime Initial Comment: I think it might be useful to be able to choose at runtime to use direct rendering (ie, GPU hardware acceleration) or not (ie, CPU software rendering). Rationale: GPUs are very fast, but transfering images back to the CPU is very slow. When rendering "offline" (eg with pix_write) it might turn out to be faster overall to use software rendering than direct rendering, depending of course on scene complexity. I don't know if it is possible to implement, but I guess the user interface would take the form of a message to [gemwin] before the "create" message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507082&aid=1908191&group_…

1 0

[ pd-gem-Bugs-1907948 ] stereoscopic mode 1 bug in Gem on Windows
by SourceForge.net 05 Mar '08

05 Mar '08

Bugs item #1907948, was opened at 2008-03-05 12:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=1907948&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: rendering (e.g. display) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Chris Willmott [pentascape] (pentascape) Assigned to: Nobody/Anonymous (nobody) Summary: stereoscopic mode 1 bug in Gem on Windows Initial Comment: There is a bug which prevents the Gem window from rendering stereoscopic images correctly. Bug evident on 3 separate Windows machines running Pure Data 0.39.3-extended. Instead of 2 separate images on either side of the separator, the 2 images are overlayed in the centre of the Gem window and overlap the separator. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=1907948&group_…

1 0

[ pd-gem-Bugs-1907867 ] pix_write TIFF are 16bit per channel
by SourceForge.net 05 Mar '08

05 Mar '08

Bugs item #1907867, was opened at 2008-03-05 10:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=1907867&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: ClaudiusMaximus (claudiusmaximus) Assigned to: Nobody/Anonymous (nobody) Summary: pix_write TIFF are 16bit per channel Initial Comment: The .tif files created by [pix_write] are 16bit per channel instead of the "normal" 8bit per channel. This means the files are 2x the size that you would expect from the resolution, and surely contributes to the slowness of [pix_write]/TIFF I can imagine a situation where 16bpc is useful (HDR rendering for example), but as a default I think it's a bit much. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=1907867&group_…

1 0

Gem vs ATi fglrx vs GLEW vs OpenGL 2.0
by Claude Heiland-Allen 03 Mar '08

03 Mar '08

Hi all, I found this: http://ati.cchtml.com/show_bug.cgi?id=193 I ran the test program attached to that bug report, it reported success. But Gem (without "--with-glversion=1.5") still fails to load with glUniform2i undefined. Then I tried some semi-random hacking of code: #include <GL/glew.h> // just before #include <GL/gl.h> in Base/GemGL.h and adding -lGLEW to the Make.config (iirc). Gem now compiles without error and loads without error, but segfaults in numerous situations, including plain texturing (gdb indicates jumping to a null pointer). The key function in the OpenGL 2.0 tester seems to be: typedef void (*__GLXextFuncPtr)(void); extern "C" __GLXextFuncPtr glXGetProcAddressARB (const GLubyte *); which is only referenced in: pd-gem/Gem/src/Base/glxew.h pd-gem/Gem/src/Base/glew.cpp I noticed glewInit() is only called on Windows: pd-gem/Gem/src/Base/GemWinCreateNT.cpp: GLenum err = glewInit(); So I hacked something in GemWinCreateXWin.cpp: #ifdef USE_GLEW GLenum err = glewInit(); if (GLEW_OK != err) error("failed to init GLEW"); else post("GLEW version %s",glewGetString(GLEW_VERSION)); #endif and added #include <GL/glew.h> in GemWinCreate.h, and I got a Gem that compiled and loaded without errors, no segfaults so far either, but also no working shaders: Direct Rendering enabled! GLEW version 1.3.4 GEM: Start rendering linking: link 1.07374e+09 0 linking: link 1.07374e+09 5.36871e+08 [glsl_program]: Info_log: [glsl_program]: Link successful. There are no attached shader objects. [pix_image]: GEM: thread loaded image: /home/claude/src/pd-gem/Gem/examples/10.glsl/img3.jpg GL: invalid value With 02_primitive_distortion.pd I get an undistorted textured sphere, similarly the other examples (everything looks like no special shaders are running). The large numbers for the shader ids look a bit suspicious to me, as does the "no attached shader objects". Would be useful if "GL: invalid value" could be made more verbose, too. So, any clues? Some more info from Pd: [glsl_vertex]: Vertex_shader Hardware Info [glsl_vertex]: ============================ [glsl_vertex]: MAX_VERTEX_ATTRIBS: 32 [glsl_vertex]: MAX_VERTEX_UNIFORM_COMPONENTS_ARB: 4096 [glsl_vertex]: MAX_VARYING_FLOATS: 44 [glsl_vertex]: MAX_COMBINED_TEXTURE_IMAGE_UNITS: 16 [glsl_vertex]: MAX_VERTEX_TEXTURE_IMAGE_UNITS: 0 [glsl_vertex]: MAX_TEXTURE_IMAGE_UNITS: 16 [glsl_vertex]: MAX_TEXTURE_COORDS: 8 [glsl_fragment]: glsl_fragment Hardware Info [glsl_fragment]: ============================ [glsl_fragment]: MAX_FRAGMENT_UNIFORM_COMPONENTS: 4096 [glsl_fragment]: MAX_TEXTURE_COORDS: 8 [glsl_fragment]: MAX_TEXTURE_IMAGE_UNITS: 16 [glsl_program]: glsl_Program Hardware Info [glsl_program]: ============================ [glsl_program]: I'm running Debian Stable with ATi proprietary fglrx driver for a Mobility Radeon 9700 card. Thanks, Claude -- http://claudiusmaximus.goto10.org

5 7

ftgl/fink/mac
by marius schebella 03 Mar '08

03 Mar '08

hi, I'm trying to compile, miss ftgl and saw that Hans maintains the fink project. unfortunately fink install ftgl gives me an error Failed: no package found for specification 'ftgl'! do I need to use a special mirror to get this? marius.

2 2

xcode gem os x
by marius schebella 03 Mar '08

03 Mar '08

hi, I would like to get gem compiling on a mac. I got sources from cvs -z3 -d:pserver:anonymous@cvs.gem.iem.at:/cvsroot/pd-gem co Gem GemLibs I found the GEM_darwin.xcodeproj and opened it, a lot of files were marked red (which means not found). Wherever I could, I changed the path or tried to get the files. it was easy for m_pd.h, it was less easy for macosx_math.cpp and macosx_math.h. I found two files of that name in the internet, but not sure if these are the missing??? I did not know where to get libftgl.a, tried with fink, but did not install. I then tried to compile ftgl myself, but that was even worse than Gem. (I don't know how to include all needed files. I thought everything that is listed under Groups and Files automatically is included in the search path? but after some time I had enough of "error: freetype/config/ftheader.h: No such file or directory".) I thought then maybe It was possible to set my xcode project to compile without ftgl? also Cg.Framework (which was not set as an absolute path) and libMallocDebug.a were missing. I had both files lying around somewhere, so I included these. but in the end it was frustrated, because I ended up with a bunch of errors. what is my problem with including the paths? should I forget xcode and do everything from command line? and how can I do the same as in pd-extended - create a lot of dynamic linked libraries? marius.

2 1

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 2008