Re: Accessing and displaying frames in custom view in FxPlug 4
Re: Accessing and displaying frames in custom view in FxPlug 4
- Subject: Re: Accessing and displaying frames in custom view in FxPlug 4
- From: Sergey via Pro-apps-dev <email@hidden>
- Date: Mon, 1 Jun 2020 11:23:25 +1000
Hi Darrin,
Sure, no problem. I've prepared test projects and submitted the
following feedback items:
FB7720606 - FxCustomParameterActionAPI_v4:currentTime deadlock in
custom view handler // FxPlug 4.0
FB7720617 - Parameters values are not preserved/reset to defaults
in custom view handler // FxPlug 4.0
Please have a look. Let me know if more information is required.
Best regards,
Sergey
On 30/05/2020 1:23 am, Darrin Cardani wrote:
Sergey,
I’ve not seen either of these happen. If you could write up a couple of
feedback issues with simple examples attached that would help in fixing these.
Thanks,
Darrin
On May 27, 2020, at 9:48 PM, Sergey via Pro-apps-dev
<email@hidden> wrote:
Hi Darrin,
Thank you for the suggestion. Calling -[FxCustomParameterActionAPI_v4
startAction:] does indeed allow for subsequent FxParameterRetrievalAPI_v6 ptr
to be obtained and used. However it still does not work quite right.
First, a call to [actionAPI currentTime] seem to deadlock in this selector.
This is not a big deal for us as our plug-in's parameters are not
interpolatable, but you might still want to have a look. I am using
CMTimeMake(0, 1) instead in all subsequent calls to param retrieval and param
set APIs (might this be the cause of the second problem below?).
Second, the param retrieaval API seems to always return the default values of
the parameter. The values are changed (to non-default ones) via
FxParameterSettingAPI_v5 in the same selector after the dialog is closed,
however when I press the button again, the values returned by
FxParameterRetrievalAPI_v6 are all reset to defaults. I have tried this with a
simple integer parameter as well as with our custom one, the result is always
the same. I do call [actionAPI endAction] after changing the values. What am I
doing wrong?
Best regards,
Sergey
On 28/05/2020 8:41 am, Darrin Cardani wrote:
Sergey,
Regarding the second one, you should be able to access parameters in your
custom button handler by calling -[FxCustomParameterActionAPI_v4 startAction:]
to access the parameter API first. Let me know if that solves the problem for
you.
Darrin
On May 24, 2020, at 7:29 PM, Sergey via Pro-apps-dev
<email@hidden> wrote:
Hi Darrin,
I've submitted FB7713563 and FB7713555. Please have a look and let me know
should more information be required. We are open for discussion on the
available solutions.
Best regards,
Sergey
On 21/05/2020 2:00 am, Darrin Cardani wrote:
Please file a feedback request for such an API and we will take it into
consideration.
Darrin
On May 19, 2020, at 6:27 PM, Sergey via Pro-apps-dev
<email@hidden> wrote:
Hi Darrin,
Is there a chance of such API being re-implemented in the next versions?
For now the only option I see is to split the setup process into two phases: to create a
kind of "Prepare" button that will trigger a hidden parameter change and
re-render, then inside the render the frames would be cached and finally yet another
button to open the actual dialog with the frames cached on previous step. This can be
implemented, but it looks like a regression compared to FxPlug 2.x.
Best regards,
Sergey
On 20/05/2020 7:07 am, Darrin Cardani wrote:
We don’t yet have a shipping solution for this use case at this time.
Darrin
On May 17, 2020, at 7:44 PM, Sergey via Pro-apps-dev
<email@hidden> wrote:
Good day pro-apps-dev,
In previous versions of FxPlug our plugin relied on FxTemporalImageAPI to get
series of frames around current time position to display (and process) in our
custom dialog (triggered by a Push Button). We need to retrieve 7 consecutive
frames before and after the current one.
Now that FxTemporalImageAPI is gone how the same can be achieved?
Best regards,
Sergey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden