Reply to Pix\_image problem on Linux on Tue, 07 Jun 2011 15:42:18 GMT

katjav — Tue, 07 Jun 2011 15:42:18 GMT

Hello,

This problem is discussed before on Pd list but still no real solution. When I create [pix_image] in a pd on Debian Linux, the object causes heavy CPU load even before it is connected to anything, some 4% per object instance. On Pd list it was suggested by several people to send message [thread 0( to the object. This will stop the crazy CPU load indeed, but now the object can no longer load images.. Sending [thread 1( reintroduces CPU load, but does not reenable image loading.

edit: the loaded images are lost (it is possible to load new images with the 'open' message, however not with initialisation argument).

This problem does not exist on Windows with the same hardware, and also not on my Macbook. On Debian, I first used the binary Gem package, but later compiled from source to include font support. Both these versions have the same problem. Can anyone confirm this issue, or report about a Gem for Linux where this problem does not occur? Or could it be a driver-related issue?

Thanks for any help or comment.

Katja

Reply to Pix\_image problem on Linux on Tue, 07 Jun 2011 22:33:59 GMT

katjav — Tue, 07 Jun 2011 22:33:59 GMT

Well here is how I 'solved' it for the moment: in pix_image.cpp constructor I changed threadMess(1) to threadMess(0), and recompiled Gem. Now I can load patches with lots of [pix_image] without the crazy CPU problem, just like on the other platforms.

But this is no real solution either of course. All the threading code was carefully written for some good reason I suppose. Better send a bug report of this.

Katja