Hello, and welcome to the Avid workflows with EMAM and an ELT
webinar.
My name is Chuck Belo. I'm the VP of business development here at EMAM. Joining us today is Anoop Thomas, director of technologies at EMEM, and Jim McCain, president of Enel Technologies.
In today's webinar, we'll be discussing the new integration with NLT near archive
and media transcoder platform, creating a seamless media and metadata workflow
with Avid interplay in Avid Inews.
EMAM has entered into a strategic partnership with NL Technologies
to advance and enhance
the Avid workflows in EMAM.
EMAM is a media asset management software that helps centralize,
organize, share, and distribute all types of media and metadata.
This new integration helps streamline
and sharing of media and metadata
between EMAM and the Avid platform.
Anoop Thomas will now talk about the integration in more detail.
Thank you, Chuck.
With the integrated system,
we can index media and metadata from Interplay into EMA.
Once the media is indexed,
users can browse the avid op atom media directly from the
Imab interface
and trigger the wrap or transcode
options,
from the Imab user interface.
Ima can also
share and distribute
the media to s three buckets,
network locations, and other systems like a premier and, Resolve.
Another workflow is to ingest or check-in the known avid media
to interplay.
To transfer media and metadata from the avid environment,
we use, NLT NeoRK
as the middleware.
Nlt is capable of,
scanning stories from INUs
and processing the associated media, Not not just
interfacing with interplay. It can also interface with INews.
Here is a high level diagram showing the flow.
Imam receives the metadata XML, the original media, h 2 26 or m p 4 proxies,
and a thumbnail
from NLT archive.
Then imam creates the asset
based on the information
provided in the XML.
In the reverse workflow,
Imam hand over the media to the NLP media transcoder.
That is a separate product from NLP,
which then, check-in the media to interplay.
If the assertive
assertive memory originated from the Avid environment,
we retain the mobility in the system.
For node Avid media, like camera, raw, pro ras, etcetera,
this process involves
transcoding
to create a mix of, obi atom media.
Now we will demo the product features from this lab setup.
We have, Imaam running from an EC two instance in Mumbai
and the Imam app node running from a physical server in the NLT lab in Boston.
Additionally,
we have Interplay, Inews,
Avid storage,
NLP media transcoder,
and EMAM storage, which is a NELS
running from the Boston office.
I will now invite Jim to demonstrate,
NLT, New Archive, and Media Transcoder
and their integration with
Avid Interplay, Inews, and MediaCentral.
After that, I will showcase the IMAM interface.
Jim,
the floor is, yours.
K. Can you see the,
EMR screen?
Yes. We can.
So this is interplay access. So this is an avid tool.
You may or may not be familiar with it.
We have some clips in here, and we can just select a couple clips
and right click, and we should have the plug in. So this is an extension to the right click menu in the Avid tools.
We use the Avid tools for the interface to the user.
So the customer is already familiar with these tools.
And, to access our archive, we simply enhance the right click to allow that.
So there are 2 entries,
the services and the management console.
So I'm gonna start with the services. What it does is it says, okay. You've selected 2 assets
and you wanna go to a target server, so we're gonna select this one to begin with.
Yeah. Let's do that one.
So this stores
the content or we can restore the content. So if these were offline, we could restore from the archive and bring the content back online.
In this case, we're gonna store it, so I'll just put a little comment down
here,
and we hit okay. So this should send a job to the
to the,
Nere archive engine that's running, and it would be processed and,
and retrieved.
Now the the management
is a web interface,
and the management interface should show you the,
the job interfaces.
And I gotta get to a proceed
unsafe state.
So these are the jobs on this particular server that were submitted,
And you can see that this was a restore operation,
and the master clip was partially restored,
and the sub clip was restored. So this is a partial file restore operation.
But, basically, when you submit a job, the near archive engine picks it up and performs the operation whether it's either gonna store content
to the external storage via NAS or something like that or restore content from the external storage back into interplay.
So this is kind of the job interface. So after you submit a job to it, this is where you would see the status.
So once the content is written there
now we had,
some demo clips on here
on the
e drive, I believe.
So these files are written
to a folder structure,
And the folder structure is what Anup
has picked up, and he's picked up the the data portions, the MXF files,
and the XML files.
And so this is the XML file that you're importing,
and it contains all of the metadata that we've taken out of interplay.
So this is all the media files, the formats, their locations,
all the metadata that describes the asset, all of the,
durations, creation dates, basically, everything that's in interplay.
The associations
to sequences,
all of that is in this XML file.
So NUP has taken this and imported it into EMAM that can describe that asset. Basically read the o p Adams and I think are making an
o p one a
and maybe using this MP 4 file, which is a proxy video of the asset
and putting that into EMA.
So this is the system configurations,
and these are pretty much static configurations that a system manager would set up.
But one of the options is integration into,
Inews.
And the the Inews server
has a portal that uses the inews web services, which is a kind of a third party definition
for how to access it. And so those web services are running on this computer on this particular port,
and we can test that and we can okay. We can talk to the web services.
And then
to talk to the Inews server itself,
we pass the host name through the web services.
So there's like a double hop going on here. So when we test this integration,
okay, it's able to talk to the Inews. It's got its IP back
and everything passed.
So what we've done is once the configuration
is set up that you can talk to Inews, you can actually go out here
and look at all of the inews,
folders and queues.
So
here we have wires.
I think I've been playing around with the
show, I believe.
And I've made a a folder called emam demo,
and here are 2 different,
queues with, I've been trying to get some stories in them.
But we can select this whole folder,
or I've already selected
the 5 o'clock and the 11 o'clock,
rundown queues.
So
you can select them individually, or you can select the whole,
the whole folders worth of rundown queues.
And you can go down here and enable the different metadata that's gonna come out of
Inews as well. So we can import the story ID, the slug, the date, the book. The story body is important.
So all of the content that's put into Inews as far as the story description,
we can pull that out and and archive that as well.
So once this is all configured,
you set up different,
schedules. So I can say, okay. At
7 PM, I want to
you know, on a Sunday or maybe every day I wanna do this,
I set up a a time where I want to query the INews server.
So anything that's changed since the last time this is run,
then we can set up another query for
midnight if we wanted to.
So this query would run at midnight. This would run at 7 PM,
and,
it would take any changes that were made in Inews from the last time it ran
based on
the folders and queues that you have selected and the metadata that you wanna pull out. So again, this is set up pretty statically.
Once you have the the shows and the queues defined and the metadata defined with the schedule,
the Nearxive server just automatically
goes out based on that schedule and queries inews,
pulls the content back. Well, basically, it creates a job just like you manually we manually selected a couple of assets and said, send these to the archive.
It would go out and query inews and create a job that would just
execute.
So that would store all of the content that it found that it changed since the last time.
And so that's that's kind of the definition.
The user would use the Inews client.
It's already running. So inews clients, the user would use the inews client. For example,
these are the the stories that I've been working on.
And so a customer would use this this interface to build the stories
that then we we would archive once they ran.
And so that's that's kind of what's going on with Inews.
We have a,
another integration with Media Central. I showed you Interplay Access, and I've showed you using Chrome as a just a browser to access
the status of what's going on with
in the archive,
application,
but we've also integrated into
MediaCentral.
And this integration provides more of an integrated approach
to,
managing all of that put together. So we can navigate to catalogs.
Go back to Emory, and we could right click
and go to the near archive services. Again, this is all integrated in here, so I could send this to
different servers.
But the the web interface is up here,
so we can go and let's pick red and see because the other one's not working.
We can see an integrated approach. So everything is presented
to the user right here.
So I can I can have a browsing with catalogs, or I can I can look at my different jobs
and see what's going on?
And so that's the integration with MediaCentral.
We've again implemented that right click with the browsing feature,
and we've integrated
an application that lets us query the web server that's running on the Mirkiv server to say, what's going on? I've submitted some some assets to be archived and restored.
This is the progress of what's going on. Were there any errors? Is it still right into tape? It'll show you all that information.
So again, all these settings are
are kind of system management level
configurations.
The user would not be in any of this.
This is where the,
the integration into Avid Web Services and then this is the Avid storage. So the host name of the Avid storage, the workspace.
So that this is basically
defining
a place where we can restore content
if the original workspace no longer exists.
So think of this as an archive and workspace names in the Avid environment can change based upon
system managers changing roles or whatever. Maybe they've got a a new piece of hardware they they brought in, and they've developed
a different workspace name. Well, when we archive content, we save the original
workspace that it came from. So we always try to restore it
exactly where it came from. But if that workspace is not available,
this definition provides a current
alternate location where it would be restored to if the original
no longer existed,
or you notice there's a restore overbite
override button.
In that case, any restores, we would use these paths to restore the high revs or proxy
to a given workspace.
That's the integration here.
And, in this case,
instead of
sending the file to LTO,
the new archive is placing the files in that, e tribe.
That that that can be the NAS and, or any other shared storage location.
So we built the integration at that level.
So we look for that location. It's configured here
periodically.
And if there is a change, if there is a new XML percent,
we take that one. And then,
at that point, we are actually not doing any transcoding or anything. We just index the media. Like, we index the OP atom media,
enema,
and,
then,
we use that proxy provided by again, there is a proxy file and the thumbnail provided by the archive.
So we load that proxy into EIMA, and that proxy goes to the cloud.
And from there, you can directly access that location, that e New York cave location,
from the browse interface, IMAM browse interface,
and then you can trigger the delivery. So if you do trigger the delivery,
at that time, we do a wrap job and wrap it as o p one a and,
send it to the
other systems, like external systems other than that of it. Then the opposite workflow,
suppose if there is a GoPro footages or files are coming from other system like the ENBS or Octopus or whatever other new systems or other sources,
we send that media to,
the media transcoder. That's a separate product. And then the media transcoder can check-in that too, the, the avid bandwidth.
So if we're just gonna receive an an o p one a type file, what we have is a
a watch folder that's designed
to just read 0 p one a media and rewrap it, which happens very, very fast.
So we have a watch folder that we've defined
on either a network share or a local drive,
and then we've defined
where we want the content to go on the Avid side. So the o p Adams are placed in this folder,
and then a check-in folder where we've defined the,
where the media is gonna be checked into. And if we wanna change that folder, we can
just select a different folder. So all of this is coming right out of,
the interplay database in real time.
So we can select a different target. We can create a new folder for a target.
But this is the check-in folder. This is where the storage is
defined for the 0pone
opatom,
and this is the watch folder where the 0poneas
would be dropped.
And we also have another another watch folder where we can take,
GoPro or MP 4 files or what have you. It's a very similar,
type of definition,
except that it has the capability
to,
not only,
watch for a folder, but to transcode it to a specific target.
So if it comes in h 260 4 in an m t s or m p 4 file,
we can say, okay. Well, the house format is xdcam 50,
and we're gonna create XDCAM 50 media from that original source
and put it in the respective
check-in and storage locations
on the Avid storage LAN.
So there's a couple of different ones that we have defined here.
We have the capability to find
multiple workflow engines to have
different watch folders. So you could have one for sports that went into a a sports ingest. You could have one for, you know, dailies. You could have one for news. You could
basically design
as many of these as you wanted to have.
K. So then, let me take out and show the,
the the view from the imam side. Give me one second.
Okay.
Here's the IMAM,
director interface.
In the browse widget,
there are options,
available to browse
different storage types.
As we are
indexing
the media from the Avid environment,
the storage will be listed
under the,
source storage.
When I go to
NLT, this is something I
am browsing,
NLP storage.
I can go to assets, maybe 400.
And then I can I can see an asset,
inside that location?
So in this case, I'm previewing the h two six or m b 4 proxy video,
that exist in the s three bucket in Mumbai. And, also, I'm,
getting the thumbnail
from the,
NLT environment. But the original media that exist in this,
NAMS location in Boston.
Let me connect to the,
TeamViewer.
So now I'm I'm in the,
the TeamViewer connect connected to the app node in Boston.
So let me go to the,
this location.
And,
so again, this is that NAS. So I'm just browsing that NAS storage.
I said it's,
4 100.
And,
Yeah. The
these, location, the files are like this one. There are,
multiple MXO files,
XML files and so on. But we are mainly scanning this folder
and indexing that in the EMAPS system.
So if you look at this XML, there is,
the name of the file coming in,
the interplay source path, and all other informations are there, locators, and all other information.
We are taking from this XML, like modify date and, the master clip details, the
the mobile ID, and all those things we are taking from this XML.
And,
showing that in the,
the EMAP system. So if you look at the metadata,
so there is,
basic metadata. This whole information is coming from that XML. There are embedded metadata. As you can see, this is an OP atom,
a mixer file, exist in that location.
And,
and then there is also
added related metadata like the mobile ID and source mobile ID and so on, and also the file path. The locators are coming from that system, from interplay.
That existed the, the storage in Boston.
And another view, let me, quickly go to the,
again, now I'm in the app node in Boston. So let me just, sign in to the MediaCentral.
So, again, there is option to sign in to the MediaCentral
or,
the interplay.
So you can
see from here. So there is, catalogs,
gym,
demo.
All those things are there. Right? The xdcam 1080.
So all these,
details are available here. And, of course, you can browse the same thing through,
here.
And,
that that information is available here too. So now if you look at EMA,
we have the the same structure. So if you let me just maybe go to the the search filter. Let me close the project.
Tuberies,
catalogues,
gym.
See that that entire structure
is available in Imams. So if you click on here,
so you can see the,
the same
view,
here too. Like,
so there is a
again, I can adjust the sort option,
all those things here. And that's the identical view,
but you can see it in
in the,
interplay. So if you,
do a side to side comparison,
so this is
very identical.
So that means we we are indexing all the media. And,
in this case, both in interplay is pointing to the media in Boston and,
what what I am seeing in the IMAP interface is just a a proxy
that is also pointing to the the media,
in Boston.
So now if you will if I need to trigger a delivery workflow, I can change my
workspace here.
So I can select,
maybe one of these,
files from here.
Okay. Let me go to
one of these files from this location.
And then I can just,
drag and drop that into my delivery.
And,
so then I have multiple options. Like, I I either I can,
wrap everything to an OP one a, like, consolidate
that, OP atom into OP one a. Or I can transcode and create that XDCAM 50 or or or some kind of a destination format.
And I'm going to add that to the,
the delivery
queue. So in this case, if I go to my dashboard,
so there is one item queued and that is processing.
So now the app node in,
Boston is going to pick up that job,
and it's going to deliver that file to this, this folder, the delivery. As you can see, the the file is appeared here,
and, it is creating new files.
And,
so that
file if you look at the media info,
this one is a wrapped file. It's a consolidated
OP 1 a mix
of with,
multiple
audio tracks. Like, there is a audio track 1, audio track 2,
3, 4, 5, 6, 7, 8, and so on. So that is a consolidated
file. So in this way, we can take
an avid op atom file
and consolidate our transcode
and, push that to, other locations. So this is, again, a distributed hybrid architecture,
managing that delivery workflow from a web user interface.
The actual job is carried out by the the app node,
running here. That app node is, again, we got a lot of background services for managing the ingest,
the
cloud connectors,
the delivery manager,
and the archive manager,
and, Adra's task manager,
and so on.
So then the
reverse workflow,
suppose if I have, the,
the Imav system,
and I have the,
the files
maybe in the an s three bucket or other location. These are the non Avid Media.
So these files may be,
coming from,
camera
or,
GoPro or some other sources.
Let me go back to the cloud storage again.
Okay. So now if I need to send this media
to Interplay, what I should do? So I can track and drop the similar it's a similar workflow, but, earlier,
I delivered a media from the interplay to the ex the other network, storage location.
In this case, I'm delivering a media that exists in s 3,
to the,
interplay.
And, so in this case, I'm going to,
trigger the delivery. Okay. Before triggering the delivery, let me just show you what is going to happen behind the
scenes. So,
the app node,
is going to pick up that job,
and,
then
it hand over that file
to,
the
media transcoder.
So the media transcoder is, an NLT product. And
in the media transcoder,
it is looking for the media coming to this location,
and then it is creating an HP cam 50 OP adder,
and then it is
check-in to the interplay to the EMA being just followed up. So that is the the
the overall workflow,
which I'm going to trigger it from the, ImaB system.
So
from the IMAM, I'm going to click on, deliver.
And in this case, I'm I'm going to select the option, send to Interplay to trigger that workflow.
And now the job is added. If you go to the dashboard, you can track that job from the imam
dashboard.
And, also,
if you come here,
that job is going to appear here in the media transcoder.
And then, eventually
so that that job is appeared here. The progress is, 0 percentage. It's progressing now.
And now if you go to the,
the media central and go to the incoming media,
and Ima Ingest,
that that's already showing up here, but now there is no media.
And, also, if you look at, here in the incoming media,
so the file,
now it's showing no head frame.
But once the process is completed,
then media will be completely,
checked into the Avid environment. From the from there, it can go to Inews or,
like, whatever kind of,
destination within the Avid environment.
So the the workflow is bidirectional.
So we can index the media from the,
Interplay environment,
in EMA, and then connect all other workflow that exist in the EMAB system. So if you look at all the, the different widgets and everything, so we can connect all these workflows.
And,
and, also, we can bring the media from the non AMID environment,
to the,
interplay environment.
This is all workflow handled handled through 2 different,
products from NLT. 1 is the neo archive, and another one is the media transcoder.
So there is a round trip, workflow between,
both the systems.
Yeah. There is lot of other things to show,
open for QA. And, so let me know if there is any questions. Please use the
the question section, and, we will,
answer those.