I've marked the RADAR as 'resolved'. cwright, I realise I was being
unreasonable. I think because QC has such a friendly face, the fact
it can do fairly low-level (and therefore potentially dangerous)
stuff is easy to lose sight of, especially for non-programmers like
myself. However, I do think that a little note added to the tooltip
and Library window documentation to the effect that it's safer to use
the Core Image Accumulator for image-based feedback might be helpful,
to prevent others falling into the same trap. People like myself not
familiar with the behind the scenes Core Image nuts and bolts, are
far more likely to reach for the Feedback patch to do... well,
feedback effects, than they are for the more obscurely-named Core
Image Accumulator. So I'm backing down as gracefully as I can manage
in the face of superior knowledge, but still partially sticking to my
guns ;)
a|x
On 10 Feb 2011, at 06:30, George Toledo wrote:
Oh, sorry. I didn't catch that post, in the flurry that happened in
a short time there.
On Thu, Feb 10, 2011 at 12:35 AM, Christopher Wright
<christopher_wri...@apple.com> wrote:
> Is there anything problematic with this kind of image feedback
setup? This always seems to work better than using the accumulator
or feedback patch for me. I'm monitoring for leaks on two different
gpu's right now, in leopard and sl, and it looks ok.
Render in Image is fine. As I said a few emails ago:
> The shader version uses Render In Image, which is little more
than a fancy FBO. It doesn't need to keep around intermediate
results beyond the previous frame used as input. This means it
uses less memory, but also means that it's somewhat less accurate
with certain operations.
Render In Image also has the convenient side effect of flattening
CI Filter chains when used. Thus, the following (which still uses
CI for the filter effect) is totally fine.
Using the RII to flatten comes in handy in a variety of circumstance.
Side notes - Some operations happen very quickly when implemented
in with the GL objects, like Billboard (like this RII vs.
Accumulator, or mocking up a box blur with billboards vs. CI). (It
also happens to be handy for sanitizing the intensity image from
the kineme kinect tools so that CI doesn't freak out... to any of
those who have experienced weird problems with that).
Of course, this is all _completely_ obvious to the casual
observer ... or something? :)
Totally.
By the way... I noticed last week that when I do an RII feedback
loop with anything less than 32 bit, it leaves a layer of crud at
the last bit that never clears (I believe). Totally obvious stuff :)
--
Christopher Wright
christopher_wri...@apple.com
--
George Toledo
gtole...@gmail.com
www.georgetoledo.com
The information contained in this E-mail and any attachments may be
confidential.
If you have received this E-mail in error, please notify us
immediately by telephone or return E-mail.
You should not use or disclose the contents of this E-mail or any
of the attachments for any purpose or to any persons.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
d...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%
40yahoo.co.uk
This email sent to the_vo...@yahoo.co.uk
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
