On Mon, 26 Sep 2005 [EMAIL PROTECTED] wrote:

> I have a problem with the version 1.8.0 in combination with the newest 
> digikam-plugin (kipi-plugin for generate a mpg file for a images archiv).

        I think something in the newest digikam-plugin is causing the 
        problem.

> I see the error from ppmto4yuv that "Error: maxval==255. Actual value is 
> 65365" - this is in the read function of yuv-header.

        That means that the digikam-plugin is generating 2 bytes/pixel PPM
        data (values of 0 to 65535) instead of 1 byte/pixel (values of 0 to 255)

        ppmtoy4m only accepts 1 byte/pixel PPM data (maximum value of 255).

> The plugin uses the script images4mpg and calls many different tools. 

        Perhaps something in one of those tools is producing PPM data with
        a range of 0 - 65535 instead of the range 0 - 255.

        Oh, and one more thing about ppmtoy4m - in 1.8.0 the default output
        chroma sampling is 4:4:4.  It will be necessary to either to use the
        "-S option (see 'ppmtoy4m -h') or resample the chroma using y4mscaler
        (see http://www.mir.com/DMG/Software/y4mscaler.html)

        Cheers,
        Steven Schultz



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to