GEM-dev March 2009

gem-dev@lists.iem.at

14 participants
28 discussions

couldn't create udpsend/udpreceive in pd-extended 0.40.3 on intel mac after several reinstallation.
by ahyan 21 Mar '09

21 Mar '09

Hi all! I am a new user of pd (I don't know whether I choose the correct mail-list. Please forgive me if I chose it wrong :D) I just found I couldn't create udpsend/udpreceive suddenly in pd extended 0.40.3 on intel macbookpro. several reinstallation had been done but the problem is still here. Before that, pd works well until a force quit. Could you guys give me a hand? Thanks a lots! I do know that may be a stupid question! regards, ahyan

3 2

imagemagick vs libjpeg
by B. Bogart 14 Mar '09

14 Mar '09

Hey all, Has anyone profiled how imagemagick compares to Gem's ol direct libjpeg? My patch is currently saving 1 650x480 image each 50ms to a RAID0 array. Here is what oprofile says: 19403412 47.3886 libMagick.so.10.0.9 9418729 23.0032 libjpeg.so.62.0.0 4391154 10.7244 Gem.pd_linux <snip> Seems pretty heavy. I'll try a Gem without imagemagick after this weekend. Just wondering if anyone else has already done the testing. Thanks, B.

1 0

anti aliasing with ATI radeon 9600
by Jack 12 Mar '09

12 Mar '09

Hello, I have an installation working on MacOSX.4 (PowerPC G5) and an ATI Radeon 9600. Using FSAA messages (or [polygon_smooth]) seems not good for anti aliasing. I have seen old posts on the list (installation of the new ATI driver and ATI preference panel for MacOSX), but the result is far than NVidia cards and the FSAA message. So with this stuff, my text from [text3d] and my line with [curve 2] are horrible. Do you know something to resolve this problem ? Thanx. ++ Jack

1 0

GEM/glsl feedback
by marius schebella 08 Mar '09

08 Mar '09

hi, I am not sure whether it is possible to do feedback in GEM (glsl?) without reading back to the cpu? Is there an example in the help patches? thanks, marius.

3 3

pix_buffer_share?
by B. Bogart 07 Mar '09

07 Mar '09

Hey all, Is there a way to share a whole pix_buffer between PD processes? I'm running my SOM stuff in a second PD instance (to make use of the second core in my installation machine). But as I'm developing both PD instances are getting more coupled and I'd like to share a whole pix_buffer. The alternative is using two [pix_share]s, one for input the other for output, controlled by netsend. The problem with this is that I need to send a lot of data quickly, 10ms between new images, and I think that could cause lots of problems. I don't think I'll be able to get the CPU usage of the second patch down low enough to not interfere with rendering in the main PD patch. Thanks, B.

3 5

Re: [GEM-dev] [gphoto-devel] segfault resulting from conflicts with imageMagick
by B. Bogart 04 Mar '09

04 Mar '09

Hmm... I've copy-pasted your code (with libmagick first) and I still get a segfault. This is on debian lenny. In the final version libmagick and libgphoto are loaded at runtime, how can the conflict be resolved? (make sure libmagick loads first?) Should not all lenny packages be compiled in a method that allows them to be used together? Is this a debian bug? (I'm now using stable versions of both libmagick and libgphoto) How to resolve this? .b. Marcus Meissner wrote: > On Tue, Mar 03, 2009 at 09:02:09AM -0800, B. Bogart wrote: >> Hey all, >> >> I reported a problem with my gphoto plugin interfering with another >> Puredata plugin (GEM) linking against libmagick. >> >> Seems that indeed libgphoto2 and libmagick have some conflict. >> >> Looks like gphoto2 calls end up calling libmagick. >> >> Can anyone reproduce this issue? > > I tried > cc xx.c -o xx -I/usr/include/gphoto2 -I/usr/include/libexif -lc -lm -lMagick++ -lgphoto2 -lgphoto2_port -lexif -lm -lusb > ./xx > > and it worked. > > The reason it might happen is that ImageMagick has compiled in its > own libtool version which might be incompatible to libgphoto2 / the > system one. > > Ciao, Marcus >

2 1

[Fwd: Re: [gphoto-devel] segfault resulting from conflicts with imageMagick]
by B. Bogart 03 Mar '09

03 Mar '09

1 0

segfault resulting from conflicts with imageMagick
by B. Bogart 03 Mar '09

03 Mar '09

Hey all, I'm writing a gphoto2 interface object for PD. For some reason I get segfaults when running functions in my external, the backtrace shows these are related to libimageMagick. If I don't load Gem my code works as expected. I've attached the code. The openCam() causes the problem. Does anyone see anything in there that would conflict with imageMagick? Thanks, B. Bogart

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 2009