From: Steven Toth <stoth@linuxtv.org>
To: linux-media@vger.kernel.org
Subject: V4L2 Advanced Codec questions
Date: Thu, 26 Mar 2009 11:59:11 -0400 [thread overview]
Message-ID: <49CBA64F.2080506@linuxtv.org> (raw)
Hello!
I want to open a couple of HVR22xx items up for discussion.
The HVR-22xx analog encoder is capable of encoded to all kinds of video and
audio codecs in various containers formats.
From memory, wm9, mpeg4, mpeg2, divx, AAC, AC3, Windows audio codecs in asf,
ts, ps, avi containers, depending on various firmware license enablements and
configuration options. Maybe more, maybe, I'll draw up a complete list when I
begin to focus on analog.
Any single encoder on the HVR22xx can produce (if licensed) any of the formats
above. However, due to a lack of CPU horsepower in the RISC engine, the board is
not completely symmetrical when the encoders are running concurrently. This is
the main reason why Hauppauge have disabled these features in the windows driver.
It's possible for example to get two concurrent MPEG2 PS streams but only if the
bitrate is limited to 6Mbps, which we also do in the windows driver.
Apart from the fact that we (the LinuxTV community) will need to determine
what's possible concurrently, and what isn't, it does raise interesting issues
for the V4L2 API.
So, how do we expose this advanced codec and hardware encoder limitation
information through v4l2 to the applications?
Do we, don't we?
Suggestions?
- Steve
next reply other threads:[~2009-03-26 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:59 Steven Toth [this message]
2009-03-26 16:46 ` V4L2 Advanced Codec questions Janne Grunau
2009-03-28 15:22 ` Hans Verkuil
2009-03-28 17:03 ` Steven Toth
2009-03-28 18:03 ` Hans Verkuil
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=49CBA64F.2080506@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=linux-media@vger.kernel.org \
/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