How to request for more than one plane data (RGB data)?

[dheeraj_c]

Hi All,

          I want to request for output/input image data for more than one plane. Currently I get R, G & B data separately in a for loop as in Dissolve example. Is there a way to get the data for all the planes at once? Can anyone please tell me how it can be done?

Thanks & Regards,

Dheeraj

[Chris Cox]

Just set the highplane and lowplane values for the planes you need.

Also, read the SDK - it explains how to do many of these things.

[Royi A]

Hi Chris,

I'm having the same problem and I can't find a solution in the SDK.

I look at the following code:

for (int16 plane = 0; plane < gFilterRecord->planes; plane++)

                              {

                                        // we want one plane at a time, small memory foot print is good

                                        gFilterRecord->outLoPlane = gFilterRecord->inLoPlane = plane;

                                        gFilterRecord->outHiPlane = gFilterRecord->inHiPlane = plane;

As I understand if I change it into:

gFilterRecord->outLoPlane = gFilterRecord->inLoPlane = 0;

gFilterRecord->outHiPlane = gFilterRecord->inHiPlane = 2;

I should have all 3 channels at once.

Yet when I go to the pointer 'gFilterRecord->inData' / 'gFilterRecord->outData'

I see a NULL pointer.

I'd be happy for a clarification.

Thank You.

[Tom Ruark]

I did the same experiment and it worked for me. I got interleaved RGB values as expected. What did advanceState return as an error code? Are you sure something else was not modified from the original example code? Is your image very large? Give me the info on the rest of the FilterRecord (width, height, mode ).

[Guest]

The answer from Chris is Correct. Partially that is...

The first part is right 😉

The second part about that the information is in the SDK is wrong. It is not.

I quote from the SDK Documentation.

Your filterSelectorStart and filterSelectorContinue

handlers should set these fields to the first and last input planes to process next.

.... to process next... If one sits down a pull that semantic apart - he will go into a never ending for loop and burn out.

The entire documentation never describes how to get interleaved data. Just that one can get it. Which does not help much.

Also, when setting data to interleaved the dissolve example code becomes unable to transport its image to the OS X preview window.

Which I do not imagine was intended for when releasing the example !

As I have been stating before... We dont need 2000 pages of documentation which makes no sense and does not enable us to write high quality plugs for Photoshop. We just need an up-to-date example along with perhaps 10 pages of documentation which does enable us to write high quality code for photoshop 😉

Given the fact that you taken so much time to write all the documentation you have - it should not be that hard to add another 10 pages which fills in all the missing spots 😉

Thanks

[Royi A]

It seems not much resources are invested in the Plug In SDK at these days.