Hi,

Ulrich Ölmann <[EMAIL PROTECTED]> writes:

> For the reasons you wrote under 2) I decided not to use 'convert' to
> directly make an MPEG coded movie out of my MIFF data. Instead I use
> convert to extract every frame of the MIFF and to save them for
> example in the PNG format. Afterwards I use 'transcode' to rebuild a
> movie out of the individual frames. Doing so I normally use the XviD
> codec to encode the video stream. I hacked all these steps together in
> a more or less not so elegant bash script 'miff2xvid' that I attached
> to this mail. It needs Image Magick (for convert), transcode and the
> XviD package to work. At least for a unix like OS it should be
> possible to install these pieces of software quite easily.
>
> Maybe this helps!
> Best regards
> Ulrich
>
>
> P.S.: If the MIFF data consists of frames with comparable high
> resolution the 'convert' process reapes a huge amount of memory to do
> his job. It looks to me that it keeps all the data for all frames in
> memory at the same time. Does anybode know a more memory friendly way
> to extract every single frame out of MIFF data?
>
>
>
> On Wed, 13 Oct 2004, D.A. Crawley wrote:
>
>> One way would be to concatenate all the files in to one file to be read in 
>> by DX. Then all the data is represented internally in your machine. You 
>> can then use the sequencer to select out the particular time slice you are 
>> interested in and use the continuous save option in the save image window 
>> to create a MIFF file with all the frames present. If you are using Linux 
>> or some other Unix you can probably use the Linux command line command
>> 
>> convert input-file.miff output-file.m2v
>> 
>> to create an mpeg. Note that if you are running RH or Fedora (and possibly 
>> other unicies as well) you'll need to download and install the MPEG codec 
>> so that convert can use it.
>> 
>> Notes:
>> 
>> 1) This method is relatively memory intensive.
>> 
>> 2) The MPEG codecs I have been able to download for convert are all a 
>> little bit buggy and frequently fall over with large complex files.
>> 
>> 3) This does depend a little bit on what format you are feeding your data 
>> in to DX, for my applications its easy, I have regularly sampled binary 
>> data of a known size, I have no idea how you are sampling your data.
>> 

Thanks to you both! Just now, 'transcode' is running...

I just had the idea to change the 'general'-file with a script and run DX in
script-mode which produces the pictures. Would that be possible?

By the way, does anybody know of good script-examples on the web?

Best Greetings!
-- 
Fabian Braennstroem
Duesseldorf/Berlin

Reply via email to