On 9 Feb 2011, at 21:00, Alex Drinkwater wrote: | That's odd. When you say 'feeding', do you mean you have a macro containing a Feedback patch, with the image output going to a texture input of a GLSL patch? I tried this myself, and it doesn't seem to make any difference. If you have a moment, could you have a look at my example? I'd be interested to know if it can be tweaked to work without leaking.
a|x
--- On Wed, 9/2/11, Chris Wood <pson...@gmail.com> wrote:
From: Chris Wood <pson...@gmail.com>
Subject: Re: Image Feedback Memory Leaks
To: "Alex Drinkwater" <the_vo...@yahoo.co.uk>
Cc: "Achim Breidenbach" <ac...@boinx.com>, quartzcomposer-dev@lists.apple.com
Date: Wednesday, 9 February, 2011,
20:56
No, the issues I had were specifically with using core image filter and feedback. I didn't try the feedback patch back then, but every other method led to a massive memory leak. It didn't affect the accumulator so far as I know.
I'm using the feedback patch at the moment, with *massive* volumes of image data. Over 400,000 images have passed through it without any noticable leaking. This is feeding glsl though, not core image.
Chris
On 9 Feb 2011, at 20:45, Alex Drinkwater wrote: | Hi Chris,
I don't think the problem is to do with feedback per-se: it's the Feedback patch, specifically. Using the Core Image Accumulator patch seems OK (is that
what you meant?). There's clearly some fundamental underlying issue though, so I'm going to file a bug.
Cheers,
a|x --- On Wed, 9/2/11, Chris Wood <pson...@gmail.com> wrote:
From: Chris Wood <pson...@gmail.com>
Subject: Re: Image Feedback Memory Leaks
To: "Achim Breidenbach" <ac...@boinx.com>
Cc: "Alex Drinkwater" <the_vo...@yahoo.co.uk>, quartzcomposer-dev@lists.apple.com
Date: Wednesday, 9 February, 2011, 11:50
Reposted to the whole
list, instead of just Alex:
No time to check just now, but are you using it with core image? I use feedback heavily without any major leaks in some of my projects, but I've switched to pure GLSL. I definitely had major leaks with core image before.
Chris
On 9 February 2011 11:43, Achim Breidenbach <ac...@boinx.com> wrote:
Hi Alex,
same issue with my hardware: iMac, NVIDIA GeForce GT 130
I also exchanged the image input into the feedback patch, as well as the image filter inside, but still the same problem.
I am not sure, if you are searching for a workaround or collecting data for filing a bug? You can certainly do the same feedback thing with an image accumulator patch.
best,
Achim Breidenbach
Boinx Software
On 09.02.2011, at 11:25, Alex Drinkwater wrote:
> I've noticed what seems to be a massive memory leak when using the Feedback patch with images. The attached file illustrates a simple case. I find that the framerate drops rapidly when running the composition. Can anyone else confirm that the same thing happens on their hardware?
>
> I've also tried using a Queue patch to implement image/video feedback in a similar way, with the same disappointing result.
>
> I seem to remember also using an undocumented _javascript_ feature in a Core Image Kernel to implement feedback in a previous version of Quartz Composer, and hitting the same issue. The two issues may be completely unrelated, however.
>
> a|x
>
> 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:
>
> This email sent to ac...@boinx.com
|
|
|
Feedback No Memory-Leak.qtz
