A Serbo-Croatian translation of this FAQ is kindly provided by Jovana Milutinovich of the University of Belgrade and WebhostingGeeks: http://science.webhostinggeeks.com/mediamosa
We want to create an upload progress meter. We found the http://mediamosa.org/content/retrieve-upload-progress-0 page with the call we need to use.
When requesting an upload ticket:
Hmm, we had some discussion about revisiting the group functions in http://mediamosa.org/trac/ticket/223. But it got depreciated to a 'Won't have now' issue due to the fact that we have been working around that in
Will reconsider that and can see to find a way to support being part of more than one group for the next release.
Yes, this can be initiated manually too. And, like you already wrote, it can be initiated by an upload process even with the FTP bulk upload by putting the right commands in the VUF file. Even multiple transcodings
We recently even have a command line tool for administrators to start any transcode or re-analyze possible. It is based on Drush, a Drupal add-on for command line actions. Very useful for batch operations. FTP is also very powerful for this.
No we don't. There was a lot of interesting work done in that TS (Dutch only: http://mediamosa.org/node/5366) and to be frankly there is still more research to be done in that field. It's all a matter of choices and right now we do think support for other content and supporting lecture recordings are more in favour.
We do too! The roadmap for 2011 is not discussed yet, but we do know that there will be funding to do a minimal of 2 releases and maybe 3 releases, like we have done this year. The first release of 2011 (MM 2.4) could be focused on the support for other content. I do like to see however that more joint effort is done.
The format of the VUF file is XML and is described in the Wiki:
The latest build of MediaMosa 18.104.22.168 (Build 956) is the recommended version if you don't have an 1.x platform running. Otherwise you need to migrate the content from the 1.x release. There are scripts for that but we are still waiting feedback from the community to have these made solid. We are using this 22.214.171.124 release on our production platform VP-Core.
See also -> http://mediamosa.org/trac/ticket/341 (Release notes of 2.2 build)
Well in fact we are using ProFTPD server for this and not a own implementation.
How this is used can be read at:
In fact you should be able to use any FTPserver for this purpose.
Yes you can do more then one transcoding, but what is key here is that 'Only original media files can be transcoded'. In that case you won't have a bad situation where you have transcodings of transcodings of transcodings with bad quality as result. You can do more than one transcoding as well, as long as it is from the original file.
We agree, this is somewhat confusing... In fact any type of content can be stored in MediaMosa, but the current workflow expects and handles only media, like audio and video, well from the aspect of analyze, creating stills and supporting transcodings.
The document "Mediamosa_an_introduction.pdf" was based on the MediaMosa 1.5.4 release of June 2009.
With the start of the new MM 2.x releases, based on the Drupal 7 framework, most of the core code was rewritten. We do keep the REST Reference guide up to date with every new release, but the documentation however needs an upgrade to be honest.
No it's not implemented in the MediaMosa 2.2. release. In the current development of MediaMosa 2.3 there is an update to support more toolsets (http://mediamosa.org/trac/ticket/265). This is considered to be the first step in supporting other type of contents.
MediaMosa is using more than one metadadata standard:
When the media analyze phase fails to determine the correct mediatype then the 'Mime Type' and/or 'Container' information will be empty. The mediafile can't be streamed. Technical metadata can't be entered manually later. You can start the analyze later again on that mediafile, i.e. when a newer version of FFMPEG is in place with better support for new codecs. -> /mediafile/$mediafile_id/analyse [POST]
WLE stands for White Label EGA. The WLE was developed to quickly show the possibilities of MediaMosa. Installation of the WLE creates a standard video portal (also) based on Drupal and it allows you to experiment with some basic webservices.
EGA is a Dutch acronym which stands for 'EindGebruikersApplicatie'. This translates to End User Application and we use it to refer to any application built on MediaMosa which communicates between the user and the MediaMosa platform.
VP-Core and VP-X were working titles of the MediaMosa Project. We are currently in the process of removing all references to these names in the code and documentation.