6
Argus Encoder Family Version 2.6 API Developer’s Guide
Argus Features
• In the
OnError()
event handler, we added the line:
pView->m_bErrorFlag = true;
to replace the earlier code (shown on next page):
if(bErrorFlag)
*bErrorFlag = true;
This change guarantees that all of the components will reset before the next cue if
the previous encode failed.
Changes made in version 2.4 to our C++ sample application include:
• We removed the
MessageBox()
calls from the
OnLog()
and
OnError()
event
handlers, since they tend to lock up the encoder.
• We enable the reset button when the encoder falls into an error state.
• There is a boolean property exposed by the Filter Manager interface called
Transcode
. Because the transcoding process is not currently supported, you
should not use the
PutTranscode()
method except to set the property to zero.
• Note that you should remove the
VTRDisconnect()
method from the error-
event and finished-event handler of your client application.
Version 2.3 changes included the following:
• Most of the properties exposed by FilterManager can now alternatively be
set using the Windows Registry. We recommend that you use the Registry
settings instead of the property
Put
and
Get
methods, which will be removed
in future interfaces. Refer to Appendices A and B for complete listings and
descriptions of Argus Registry settings.
• Similarly, the properties that were once defined in ArgusConfig.txt (using
the CFInterface application) are now set using the Windows Registry.
• A number of database-related methods were added to the FilterManager
interface so that it can be used by our standard Argus application, EDL
Editor. As a result of these interface changes, you no longer need to register
a separate set of COM components in order to run EDL Editor. Additionally,
when you encode using EDL Editor, you'll see that it creates and updates
Windows Registry tables identical to those used by the sample application
that we provide with the SDK. These changes should make it easier for you
to compare the functionality of your application with that of our standard
application, a definite advantage in debugging.
Please do not use the new
database-related methods in your application, as they will not be supported
in future releases.
• For easier debugging, the list of defined error codes has been expanded and