in imGetPrefs8 why don't you check for privateInstance == NULL then create as needed.
If != NULL call your modification function.
imGetInfo89 should only populate the selector struct with info from the private data (already allocated by imGetPrefs8).
I've never looked at the synthetic importer example but this is exactly what you're doing so that should be your starting code to hack on.
The private data (instance data) pointer has to be allocated in imGetInfo and not imGetPrefs.
The pointer which is allocated in inGetInfo is only received in imImportImage not which is allocated in imGetPrefs.
1 person found this helpful
Agreed, it is not ideal that imGetInfo8 is not called (bug # 3010899). Would you be able to workaround it by checking some basic attributes in imImportImage (perhaps by making some comparisons with the prefs) to make sure that your custom class in privateData is up-to-date? If the class is out-of-date, you could modify it before returning from imImportImage.
Any progress on bug #3010899?
Yes, this bug was fixed in the 2014 release of Premiere Pro CC.
Thanks, Zac. I've noticed that with PPro CC 2015, imGetInfo8 is not called following an "edit" via imGetPrefs8.
Have you tried to reproduce the behavior using the Synth_Import or SDK_Custom_Import samples? I'm not able to reproduce the problem with either sample in CC 2015.
Related to the modification query we initially raised, We checked with Premiere Pro CC2015, that after GetPrefs, GetInfo, imCloseFile
is also called which actually closes the instance.
I checked it with the sample SDK_Custom_Import also.
The sample also crashes Premeire, the second time I modify.