Hi all
Since there is such a wide variety of hardware, and drivers, available for video and graphics, I think it might be useful to compile a list of problems associated with specific configurations and GEM. This will help the developers determine what problems are in the GEM code, and also provide a reference for users. Keep in mind that it is impractical for the GEM developers to test even a small fraction of the possible configurations. I will put the info up on my GEM page.
A little form to help gather information:
Platform: OS version: Vendor: CPU: RAM: HD: GPU: GPU Driver: Other Software/Drivers: Other video hardware Bugs/Issues:
Here's a sample for my config:
Platform: OSX
OS version: 10.3.4
Hardware Vendor/Model: Apple PowerBook Titanium
CPU: 1Ghz G4 PPC 7450
RAM: 512MB
HD: 60GB 4200rpm
GPU: ATI Radeon Mobility 64MB
GPU Driver: Apple/ATI 10.3.4 standard
Other Relevant Software/Drivers: Quicktime 6.5
Other video hardware: crappy iBot webcam
Bugs/Issues: YUV textures do not blend properly with ARGB masks.
Texture corruption with CLIENT_STORAGE_APPLE enabled, Altivec
processing and QT internal tasking - pix_film + pix_texture (pix_movie
circumvents the issue).
You can post on or off list if you have some current issue to be solved. Any other submissions can probably be sent directly to me.
Thanks cgc
ps - if someone wants to put up a nice web based form to do this automatically, that would be fantastic.
hello chris, list,
Platform: Gentoo Linux x86 OS version: 2.6.7-ck2 Hardware Vendor/Model: Compaq Evo N800w CPU: P4-M 2GHz RAM: 512MB HD: 40GB 5400rpm GPU: ATI FireGl 9000 Mobility GPU Driver: ATI fglrx 3.9.0-r1 Other Software/Drivers: alsa 1.0.5a, jack 0.98.1-r1 Other video hardware: Bugs/Issues: everything is fine, have some weird issues in RT though, not GEM related but really annoying (GEM 0.90 + RT = freeze/crash/watchdog, PDP 0.12.3 + RT + GLX window = freeze/crash/watchdog).
+! aym3ric.
On Jul 3, 2004, at 6:35 AM, aym3ric wrote:
Bugs/Issues: everything is fine, have some weird issues in RT though, not GEM related but really annoying (GEM 0.90 + RT = freeze/crash/watchdog, PDP 0.12.3 + RT + GLX window = freeze/crash/watchdog).
I think a similar thing happens on OSX using -rt as well. The GUI locks up when the CPU loads gets high although GEM continues to render to the window. I've always thought it had to do with GEM monopolizing the video hardware and not giving other processes a chance to draw, and do other UI events. The problem seemed to stem from OSX's GUI being an OpenGL process itself, but looks like that might not be the case.
Thanks cgc
+! aym3ric.
who should use -rt? who not? what does it do?
Am 03.07.2004 um 19:05 schrieb chris clepper:
On Jul 3, 2004, at 6:35 AM, aym3ric wrote:
Bugs/Issues: everything is fine, have some weird issues in RT though, not GEM related but really annoying (GEM 0.90 + RT = freeze/crash/watchdog, PDP 0.12.3 + RT + GLX window = freeze/crash/watchdog).
I think a similar thing happens on OSX using -rt as well. The GUI locks up when the CPU loads gets high although GEM continues to render to the window. I've always thought it had to do with GEM monopolizing the video hardware and not giving other processes a chance to draw, and do other UI events. The problem seemed to stem from OSX's GUI being an OpenGL process itself, but looks like that might not be the case.
Thanks cgc
+! aym3ric.
Bugs/Issues: everything is fine, have some weird issues in RT though, not GEM related but really annoying (GEM 0.90 + RT = freeze/crash/watchdog, PDP 0.12.3 + RT + GLX window = freeze/crash/watchdog).
I think a similar thing happens on OSX using -rt as well. The GUI locks up when the CPU loads gets high although GEM continues to render to the window. I've always thought it had to do with GEM monopolizing the video hardware and not giving other processes a chance to draw, and do other UI events. The problem seemed to stem from OSX's GUI being an OpenGL process itself, but looks like that might not be the case.
well in my case it just can't render one single frame, as soon as the window is created (either gem or pdp_glx), pd is either gone/watchdoging or in worst cases linux freezes.
so i'm afraid it has to deal with the gl libs and the fglrx driver...
+! aym3ric.
i might add to the confusion a bit.. there is something going on with opengl, threads and RT scheduling. i've been chasing the problem for quite a while but i can't find what it is..
the only relyable way i found to work around the problem is to initialize gl (talking about the glut thing in wvvw) in a non-rt thread, which is explicitly started with SCHED_OTHER, and synchronize using condition variables, effectively stopping the rt thread until the initialization is done.
now, this works for gl running non-RT in an otherwize RT program. for gl in RT thread, there seems to be something really wrong.
i haven't tried this, but maybe it would work to disable RT scheduling temporarily, initialize all gl things, and enable RT again.
anyway, this smells.
On Mon, 5 Jul 2004, aym3ric wrote:
Bugs/Issues: everything is fine, have some weird issues in RT though, not GEM related but really annoying (GEM 0.90 + RT = freeze/crash/watchdog, PDP 0.12.3 + RT + GLX window = freeze/crash/watchdog).
I think a similar thing happens on OSX using -rt as well. The GUI locks up when the CPU loads gets high although GEM continues to render to the window. I've always thought it had to do with GEM monopolizing the video hardware and not giving other processes a chance to draw, and do other UI events. The problem seemed to stem from OSX's GUI being an OpenGL process itself, but looks like that might not be the case.
well in my case it just can't render one single frame, as soon as the window is created (either gem or pdp_glx), pd is either gone/watchdoging or in worst cases linux freezes.
so i'm afraid it has to deal with the gl libs and the fglrx driver...
+! aym3ric.
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
chris clepper wrote:
Hi all
Since there is such a wide variety of hardware, and drivers, available for video and graphics, I think it might be useful to compile a list of problems associated with specific configurations and GEM. This will help the developers determine what problems are in the GEM code, and also provide a reference for users. Keep in mind that it is impractical for the GEM developers to test even a small fraction of the possible configurations. I will put the info up on my GEM page.
this is a great idea, but probably it would be best to put it on some community-based site (like http://puredata.info ), so people could commit information without the need for some webmaster to put it online.
mfg.asd.aser IOhannes
this is a great idea, but probably it would be best to put it on some community-based site (like http://puredata.info ), so people could commit information without the need for some webmaster to put it online.
Ok, I took Johannes' suggestion and put a page up in my puredata.info folder:
http://puredata.info/Members/cgc/gem_hardware/document_view
I don't know if the default is to allow anyone to add to the page or not, so if I need to change a setting or put it in a different location then let me know.
cgc
-
aym3ric -
chris clepper -
IOhannes m zmoelnig -
lee -
Max Neupert -
Tom Schouten