Re: [MPlayer-dev-eng] Need a guide to implement a codec library using hardware video codec
Small GPL warning:
Make sure that your company is aware to the fact that MPlayer is licensed only through a GPL license.
IANAL, so I am not sure what exactly is needed for you to comply with said license, though I am rather sure that releasing all of the source code of your modified version of MPlayer is part of this. Take that into account while working on this project - the MPlayer/ffmpeg gang is well known for chasing GPL violators.
--Shachar
On Tue, Apr 15, 2008 at 3:50 AM, Lee Kwangwoo <kwlee@mtekvision.com> wrote:
-----Original Message----- From: mplayer-dev-eng-bounces@mplayerhq.hu [mailto:mplayer-dev-eng- bounces@mplayerhq.hu] On Behalf Of Compn Sent: Monday, April 14, 2008 9:17 PM To: mplayer-dev-eng@mplayerhq.hu Subject: Re: [MPlayer-dev-eng] Need a guide to implement a codec library using hardware video codec
On Mon, 14 Apr 2008 14:04:38 +0900, Lee Kwangwoo wrote:
Hello,
I'm porting the mplayer with a hardware video codec in a SoC.
which project is this for?
This project is for my company, which makes ARM based mobile
including hardware video codec.
It is capable of decoding H.264 and MPEG4. It can also encode
with such formats.
In the libmpcodecs/vd.c you explicitly note a comment - "do not add any new decoders here" for mpcodes_vd_drivers[]. So if I use the libavcodec/h264.c, should I replace that file with my own decoder file or add feature to support a hardware decoder with a define macro?
this just means that any new codecs should go into libavcodec from ffmpeg. if you are porting mplayer to a new hardware device, you can ignore this warning.
Thank you for your guide.
I think that I need to replace the functions, for example - decode_nal_units(), because the hardware decoder requires one
The modified code of the mplayer will be released under the GPL. But I have one question about codec library. If I write a library for a hardware device which can be used to control the hardware device commonly and which can also be used with mplayer, is it released under the GPL license? In my situation, I can not open the control code of the hardware device. If I must release the hardware codec library under the GPL license, I should rethink using mplayer code. Should I implement whole things? well.. get permission from my boss??? Let me know the right solution about this situation, please. Thank you. Kwangwoo Lee On Monday, April 21, 2008 9:25 AM, Raindel <shacharr@gmail.com> Wrote: processor frame frame
starting with nal header and output a decoded YUV420 frame.
Any comments and guide will be very helpful. Thank you,
Kwangwoo Lee
good luck
-compn
Thank you.
Kwangwoo Lee
_______________________________________________ MPlayer-dev-eng mailing list MPlayer-dev-eng@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
On Monday 21 April 2008 12:08:22 Lee Kwangwoo wrote:
The modified code of the mplayer will be released under the GPL. But I have one question about codec library. If I write a library for a hardware device which can be used to control the hardware device commonly and which can also be used with mplayer, is it released under the GPL license?
this is up to the author, but read below
In my situation, I can not open the control code of the hardware device. If I must release the hardware codec library under the GPL license, I should rethink using mplayer code. Should I implement whole things? well.. get permission from my boss???
the point is that if your library isn't gpl-compatible you can't distribute mplayer (that is gpl) with it
Let me know the right solution about this situation, please. Thank you.
easy: write your library as gpl
Kwangwoo Lee
please, use only interleaved posting here
On Mon, Apr 21, 2008 at 12:26:23PM +0200, Nico Sabbi wrote:
On Monday 21 April 2008 12:08:22 Lee Kwangwoo wrote:
The modified code of the mplayer will be released under the GPL. But I have one question about codec library. If I write a library for a hardware device which can be used to control the hardware device commonly and which can also be used with mplayer, is it released under the GPL license?
this is up to the author, but read below
In my situation, I can not open the control code of the hardware device. If I must release the hardware codec library under the GPL license, I should rethink using mplayer code. Should I implement whole things? well.. get permission from my boss???
the point is that if your library isn't gpl-compatible you can't distribute mplayer (that is gpl) with it
Well, if you dlopen your library, have a rather generic API for the library (maybe even a gpl'd variant of the library that provides the same features just e.g. via software emulation) and distribute MPlayer and that non-GPL library separately there is a good chance there is no problem (and there is no problem at all if you do not distribute), but for definitive answers you will have to ask a lawyer, sorry. Greetings, Reimar Döffinger
participants (3)
-
Lee Kwangwoo -
Nico Sabbi -
Reimar Döffinger