Frederico, I'm curious if you just installed PD via a repository on the Pi3 or downloaded a special version of PD compiled for the Pi. Did you install Gem separately or use a version that came bundled with the PD you used ? Thanks, Jim
Hello,
I have tried Gem on the Pi3 and it works. I did not try Gem *completely* because I had no time, but did not encounter major issues other than video capture. I could not use video capture since it overworked the CPU. However, accessing the video feed with openCV (not through Gem) gave *very* reasonable CPU usage (while doing Face Tracking, for example). I am not sure why I encountered such a difference, but I just couldn't use Gem for *that*.
Cheers,
Fede
On Sat, Dec 9, 2017 at 4:01 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 12/09/2017 09:36 PM, Jim Ruxton wrote:
I am wondering what is the current best option of using Gem on the Pi 3. Would I be best to use Purr Data? or Vanilla PD?
i think this is the wrong question.
Gem on the rpi is kind of limited as it (Gem) depends on openGL and the rpi provides openGL-ES (though there *are* experimental (still?) drivers for openGL as well). this is quite independent of purr data, pd-vanilla or whatever.
gfmdasr IOhannes
Hi Jim,
I dont have a very clear log of what i did. But mainly I compiled pd and Gem from git, fetching all dependencies in pd's INSTALL.txt instructions and (I think) Gem's dependencies from either a debian package or looking into old puredata.info entries on Gem's dependencies. I dont remember id there is a Gem package already. There is no need for compiling Pd, but I think you need to compile Gem. Please, anyone correct me if I'm wrong!
Cheers,
Fede
fdch.github.io/tv
On Dec 10, 2017, at 2:23 PM, Jim Ruxton jim.ruxton@gmail.com wrote:
Frederico, I'm curious if you just installed PD via a repository on the Pi3 or downloaded a special version of PD compiled for the Pi. Did you install Gem separately or use a version that came bundled with the PD you used ? Thanks, Jim
Hello,
I have tried Gem on the Pi3 and it works. I did not try Gem *completely* because I had no time, but did not encounter major issues other than video capture. I could not use video capture since it overworked the CPU. However, accessing the video feed with openCV (not through Gem) gave *very* reasonable CPU usage (while doing Face Tracking, for example). I am not sure why I encountered such a difference, but I just couldn't use Gem for *that*.
Cheers,
Fede
On Sat, Dec 9, 2017 at 4:01 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 12/09/2017 09:36 PM, Jim Ruxton wrote: I am wondering what is the current best option of using Gem on the Pi 3. Would I be best to use Purr Data? or Vanilla PD?
i think this is the wrong question.
Gem on the rpi is kind of limited as it (Gem) depends on openGL and the rpi provides openGL-ES (though there *are* experimental (still?) drivers for openGL as well). this is quite independent of purr data, pd-vanilla or whatever.
gfmdasr IOhannes
On 12/10/2017 11:04 PM, Fede Camara Halac wrote:
Hi Jim,
I dont have a very clear log of what i did. But mainly I compiled pd and Gem from git, fetching all dependencies in pd's INSTALL.txt instructions and (I think) Gem's dependencies from either a debian package or looking into old puredata.info entries on Gem's dependencies. I dont remember id there is a Gem package already. There is no need for compiling Pd, but I think you need to compile Gem. Please, anyone correct me if I'm wrong!
while i have no experience with the rpi3, i wonder why you did recompile.
Debian (and thus raspbian) provides both puredata and gem.
since the stock Debian images are targeted at a baseline CPU below the rpi3, you can probably get quite a performance boost if you compile the packages yourself with the right flags (and I don't know whether raspbian provides optimized builds for all the packages in Debian, or just points you to the stock Debian packages mostly).
but you must provide those flags to enable optimization, and from your description it doesn't sound like you did.
fmard IOhannes
Indeed, you are right. I will try to find the flags I used. I remember trying to use the raspbian package and not succeeding, hence my need to compile. But I can't prove that right now. I will try later this week.
i'm interested in those optimization flags, though :)
fdch.github.io/tv
On Dec 10, 2017, at 5:27 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
you must provide those flags to enable optimization, and from your description it doesn't sound like you did.
I have compiled Gem on the pi3 and it compiles fine and the examples run ok. If there are some magic optimization flags that make it run even better I world also like to know :)
There is one important issue about the OpenGL driver tho. On the latest raspbian Stretch the OpenGL driver runs at 1/4 the speed of the previous raspbian Jessie so I recommend to use Jessie instead for now. You can get it here:
http://downloads.raspberrypi.org/raspbian/images/
"For OpenGL 2.1, you need any version from September 2016 onwards. The last version is 2017-01-11-raspbian-jessie-lite.img"
I got this information from here:
http://www.questions4steveb.co.uk/html/Raspberry_Pi/Stellarium-on-the-Pi
There are other tips in that page that can help.
Another issue is that with the OpenGL driver you can only use the HDMI output. No composite out for now.
On 10 December 2017 at 23:02, Fede Camara Halac camarafede@gmail.com wrote:
Indeed, you are right. I will try to find the flags I used. I remember trying to use the raspbian package and not succeeding, hence my need to compile. But I can't prove that right now. I will try later this week.
i'm interested in those optimization flags, though :)
fdch.github.io/tv
On Dec 10, 2017, at 5:27 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
you must provide those flags to enable optimization, and from your description it doesn't sound like you did.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
-
Fede Camara Halac -
Francisco Medeiros -
IOhannes m zmölnig -
Jim Ruxton