On Fri, Mar 29, 2019, 00:16 Yufei He wrote:
> On 03/28/2019 04:18 PM, Dennis Mungai wrote:
> > On Thu, 28 Mar 2019 at 22:40, Nicolas George wrote:
> >
> >> No need to Cc me, I am subscribed to the list.
> >>
> >> Yufei He (12019-03-28):
> >>> In windows, we need provide the interface library
On 03/28/2019 04:18 PM, Dennis Mungai wrote:
> On Thu, 28 Mar 2019 at 22:40, Nicolas George wrote:
>
>> No need to Cc me, I am subscribed to the list.
>>
>> Yufei He (12019-03-28):
>>> In windows, we need provide the interface library mvM264.lib to our
>>> customers so that they can build. But
On Thu, 28 Mar 2019 at 22:40, Nicolas George wrote:
> No need to Cc me, I am subscribed to the list.
>
> Yufei He (12019-03-28):
> > In windows, we need provide the interface library mvM264.lib to our
> > customers so that they can build. But driver installation of the card
> > does not have the
On 28.03.2019 13:40, Yufei He wrote:
> On 03/27/2019 11:35 AM, Nicolas George wrote:
>
> Yufei He (12019-03-27):
>
>
> Here is the fixed patch for a new H.264 codec with Matrox M264 card.
>
> It calls the default library from the card's driver installation.
> Please review.
>
>
>
> You are still
No need to Cc me, I am subscribed to the list.
Yufei He (12019-03-28):
> In windows, we need provide the interface library mvM264.lib to our
> customers so that they can build. But driver installation of the card
> does not have the interface library. It just install mvM264.dll.
>
> We call
On 03/28/2019 10:00 AM, Jean-Baptiste Kempf wrote:
>
> On Thu, 28 Mar 2019, at 13:41, Yufei He wrote:
>> In windows, we need provide the interface library mvM264.lib to our
>> customers so that they can build. But driver installation of the card
>> does not have the interface library. It just
2019-03-28 13:40 GMT+01:00, Yufei He :
> In windows, we need provide the interface library mvM264.lib
And you should.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe,
On Thu, 28 Mar 2019, at 13:41, Yufei He wrote:
> In windows, we need provide the interface library mvM264.lib to our
> customers so that they can build. But driver installation of the card
> does not have the interface library. It just install mvM264.dll.
Why does mvM264.dll return 0 Google
On 03/27/2019 11:35 AM, Nicolas George wrote:
Yufei He (12019-03-27):
Here is the fixed patch for a new H.264 codec with Matrox M264 card.
It calls the default library from the card's driver installation.
Please review.
You are still using programmatic dynamic linking instead of normal
2019-03-27 16:30 GMT+01:00, Yufei He :
> Here is the fixed patch for a new H.264 codec with Matrox
> M264 card.
Please do not send another version of this patch that doesn't
add the non-free requirement in configure (or open-source
your library).
Carl Eugen
Yufei He (12019-03-27):
> Here is the fixed patch for a new H.264 codec with Matrox M264 card.
>
> It calls the default library from the card's driver installation.
> Please review.
You are still using programmatic dynamic linking instead of normal
dynamic linking, and you have not given a good
fre 2019-03-15 klockan 18:45 +0100 skrev Nicolas George:
> Yufei He (12019-03-15):
> > I did not find a better way to make this work.
>
> It exists: make your client libraries GPL-compatible.
I second this
/Tomas
___
ffmpeg-devel mailing list
On Thu, Mar 14, 2019 at 05:55:41PM +, Yufei He wrote:
> Hi
>
> Here is the patch for a new H.264 codec with Matrox m264 card.
>
> Please review.
>
> Thanks.
>
> Yufei.
>
>
> Changelog |1
> configure |2
> libavcodec/Makefile |2
>
On Fri, 15 Mar 2019, Ronald S. Bultje wrote:
Hi guys,
On Thu, Mar 14, 2019 at 1:55 PM Yufei He wrote:
Hi
Here is the patch for a new H.264 codec with Matrox m264 card.
I want to bring up again that this library is closed-source. I don't think
FFmpeg should link to closed-source
Hi,
On Fri, Mar 15, 2019 at 2:19 PM BIGLER Don (Framatome) <
don.big...@framatome.com> wrote:
> >Yufei He (12019-03-15):
> >> I did not find a better way to make this work.
>
> >It exists: make your client libraries GPL-compatible.
>
> Or alternatively creating open-source headers that allow the
>Yufei He (12019-03-15):
>> I did not find a better way to make this work.
>It exists: make your client libraries GPL-compatible.
Or alternatively creating open-source headers that allow the m264 drivers to be
used similar to NVidia's Video Codec SDK:
https://github.com/FFmpeg/nv-codec-headers
Yufei He (12019-03-15):
> I did not find a better way to make this work.
It exists: make your client libraries GPL-compatible.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list
Hi Jean-Baptiste
Sorry for the complexity and confusion to so many people involved on
this new patch.
We have been working on this for 4 months because some of our big
customers on internet business have been asking Matrox to make our M264
card to support FFmpeg on h.264 transcoding, esp on
On Fri, 15 Mar 2019, at 15:02, Tomas Härdin wrote:
> > +#ifdef _WIN32
> > +lib_handle = dlopen("mvM264Ffmpeg.dll", RTLD_LAZY);
> > +#else
> > +lib_handle = dlopen("libmvM264Ffmpeg.so", RTLD_LAZY);
> > +#endif
>
> Still dlopen() I see. You should link to these libraries
Hi guys,
On Thu, Mar 14, 2019 at 1:55 PM Yufei He wrote:
> Hi
>
> Here is the patch for a new H.264 codec with Matrox m264 card.
>
I want to bring up again that this library is closed-source. I don't think
FFmpeg should link to closed-source software in its public mainline
version. Matrox is
tor 2019-03-14 klockan 17:55 + skrev Yufei He:
> Hi
>
> Here is the patch for a new H.264 codec with Matrox m264 card.
>
> Please review.
> --- a/libavcodec/codec_desc.c
> +++ b/libavcodec/codec_desc.c
> @@ -1705,7 +1705,6 @@ static const AVCodecDescriptor
> codec_descriptors[] = {
>
21 matches
Mail list logo
