GEM-dev March 2006

gem-dev@lists.iem.at

15 participants
34 discussions

Weird performance issues when using Pd, Gem, and realtime-lsm on Linux
by Ivica Ico Bukvic 17 Mar '06

17 Mar '06

Greetings all (again :-), I have another peculiarity I've encountered on my machine. This was not a problem on non-Ubuntu setup, so it is likely something specific to my configuration. Yet, I am at a loss as to what may be the cause of this. I am using 32-bit Ubuntu Hoary, Pd 0.38, Gem 0.90, h/w is eMachines M6807 (AMD64) laptop with the latest BIOS installed. Video driver is fglrx (proprietary ATI) on top of X.org. I've installed realtime-lsm and it works fine (good latency via jack etc.). It is using default settings. The kernel in quesiton is 2.6.10. Pd also runs fine, *except* in the following 2 scenarios: 1) When running as a root or non-root user with -rt flag and I start any Gem example, once the Gem window is created *and* enabled, if I move any open window (Pd-related or non-Pd-related), the system starts hanging for a couple of seconds, then I guess the pd watchdog kicks in (albeit extremely sporadically) and allows me a split second to release mouse button (or click a couple times as if the release I made during the hanging process did not get registered properly) and if I am lucky the hick-up stops (the cpu usage during the hang is 100%). By this time my dragged window usually shows up somewhere else on the desktop. If I do not move the window, everything is fine. Clicking on the buttons/options inside the patch is not a problem as well as doing anything else on computer. Ironically, when running Pd without -rt flag, there are no problems whatsoever of this kind (could it be that perhaps Gem somehow is not quite aware of the realtime-lsm behavior or something like this in respect to X server, so it supersedes the X server itself in importance, or something like that?). 2) When trying to play Gem examples that use prerecorded movies as textures of the OpenGL objects. Trying to play videos (by sending "auto" option, like in ../gem/examples/04.pix/movie.pd) eats so much resources in user mode that I have to kill the X server (sometimes I have to even forcefully shut the machine down). Cycling through the frames using the frame number inlet/counter (right inlet on pix_movie) is no problem whatsoever. Using the same patch as root allows everything to proceed but at an extremely low framerate (the video card is ATI mobility 9600 so this should not be an issue), i.e. 0.5 frames/sec. Again, manually cycling through the frames via the frame number inlet (I guess one could use metro for this) is a breeze as long as the "auto" is turned off. When trying to run patches which utilize movies I get the following messages depending upon the movie format: .avi file: <ffindeo3> : doesn't support DR1 .mpg file: mpeg3video_seek: frame accurate seeking without a table of contents is no longer supported. Use mpeg3toc <mpeg file> <table of contents> to generate a table of contents and load the table of contents instead. .mov is fine. Doing the same thing without the -rt flag makes playing of the movie painfully slow (similar like when running as a root), but again when using frame counter instead it's an absolute breeze no matter how quickly you cycle through the frames. At any rate, I would greatly appreciate any help I can get regarding these two issues. Best wishes, Ico

2 1

Gem and video capture
by Ivica Ico Bukvic 17 Mar '06

17 Mar '06

Greetings all, I have just started messing with the video in on my Linux laptop and have encountered some problems with Gem: *The OS is Ubuntu Hoary, Pd 0.38, and Gem 0.90. *I am using ADVC-100 ieee1394 interface which allows me to connect any S-Video device to my laptop. The device works fine with Kino (dvgrab). *My /dev folder includes /dev/raw1394 and /dev/video1394/0 *All of the stuff is installed TTBOMK properly. *When using Gem, I cannot get the video to work as I do not have v4l devices available (/dev/video0) with this device, and the ieee1394 devices Gem looks for under /dev/ieee1394/dv/host<x>/<y>/in which obviously fails on my system. The exact error in the terminal is: /dev/ieee1394/dv/host0/PAL/in: No such file or directory *I tried linking /dev/raw1394 to /dev/video0 (I am not sure as to what is the difference between the two, so this may have been stupid--nonetheless I tried it just to cover all possibilities) and then using ../gem/examples/04.video/00.SimpleVideo.pd tutorial generates one complaint: get capabilities: Invalid argument and I get no video. All permissions should be properly set on the devices/links (root:video 660). *I tried using latest vloopback driver (0.97) and when I modprobe it, I get /dev/video0 and /dev/video1 devices (81,0). However, connecting to them yields following in PD: video4linux ieee1394 for linux Direct Rendering enabled! GEM: Start rendering pix_videoNEW: starting transfer cap: name Video loopback 0 input type 0 channels 1 maxw 0 maxh 0 minw 20 minh 20 picture: brightness 32768 depth 32768 palette 0 channel 0 name Composite1 type 2 flags 0 setting to channel 0 buffer size -1397530602, frames 2, offset 0 -698765301 wanted format is 0x1908 setting cmcapture to 0x0 5 now trying standard palette 0 closing video pix_texture: not using client storage In addition, the terminal also spits out: VIDIOCMCAPTURE: Invalid argument *I tried using dc1394_vloopback with various settings including: dc1394_vloopback --video1394=/dev/video1394/0 --vloopback=/dev/video0 but that simply tells me "no cameras found :(" no matter what settings I try (I also made sure that the vloopback driver was unloaded). I am not aware of any other way to bridge ieee1394 feed and v4l, nor am I sure as to how to force pix_video to use different ieee1394 source (not sure whether this even works with the advc-100). *I tried accessing Gem CVS to see if there were any changes since the 0.90, but the CVS seems to be inaccessible: cvs -z3 -d:pserver:anonymous@cvs.gem.iem.at:/cvsroot/pd-gem login Logging in to :pserver:anonymous@cvs.gem.iem.at:2401/cvsroot/pd-gem CVS password: cvs [login aborted]: unrecognized auth response from cvs.gem.iem.at: M -!- Project map lookup failed () So, I have pretty much run out of ideas and I was hoping that someone might be able to help me out with this one, namely: 1) Is there a way to use my ADVC-100 to stream video to PD/Gem? 2) If there is no native way to do that is there a way to use vloopback or some similar method to channel its feed into the v4l format? 3) any other ideas/suggestion (other than spending money and buying myself a new <whatever> :-) I would greatly appreciate assistance in this matter! Best wishes, Ico

1 1

Re: [GEM-dev] removing files from CVS
by IOhannes m zmoelnig 17 Mar '06

17 Mar '06

