On 11/15/17, Carl Eugen Hoyos wrote:
> 2017-11-15 17:26 GMT+01:00 Vittorio Giovara :
>
>> There is a stable release with this code, and it's a minor update,
>> not sure if it warrants a configure check, but I'll add it if requested.
>
> Does it compile without? Does configure succeed?
>
> The patc
2017-11-15 17:26 GMT+01:00 Vittorio Giovara :
> There is a stable release with this code, and it's a minor update,
> not sure if it warrants a configure check, but I'll add it if requested.
Does it compile without? Does configure succeed?
The patch must not lead to a situation where configure
pa
---
Now without mxf code >_>
There is a stable release with this code, and it's a minor update,
not sure if it warrants a configure check, but I'll add it if requested.
Vittorio
libavfilter/vf_zscale.c | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git
2017-11-15 1:56 GMT+01:00 Vittorio Giovara :
> @@ -2111,6 +2124,12 @@ static int mxf_parse_structural_metadata(MXFContext
> *mxf)
> st->codecpar->codec_id = container_ul->id;
> st->codecpar->width = descriptor->width;
> st->codecpar->height = descriptor-
On 11/15/2017 12:56 AM, Vittorio Giovara wrote:
> ---
> libavfilter/vf_zscale.c | 26 --
> libavformat/mxfdec.c| 20
> 2 files changed, 44 insertions(+), 2 deletions(-)
Accidental inclusion of MXF code?
Also, Does the minimum zimg version need to
---
libavfilter/vf_zscale.c | 26 --
libavformat/mxfdec.c| 20
2 files changed, 44 insertions(+), 2 deletions(-)
diff --git a/libavfilter/vf_zscale.c b/libavfilter/vf_zscale.c
index 09fd842fe5..7d048da1ef 100644
--- a/libavfilter/vf_zscale.c
+++ b/