Quantcast
Channel: Adobe Community : Popular Discussions - Premiere Pro SDK
Viewing all articles
Browse latest Browse all 53010

Exporter API - neccesary re-init?

$
0
0

Hi all,

 

I took Zac's exporter example and moved the Parameter|Value from being locals in eSDKDefaultParameters() and put them into the (per Instance) ExportSettings struct so that I could manipulate them again in eSDKValidateParameters().

 

Is it really necessary to set all the [value[.rangeMin|Max], .value.*, etc etc again in eSDKPostProcessing(). From what I can see in the debug watch there is no corruption of any of it from its initialization in eSDKDefaultParameters().

 

I've also noticed that no matter what I set in eSDKDefault* and eSDKPostProcess() for a values of some parameters they always come up as the first entry (be it radio button or dropbox).

 

I deleted the .epr in the /User/[Username]/AppData/Roaming/Adobe/Adobe Media Encoder/4.0/ but it STILL comes in as the first entry.

Is there some other cache floating around?

 

I guess it doesn't matter in the long run because you ship presets with an Exporter but it sure is bugging me from a coding standpoint.

 

PS: this is with SDK CS4 on AME CS4.

- In my next post I'll follow on from an old question on the MemorySuite coz I can't get CS5 SDK to work on AME CS4.


Viewing all articles
Browse latest Browse all 53010

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>