Dear Genis, On 05/20/2013 11:28 PM, Genis Musulmanbekov wrote: > “Your video submission *A demo video* was successfully processed. > The file you uploaded was *kazakov1.avi*. > Your video is now available here: http://lt-jds.jinr.ru/record/6288. > [...] > > However, the master-file is not converted and webm-files are not created.
Looking at some videos uploaded on your server and given the fact that you are using unmodified "batch_template_submission.json" and "encoding_profiles.json" configuration files, it might be simply that that the ‘webm‘ and ‘mp4‘ are not created because the master video is not considered in a high quality enough according to the settings. Some explanations: - encoding_profiles.json defines some encoding presets: format, size, bitrate, etc. are defined for each preset. - batch templates (such as "batch_template_submission.json" used in demo video submission workflow) define a list of encoding jobs to execute, referring to the different profiles existing in "encoding_profiles.json". Such batch templates also define some conditions on the job conversion, as well as what do with the created files. One particularly interesting parameter in this case is the "assure_quality" option, which ensures that BibEncode is not trying to encode videos in a higher quality than the original master file (which would not make sense). I am assuming that in your case the "assure_quality" option is preventing the ‘mp4‘ and ‘webm‘ options to be created. Indeed, the profiles used in the default "batch_template_submission.json" create videos sized at minimum 854x480 (*_480P) while your input videos are 720x576 (PAL) max. In order to validate this assumption you could try uploading a larger video on your server, such as the demo one (Full HD): <http://invenio-demo.cern.ch/record/107/files/CERN-MOVIE-2010-075.mpg> Some additional explanations on batch templates: - batch templates (such as "batch_template_submission.json") can define "fallback" jobs, such that the job is executed if the "assure_quality" setting has filtered out all other jobs (see "fallback" option in sample "batch_template_submission.json"). - batch templates (such as "batch_template_submission.json") can "enforce" jobs, such that the job is executed in any case (see "enforce" option in sample "batch_template_submission.json"). You should then be able to tweak your configuration to have the videos encoded according to your wish, either by providing lower quality profiles (do not forget to provide a customized batch template as parameter to the WebSubmit Video_Processing function), or having fallback/enforced jobs in your custom batch template(s). Best regards -- Jerome Caffaro ** CERN Document Server ** <http://cds.cern.ch/>
