On Thu, 28 Feb 2008, Stan Gammons wrote:
> That's Ok with me. What do I need to change to make it work?
It'll be _REALLY_ obvious when you try to compile it ;)
Basically all the old LOG_WARN, LOG_ERROR, LOG_INFO, ... defines
are no longer public. You have two choices when something like
mjpeg_log(LOG_WARN, ...)
is encountered. Either change it to
mjpeg_warn(...)
or
mjpeg_log( mjpeg_loglev_t("warn"), ...)
This was changed to avoid conflicts with LOG_* and system defines (and
to avoid yet another package adding its own LOG* stuff to the namespace)
> Looks like I misunderstood what you were saying. From what I saw on the
It was mutual. You won't obviously be able to pipe into the encoder.
But I thought you knew it would be up to you to create whatever
container an encoder would need.
> website, tmpgenc requires an avi file. So, I wondered how one took raw
> DV, edited it with Kino, and so forth an ended up with an avi file for
> tmpgenc to process?
Kino can write an AVI file, right? It's been 5 or 6 years since I ran
it but I thought it could write AVI files back out.
With ANY other encoder it's up to you to get the data into whatever
container the program will accept. I create Quicktime files with
uncompressed 4:2:2 video since that's the most convenient format.
> I'll go back to the old version of mjpegtools.
That's probably the best way.
Steve
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mjpeg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
