In PS 7, I filtered a whole image which was 2560x1920 pixels, which is 4.9 mp.
Then I reversed this and made a selection which would fit into a crop of 700x1216 pixels, or 0.8mp, (I did not crop), but it was an irregular shape so I guess it would be about 600,000 pixels - about 1/8th of the area of the image.
Using PS7's timer function, NI 2.6 filtered the whole image in 180 secs, but to filter only the small selection it took 166 seconds.
Why is the time so out of proportion?
Thank you for all the continued improvements, especially the plug in. Best wishes.
filtering time for selection in Plug In
Plug in time for selections
Vlad
I played with this a bit more. In the first note I sent today, I omitted to say that I had made the selection into a new layer. Then I filtered the whole of the new layer, which was the same size as the original image, although 7/8ths of the area was empty and transparent.
If I select the transparent area and then intervt the selection to get just the irregular opaque are, then it filtered in 38 seconds.
So the problem is that NI does not have the ability to ignore empty pixels and just work on the the opaque ones.
I also get similar fast results if I just make the selection without making it into a new layer. So NI is able to ignore unselected areas, but not empty areas.
Bryan
I played with this a bit more. In the first note I sent today, I omitted to say that I had made the selection into a new layer. Then I filtered the whole of the new layer, which was the same size as the original image, although 7/8ths of the area was empty and transparent.
If I select the transparent area and then intervt the selection to get just the irregular opaque are, then it filtered in 38 seconds.
So the problem is that NI does not have the ability to ignore empty pixels and just work on the the opaque ones.
I also get similar fast results if I just make the selection without making it into a new layer. So NI is able to ignore unselected areas, but not empty areas.
Bryan
Re: Plug in time for selections
Yes, it seems you are right about that. We will look into the code details.Bryan Stone wrote: So the problem is that NI does not have the ability to ignore empty pixels and just work on the the opaque ones.
Thank you,
Vlad