Postponed (maintainer needs more info)
Project:
Media Mover
Version:
5.x-0.4-1
Component:
Miscellaneous
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 May 2008 at 07:50 UTC
Updated:
20 May 2008 at 16:59 UTC
Comments
Comment #1
arthurf commentedSorry, either I don't understand your question, or you're are missunderstanding what the "configurations" are for media mover. Media mover requires the creation of a configuration which defines where files come from, what is done to those files and where the processed files are stored. If for example, you want to convert all video files that are attached to blog nodes, you create a configuration, choose harvest from attachments, select the node type and file types you want this configuration to work on. Then chose the ffmpeg options and set what kind of transcoding you need.
Comment #2
NewZeal commentedHi Arthur,
Thanks for your response. I'm the developer who was stonewalled. In the DruTube video demonstration of how to set up Media Mover the facilitator appeared to say that a new config had to be created for every file upload and that endless numbers of configs could be set up. This was described in the video as a limitation that could not be avoided at this stage.
I managed to get Media Mover to successfully transcode one .avi file out of a selection of 4 which were harvested (including an .mpg and a .rm). MM created two empty .flv files for two of the other media files and that was it. It got stuck in the middle of the other. Some of these files were not very big. Then I went back through the video and found the part where at 33.50 the facilitator says "every config makes only one file". What does this mean? Only one file, or one file type (eg flv).
Should it be possible for multiple files to be converted from one config without any problem? If so, why are we getting empty .flv files?
Later: Ok so I've located part of the problem is due to one of the files being .mpg which is not supported by ffmpeg, however the other files are .rm which are supported. The only place I need to have the .rm file type specified is in the config, right? I've also specified it in xspfplaylist, but surely this is not necessary since by this time all files played will be .flv or static files like .jpg.
Later Again: I created a new config and processed 8 files of different extensions. MM created a .flv for each but only the first one has content, the rest are 0 bytes. It is the same file that succeeded in previous configs. So MM is only successfully processing one file.
Comment #3
orces commentedSorry, probably I could not describe it well (lack of English). The post after me is from my developer- hope that is more clear.
My best,
Tansel