On Tue, 28 Feb 2006, E.Chalaron wrote:

> I still have some troubles to run y4mtoqt. 
> What chromass should I feed into it ? I am using 422 and -X

        and later

> I am not clear enough, sorry. 
> I can not read files produced with y4mtoqt.
> lqtplay is telling me about a bad header and mplayer is running without any 
> display.

        Wow - those are rather different problems.  The first one sounded
        like a problem creating the .mov file and the second problem is
        that the file was created but now a program doesn't understand the
        contents.

        IF I have figured out the real problem it is that you have successfully
        created a Quicktime file with y4mtoqt but lqtplay and MPlayer do not
        know how to deal with a '2vuy' Quicktime file.

        Correct?

        What does 'qtinfo' (a utility from libquicktime) say about the file.
        If I run 'qtinfo pocket.mov' (a file I happen to have available at
        the moment) I get something like this:

File /Volumes/RAID/tmp/pocket.mov:
  1 audio tracks.
    2 channels, 16 bits, sample rate 48000, length 393422223 samples, 
compressor twos.
    Sample format: 16 bit signed.
    supported.
  1 video tracks.
    720x486, depth 24, rate 29.969999, length 245643 frames, compressor 2vuy.
    Native colormodel:  YUV 4:2:2 packed (YUY2)
    Interlace mode:     None (Progressive)
    supported.

        Obviously your numbers will be different (different number of frames,
        etc) but the 'compressor 2vuy' part is the key.

        But unless you're using FinalCutPro (or similar program) DO NOT USE
        '-X'.  10bit 4:2:2 (what's called "v210") is a moderately esoteric
        format used by higher-end capture cards.
                
        IF you see 'compressor v210' then you've created a file that FinalCut
        will understand but probably isn't what you want ;)

        The (bad) news is that MPlayer has no idea what '2vuy' (8bit 4:2:2)
        is (well, it might know 4:2:2 but not how to parse it from a Quicktime 
        file).

        But if 'qtinfo' gives info similar to that above then I have no idea
        why 'lqtplay' is complaining about a bad header.

        Hmmm, what exactly does lqtplay say?  Or are you thinking of 'yuvplay'?
        yuvplay won't work - general Quicktime decoding capability is not
        (at the moment) present in mjpegtools.  

        qttoy4m should be able to play the file - from there you can feed the
        data into mjpegtools pipeline.

        Cheers,
        Steven Schultz



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to