 Good morning. My name is Peter Forgach. I am one of the developer of Media Mosa. I am working at MedCap, and my presentation is about Media Mosa, the open source video backend. First, let's see what we can do with Media Mosa. We can upload videos, we can play videos, we can create still images from the videos, we can create metadata, like title, description, 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 in one format or another format, and we can easily change metadata. Ok, let's see what we can do and how. First of all, this is the official description of Media Mosa. Media Mosa is a robust, flexible, and highly scalable media management platform. There are a lot of universities and education organizations across Europe using this application. For example, we have clients in Italy and England. Media Mosa is an open source video backend. I will explain a little bit this open source video backend. Media Mosa is easy, so you can download the source code, you can change the source code, you can share it. We have tracking system, we have SVR repository, you can send patches for us, so it's open. The framework is Drupal 6 for earlier version and Drupal 7 for later versions. This is not a Drupal module, it's a complete installation. Media Mosa 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 media mosa, reusing res calls, post and get calls, and the response usually XML. Why this separation? It has two advantages. 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, the newest one is the media mosa construction kit. We will release this second one soon. Of course, you can create a video client if you are not satisfied with these two applications. Your application should communicate with media mosa through res calls. What you can do with media mosa? You can upload videos, store them, transcode videos for different formats, generate video objects, download links, create still images. There are different methods to create still images. You can create one image from the video for every five seconds, or five stills for all videos. Or the more exciting you can create still images for the scene changes. You can create metadata, title, description, 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 media mosa, about the main elements. Media mosa store 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, size, duration, and you can store this data in the media file. You can transcode the media file to another format. Then you have an original video and transcode that one. And you can upload another media file. So you have two originals and one transcode it. You can easily create 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. OK, it seems cool how you can download it. We have a website, mediaMozor.org. We have different mediaMozor versions. I suggest to use the latest one because the 1.7 version 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 the same reason. There are a lot of recommended applications like Love2Youve. It's part of the MEPEG tools. It's responsible for the still creation. Installation, it's like a Drupal installation. We have an install profile called mediaMozor. You can use that one. And the application will be installed perfectly. OK, let's make it easier because sometimes it's too difficult for the users. We have virtual machine image on mediaMozor.org. You can use that. Or we have a demo site. It's a, sorry, very easy admin-admin, user name 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 mediaMozor is very flexible. You can create separate installations for example for admin interface. Admin interface where the admin user can make the change the settings. You can separate the application interface for the rest course. 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 can be a file directory or you can use a sannas point point if you want. I talked about the rest course. It is the communication interface between the clients and the servers. If the client use get, it's getting data. If you use post, you want to change something or create, something for example create an asset. The output is usually an XML. We have a very good documentation page on mediaMozor.org. This is the page. You see the rest course here. If you click one of them, you see the parameters, requested parameters, the response fields, and there are examples. Data is not important. It is just for an example of how the response looks like. The demo front-end has a nice tool for developers. You can test your rest course like this. How you can upload a video? Your front-end application should create an asset. With asset create a rest call. The response is a unique asset ID. Then you can create a media file. Then the response is a unique media file ID. Then you can create an upload ticket. This is for security reasons. Your response action URL, where your form should be submitted. There is an upload progress URL for nice e-jquery progress bars. These are real applications. You see the progress bar and the upload fields, the metadata fields. Future developments. We implemented the solar integration. It's really speed 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 open API, open authentication and embed. These different open methods. This is the front page of the MediaMozor. You see the fruit page status. Every status should be green or minimum yellow. If it's red, it should fix something on your installation. It's a very handy page, by the way. We have a browser and a statistic page. The browser page you can browse your assets. You can search assets if you want to change something in your backend. Here is the asset browser. Here is the collection browser. You can see the log entries. You can check your rescores. 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 MediaMozor, you can create pre-fetch data in 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, 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 main points. You see here Windows main point. It is for historicalism. We don't support Windows. You can try, but I suggest Unix. Then we have tool parameters. Tool parameters for FAMPEG. If you are familiar with FAMPEG, you see a lot of parameters for FAMPEG. 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 profiles. Questions? If you have my website, and if you have questions, now I can answer.