הלו,זה צ'ק פילו עם אימאם,
והיום אני רוצה להודה לך לנו לפרסם ספקטרום.
אז זה will go through some of the changes that ספקטרום רץ עשה עם EM and basically all content in editing processing into the cloud system in AWS and thenage ופרטים וכו,קלאוד,
אז עוד פעם,
אנחנו כמה slides here and show you couple demonstrations על איך זה היה.
אז עוד פעם,ספקטרום רץ,
הם קבל קרנל,
שזה אינטרנלי לטרום רץ,
הם עושים כל ads ורומות וכו וכו,אז הם בעצם אורים שהם across the country.
photographers that are shooting media and so on and so the idea was to provide a system where they can do collaboration,
centralize all the types of media and so on that they have,
but mostly for them it's all שלשים second spots and so on and then of course remote editors.
throughout the country and then of course the photographers,
אז הם רוצים לסטנדרטיז על Amazon,AWS וסטורג and processing media all from the cloud,
that was really goal and then using the system to manage the content
for the check in check out of media,organization of media and then of course permission and so on.
So we've actually moved into enterprise.
With the system and then of course meeting all of the challenges that charter has and with their IT and permission as well,
that they have set,that we need to meet on a daily basis,
the challenges that they had,again,
wanting to centralize the workflows and so on with wide access to all of the editors.and producers around the country in the US
and then be able to move large amounts of data across multiple locations,I mean that was an issue for them mostly because they were actually saving everything on hard drives,shipping hard drives and so on.
So again the centralization of the media was really key for them
all the remote are done
throughout the country
so again there about מאה editors and so on that they have and then of course distribution of the media.
heads and so on that they delivering content and the promos,spots and so on that they're doing
as well,
and then of course keeping it very efficient
and secure of the media,so again,
keeping track of where the המדיה goes,
who gets access to that,
that was really key for them and of course collaboration across the US and the folk in different regions
around the country.
So the idea here again was all the assets in
andralized into S שלש,
זה היה באמת קבסס את המידיה,upload the content,
store it in the AWS שלש bucket,
also glacier for archive
management,
putting away assets that they not using and so on.
עוד פעם,all the assets ה
שלש files transferred from the camera,first,this is how the process work,so they have the cameras,transfer all המידיה ללפטופ או דסטופ in remote and then from there
there are processes that they can use within the system
to be able to upload content.
עכשיו,
אנחנו גם מילים את המים של AWS ווד שהם יכולים לעשות לנו,
ליטופים.
using h מאה ששים וארבע Proxy for viewing and preview within the system and then of course with elemental media convert that's where they're doing all the process for trancoding.
So the upload process for them is quite simple where they're just drag and dropping the content into a window here,
we also have an application called feeder,
where they can actually download that and use that locally.
When they're adding files or folders,it's quite simple,
being able to go in,
look for the different content that they have,
you know,with simple video and so on,
they can also upload different folder structure as well,and then we actually bring that in as media that
in categories,what we call categories,
so the idea here is that they will have profiles that make it quit simple for uploading to specifications and so on.
הם יכולים להן את זה לים ספציפיים פרויקט,המדיה שהיא
And then of course different categories
as well,in case they use adobe premiere for editing,
then they can also tag the media and make it available
with search capabilities with the media,so globally tagging the content as it's going as well
and then on the category we'll talk about this a little bit,
which is the categories permission
to be able to manage who gets to see what
and what they get to do with the media once it's uploaded.
The contents always uploaded
and there's also a dashboard that's also given always to see what the process is,
how things are going and so on that upload and then of course we do things where they can edit what they as media andata for media that's going well and simply hitting the upload.
המדיה עכשיו היסטורי,
אז זה פשוט זה לפרסס את המידיה ולהיד את הקלאוד.
So the idea is being able to publish the content or view the content in various different types of platforms and so on,
we can automate this whole process,
send out review and approved media
to master control,to VOD,to social media.
share the content through a web interface,
it's quite simple actually to drag and drop media to be able to share or go ahead and deliver or package
the content as well,
which is quite nice if I'm packaging media with multiple audio files and then of course caption files,graphics bugs,lower th and so on,
I can deliver.
Tcoders to be able to process media and then be able to share את המידיה,
this is actually customizable with us where we can actually
place inside of an email and then be able to have it as a link and then just click on the link and it opens up into a local browser
also with finished assets then we can get very specific on the packaging as I mentioned.
And then being able to share that with other platform
or deliver to automation and broadcast and play out
there as well
so
on the archiving this was quite nice where e offer option for s glacier and tearing
of the content so
with this media
once it moves a production,
it can be placed and put into.
In archive that's more cost effective to store the media until it's used again and then restored
so the idea here is that you can set up different permission levels within or different tiers
to get access to the archive,
being able to move את המדיה.
S שלשקט,שזה קצת יותר costly,
then
and then be to it,
but also the proxy and the המידה הם עדיין מ within the system to be able to share that
there as well.
file retrieval,
it depends on what you are going with,
you can go to the deep archive or some of the lower,which is easier to
bring back.
שכל המידיה is secure based on everything related to AWS
security that they meet and then of course login featuring different things,we'll talk about that in a second.
אנחנו גם כמובן מור different project files and things and then of course the metadata,is key for specific information that they want to keep,we do manage that process
with different groups of metadata,
giving people e access to view את המטאטה או את המטה,
אנחנו יכולים לול זה through permission.
then again on the restoring the content,
it's quite easy,
so you have the media,
you have all the project files,you have everything related to projects and so on
and very specific UIDs to the content and so on
and the convention that built the system to keep everything quite unique
within the system.
tools available quickly to pull back that content
from the cloud
production storage in the cloud and then be able to edit that again
so we can bring back all the project files and then of course all the media that associated with that as well
and then dynamicinking with proxy and restor original content as well
so we manage all of that process for the clients
or the system
and so on.
מאוד פשוט את הפרוסס הזה.
We also add to the security where we can actually create
the different groups and that's all based on active Directory or
Octa for sign on and so on,
but the users are actually assigned to user groups that have permissions and accessibility,so we actually define.
within the interface as an admin so these are of course admin users setting this where they're setting up a user and number of users and with that group apply the different settings to categories that they יכולים לראות מיה is available to them and then be able to access את המידיה ופרסס את המידיה.
מה שהם יכולים לעשות עם המידיה using the admins
and we use the category if
may contract en certain that we have we have access to
אוטומטיק קטגוריה שאף אחד לא access to or they only have access to proxy with
bugs across the video and so
that they can't use it within the project so very nice
within the system that you're able to do that
within the system.
We've taken into consideration and built in for charter and the security that they can set through the AWS platform
so lots of protection and security set
within the system.
So the corporate security from their IT department
and then also they also give us
the ability to get into the account as well to
manage the system and help them manage the system,but
the team.
work together
on state of the art,
AWS protections that they have built in
the platform,
so we'll utilize that with the firewalls and load balancing
you know and the different configurations and security that we have available through AWS and apply that to platform.
So then of course,
all of the content to secure the S שלש buckets secure
so
nody can access that content unless they going through the system and through these credentials
Charter also uses a sign
where they are doing
through their system and through AWS and they can control and manage who gets to access to the content.
ואז כמובן,על,על המים,
אז הם יכולים מידיה הם אקסס ומה הם יכולים לעשות.
אז אנחנו הסיסטם,
אז אסים יש
Project Metadata is created
CRM passed,
so we do have through charter,
they will actually create projects outside of the system and then of course project metadata
and then of course we can not only the UID but also the metadata that part of that project
to each of the assets.
media workflows that we have non destructive,
מה שאנחנו עושים זה אנחנו קבל את המידיה,the original content,
we create a proxy froment
and with that content.
create proxy and then users will view that proxy
and utilize all different and different editing based on proxy first and then can link with the original content,
אבל אנחנו לא נ or touch original content until they're transcים מהנט למשהו אחר,קודק וכו.
כל מהפרויקטים עוד פעם,יכול להיות,
הפאנל,כמו עם Adobe Premiere because they use all the Adobe.
you also have built in for charter multiple multiple workflows that they have so different types of events like ifata changes on a project
may process the media a little bit different or move the content because it's reached the stage where they've done production and distributed.
Distributed the spot
and then delivered that they can change the metadata on all that project and so on and then that could also trigger another type of workflow to move content over to archive and then it
restore.
needed
a number of conditions that can happen and again,this is all menu driven,
which is really nice,so there is no programming here involved and so on,if you want to,we do have options to add some scripts and various things,but
most of this is menu driven,
where we can actually go in.
There's an event,
so some type of event like change in,
dat is reached,
scheduled dates and so on,
then there's a condition,
so if it's a condition with the metadata that's available to us and it is rights management is because we have a contract to be able to deliver the media
and then you select an action so like you know deliver the content
then move the content from category to another
and then be able to distribute and deliver content
so these are fully automated workflows that we have built in,
they can be triggered bys as well,so if a condition or a process there as well.
So on the side,which is quite nice is you can customize delivery profiles for packaging
and various side information that be delivered
in different are required
on the outbound,so whatever platform.XMLXF file text file or something that
we can provide that with the media
and deliver to trancoder for processing and of course the data by platform