On Thu, 2008-02-28 at 20:02 -0800, Steven M. Schultz wrote:
> 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"), ...)
>
Ok. I may give it a whirl.
> > 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.
Yes, but I didn't know what tool I need to use to create it...
> 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.
I think so. Although I haven't tried it. Provided it does export an avi,
what tools on Linux would one then use to clean up a capture from a
video tape? I guess there aren't any?
> > I'll go back to the old version of mjpegtools.
>
> That's probably the best way.
In trying to keep most everything on the Linux platform, I think that's
the best option. Authoring a DVD on windoze is all I care to do on that
platform. Since the windoze authoring software doesn't run correctly
under wine, I don't have a lot of choice. I could use a lot expletives
when trying to run it under wine. Wouldn't help matters any an would
take 2 or 3 times as long. Easier to author the DVD on a windoze box.
As always, thanks for the help.
Stan
-------------------------------------------------------------------------
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
