on content
distribution for broadcasting applications using HEVC and provide an
alternative codec to ffmpeg. Clearly we were wrong.
We'll distribute the patch onto our website for those who are interested in
having Turing in FFmpeg and stop pestering you with new requests.
- This patch contains the changes required to interface the Turing codec
(http://turingcodec.org/) to ffmpeg
---
Changelog | 1 +
LICENSE.md | 1 +
configure | 6 +
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/libturing.c
This patch contains the changes required to interface the Turing codec
(http://turingcodec.org/) to ffmpeg
---
LICENSE.md | 1 +
configure | 6 +
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/libturing.c | 318 ++
> That's pretty old by now. Can you send a v4 patch set?
Sorry my bad, I've already sent a v4 on the 14/12. Do you want me to rebase the
patch to the latest commit on the branch master?
Re: On removal of malloc, free, etc. I think this v4 takes care of this as the
commit messages says.
Hello everyone,
Any news on the integration of the patch identified in the subject line?
Best regards,
Matteo
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> > It has. It points to the position in the options buffer which is going to be
> filled with the command line being parsed. So it's not redundant.
>
> Then what does buffer_filled do?
It keeps track on the number of characters written in the options buffer so
far. I appreciate this could have
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) with ffmpeg. The patch was modified to address
the comments in the review as follows:
- Added a pkg-config file to list all dependencies required by
libturing. This should address the issue pointed out
> Missing error handling, and maybe overflow handling. Also, we don't use
> malloc/realloc/free, but av_malloc/av_realloc/av_free. I'm not sure why we
> do this (it doesn't have much of a justification for realloc at least), but
> it's
> probably better to be consistent.
Ok, point taken on the av
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) to ffmpeg. The patch was modified to address
the comments in the review as follows:
- Added a pkg-config file to list all dependencies required by
libturing. This should address the issue pointed out b
Please discard this message, I've sent the wrong patch. Sorry
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
- The libturing.pc file is added in CMAKE_INSTALL_PREFIX/lib/pkgconfig
and contains some CMAKE variables which get expanded during
installation
- Fixed some editorial typos and trailing space
- Fixed version numbering in the std output
- Added function to check for binary option as passed when
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) to ffmpeg. The patch was modified to address
the comments in the review as follows:
- Added a pkg-config file to list all dependencies required by
libturing. This should address the issue pointed out b
> I hope it copes well with multiple definitions of the same option, like the
> last
> overwriting the previous ones.
The latest stable version of the Turing codec deals correctly with multiple
definitions of the same option.
Matte
eed=value). The reason why we decided to go for this
option is because we want to be as less invasive as possible so that if we
decide to change the name for a given option the changes will be transparent to
FFmpeg.
Matteo Naccari
> -Original Message-
> From: ffmpeg-devel [mailto:ff
f options passed by the
user for the Turing codec.
Matteo Naccari
-
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless
specifically stated.
If you have received it in
error,
s suggested
Matteo Naccari
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Hendrik Leppkes
> Sent: 18 November 2016 18:51
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PA
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) to ffmpeg. The patch was modified to address
the comments in the review as follows:
- Added a pkg-config file to list all dependencies required by
libturing. This should address the issue pointed out b
> Can't currently test on macOS as libturing doesn't have macOS support
> (https://github.com/bbc/turingcodec/issues/5), but it is being worked on
> (supposedly), so it may make sense to wait until then before this is applied.
>
Ok we'll try to get this sorted out and then get back to you. Thanks
- The Turing codec is an open source HEVC encoder licensed under GPLv2
- More information at http://turingcodec.org/
---
LICENSE.md | 1 +
configure | 5 ++
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/libturing.c | 229 +++
fmpeg_build/lib-L/path/to/turing/source/code/build/release/boost"
--bindir="$HOME/bin" --enable-gpl --enable-nonfree --enable-libturing
Many thanks for your help!
Best regards,
Matteo
--
Matteo Naccari, Ph.D., Senior Research Engineer BBC R&D, Centre House, London,
20 matches
Mail list logo