Hans-Christoph Steiner wrote: > > Sounds great to me! The only thing I don't know about is the vector > stuff in MarkEx. The code is indeed in the pure-data CVS, but I don't > think its being built as part of the build system. The rest of MarkEx > is, and has been for a while. > i have added the hsv<->rgb conversion and the vector-stuff to the markex-directory. so now everything should be there, split into small files and using the hex-loader where appropriate (that is when i noticed that it didn't work properly) the library can be built both as small externals or as a big library. so no information should be lost. however i haven't had a chance to test the build-system on anything but linux. fmg.asdr. IOhannes

2 1

External example ?
by Alexandre Quessy 16 Mar '06

16 Mar '06

Hi, I searched the web and the list a little bit, but I can't find an example of a Gem external's source code. My idea would be basically to get info about a pix. Where should I look for such a hello world example ? Thanks ! aalex http://alexandre.quessy.net/

2 1

Re: [GEM-cvs] pix_share_*
by IOhannes m zmoelnig 15 Mar '06

15 Mar '06

IOhannes m zmÃ¶lnig wrote: > Update of /cvsroot/pd-gem/Gem/src/Pixes > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23076 > > Modified Files: > pix_share_read.cpp pix_share_read.h pix_share_write.cpp > pix_share_write.h > Log Message: > made it work on linux (even without crashes!); > now you can also specify the 4th argument (color) as symbolic name like "RGBA" or "YUV": > of course this needs to be back-checked on osX. now that there are help-patches it should be fairly easy. chris: great object, btw. mfg.hztr.a IOhannes

2 4

removing files from CVS
by IOhannes m zmölnig 12 Mar '06

12 Mar '06

hi i'd like to remove following files from the CVS: src/MarkEx/*.* (since it is in puredata-cvs as separate library) src/Pixes/pix_blur.{cpp,h} (i think this is replaced by pix_motionblur) any objections? mf.adsr IOhannes

1 0

OSX installation - PD CPU usage...
by B. Bogart 10 Mar '06

10 Mar '06

Hey all, Here is that patch that is acting up. I tried loading the clips in RAM, but that really does not help, in fact its much worse since I can't fit all the clips into ram on this machine. Anyhow I hope other people see this same issue, having the playback suffer after playing for an hour or so. Maybe someone can see something that is going wrong... Thanks all, ..b.

1 0

G5 terminal compile of Gem.
by B. Bogart 08 Mar '06

08 Mar '06

Hi Jamie, In the process of finding my CPU usage problems I found I could not compile Gem on the g5 from the terminal: g++ -c -fPIC -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -faltivec -I.. glsl_fragment.cpp -o glsl_fragment.o g++ -c -fPIC -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -faltivec -I.. glsl_program.cpp -o glsl_program.o glsl_program.cpp: In member function `void glsl_program::createArrays()': glsl_program.cpp:89: error: `m_size' undeclared (first use this function) glsl_program.cpp:89: error: (Each undeclared identifier is reported only once for each function it appears in.) glsl_program.cpp:89: error: `m_uniformCount' undeclared (first use this function) glsl_program.cpp:90: error: `m_type' undeclared (first use this function) glsl_program.cpp:91: error: `m_symname' undeclared (first use this function) glsl_program.cpp:92: error: `m_param' undeclared (first use this function) glsl_program.cpp:93: error: `m_flag' undeclared (first use this function) glsl_program.cpp: In static member function `static void glsl_program::linkCallback(void*)': glsl_program.cpp:481: error: 'class glsl_program' has no member named ' m_wantLink' make[1]: *** [glsl_program.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [Manips] Error 2 I'll remove the failing stuff for now, but wanted to let you know. 2Hgz g5 dual 10.3.9 is the machine. Thanks .b.

3 3

new message to [pix_texture] vote
by james tittle 06 Mar '06

06 Mar '06

heya, ...as usual, I start working on one thing, open up the red book, and find something else missing from Gem! In this case it is a selectable GL_TEXTURE_ENV_MODE...currently this is auto set GL_MODULATE at the end of pix_texture::setUpTextureState()...of course there are many other possibilities: GL_DECAL, GL_REPLACE, GL_BLEND, GL_ADD, and GL_COMBINE... ...so I'd like to add a message to select between these, and just want to get an opinion on what to call the message: my first thought would be [env $1<, but I guess it could be env_mode or envmode or...? ...also, it seems that this is auto set when rectangle textures aren't available, or if using rectangle textures AND [mode 1<, which doesn't seem right... thoughts? jamie

2 2

stencil
by cyrille henry 04 Mar '06

04 Mar '06

hello, does anyone have succefully used stencil buffer with GEM? here is what i'm trying to do, without succes... thanks cyrille #N canvas 0 0 911 552 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 585 153 gemhead 31; #X obj 585 129 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1; #X obj 585 220 GEMglClear; #X obj 650 198 GLdefine GL_STENCIL_BUFFER_BIT; #X obj 650 177 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X floatatom 659 220 5 0 0 0 - - -; #X obj 585 269 GEMglStencilMask; #X msg 692 246 1; #X obj 585 369 GEMglStencilFunc; #X msg 692 344 1; #X floatatom 634 335 5 0 0 0 - - -; #X obj 620 289 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 620 312 GLdefine GL_ALWAYS; #X obj 713 62 loadbang; #X obj 188 132 loadbang; #X msg 585 107 0; #X text 621 127 to draw in the stencil buffer; #X obj 54 454 square 3; #X obj 54 428 color 1 0 0; #X text 219 282 enable the stencil buffer; #X text 220 303 the red square should not be seen. (?); #X obj 396 90 gemwin; #X msg 396 42 create \, 1; #X msg 404 67 0 \, destroy; #X obj 585 397 square 1; #X connect 0 0 12 0; #X connect 1 0 36 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 20 0; #X connect 19 0 18 0; #X connect 20 0 24 0; #X connect 21 0 20 1; #X connect 21 0 23 0; #X connect 22 0 21 0; #X connect 24 0 26 0; #X connect 25 0 24 1; #X connect 26 0 42 0; #X connect 27 0 26 3; #X connect 27 0 26 2; #X connect 29 0 30 0; #X connect 30 0 28 0; #X connect 30 0 26 1; #X connect 31 0 21 0; #X connect 31 0 25 0; #X connect 31 0 30 0; #X connect 31 0 27 0; #X connect 31 0 33 0; #X connect 32 0 10 0; #X connect 32 0 15 0; #X connect 32 0 6 0; #X connect 32 0 11 0; #X connect 33 0 19 0; #X connect 36 0 35 0; #X connect 40 0 39 0; #X connect 41 0 39 0;

2 2

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