Hi,

sometimes i overload my CPU with a lot of videos and Gem slows. Is there some way i could see the real fps wich Gem is rendering? or some type of data showing the Gem performance...

Regards.

Here's something I run in my live patches: a frame rate pressure valve.

GEM wants to run at 20fps, default, but you can specify fps with a [frame $1(. You can run at a real high frame rate, and then as cpu load increases, you implement a frame rate dropper. I've enclosed an example which keeps the fps at 20 until cpu load hits 80%, and then linerarly drops it to 0fps at 100%cpu. Different systems benefit from different compression algorithms.

http://www.pdpatchrepo.info/hurleur/framerate.control.gem.pd

Thanks for the patch, is a simple solution, but still slows the render and worse, alternates between 20 and 0 all the time when i overload the cpu.

So, higher than 100% Gem will loose render frames? i'm thinking about warning the user when Gem is going slow. I'm preparing a huge patch and it's very probable these happens.

Ya, you don't have to drop the frame rate when you're overloading the cpu, i was just demonstrating how you can use the load meter to review perfornance and affect frame rate.

ok thank you

Looking for another thing in the Gem examples, i've found how show the real fps pf Gem...

[gemhead]
|
[t b b]
| |
[realtime]
|
[/]
|
[+ 0.5]
|
_

Really easy._

hello all,

i'd be interested in displaying the fps of my gem output, but can't get Belfegor's solution to work (and not understanding it completely i'm afraid..)

if anyone is willing to help, that'd be real nice !
thanks in advance,
em

Hi, I realise this is an ancient thread, but in case anyone else like me comes across it looking for a framerate display for Gem: I attached a functional subpatch based on Belfegor's hint.

Note that I used [avg~] to smoothen the output a little - probably not the best approach (I'm a beginner). If you don*t want this, just take the value just after the division. Also, because [avg~] is a sound object, this version requires DSP to be switched on. An alternative without DSP would be the [average] object from Gem, or any of the [average], [history], [mean], [mavg]... objects from various libraries.

framerate.pd

I discovered by accident a while ago that this undocumented functionality is actually built in to the [gemwin] abstraction. (I can't test this on versions of Gem where [gemwin] is an object that cannot be opened, which I've come across in the past, maybe in Pd-Extended?)

You can just do this (send "debug 1" message to turn on FPS output):

|debug 1(
|
[gemwin]
|
[route real_fps]
|
|here'syourFPSoutput\

@korakinos I haven't looked at your framerate patch, but as you mentioned, [avg~] as a smoother requires DSP... if the goal is to keep FPS high, you wouldn't want unnecessary calculation going on (indeed, if you're doing any audio at the same time as your visuals, best to run it in a separate Pd instance). The other external objects you mentioned would work, or there are a number of vanilla ways you could slow/smooth output in the control domain. I myself send the real_fps output to a vslider as my FPS meter—I don't use smoothing, but I only turn on the debug output for testing purposes, never in performance.