Hello Valentin, this was a Linux specific issue which has been fixed in version AMT-3.15.0-linux-CentOS-7.3-x86_64-5.1.0.10089. Filename generation is supposed to be random.

Hi Simon, I am missing a little bit of context here (what are you feeding and what are you trying to do?) so assuming that what you want to do is to write XDCAM HD 50 progressive , 25fps from the frame based interface? Just to confirm upfront that this operating point exists and is supported. Remember there is no 50 for 59.94 1080p in the XDCAM format

Hi Simon, We intentionally do not expose the ability to specify a file name. In an AAF-based workgroup environment file names do have a special meaning and the naming algorithm is designed to avoid naming collisions. Can you elaborate on why you have a need for naming files explicitly?

Hi Valentin, sorry if I wasn't clear. We do not have a CTMS notifier yet since the ability to check in AAFs through CTMS became available only recently. Currently your only option is a IPWS (web services) notifier. Hope this helps Andy

Hi ValentinDesplanque, Re 1: When configured for EWC support, AMT3 handles EWC AAF check-in for you. AAFs will be provided as soon as they are available to minimze latency. The notification mechanism currently supports Interplay Web Services (IPWS); just configure an IPWS end point and the check-in frequency and everything should be automatic from there

Hi Grégoire, sorry for taking a while to come up with a reply. It looks like you have run into the following issue [MPI-29483] Updated MediaProcessor to close input sample-based sinks when error occurs on performing job which is already fixed but not yet released as AMT3. We'll have that version coming soon. What you can do on your side as

Hi Grégoire, sorry for taking a while to come up with a reply. It looks like you have run into the following issue [MPI-29483] Updated MediaProcessor to close input sample-based sinks when error occurs on performing job which is already fixed but not yet released as AMT3. We'll have that version coming soon. What you can do on your side as

Hi Gregor, we are reviewing your question and agree that we need to improve our documentation here. Upfront, here are the definitions of the different enums: kCT_Invalid, kCT_8Bit, // 8 bits per component, no padding kCT_USHORT_4_12, // Unsigned short with 12 LSB bits carrying sample information kCT_USHORT_12_4, // Unsigned short with 12 MSB bits carrying

Hi Gregor, in many calls where MobIDs are required you can simply omit the mobid parameter and AMT3/MediaProcessor will generate one for you. That's for example the case in the demos where you can optionally specify MobIDs using command line arguments: -mmid <MasterMob ID>: MediaParameters::masterMobID -psmid <Physical SourceMob ID>

Rich, we'll be looking into this in one of our upcoming sprints. This is an external dependency.