On 4/20/2017 12:34 PM, Vittorio Giovara wrote:
Change input type of the type->str function and return a proper
error code for the str->type function.
---
Similar reasoning to the previous patch.
Vittorio
libavutil/stereo3d.c | 6 +++---
libavutil/stereo3d.h | 2 +-
2 files changed, 4
Also refactor a little and improve error messages to make failure
cases easier to understand.
---
Removed the useless device reference.
Example use:
./avconv -y -init_hw_device vaapi -hwaccel vaapi -hwaccel_output_format vaapi
-i in.mp4 -an -vf
Use the flags argument of av_hwframe_ctx_create_derived() to pass the
mapping flags which will be used on allocation. Also, set the format
and hardware context on the allocated frame automatically - the user
should not be required to do this themselves.
---
Added APIchanges + version bump.
This is something of a hack. It allocates a new hwframe context for
the target format, then maps it back to the source link and overwrites
the input link hw_frames_ctx so that the previous filter will receive
the frames we want from ff_get_video_buffer(). It may fail if
the previous filter
---
Kindof hacky, but a simple way to make hardware transcode with dxva2 work in
avconv without needing the hw_device_ctx support to convert it to the
hw-generic tooling.
Slightly unfortunate that the pixfmt is called "dxva_vld", though.
Example:
./avconv.exe -y -init_hw_device dxva2 -hwaccel
Factorises out existing surface initialisation code to reuse.
---
No change.
libavutil/hwcontext_qsv.c | 174 +-
1 file changed, 142 insertions(+), 32 deletions(-)
diff --git a/libavutil/hwcontext_qsv.c b/libavutil/hwcontext_qsv.c
index
Some frames contexts are not usable without additional format-specific
state in hwctx. This change adds new functions frames_derive_from and
frames_derive_to to initialise this state appropriately when deriving
a frames context which will require it to be set.
---
map_frames_to/from renamed to
This only supports one device globally, but more can be used by
passing them with input streams in hw_frames_ctx or by deriving new
devices inside a filter graph with hwmap.
---
Added doc.
avtools/avconv.h| 1 +
avtools/avconv_filter.c | 10 --
avtools/avconv_opt.c| 21
---
Now uses frame context derivation, so should properly support DXVA2 (previously
it didn't look like a fixed-size pool, but that didn't actually matter for some
use-cases).
It feels like the MemId stuff should be done more consistently, but actually
every use is slightly different so the
---
Rearranged a bit to avoid some duplication.
libavutil/hwcontext_qsv.c | 113 ++
1 file changed, 84 insertions(+), 29 deletions(-)
diff --git a/libavutil/hwcontext_qsv.c b/libavutil/hwcontext_qsv.c
index 3409e9b97..46636ef9e 100644
---
It requires pthreads.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index e83a4cf697..dde172d011 100755
--- a/configure
+++ b/configure
@@ -4693,7 +4693,7 @@ if ! disabled pthreads && ! enabled w32threads; then
fi
enabled pthreads &&
-
On 4/6/17 6:14 PM, Luca Barbato wrote:
> The function is used to filter out ldflags arguments that may contain $.
> Update filter() as well to be consistent.
> ---
>
> Ping in form of updated patch.
>
> configure | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On 4/18/17 7:11 PM, Luca Barbato wrote:
> On 17/04/2017 18:04, Vittorio Giovara wrote:
>> On Mon, Apr 17, 2017 at 9:48 AM, Luca Barbato wrote:
>>> print_str() cannot print NULL.
>>>
>>> Bug-Id: 1040
>>> CC: libav-sta...@libav.org
>>> ---
>>> avtools/avprobe.c | 36
On 4/23/17 1:19 AM, Sean McGovern wrote:
> Bug-Id: 1013
> CC: libav-sta...@libav.org
> ---
> libavcodec/vc1dec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/vc1dec.c b/libavcodec/vc1dec.c
> index 89b4f4b..51745c1 100644
> --- a/libavcodec/vc1dec.c
> +++
14 matches
Mail list logo