yes you are right, once it was 3 times slower, once it was 3 times faster. Gem is on default framerate, I guess you mentioned it is 20fps. Monitor is on 60Hz. There is a ratio of 1:3 indeed but I hope it has nothing to do with metro.
On Mon, Oct 1, 2018 at 8:43 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 10/1/18 6:30 PM, Csaba Láng wrote:
Indeed, annoying it is during developing the patch, however had a feeling that maybe Gem makes my metro work slower exactly 3 times, one second
lasts
3 seconds in real time.
i'm a bit confused now: in your last thread you stated that the metro was exactly 3 times faster (that is a [metro 1000] running a 333ms; now a [metro 1000] is running at 3000ms). while a slower/faster metro is entirely possible and te two problems might be unrelated, i wonder why exactly the same factor "3" occurs in both issues. could it be that the problem is somewhere else (e.g. a simple patch error?)
at which framerate is your Gem-patch running? at which framerate is your monitor running?
it is in no correlating with the source of the bug.
afaict, this is unrelated to the crasher bug you are describing.
But will never get the answer.
i'm not sur what you mean by this.
fgmsard IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list