I've noticed a difference in a plugin behaviour in CS6 and CS5.5.
The following call generates a PF_Cmd_ARBITRARY_CALLBACK in CS6. The PF_Cmd_ARBITRARY_CALLBACK appears later in a plugin work and doesn't work properly in CS6. Though in CS5.5 there is no problem with this function, it doesn't generate any weird events.
suites.ParamUtilsSuite1()->PF_GetCurrentState(in_data->effect_ref, &seqData->curSessionParamState); (code for CS5.5)
suites.ParamUtilsSuite3()->PF_GetCurrentState(in_data->effect_ref,PF_ParamIndex_CHECK_ALL, NULL, NULL, &seqData->curSessionParamState); (updated code for CS6, in respect that the signature of PF_GetCurrentState has changed)
I work in Windows 7, x64. CS6 is 220.127.116.118 version, CS5.5 is 10.5.0.253 version. Do you have any idea what might have changed in CS6 to provide such an error?
Rick, thank you for the answer. I'll also try to ask at Adobe AE SDK forum.
Yes, I have a plugin that works in CS5.5. And now I'm trying to set it work in CS6.
Those are not error messages, but the different behaviour of a plug in in a debug mode. I just apply the effect to some footage and the bug occurs at the plug in initialization state. So I suppose that the problem is inside a new SDK. But I have no guess where it may be..