Hello everyone in this video I I will walk you through the file ingest and delivery workflow with e-mail and Moog.
Similar to the capture workflow, the configurations has to start from the storage configuration.
If it is already configured for the capture workflow, we can use the same storage configuration for Emma or if you have a multiple storages that configuration also can be done at here.
And then when it comes to the delivery.
So if you have a separate delivery destinations like South Three or Avid Unity, that configuration also can be done it from here.
For the delivery and ingest, the storage configuration can be done it from here.
And then for the transcode workflow, we don't need the asset management and locators configuration because that is only applicable for the capture workflow.
Then the input output, I don't think so any configurations are required here too because we are not doing any input like a stream or anything.
So then we can directly go to the workflows.
But the metadata profiles is important here.
So similar to the capture profile, we we did a destination profile and this is to create the naming template.
And there is no need of custom metadata to be handed here because this is going to be automated.
The ingest and delivery operations are completely automated and managed by IMAP, but you need a metadata profile to create a naming template.
You go back here and go to the workflows and then create the naming template and that is where you create a different naming template for the the transcode workflows and then you select the destination profile.
Then you assign the destination file name as the parameter and in this case EMAM.
EMAM is actually passing the value to this metadata field to create the destination file name.
In that way EMAM can control the the destination UUID file name.
If it is a ingest workflow, the destination file name will be UUID.
If it is a delivery workflow, that will be the the file name or what the template delivery name template configured in will be passed to the the MOG.
So once the metadata naming templates are configured, you can go ahead and create a workflow profiles.
In this case I have a workflow to create the proxy.
In this case, my operation is ingest, it is a capture, it is a record.
If the operation is ingest and the higher US, I'm not selecting anything because I don't need to create another higher US and I just always create a proxy.
In this case I I don't have the high risk configuration but just the proxy configuration.
And this base path slash proxy is the path configured in the IMAP super admin because that is our proxy.
So that is a proxy configuration and then clip naming the destination file name is there.
Metadata is not critical here.
And also there is no need of asset management configuration here because it's a managed workflow, the only difference between an ingest and delivery workflow.
For the ingest workflow we are just creating only the proxies and as of now I'll be tested only one proxy.
If you need to create multiple proxies it will be multiple like renditions like multiple work flows to create different proxies and that can be configured in IMAP.
Then for the delivery workflow in this case is IMAP delivery to Avid.
So my output instead of proxy I'm I'm using the higher as as the output in this case DNX, ABID, DNX HD or an OP atom.
So that is the base path for the ABID destination.
So, so that is the fundamental difference between the delivery profile and the ingest profile.
Then for the ingest profile, if you look closely, this is the workflow ID which is highlighted here.
And now if you go to the delivery, that is the workflow ID for the delivery that that workflow profile.
So the remaining configuration is in e-mail.
So for that you have to go to the IMAM super admin, go to the interest profiles.
First you create the MOG encoder as the France code server.
So we have introduced the transcoder type here, the MOG encoder that's available as a drop down that will give additional option to enter the Restful API URL for the MOG encoder or MOG for for pro or whatever product right.
So then the username and password to communicate with that API.
So that is a basic configuration.
Once the server is configured, we can go ahead and create the ingest profiles.
So in this case I am using the manage transcode using the IMAP interest manager and there is a storage config that is available in the storage tab.
It's same thing.
And the transcode server is MOG encoder that is the one I created here.
And then this is the destination path.
So this much is that base path configured in MOG.
And then there is a watch folder for EMA and then in the advanced settings that is where you put the workflow ID.
So if you go to the face this is the workflow ID CB 404 4:00.
So that is a CB 404 that's a complete workflow ID.
And if I if I need to create multiple renditions, I have to create separate separate workflows for each format and then I can edit it and put that workflow ID here to create multiple renditions.
Remaining configurations are like same like the main change.
We have introduced MOG encoder as a drop down in our ingest servers.
So how this works?
So you go to the system.
Now the system is in Portugal, so I'm going to upload something from my workstation in New Jersey.
So there is a geographical latency, but let me try.
I'm just going to drag and drop something to the UI and selecting that interest profile.
A connection is good showing green and I'm going to select test as the category destination.
I'm going to hit upload.
So the upload is progressing.
So once the upload is completed, so you can track that from the dashboard, it's uploading and it is added and now it is queued and it is processing and the job is submitted to MOOC to create the the proxy so that you can track it from the the dashboard to in this case, I think the job is completed and we refresh it here.
Yeah, the job is completed.
And if I go back here, So yeah, that is the video I just ingested and and then the similar configuration for the delivery.
So the delivery also we have the same transcode server configured, it is available for delivery and then if you create a delivery profile, you can export to Avid, export MXF and XML, export MOV.
You need to export to Avid, select the transcode delivery, then Moog encoder as the destination transcoder and then the workflow ID.
So let me cross check the workflow ID.
So this go to the workflow profiles even deliver it to Avid that is 70C77 starting with the workflow ID, starting with the 70C77 just copy that in their workflow ID and place it here the 70C77 and so on and then the destination file name.
So this is what I was telling Imam is managing that workflow and passing this file name to the metadata field and then there is a destination.
So the workflow is similar, you just go to the delivery, drag and drop my GoPro clip to that one which I just uploaded and click on deliver and export to Avid.
On add it will create a delivery job and it is and it will be picked up by the delivery service.
Again, it's a standard process, so it is processing and the job is submitted to the book.
And again, you can track from the dashboard here in this case Imam delivery to Avid, the progress is 100 percentage and the Adobe is disappeared from here.
And the my GoPro clip in MP4 is delivered to Avid in MX of OP Atom.
So that's a delivery workflow.
So there are more options for delivery which that can be explored or it can you can consult with the MOG team to create different delivery profiles to deliver the media to the social media platforms and to the OTT.
So those all Oregon options are there.
But for IMAM, the configuration is just the workflow from here and the remaining configurations can be here to send it to the OTT and social media platforms and so on.
Thank you.
Thanks for watching.