On Wed, Feb 25, 2004 at 11:28:52AM -0800, Mike Smith
wrote:
> **ERROR: [mplex] Need to split output but there
> appears to be no %d in the filename pattern
output.mpg
> 
> ...
> 
> What's going on here?  How can I get mplex to create
> a larger output file?

What version of the mjpegtools do you have.  This
sounds like a bug
that was corrected in a later version, so simply
upgrading to the
latest mplex might just make it go away.

I'm using the latest:

[EMAIL PROTECTED] root]# mplex --help
mjpegtools mplex-2 version 1.6.2 (2.2.3)



Alternately, how did you encode the movie, if you
didn't use -f 8 to
mpeg2enc when you encoded it, then you should not use
-f 8 to mplex
when you multiplex it.  I.e., the -f # option should
be identical
between mplex and mpeg2enc.



In any case, if you encoded with a format that causes
the mpeg
encoder to include split markers, you are stuck, as
there's no option
to tell mplex to ignore embedded split markers in the
raw mpeg data. 


That's the problem.  The script I'm using,  on the
mpeg2enc step they have "--sequence-length 795".  I
didn't know what it was for.  That may solve the
problem.

Thanks,

Mike

You then need to to use a filename with a %d in it
somewhere so mplex
can create the multiple files that the mpeg encoder it
telling it to
create.


PS to Andrew - Maybe this is an idea for an additional
mplex flag.
"--ignore-split-markers" that causes it to ignore the
embedded split
markers and just make one large mpeg file anyway.  Is
this possible?


__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to