Was there ever any answer on if this was fixed in a later SDK?
Export Controller exports honor the settings in the .epr file; If the output preset specifies drop-frame timecode, it'll produce drop-frame timecode. If you can reliably reproduce a counter-case, please file a bug.
I also meet the same problem.
I have created a 'Export Controller' plug-in. when export media using this plug-in, and choose the preset 'DV 25 NTSC', MXF OP1a.
Confirm that sequence setting is 29.97 drop-frame.
But export mxf file is always NDF.
However, using Export->Media, and choose MXF OP1a + DV 25 NTSC, will export DF mxf file.
Could you help to double check it?
I have check from code, it will get correct result (DF or NDF) after call function 'GetTimecodeDropFrame' in 'Sequence Info Suite' , so what's the problem would be?
The output timecode format is determined by the output preset settings, not the sequence settings.
If either of you can provide an .epr file (output preset) targeting a format using drop-frame timecode, which produces NON-drop-frame timecode when rendered, we'd really like to see that .epr file.
Do you mean when we use the menu 'Export->Media', it will load some sequence setting into .epr file, because for export 'DV 25 NTSC' mxf file, I think it is using the same system preset file 'DV 25 NTSC.epr' no matter it is DF or NDF.
However in my export controller plug-in, I missing the operate that overwrite some parameter in preset file to reflect the sequence setting like DF or In\Out position ?
If yes, is there any document to introduce the preset file structure or parameter?
(Additional, in my plug-in, I am using system preset that locate at Premiere Pro CC 2014.app\MediaIO\systempresets\58444341_4d584658\DV 25 NTSC.epr)
I understand your question now.
There is no API for Export Controllers to intercept or modify the render parameters, contained in the used .epr file.