On Tue, Mar 8, 2016 at 3:22 PM, Diego Biurrun wrote:
> libavutil/hwcontext_vdpau.c:305:37: warning: cast from pointer to integer of
> different size
> ---
> libavutil/hwcontext_vdpau.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavutil/hwcontext_vdpau.c b/liba
libavutil/hwcontext_vdpau.c:305:37: warning: cast from pointer to integer of
different size
---
libavutil/hwcontext_vdpau.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavutil/hwcontext_vdpau.c b/libavutil/hwcontext_vdpau.c
index faae5f8..e1545d5 100644
--- a/libavut
On Tue, Mar 8, 2016 at 11:55 AM, Diego Biurrun wrote:
> ---
> libavcodec/h264.c | 2 +-
> libavcodec/h264.h | 2 +-
> libavcodec/h264_slice.c | 4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
I'd use "internally public function" to avoid confusion with "public
api" in the
---
libavcodec/h264.c | 2 +-
libavcodec/h264.h | 2 +-
libavcodec/h264_slice.c | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/libavcodec/h264.c b/libavcodec/h264.c
index 0b5b6c2..e9c13cc 100644
--- a/libavcodec/h264.c
+++ b/libavcodec/h264.c
@@ -424,7 +424,7
On 08/03/16 10:38, Mark Thompson wrote:
> Something like:
>
> 2016-03-xx - xxx - lavu 55.y.z - pixfmt.h
> Deprecate all AV_PIX_FMT_VAAPI_* formats.
> Replaced by AV_PIX_FMT_VAAPI.
Seems good.
lu
___
libav-devel mailing list
libav-devel@libav.or
And properly reset the entries count when resetting the entries.
CC: libav-sta...@libav.org
Bug-Id: 929
---
There is a similar problem for other blocks, if you are ok
I'd add some sc->${count} = 0 for all of them.
And probably some block parsers should also have a av_free().
libavformat/mov.c
On 08/03/16 09:25, Diego Biurrun wrote:
> On Mon, Mar 07, 2016 at 11:21:45PM +, Mark Thompson wrote:
>> --- /dev/null
>> +++ b/libavutil/hwcontext_vaapi.c
>> @@ -0,0 +1,822 @@
>> +
>> +// On current Intel drivers, derive gives you memory which is very slow
>> +// to read normally. Assu
On Tue, Mar 08, 2016 at 10:34:12AM +0100, Hendrik Leppkes wrote:
> On Tue, Mar 8, 2016 at 10:20 AM, Diego Biurrun wrote:
> >> --- a/libavutil/pixdesc.c
> >> +++ b/libavutil/pixdesc.c
> >> @@ -1093,6 +1093,7 @@ static const AVPixFmtDescriptor
> >> av_pix_fmt_descriptors[AV_PIX_FMT_NB] = {
> >>
On 08/03/16 09:20, Diego Biurrun wrote:
> On Mon, Mar 07, 2016 at 11:21:00PM +, Mark Thompson wrote:
>> ---
>> libavcodec/h263dec.c | 2 +-
>> libavcodec/h264_slice.c | 2 +-
>> libavcodec/mpeg12dec.c | 2 +-
>> libavcodec/vaapi_h264.c | 2 +-
>> libavcodec/vaapi_mpeg2.c | 2 +-
>>
On Tue, Mar 8, 2016 at 10:20 AM, Diego Biurrun wrote:
>> --- a/libavutil/pixdesc.c
>> +++ b/libavutil/pixdesc.c
>> @@ -1093,6 +1093,7 @@ static const AVPixFmtDescriptor
>> av_pix_fmt_descriptors[AV_PIX_FMT_NB] = {
>> },
>> .flags = AV_PIX_FMT_FLAG_RGB,
>> },
>> +#if FF_API_
On Mon, Mar 07, 2016 at 11:21:45PM +, Mark Thompson wrote:
> --- /dev/null
> +++ b/libavutil/hwcontext_vaapi.c
> @@ -0,0 +1,822 @@
> +
> +// On current Intel drivers, derive gives you memory which is very slow
> +// to read normally. Assume for now that a user who asks for read access
On Mon, Mar 07, 2016 at 11:21:00PM +, Mark Thompson wrote:
> ---
> libavcodec/h263dec.c | 2 +-
> libavcodec/h264_slice.c | 2 +-
> libavcodec/mpeg12dec.c | 2 +-
> libavcodec/vaapi_h264.c | 2 +-
> libavcodec/vaapi_mpeg2.c | 2 +-
> libavcodec/vaapi_mpeg4.c | 4 ++--
> libavcode
Quoting wm4 (2016-03-07 21:34:34)
>
> Sure, and the examples also have to be updated. This stuff can be done
> later. First we should discuss whether we want to deprecate these
> functions at all yet.
I already stated my reasons for deprecating them now. Is anyone against?
--
Anton Khirnov
13 matches
Mail list logo
