[FFmpeg-devel] [V3 PATCH 0/3] Codec wrapper for librv11 and RMHD muxer/demuxer

Rostislav Pehlivanov atomnuker at gmail.com
Mon Apr 23 22:51:57 EEST 2018


On 23 April 2018 at 20:32, Paul B Mahol <onemda at gmail.com> wrote:

> On 4/23/18, Thilo Borgmann <thilo.borgmann at mail.de> wrote:
> > Am 23.04.18 um 03:36 schrieb James Almer:
> >> On 4/22/2018 6:43 PM, Paul B Mahol wrote:
> >>> On 4/22/18, Thilo Borgmann <thilo.borgmann at mail.de> wrote:
> >>>> Hi,
> >>>>
> >>>> V3 drops the MLTI part, no idea how it survived
> >>>> 02fff499362daedcdcb0a9cdd517257843600563 on our side...
> >>>> Also dropped audio override, could not get a sample requiring it.
> >>>>
> >>>> Adapted to current HEAD.
> >>>
> >>> I'm strongly against applying this to our tree.
> >>
> >> The de/muxing code can and should be applied as long as there are not
> >> technical limitations. They are native code and depend on nothing
> >> external.
> >>
> >> And regarding the decoder and encoder wrappers, you need to explain the
> >> reasons for your hard NAK...
> >
> > Yes Paul please do, and while you're on it, please add your thoughts
> about
> > making it good enough for our tree that come to your mind. I assume it is
> > not RV11 or its library wrapper for itself you don't like to see
> pushed...
>
> This will allow any random guy to send wrappers that supports any closed
> source
> solution.
>
> Yes, we have hardware stuff and other devices, but for decoders I
> strongly object
> to commit this wrapper for closed source solution.
>
> If we go to the closed source way, we may kill project right a way and
> remove all
> native code.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>

I agree.


More information about the ffmpeg-devel mailing list