ED] [mailto:ivtv-devel-
> > [EMAIL PROTECTED] On Behalf Of John Harvey
> > Sent: 30 November 2004 22:14
> > To: [EMAIL PROTECTED]
> > Subject: RE: [ivtv-devel] State of YUV playback/decodeing.
> >
> > Just a quick summary since I have to stop now.
> > Part of the p
s?
>
> Anyway I'll experiment a bit more over the next few
> evenings.
>
> John
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:ivtv-devel-
> > [EMAIL PROTECTED] On Behalf Of John
> Harvey
> > Sent: 30 November 2004 22:
t more over the next few evenings.
John
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of John Harvey
> Sent: 30 November 2004 22:14
> To: [EMAIL PROTECTED]
> Subject: RE: [ivtv-devel] State of YUV playback/decodeing.
>
> Just
kevin thayer wrote:
right, but i think writing it back it takes YV12.
Interesting ... I wonder why the different formats?
you really should read a full-frame at a time.
You don't need to be told which byte in the stream is
which - each frame is the same size - just need to
remember where you are i
> 1. The YUV from the card (/dev/video32) is not
> YUV420 (YV12) but rather
> Hauppauge's HM12 macroblock format. It requires a
> routine to manipulate
> it into YUV420. Not hard, but it has to be done
> before doing anything
> useful with the frame.
right, but i think writing it back it takes
kevin thayer wrote:
also from what i can recall, the yuv you get from the
encoder may not be valid yuv to feed to the output
side.
i think it's more meant to work on the output from a
software decoder (aka yv12).
Notes from my PVR-350 YUV (0.2.0-rc3) experiences
1. The YUV from the card (/dev/
To: [EMAIL PROTECTED]
> Subject: RE: [ivtv-devel] State of YUV playback/decodeing.
>
> That would be even better if its true since its easier to feed that from
> XV
> rather than the strange muddled up stuff from the encoder. I'll create
> some
> test yv12 data to try it with as
Message-
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of kevin thayer
> Sent: 30 November 2004 21:26
> To: [EMAIL PROTECTED]
> Subject: RE: [ivtv-devel] State of YUV playback/decodeing.
>
> also from what i can recall, the yuv you get from the
>
[mailto:ivtv-devel-
> > [EMAIL PROTECTED] On Behalf Of Chris
> Kennedy
> > Sent: 30 November 2004 19:06
> > To: [EMAIL PROTECTED]
> > Subject: Re: [ivtv-devel] State of YUV
> playback/decodeing.
> >
> > On Tue, Nov 30, 2004 at 06:41:46PM +, John
> H
On Tue, Nov 30, 2004 at 01:05:55PM -0600, Chris Kennedy wrote:
>
> 0x01024000-0x01026fa0 - YUV Buffer for Decoding?
> 0x01029000-0x0107d600 - YUV Buffer for Decoding?
> 0x0108e400-0x010b8700 - YUV Buffer for Decoding?
> ...
> 0x01240400-0x012949f0 - YUV Buffer for Decoding?
> 0x012a5800-0x012cfb00
10 matches
Mail list logo
