Question about Transmitter plugin

[Andy Hwang]

Hi Aodbe

I am testing the transmitter plug-in among the plug-in example sources.

If you look at the Adobe premiere sdk document, it says that the Startup function is called to start the plug-in, and Shutdown is called to release the plugin.

But shotdown function of the transmitter plug-in is not called.

When developing a transmitter plugin, is there a function that needs to be additionally set or called so that the shutdown function is called?

Or do you need to change any settings in Premiere Pro?

Please tell me what I should do.

Thanks.!!

Best Regards,

Andy Hwang

[Bruce Bullis · Accepted solution]

To get sent Shutdown, the transmitter must have allocated memory during Startup.

[Andy Hwang]

What do you mean by Memory?

Do you mean ioPrivatePluginData in tmStdParams?

ioPrivatePluginData is the same as provided in the original sample. New TransmitPlugin class and put it in ioPrivatePluginData.

[source code]

static tmResult Startup(

       tmStdParms* ioStdParms,

       tmPluginInfo* outPluginInfo)

{

     ioStdParms->ioPrivatePluginData = (void*)new TransmitPlugin(ioStdParms, outPluginInfo);

     return tmResult_Success;

}

Please tell me what I should do.

[BillClag]

I have the same issue and I am allocating memory during Startup. 

[Andy Hwang]

I'm creating a plugin for the first time and need help.

How do you allocate memory?

[BillClag]

I tried allocating memory every which way in the constructor(TransmitPlugin::TransmitPlugin()) setting the three places in ioStdParms->  and still no call back in the destructor (TransmitPlugin::~TransmitPlugin()). The destructor never gets called. How do we fix this?

[Andy Hwang]

With two Sequences loaded in the timeline, I was able to confirm that the TransmitPlugin destructor is called when I select the first and second Sequences one by one.

However, when Premiere exits, the destructor is still not called.

I've contacted Adobe about this and am awaiting a response.

Hope this helps

[Bruce Bullis]

We haven't forgotten your enquiry; just trying to determine what 'recommended behavior' is. 🙂

[BillClag]

Any news or updates?

[Bruce Bullis]

None so far.

[BillClag]

Any news or updates?

[Bruce Bullis]

Update: I'm unable to convince PPro to send the Transmitter sample anything like a Shutdown call. 

I suspect this change may have been made during PPro's "Faster shutdown" work, a few years ago; I've asked all available sources of lore, for specifics around this change; will update the docs accordingly. 

[BillClag]

Please let us know as any information is available at all. This is a show stopper for us. Thanks. 

[BillClag]

Any news yet? Please let us know as any information is available at all. This is a show stopper for us. Thanks.

[Bruce Bullis]

I believe you, and...

How is the inability to know when to properly release memory, a showstopper for you?

[BillClag]

I have to launch a separate process to encode and send the encoded video and delayed audio with proper timing. This external process also offloads (to separate cores) much burden to Premiere for the stuff Premiere needs to do. I need to kill this process when Premiere exits. That's why I need the exit callback. 

[Bruce Bullis]

Understood. 
For now, you may be better off with a "I haven't heard from the plugin in N seconds, so it's time to kill this process" approach. 

[BillClag]

Hi Bruce.

This won’t work for me as my plug-in handshakes with Premiere and if my app quits wrongly then Premiere hangs.

My solution is to send the process ID for Premiere to my application and then check it periodically for exit code.

The exit code I get from Premiere is  0XCCCCCCCC 

Please verify that this exit code is set in stone.

[Bruce Bullis]

We can't promise that PPro will never send a different exit code, but if your testing has shown that to be the common value, that sounds like a workable approach.

[BillClag]

Of course. Thanks.