We've noticed errors when using AMT if the MOB IDs don't follow the proper format.  For example, if we set it to 'test' instead of something like '060a2b340101010101010f0013-000000-4fd6340fea6337e1-060e2b347f7e-2a81'.

We'd like to do some validation of these values before passing them to the AMT SDK.

Is there a description of the string format for MOB IDs we could use to perform such validation?

Hi Simon,

MobIDs follow a specific narrowly defined format and are generally UMIDs as defined by SMPTE 330:2011. You should not have to create them yourself, the AMT SDK will do this for you you unless you override this mechanism by specifically providing MobIDs (which is only meant to be used in very specific cases where typically it was also AMT that has generated a MobID). AMT's Mob ID generation follows the algorithm defined in Annex A of SMPTE 330:2011.

Hi, 

In AMT3, I dont see any MobIds generation function (AMT2 GetMobIDs equivalent).

Any idea ?

Gregor 

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>: MediaParameters::physicalSourceMobID

If you omit those arguments, AMT3/MP will create the MobIDs for you.

If you want to create MobIDs for later explict use, AMT3/MP also has a function for this. Check out ~\include\MediaProcessor\Core\UMID.h, there is a UMID class with a create() call that will return a value that can be used as a valid MobID.

Thanks a lot, Andy.

We're going to try that ASAP.