Thank you for your reply.
Since my request is about modifying the source code to work with the
raspberry pi hardware I am in the correct mailinglist. I would gladly
contribute myself, but alas I am not a skilled programmer, hence my request.
It is true that the raspberry is all but open, and the Rpi community is
leaning heavily upon Broadcom to reveal their secrets.
I thought -hoped- that the Openmax API would be enough to recode the
library to a Rpi hardware accelerated library.
And yes I could get a Beagleboard or Pandaboard. That's not the issue in
my opinion. I already have a working TV server with my desktop computer,
which is an even faster computer than the forementioned boards. The
challenge here is to get the library to work with this small board.
Further, if the library could work with the Openmax Api it would not
only serve the Raspberry board but all the other hardware that utilizes
the Openmax Api.
Or am I overlooking something?
Arjen
On 1-12-2012 8:39, Attila Kinali wrote:
Dear raspberry pi user
On Fri, 30 Nov 2012 20:33:28 +0100
Arjen Vellekoop <[email protected]> wrote:
I am a bit confused, just subscribed and expected to be redericted to a
forum. Since this is not the case I'll try this way. Hope not to spam
the whole list. pls point me to the right direction if I am in the wrong
list here.
Welcome to the world of opensource, where webforums are frowned upon,
because they are damn inefficient to use if you are dealing with
hundreds of messages every day.
A request for compiling an avconv version that is hardware accelerated
probably already exists (if not pls consider to do so), however for my
application I only need scaling. My DVB-T dongle receives MPEG2 in SD
(704x576) And I only need to transcode it to the same codec but at a
quarter resolution (CIF=352x288)
Well.. You should note a few things.
First, this mailinglist is about development of libav, not about its usage.
This means, if you have questions about how to modify the code of libav,
or have done some modifications that you would like to share with others,
then you are at the right place. If it's just about usage, and compiling
without modification of the _code_ is usage, then you should choose
a different mailinglist.
The second thing is, we do not provide binaries of the library.
This is the job of distributions. All you get from us is the source code.
(Ok, a few of those who package libav for distributions are also
libav developers, but that's beside the point)
The third thing is, that the raspberry pi is a horribly closed and
undocumented piece of hardware. About the only thing that is documented
is it's CPU core, and that documentation comes from ARM and not from
Broadcom. With this little documentation it is nearly impossible to
support even the most basic functionallity properly. Even Nvidia provides
more help for getting their hardware working with opensource software.
The insane amount of bit baning raspberry pi users have to do, even for
the most simple stuff (like I2C)[1] is a tell tale of this. I really feel
pitty for all of you, who have been tricked into buying this piece of
*censored* by the raspberry pi foundation and the hype they created.
Or to summarize: it's very unlikely that anyone has been able to modify
libav or any other encoding library to use the hardware acceleration of
the raspberry pi. I recommend you to get yourself either a BeagleBoard
or a PandaBoard which are fully documented and most of its hardware
drivers are already in the mainline kernel. The PandaBoard with its
dual core 1.2GHz should even have enough cpu power to encode your video
in real time without using any hardware acceleration, which would be
also available.
Attila Kinali
[1]http://www.google.com/search?q=raspberry+pi+bit+banging
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
