oh, thanks a lot, Kas.
> This I don't know about, it's not something I think I heard of in the > Fluxus context. For filtering and so on we do support GL shaders. > All I know is it's listed on the FreeFrame host apps listing: http://community.freeframe.org/hostdatabase I'm not sure I understand what you're suggesting. Would that be writing the output to a texture and then mapping it to the surface of a plane rendered at full screen? Are you saying I may have access to the texture pixels? If so that would work for me, I guess. I don't need much precision, rather the opposite, because all I want is to add glitches to the images. too bad fluxus is not the 'right' tool for that anyways, I was just getting into it and I really like it. But I'll be using it for other stuff for sure > > > 2. Is there any way to access the video buffer so I can manipulate > it's > > data? Is it possible to write to the buffer in real-time? > > > > the reason for question #2 is that I want to overwrite the video buffer > > after manipulating it. In other words, I want to write the filtered and > > manipulated result to the same buffer I was reading from. The workflow > > would be something like this: > > Well, yes, and no. You can't write to the video buffer directly (as in > setting pixels and so on) but you can do that to textures and > textures can consist of the output of a renderer. So; if you would > create aplane covering the whole screen, give it a texture like that > then you would have more or less what you need. > > On the down-side; doing per-pixel per-frame manipulations on those > will be fairly slow which will be a issue for the realtime performance > you require. > > As much as I'd like to "sell" you a copy, I'm not so sure Fluxus would > be a very good match for these requirements in practice. > > Yours, > Kas. >
