[MEncoder-users] Simple Mencoder call using Exec

[DaveG]

On Saturday 10 February 2007 22:25, you wrote:
> Hi Dave,
>
> Thanks for the response.  What is the purpose of the {} in the path names.

Habit :-)  It stops variable names from being mis-interpreted if there is 
following text with no spaces eg

    echo ${fred}bloggs
is different to
    echo $fredbloggs

> I have had the encoding line working before using relative path
> names....this is that I am calling
>
> mencoder "mf://../../*.jpg" -ofps 25 -o ../test.flv -of lavf -ovc
> lavc -lavcopts
> vcodec=flv:keyint=50:vbitrate=600:mbd=2:mv0:trell:v4mv:cbp:last_pred=3 
> -vop scale=320:240 -lavfopts
> i_certify_that_my_video_stream_does_not_use_b_frames
>
> So check the folder two folders above the mencoder.exe for jpgs and output
> the FLV to the folder above.....
>
> Should work yeah?
>
> Well it does if the JPG's in the two folders above are also in the same
> folder, otherwise it crashes on writing the header file.
>
> Any more ideas?

I've only used it with absolute paths.  Assuming no other causes, maybe 
something in the code which interprets the the path for mf:// type source or 
something about the way you need to type it?  Checking and understanding the 
source code is a bit beyond my skill level to assess .

-- 
Dave