JakaBac and omsupport, we actually tried to ensure the wording was accurate before posting to the forum. Let me reinforce that you should not attempt to have more than _one_ session running at the same time per _process_, ie executable. AMT is not designed to support concurrent operations that require multiple sessions. Ignoring this recommendation

Hi omsupport, even though is mainly a forum for supporting Interplay Web Services, to avoid misunderstandings let me point out that you cannot have multiple concurrent AMT sessions in the same process . A session in this context means an object of type amtSession_t; having more than one in a single executable means calling for trouble. Hope this helps

EndOfTape, From an Interplay Production perspective, rendered effects are in some aspects different from 'normal' media files. Can you give us some details about the use case you would expect to support with your request?

Hi danstone, no problem, depending on the operation there are many path forms which can be confusing. The reason that you can use a mobid (only) for setting a headframe is that the headframe is 'global' for all database assets, so the target of the operation is unambiguously identified by a mob id. In the case of deletion, this is not the case

Danstone, from the IP WS documentation: The DeleteAssetsType XML type defines the parameters passed in to the DeleteAssets operation. The first required parameter is a list of Interplay URIs representing the assets to be deleted. These must be path-based URIs , since deleting by mob ID only is not allowed. For each Interplay URI that does not reference

Jaka, when using this call, both referenced arguments should be set to NULL or 0 for normal use cases; this will tell AMT to allocate memory for the mob ID list. If something other than NULL is passed in for mob_id_list then this needs to reference a valid mob_id_list which will then be modified. For the purpose of this call, mob_id_count should always

That would be your choice - whatever you consider appropriate for your integration; this headframe will be shown in the Interplay clients and should probably contain something that allows the user to clearly identify the asset. Technically the headframe should be a 400x300 pixel image in one of the supported formats listed in the documentation. From

For many codec formats, AMT supports extraction if single frames from clips; Avid uses this feature internally for implementing head frame generation in some products. Recent AMT releases contain code changes to fully support this use case. Implementation of head frame generation is straightforward for I-frame media; for LongGOP formats implementation