From: Basil Mohamed Gohar <abu_hurayrah@hidayahonline.org>
To: video4linux-list@redhat.com
Subject: Re: .yuv file
Date: Thu, 18 Mar 2010 09:38:07 -0400 [thread overview]
Message-ID: <4BA22CBF.3080902@hidayahonline.org> (raw)
In-Reply-To: <fe6fd5f61003180356i4f9346b9j31089e4d6fa94a44@mail.gmail.com>
On 03/18/2010 06:56 AM, Carlos Lavin wrote:
> hello, I am making an application for save images in yuv format in files
> with .yuv extension, but I don't find information about how the information
> about the image is save in the file, how the image is saved in the file? how
> it is organized in the file .yuv? anyboy can help me? anybody kwon any link
> where to explain my problem? thanks
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
A "yuv" format image is a raw stream of bits. It does not normally
store *any* metadata about the image itself. So, typically, there's no
way to know the dimensions of the image, the framerate of the stream, or
even the format of the pixels themselves. You will have to know these
yourself if you wish to work with those images, and since you're
creating them, that shouldn't be a problem.
If, on the other hand, you want to store raw, uncompressed data but
retain some metadata about it, you can choose the yuv4mpeg format, which
can store data such as the resolution, pixel format, frame rate, and
even whether the frames are progressive or interlaced. A yuv4mpeg file
has nothing explicitly to do with mpeg video, it was just named that
because that was the original primary use for such raw data.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2010-03-18 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 10:56 .yuv file Carlos Lavin
2010-03-18 13:38 ` Basil Mohamed Gohar [this message]
2010-03-19 0:18 ` Charlie X. Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA22CBF.3080902@hidayahonline.org \
--to=abu_hurayrah@hidayahonline.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox