Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-06-29 Thread wm4
On Tue, 16 May 2017 07:45:14 + Saverio Blasi wrote: > Dear all, > > We would appreciate if you could let us know the procedure and expected > timeline for integration of our patch related with the Turing codec within > the ffmpeg project. FFmpeg is a project by

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-31 Thread Saverio Blasi
Hello, Could you please provide us with some feedback on this patch? Thanks, Saverio -Original Message- From: Saverio Blasi [mailto:saverio.bl...@bbc.co.uk] Sent: 09 May 2017 11:08 To: ffmpeg-devel@ffmpeg.org Cc: Saverio Blasi Subject: [PATCH v10] - Added

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-16 Thread Saverio Blasi
...@ffmpeg.org] On Behalf Of Saverio Blasi Sent: 11 May 2017 08:21 To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg Dear all, First of all thank you very much for all the help you pr

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-11 Thread Saverio Blasi
Dear all, First of all thank you very much for all the help you provided with this patch. We are now at the tenth iteration, and the patch greatly improved since the first time we submitted it. In fact most of the lines of code in the current version of the patch were suggested by you or

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-10 Thread Hendrik Leppkes
On Wed, May 10, 2017 at 8:14 PM, Paul B Mahol wrote: > On 5/10/17, Saverio Blasi wrote: >> Dear Michael, >> >> >> Why do you pass a single string of all options and then manually parse >> all options out of it instead of specifying the options each in

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-10 Thread Paul B Mahol
On 5/10/17, Saverio Blasi wrote: > Dear Michael, > > >> Why do you pass a single string of all options and then manually parse > all options out of it instead of specifying the options each in teh AVOption > array ? > > We prefer to pass a single string so that we can be

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-10 Thread Saverio Blasi
Dear Michael, >> Why do you pass a single string of all options and then manually parse all >> options out of it instead of specifying the options each in teh AVOption >> array ? We prefer to pass a single string so that we can be more flexible how we then parse it and what to do with it.

Re: [FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-10 Thread Michael Niedermayer
On Tue, May 09, 2017 at 10:08:17AM +, Saverio Blasi wrote: > - 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

[FFmpeg-devel] [PATCH v10] - Added Turing codec interface for ffmpeg

2017-05-09 Thread Saverio Blasi
- 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