We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

MediaMosa: Open source video backend

00:00

Formal Metadata

Title
MediaMosa: Open source video backend
Title of Series
Number of Parts
64
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
In this presentation you will hear about: * The main ability of this platform * Why it is a good solution for (educational) video sites * You will see a demo video front end (WLE) for MediaMosa * Introducion REST (Representational State Transfer) interface as a communication channel between the video frontend and backend * How to: upload video, transcode video, create (multiple) still images * How you can add and search metadatas (title, description, Dublin Core, Qualified Dublin Core) with CQL * How you can increase the performance of MediaMosa using multiple servers * Future developments
Front and back endsOpen sourceVideoconferencingSoftware developerFront and back endsOpen sourcePresentation of a groupSoftware developerVideoconferencingSpherical capComputer animationXMLLecture/Conference
Spherical capMetadataVideoconferencingCanonical ensembleField (computer science)Key (cryptography)Computer animation
Digital mediaForm (programming)File formatSelf-organizationDescriptive statisticsData managementUniverse (mathematics)Computer fileComputer animation
Spherical capScalabilityData managementDigital mediaComputing platformContent (media)VideoconferencingRevision controlOpen sourceFront and back endsSoftware frameworkScalabilityDigital mediaData managementBitOpen sourceTrailClient (computing)Software frameworkRevision controlFront and back endsUniverse (mathematics)VideoconferencingPatch (Unix)Computing platformCartesian coordinate systemModule (mathematics)Self-organizationDescriptive statisticsPhysical systemDemosceneEndliche ModelltheorieSource codeGroup actionComputer animationLecture/Conference
System callVideoconferencingFront and back endsOpen sourceDependent and independent variablesOpen sourceFlow separationDebuggerClient (computing)Digital mediaVideoconferencingFront and back endsComputer animation
Flow separationClient (computing)Front and back endsDisintegrationWebsiteDemo (music)Computer-generated imageryVideoconferencingStreaming mediaTranscodierungLink (knot theory)VideoconferencingStreaming mediaFront and back endsData storage deviceField (computer science)Cartesian coordinate system2 (number)TranscodierungDifferent (Kate Ryan album)Electric generatorWebsiteClient (computing)DemosceneINTEGRALCore dumpConstructor (object-oriented programming)AuthenticationSoftware development kitDigital mediaObject (grammar)Link (knot theory)Uniform resource locatorSoftware testingGoodness of fitFile formatOrder (biology)Descriptive statisticsComputer animationLecture/Conference
Computer fileDigital mediaComputer-generated imageryVideoconferencingTranscodierungFile formatDefault (computer science)WebsiteElement (mathematics)Digital mediaWebsiteData storage deviceDefault (computer science)Web pageComputer configurationSet (mathematics)VideoconferencingTransportation theory (mathematics)Object (grammar)TranscodierungMetadataFile formatComputer fileField (computer science)CodecComputer animation
VoltmeterVideoconferencingWebsiteWeb pageVideoconferencingWebsiteCartesian coordinate systemDefault (computer science)Front and back endsMetadataComputer animationLecture/Conference
Installation artUser profileSpherical capTranscodierungReading (process)MereologyDigital mediaFormal languageRevision controlCartesian coordinate systemNoise (electronics)Point (geometry)Moment <Mathematik>Perfect groupVideoconferencingDependent and independent variablesFreewareProfil (magazine)Front and back endsOpen setComputer animationLecture/Conference
Computer-generated imageryWebsiteDemosceneTime travelWebsiteDemo (music)Virtual machineComputer animationLecture/Conference
Computer-generated imageryIntelDemosceneWebsiteMenu (computing)WebsitePasswordVideoconferencingClient (computing)Interface (computing)Computer animationLecture/Conference
Data storage deviceServer (computing)Storage area networkInterface (computing)VideoconferencingSpherical capTelecommunicationSystem callFunction (mathematics)Representational state transferClient (computing)Function (mathematics)Web pageComputer fileSystem administratorDirectory serviceInterface (computing)Cartesian coordinate systemGoodness of fitServer (computing)Process (computing)Flow separationInstallation artData storage deviceDatabaseMultiplicationTelecommunicationDependent and independent variablesObservational studyMetreMathematicsComputer animation
Dependent and independent variablesField (computer science)Parameter (computer programming)Web pageWeb pageDependent and independent variablesComputer animationLecture/Conference
TelecommunicationInterface (computing)Client (computing)Uniform resource locatorGroup actionDependent and independent variablesParameter (computer programming)Dependent and independent variablesArithmetic progressionUniqueness quantificationBoss CorporationCartesian coordinate systemMultiplication signForm (programming)Demo (music)Digital mediaInformation securityGroup actionVideoconferencingSoftware developerUniform resource locatorComputer fileLecture/ConferenceComputer animation
Group actionArithmetic progressionField (computer science)MetadataComputer animationLecture/Conference
Computer-generated imageryEmbedded systemSoftware developerINTEGRALMetadataPlanningImplementationOpen setDifferent (Kate Ryan album)Computer animationLecture/Conference
Web pageConfiguration spaceExecution unitWeb pageDemo (music)Computer animation
Web pageStatisticsWeb browserStatisticsOrder (biology)Web pageSet (mathematics)Computer animation
StatisticsWeb pagePrisoner's dilemmaStatisticsWeb browserComputer animation
Configuration spaceWeb pageSet (mathematics)Client (computing)WebsiteCartesian coordinate systemWeb pageConfiguration spacePoint (geometry)Server (computing)WindowComputer animation
Configuration spaceWeb pagePoint (geometry)MetreProfil (magazine)Greatest elementTranscodierungParameter (computer programming)Default (computer science)Computer animation
WebsiteComputer animationLecture/Conference
Transcript: English(auto-generated)
Good morning. My name is Peter Furgatch. I'm one of the developers of MediaMosa. I am working at Metcapp and my presentation is about MediaMosa, the open source video backend.
First, let's see what we can do with MediaMosa. We can upload videos, we can play videos, we can create still images from the videos, we can create metadata like title, description, and other fields, and of course we can change the pictures,
we can order them, we can create a transcode, we can transcode a media file from one format to another format, and we can easily change metadata. Okay, let's see what we can do and how. First of all, this is the official description of MediaMosa. MediaMosa is a robust, flexible, and highly scalable
media management platform. There are a lot of universities and educational organizations across Europe using this application. For example, we have clients in Italy
and England. MediaMosa is an open source video backend. I will explain a little bit this open source video backend. Open source is easy, so you can download the source code, you can change the source code, you can share it, and
we have a tracking system, we have an SVR repository, you can send patches for us, so it's open. The framework is Drupal 6 for an earlier version and Drupal 7 for later versions. This is not a Drupal module. It's a complete installation.
So MediaMosa is an open source video backend. What does it mean video backend? The users usually meet with the video front-end, and the video front-end is a talk with the MediaMosa, reusing REST calls, POST, and GET calls, and the response is usually XML.
Why this separation? It has two advantages. One of them, one video backend can support more than one video client. So it is cheaper, easier to maintain, and it has other advantage.
It is integration for existing websites. So you have a website you want videos there, you can easily integrate it. What about the front-end? We have two different video front-end. The oldest one is the VLE, White Leber Lijo.
The newest one is the MediaMosa construction kit. We will release this second one soon. And of course you can create a video client if you are not satisfied with these two applications. Your application should communicate with MediaMosa through REST calls.
What you can do with MediaMosa? You can upload videos, store them, transcode videos for different formats, generate video object, download links, create still images. There are different methods to create still images. You can create one
image from the video or for every five seconds or five stills for all videos. Or the most exciting thing, you can create still images for the scene changes. You can create metadata, title, description,
doubling core fields, qualified doubling core fields. You can create video collections. You can stream your videos. You can create authentications. You can decide who can see videos, video or videos.
A short introduction about MediaMosa, about the main elements. MediaMosa stores assets, and the asset is a container where you can store title, description and other fields. An asset may have a media file or more.
And the media file may have a video. Video of course has a codec file size duration and you can restore this data in the media file. You can transcode the media file to another format. Then you have an original video and a transcoded one.
And you can upload another media file. So you have two originals and one transcoded. You can easily create the still images from the videos, one or more, and you can set one of them as a
default one. Let's see why is it good. This is an example video site, you see assets with default still images and metadata. And this is a video page which has a video object, still images and
metadata. This is a real application. This is the white label IHA. You see four assets here with default still images. And this is one of the video site. You see a lot of still images and
a lot of metadata. You can decide what you put on your video front-end. Okay, it seems good. How you can download it? We have a website, media-mosa.org. We have different media-mosa versions. I suggest to use the latest one
because the 1.7 version will be won't be supported anymore. And you can download the video front-end too. You need LAMP, it means Linux, Apache, MySQL, PHP. But of course if you have free BSD or open BSD, you can use it instead of Linux or MariaDB works fine with this
installation. You need FFmpeg for transcoding videos, creating still images, checking the videos. And you need Lua. Lua is a scripting language with LPG and Stansron
with the same reason. There are a lot of recommended applications like Love2UVE. It's part of the M-U-PEC tools. It's responsible for the still creation. Installation, it's like a Drupal installation. We have an install profile called Media-Mosa.
You can use that one and the application will be installed perfectly. Okay, let's make it easier because sometimes it's too difficult for the users. We have virtual machine image on Media-Mosa.org. You can use that or we have a demo site. It's a sorry,
very easy, admin, admin, username, password. You can use that, you can change that, you can freely modify anything. The site is reset itself in every hour. And if you have multiple clients with
hundreds of thousands of videos, you need performance improvement. So Media-Mosa is very flexible. You can create separate installations for for example for an admin interface, admin interface where the admin user can change the settings. You can separate the application interface for the Rescos.
You can separate the upload interface, download interface, and the job interfaces. The job interfaces are responsible for the transcoding video, creating still images, and other heavy things. You should use common database server and
storage. Storage can be a file directory or you can use a Sanas mindpoint if you want. I talked about the Rescos. It is the communication interface between the clients and the servers.
If the client uses GET, it's getting data. If you use POST, you want to change or something or create something, for example, create an asset. The output is usually an XML. And we have a very good documentation page
on Media-Mosa.org. This is the page. You see the Rescos here. If you click one of them, you see the parameters, requested parameters, the response fields, and there are examples. This is, that is not important. It is just for an example, but how
is a response looks like. The white level, you have the demo front-end, has a nice tool for developers. You can test your Rescos like this. So how you can upload
a video? Your front-end application should create an asset with asset creator Resco. The response is a unique asset ID. Then you can create a media file. Then the response is a media file, unique media file ID, and then you can create upload ticket.
This is for security reason. Your response action URL, where your form should be submitted, and there is an upload progress URL for nice GQuery progress bars. These are real applications. You see the progress bar and the upload fields, the metadata fields.
Future developments. We implemented the Solari integration. It really speeds up your metadata searches.
We will implement Atom, JSON, and RSS feed too. We will implement watermarking still images. It's very cool. You can easily watermark your still images. Then we will implement OpenAPI,
OpenAuthentication, and Wombat. These are different Open methods. Okay. This is MediaMuseum. This is the front page of the MediaMuseum. You see the front page status. Every status should be green or
minimum yellow. If it's red, you should fix something on your installation. This is a very handy page, by the way. We have a browser and the statistics page. The browser page, you can browse your assets. You can search assets if you want to change something on your
backend. There is a... So here is the asset browser. Here is the collection browser. You can see the log entries. You can see... You can check your rescorts.
This is your statistics. It will be improved later. It knows the basic statistics. This is the configuration page. You can configure a lot of things, for example servers.
You don't have to worry about it. If you install your MediaMuseum, it will prefetch data, these fields. Later you can change if you want. You can create client applications. This is the applications. This is the client servers.
This is good for the client servers. You can set names, your passwords, quota and a lot of other things. You can configure your website, for example.
You can set the debug settings. You can set the amount points. You see here Windows' amount point. It is for historical reason. We don't support Windows. You can try, but I suggest UNIX.
Then we have tool parameters. Tool parameters for FFmpeg. And if you are familiar with FFmpeg, you see a lot of parameters
for the FFmpeg. You can define new ones. It filters your transcode profiles. Here are the transcode profiles. For example, the most interesting is this H.264. This is the default in my installation. You can easily define other transcode profiles if you want to transcode for other
for other transcode profiles. Questions if you have my website, middlemosa website. And if you have questions, now I can answer.