[PD] gem - pix_buffer strangeness

[B. Bogart]

Hey Thoralf,

Indeed my system does not fit well into input->filter->output, but then
again neither does Gem. Now this is how PDP is designed and worked very
well for doing this.

I'm developing PixelTANGO which is a Gem-based VJ tool and I have run into
many of the issues your talking about. I would argue that if you want to
make effective use of gem forget your input->filter->output idea or use
PDP.

That being said I don't see anything in your project (mixing images) that
is dependant on this idea.. Or am I missing something? You must be doing
much more than just mixing images... ?

I have used pix_composite but it was pretty damn slow (on linux) no chance
for GPU optimization, since the work in done on the CPU and then passed
onto the graphics card for the easy part, putting it on an object.

Anyhow good luck!

B>


> Ben,
>
>> the BEST way to do this in Gem is to make a
>> different square/rectangle for each image
>> and stack them on top of one and other
>
> sounds promising - unfortunately, this approach
> doesn't fit into the framework of the thingie i want
> to use this patch for (a vj-tool). it's based on
> input->filter->output-chains, and their
> interconnections are one and only one gem-renderchain.
> I would have to do rendering in the input-part and
> make snapshots there, and i'm somewhat reluctant to do
> so ...
>
>> make the mix. This is much more simple, much easier,
>> and way way more
>> optimized.
>
> then again, this sounds convincing. hmm.
> at the moment i'm tempted to screw my approach and do
> the mixing in a really dull and ugly (but working) way
> - buffered with (number of pics-1) pix_composite
> objects.
>
> with kind regards,
> thoralf.
>
>
>
>
>
>
> ___________________________________________________________
> Gesendet von Yahoo! Mail - Jetzt mit 250MB Speicher kostenlos - Hier
> anmelden: http://mail.yahoo.de
>