Copy link to clipboard
Copied
Hey!
Im using the standard color picker with preview in my effect in that way: while I choosing the color, algorithm is akso working and calculating the sequence data.
After clicking Ok after effects doing some work and sometimes it can take a few seconds! During that process AE`s UI is not accesseble.
So what that could be and how can I prevent or optimze my work with color picker to avoid that pause?
By the way, color picker without 'preview' check box never produce that king of problem.
Copy link to clipboard
Copied
System Specs would be helpful here.
Resetting Preferences might help:
Press Alt (Windows) or Option (Mac OS) while launching After Effects. You can release the Alt or Option key when the splash screen appears. To reset preferences and plug-in cache at the same time, hold down Control-Shift-Alt (Windows) or Command-Shift-Option (Mac OS) while the application is starting.
Also going into preferences and deleting/cleaning disk cache might be helpful.
Copy link to clipboard
Copied
Thanks!
Its not working for me.
To be honest, I think there should some more suitable way to use it in my plugin.
I think the problem is in my plugin, actually.
Copy link to clipboard
Copied
how does AE behave with other plug-in when selecting a color on you machine?
is it only your plug-in that causes such a freeze?
Copy link to clipboard
Copied
Yep, just my plugin.
Freezing takes longer the longer I choose a color. If I just pick a color I need - it is fast. If Im looking for suitable colorm choosing different options - "Ok" or "Cancel" will take some time.
It have some king of cumulative effect or so.
And if Im not using the preview - no freeze.
How it works:
Color is supervized param. If it was changed, my arb data also changing, after that seqence data is changing, doing some calculations and arp parameter takes two flags:
params[PARM_ARB]->uu.change_flags |= PF_ChangeFlag_CHANGED_VALUE;
suites.ParamUtilsSuite3()->PF_UpdateParamUI(in_data->effect_ref, PARM_ARB, params[PARM_ARB]);
After that render view is updating and my arb param also re-drawing.
color parm -> arb data -> seq data -> calculations -> render -> arb param redraw
Copy link to clipboard
Copied
And sorry, I need to clarify. Im using that color choosing window, with preview checkbox. Not color picker itself.
Copy link to clipboard
Copied
does you plug-in get any calls during that freeze? is it being bombarded with arb and seq_data calls?
what else can you tell abuot that freeze?
Copy link to clipboard
Copied
Trying to dig out more. So what I have now..
//22 is a command fot arb data event.
//the number after 22 - is the code of arb data event
1) Action - color was changed with preview, but "cancel" pressed
22 2 PF_Arbitrary_COPY_FUNC ... 3 times
22 1 PF_Arbitrary_DISPOSE_FUNC ... 3 times
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
22 2 PF_Arbitrary_COPY_FUNC ... 3 times
22 1 PF_Arbitrary_DISPOSE_FUNC ... 3 times
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
7 PF_Cmd_SEQUENCE_FLATTEN
6 PF_Cmd_SEQUENCE_RESETUP
22 2 PF_Arbitrary_COPY_FUNC ... 3 times
22 1 PF_Arbitrary_DISPOSE_FUNC ... 3 times
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA
7 PF_Cmd_SEQUENCE_FLATTEN
6 PF_Cmd_SEQUENCE_RESETUP
after that :
22 => 1-3-4; 1-2-3-4; 1-1-1-1-3-4 etc. many many times
// 1 PF_Arbitrary_DISPOSE_FUNC,
// 2 PF_Arbitrary_COPY_FUNC,
// 3 PF_Arbitrary_FLAT_SIZE_FUNC,
// 4 PF_Arbitrary_FLATTEN_FUNC,
----- end of test ------
2) Action - color selected without preview and "cancel" pressed
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
14 PF_Cmd_UPDATE_PARAMS_UI
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
15 PF_Event_...
----- end of test ------
3) The same color selection without preview and "ok" pressed
{
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
14 PF_Cmd_UPDATE_PARAMS_UI
} ... 3 times
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
13 PF_Cmd_USER_CHANGED_PARAM
22 2 PF_Arbitrary_COPY_FUNC
28 PF_Cmd_GET_FLATTENED_SEQUENCE_DATA ... 4 times
7 PF_Cmd_SEQUENCE_FLATTEN
6 PF_Cmd_SEQUENCE_RESETUP
{
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
22 3 PF_Arbitrary_FLAT_SIZE_FUNC
22 4 PF_Arbitrary_FLATTEN_FUNC
} ... many times and variations
23 PF_Cmd_SMART_PRE_RENDER
24 PF_Cmd_SMART_RENDER
14 PF_Cmd_UPDATE_PARAMS_UI
15 PF_Event_...
{
22 2 PF_Arbitrary_COPY_FUNC
22 1 PF_Arbitrary_DISPOSE_FUNC
22 3 PF_Arbitrary_FLAT_SIZE_FUNC
22 4 PF_Arbitrary_FLATTEN_FUNC
} ... many many times and variations until end
You was right, something happening with arb data.
Digging for more information...
Copy link to clipboard
Copied
Im not active about that now, but noticed that I dont have that issue on mac.