[GEM-dev] gemframebuffer flood

cyrille henry ch at chnry.net
Thu Oct 20 17:25:40 CEST 2011


hello,
welcome,

You should create multiple framebuffer during initialisation. one for each size.

I think the main problem with changing framebuffer size is not only the message in the console, but also poor performances.

cheers
Cyrille
  


Le 20/10/2011 11:03, Guido Tamino a écrit :
> Hello everybody, I'm new to the list.
>
> I'm working on a multipass glsl blur for Gem which needs downsampling for each pass. I managed to do that easily with a dimen message. It works fine, but [gemframebuffer] is flooding the console with "init" messages for every dimen change.
>
> [gemframebuffer]: using rectmode 1:GL_TEXTURE_RECTANGLE
> [gemframebuffer]: using type: BYTE
> [gemframebuffer]: using color: RGB
> [gemframebuffer]: using texunit: 0
>
> Is there a way to silence [gemframebuffer]? Am I supposed to take a different approach? I'm not an expert but I guess this is not an isolated case, downsampling seems to be a common technique when working with textures for glsl use.
>
> Best,
> Guido
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
>



More information about the GEM-dev mailing list