Re: [FFmpeg-devel] [PATCH] avcodec: add IMM5 decoder

2019-07-16 Thread Hendrik Leppkes
On Tue, Jul 16, 2019 at 3:26 PM James Almer wrote: > > > +.priv_data_size = sizeof(IMM5Context), > > +.caps_internal = FF_CODEC_CAP_INIT_THREADSAFE | > > + FF_CODEC_CAP_INIT_CLEANUP, > > You could set DR1, and set both h264_avctx->get_buffer2 and >

Re: [FFmpeg-devel] [PATCH] avfilter: add rawdump filter

2019-07-10 Thread Hendrik Leppkes
On Wed, Jul 10, 2019 at 12:13 PM Fu, Linjie wrote: > > > -Original Message- > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > > Of Paul B Mahol > > Sent: Wednesday, July 10, 2019 15:55 > > To: FFmpeg development discussions and patches > de...@ffmpeg.org> > >

Re: [FFmpeg-devel] [PATCH] lavc/videotoolboxenc: add hdr10, linear, hlg color transfer function for videotoolboxenc

2019-07-10 Thread Hendrik Leppkes
On Wed, Jul 10, 2019 at 4:23 AM Dennis Mungai wrote: > > On Wed, Jul 10, 2019, 03:05 Aman Gupta wrote: > > > On Wed, Jun 26, 2019 at 4:25 AM wrote: > > > > > From: Limin Wang > > > > > > Below is the testing ffmpeg command for the setting: > > > ./ffmpeg -i input.ts -c:v hevc_videotoolbox

Re: [FFmpeg-devel] [PATCH 2/2] lavc/vaapi_decode: recreate hw_frames_ctx without destroy va_context

2019-07-07 Thread Hendrik Leppkes
On Sun, Jul 7, 2019 at 6:41 AM Linjie Fu wrote: > > VP9 allows resolution changes per frame. Currently in VAAPI, resolution > changes leads to va context destroy and reinit. This will cause > reference frame surface lost and produce garbage. > > As libva allows re-create surface separately

Re: [FFmpeg-devel] [PATCH] avcodec: Implement DM PAR Muxer/Demuxer

2019-07-05 Thread Hendrik Leppkes
On Fri, Jul 5, 2019 at 10:53 PM Tom Needham <06needh...@gmail.com> wrote: > > Samples are Available from > > https://transfernow.net/131xk9g4u0jt > > Signed-off-by: Thomas Needham <06needh...@gmail.com> > --- > Changelog |1 + > configure |7 + >

Re: [FFmpeg-devel] [PATCH] avutil: add av_memcpy() to avoid undefined behavior with NULL, NULL, 0

2019-07-04 Thread Hendrik Leppkes
On Thu, Jul 4, 2019 at 8:45 PM Michael Niedermayer wrote: > > On Wed, Jul 03, 2019 at 12:50:59PM +0200, Hendrik Leppkes wrote: > > On Wed, Jul 3, 2019 at 10:46 AM Michael Niedermayer > > wrote: > > > > > > On Wed, Jul 03, 2019 at 09:4

Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add myself to the AMF section

2019-07-03 Thread Hendrik Leppkes
On Thu, Jul 4, 2019 at 12:42 AM Lynne wrote: > > NAK for reasons said on IRC For everyones benefit, why don't you actually formulate your reasons here instead of asking people to piece them together from some chat history, that way people can actually understand or respond to them. I, for one,

Re: [FFmpeg-devel] [PATCH] avutil: add av_memcpy() to avoid undefined behavior with NULL, NULL, 0

2019-07-03 Thread Hendrik Leppkes
On Wed, Jul 3, 2019 at 10:46 AM Michael Niedermayer wrote: > > On Wed, Jul 03, 2019 at 09:41:41AM +0200, Reimar Döffinger wrote: > > > > > > On 03.07.2019, at 08:29, Michael Niedermayer wrote: > > > > > On Tue, Jul 02, 2019 at 08:42:43PM -0300, James Almer wrote: > > >> On 7/2/2019 5:56 PM,

Re: [FFmpeg-devel] [PATCH 4/5] lavc/qsvdec: add ChromaFormat support for YUV422/YUV444

2019-06-27 Thread Hendrik Leppkes
On Thu, Jun 27, 2019 at 4:31 PM Linjie Fu wrote: > > Currently, ChromaFormat passed to libmfx is set to YUV42O by default. > > Modify to choose ChromaFormat according to fourCC. > > Signed-off-by: Linjie Fu > --- > libavcodec/qsvdec.c | 20 +++- > 1 file changed, 19

Re: [FFmpeg-devel] [PATCH 1/5] lavu/pixfmt: add Y210/AYUV/Y410 pixel formats

2019-06-27 Thread Hendrik Leppkes
On Fri, Jun 28, 2019 at 1:26 AM James Darnley wrote: > > On 2019-06-28 04:26, Linjie Fu wrote: > > Previously, media driver provided planar format(like 420 8 bit), but > > for HEVC Range Extension (422/444 8/10 bit), the decoded image is > > produced in packed format. > > > > Y210/AYUV/Y410 are

Re: [FFmpeg-devel] [PATCH, v3] lavc/pthread_frame: update context in child thread in multi-thread mode

2019-06-27 Thread Hendrik Leppkes
On Thu, Jun 27, 2019 at 1:56 PM Linjie Fu wrote: > > Currently in ff_thread_decode_frame, context is updated from child thread > to user thread, and user thread releases the context in avcodec_close() > when decode finishes. > > However, when resolution/format changes, ff_get_format is called,

Re: [FFmpeg-devel] [PATCH, RFC] lavc/phtread_frame: update context in child thread in multi-thread mode

2019-06-26 Thread Hendrik Leppkes
On Wed, Jun 26, 2019 at 9:06 AM Linjie Fu wrote: > > Currently in ff_thread_decode_frame, context is updated from child thread > to main thread, and main thread releases the context in avcodec_close() > when decode finishes. > > However, when resolution/format change in vp9, ff_get_format was

Re: [FFmpeg-devel] [PATCH, RFC] lavc/vp9dec: fix the multi-thread HWAccel decode error

2019-06-11 Thread Hendrik Leppkes
On Tue, Jun 11, 2019 at 9:20 AM Linjie Fu wrote: > > Fix the multi-thread HWAccel decode error for vp9. > > VP9 supports the resolution changing. In multi-thread mode, worker-threads > destroy and free the first created VAAPIDecodeContext if resolution change > happens and create new one. Other

Re: [FFmpeg-devel] [PATCH] libavfilter: Add derain filter Changelog

2019-06-10 Thread Hendrik Leppkes
On Mon, Jun 10, 2019 at 12:46 PM Xuewei Meng wrote: > > Signed-off-by: Xuewei Meng > --- > Changelog | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Changelog b/Changelog > index 1facc1fc46..b60aa5dd0b 100644 > --- a/Changelog > +++ b/Changelog > @@ -31,7 +31,7 @@

Re: [FFmpeg-devel] [PATCH V1 4/5] lavc/webvttenc: fix ffmpeg -h full can't display webvtt encoder

2019-06-04 Thread Hendrik Leppkes
On Tue, Jun 4, 2019 at 7:39 AM Jun Zhao wrote: > > From: Jun Zhao > > fix ffmpeg -h full can't display webvtt encoder > Whats the point of adding an empty help section without any options in it? If you use ffmpeg -encoders, for example, you'll get a full list of all supported encoders. An empty

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_zscale: add slice threading

2019-05-31 Thread Hendrik Leppkes
On Fri, May 31, 2019 at 5:32 PM Paul B Mahol wrote: > > On 5/31/19, Lynne wrote: > > > > > > > > May 31, 2019, 2:33 PM by one...@gmail.com: > > > >> On 5/31/19, Lynne wrote: > >> > >>> > >>> > >>> > >>> May 31, 2019, 2:16 PM by one...@gmail.com: > >>> > On 5/31/19, Lynne wrote: > >

Re: [FFmpeg-devel] [PATCH] libavcodec/vp9: Fix VP9 dynamic resolution changing decoding on VAAPI.

2019-05-28 Thread Hendrik Leppkes
On Tue, May 28, 2019 at 9:46 AM Yan Wang wrote: > > > On 5/28/2019 3:16 PM, Hendrik Leppkes wrote: > > On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote: > >> When the format change, the VAAPI context cannot be destroyed. > >> Otherwise, the reference frame surfac

Re: [FFmpeg-devel] [PATCH] libavcodec/vp9: Fix VP9 dynamic resolution changing decoding on VAAPI.

2019-05-28 Thread Hendrik Leppkes
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote: > > When the format change, the VAAPI context cannot be destroyed. > Otherwise, the reference frame surface will lost. > > Signed-off-by: Yan Wang > --- > libavcodec/decode.c | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git

Re: [FFmpeg-devel] [PATCH] swresample/swresample: check for invalid sample rates

2019-05-25 Thread Hendrik Leppkes
On Sat, May 25, 2019 at 5:58 PM Michael Niedermayer wrote: > > On Fri, May 24, 2019 at 06:05:42PM +0200, Paul B Mahol wrote: > > Signed-off-by: Paul B Mahol > > --- > > libswresample/swresample.c | 8 > > 1 file changed, 8 insertions(+) > > > > diff --git a/libswresample/swresample.c

Re: [FFmpeg-devel] [PATCH] avformat/cache - delete cache file after closing handle

2019-05-23 Thread Hendrik Leppkes
On Thu, May 23, 2019 at 9:55 PM Gyan wrote: > > > > On 24-05-2019 12:58 AM, Nicolas George wrote: > > Gyan (12019-05-24): > >> avpriv_io_delete will call the file protocol's delete which is guarded > >> with a header check, not done here. > > Do you have report of a build failure caused by

Re: [FFmpeg-devel] [PATCH] avutil/file_open: log temp filename

2019-05-22 Thread Hendrik Leppkes
On Wed, May 22, 2019 at 12:14 PM Gyan wrote: > > > > On 22-05-2019 03:29 PM, Hendrik Leppkes wrote: > > On Wed, May 22, 2019 at 11:51 AM Gyan wrote: > >> > >> > >> On 22-05-2019 02:29 PM, Hendrik Leppkes wrote: > >>> On Wed, May 22, 2019 a

Re: [FFmpeg-devel] [PATCH] avutil/file_open: log temp filename

2019-05-22 Thread Hendrik Leppkes
On Wed, May 22, 2019 at 11:51 AM Gyan wrote: > > > > On 22-05-2019 02:29 PM, Hendrik Leppkes wrote: > > On Wed, May 22, 2019 at 10:53 AM Gyan wrote: > >> > >> > >> On 22-05-2019 01:41 PM, Liu Steven wrote: > >>>> 在 2019年5月22日,下午3:10

Re: [FFmpeg-devel] [PATCH] avutil/file_open: log temp filename

2019-05-22 Thread Hendrik Leppkes
On Wed, May 22, 2019 at 10:53 AM Gyan wrote: > > > > On 22-05-2019 01:41 PM, Liu Steven wrote: > > > >> 在 2019年5月22日,下午3:10,Gyan 写道: > >> > >> > >> Helps users to identify temp files for a given instance. > >> > >> In the longer term, we should aim to clean up all temp files. > >> > >> Gyan > >>

Re: [FFmpeg-devel] [PATCH] mpeg12enc: Use all Closed Captions side data

2019-05-20 Thread Hendrik Leppkes
On Mon, May 20, 2019 at 9:44 AM Reimar Döffinger wrote: > > > > On 20.05.2019, at 09:23, Mathieu Duponchelle wrote: > > > Thanks :) > > > > On 5/19/19 7:00 PM, Devin Heitmueller wrote: > >> Hello Paul, > >> > >> On Fri, May 17, 2019 at 4:44 AM Paul B Mahol wrote: > >>> On 5/17/19, Mathieu

Re: [FFmpeg-devel] [PATCH] Populate MPEG2TS codec_tag using ff_codec_movvideo_tags/ff_codec_movaudio_tags (av4cc) rather than the PES stream_type. For MPEG2TS files containing h264, ffprobe currently

2019-05-16 Thread Hendrik Leppkes
On Thu, May 16, 2019 at 6:12 PM Damien Lévin wrote: > > Thanks Hendrik, > > The documentation from the AVCodecParameters codec_tag changed here (and > not AVCodecContext which you are referring to) seems pretty explicit about > being an AVI fourcc. So I'm not sure I understand why setting the PES

Re: [FFmpeg-devel] [PATCH] "assert(a && b)" --> "assert(a); assert(b)" for more precise diagnostics, except for libformat

2019-05-15 Thread Hendrik Leppkes
On Wed, May 15, 2019 at 9:21 PM Adam Richter wrote: > > On Tue, May 14, 2019 at 6:48 PM myp...@gmail.com wrote: > > > > On Wed, May 15, 2019 at 7:01 AM Hendrik Leppkes wrote: > > > > > > On Tue, May 14, 2019 at 11:25 PM Adam Richter > > > wrote:

Re: [FFmpeg-devel] [PATCH] avcodec/qtrle: return last frame even if unchanged

2019-05-15 Thread Hendrik Leppkes
On Wed, May 15, 2019 at 8:41 PM Michael Niedermayer wrote: > > Fixes: Ticket7880 > > Signed-off-by: Michael Niedermayer > --- > libavcodec/qtrle.c| 27 +-- > tests/ref/fate/qtrle-8bit | 1 + > 2 files changed, 26 insertions(+), 2 deletions(-) > > diff --git

Re: [FFmpeg-devel] [PATCH] Populate MPEG2TS codec_tag using ff_codec_movvideo_tags/ff_codec_movaudio_tags (av4cc) rather than the PES stream_type. For MPEG2TS files containing h264, ffprobe currently

2019-05-15 Thread Hendrik Leppkes
On Wed, May 15, 2019 at 6:15 PM Damien Levin wrote: > > --- > libavformat/mpegts.c | 9 +++-- > tests/ref/fate/concat-demuxer-simple2-lavf-ts | 4 ++-- > 2 files changed, 9 insertions(+), 4 deletions(-) > > diff --git a/libavformat/mpegts.c b/libavformat/mpegts.c >

Re: [FFmpeg-devel] [PATCH] "assert(a && b)" --> "assert(a); assert(b)" for more precise diagnostics, except for libformat

2019-05-14 Thread Hendrik Leppkes
On Tue, May 14, 2019 at 11:25 PM Adam Richter wrote: > > Consider, for example, if you agree that columnization makes this range check > more recognizable in a glance and makes it easier to spot what the bounds are > (the sixteen space indentation is taken from the code in which it appeared): > >

Re: [FFmpeg-devel] [PATCH 2/2] Revert "lavf/utils: Allow url credentials to contain a slash."

2019-05-14 Thread Hendrik Leppkes
On Tue, May 14, 2019 at 10:34 PM Marton Balint wrote: > > > > On Sun, 5 May 2019, Carl Eugen Hoyos wrote: > > > Am So., 5. Mai 2019 um 20:51 Uhr schrieb Marton Balint : > >> > >> This reverts commit dd06f022b07438d650c82255dff16908ba04244a. > >> > >> Fixes ticket #7871 and reopens ticket #7816. >

Re: [FFmpeg-devel] [DECISION] Project policy on closed source components

2019-05-13 Thread Hendrik Leppkes
On Mon, May 13, 2019 at 10:53 PM Carl Eugen Hoyos wrote: > > > Release branches provide a guarantee of API, ABI and feature > > stability. > > And we sadly did not always hold that guarantee=-( Mistakes have been made. We shall strive to be better in the future, and not use them as an excuse to

Re: [FFmpeg-devel] [DECISION] Project policy on closed source components

2019-05-13 Thread Hendrik Leppkes
On Mon, May 13, 2019 at 10:37 PM Carl Eugen Hoyos wrote: > > Am Mo., 13. Mai 2019 um 22:32 Uhr schrieb James Almer : > > > > On 5/13/2019 5:23 PM, Carl Eugen Hoyos wrote: > > > Am Mo., 13. Mai 2019 um 22:18 Uhr schrieb James Almer : > > >> > > >> On 5/13/2019 5:13 PM, Carl Eugen Hoyos wrote: > >

Re: [FFmpeg-devel] [PATCH v2] libavutil: add an FFT & MDCT implementation

2019-05-13 Thread Hendrik Leppkes
On Mon, May 13, 2019 at 8:57 AM Reimar Döffinger wrote: > > On 13.05.2019, at 04:54, Pedro Arthur wrote: > > > Em dom, 12 de mai de 2019 às 18:11, Hendrik Leppkes > > escreveu: > >> > >> On Sun, May 12, 2019 at 11:05 PM Carl Eugen Hoyos > >> wr

Re: [FFmpeg-devel] [PATCH v2] libavutil: add an FFT & MDCT implementation

2019-05-12 Thread Hendrik Leppkes
On Sun, May 12, 2019 at 11:05 PM Carl Eugen Hoyos wrote: > > But seriously: We are of course not allowed to remove copyright > statements, no matter if we consider them relevant or not. > Please provide a source for such claims. - Hendrik ___

Re: [FFmpeg-devel] [PATCH v2] libavutil: add an FFT & MDCT implementation

2019-05-12 Thread Hendrik Leppkes
On Sun, May 12, 2019 at 10:38 PM Carl Eugen Hoyos wrote: > > Am So., 12. Mai 2019 um 22:37 Uhr schrieb Paul B Mahol : > > > > On 5/12/19, Carl Eugen Hoyos wrote: > > > Am Fr., 10. Mai 2019 um 17:15 Uhr schrieb Lynne : > > >> > > >> Patch updated again. > > >> Made some more cleanups to the

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

2019-05-06 Thread Hendrik Leppkes
On Tue, May 7, 2019 at 1:39 AM Hendrik Leppkes wrote: > > On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer > wrote: > > > > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: > > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > >

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

2019-05-06 Thread Hendrik Leppkes
On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer wrote: > > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote: > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > > > > I don't think it is a good idea to drop frames from CFR input just because > > they > > are

Re: [FFmpeg-devel] [PATCH]lavf/utils: Do not read "@" without ":" as user name separator

2019-05-05 Thread Hendrik Leppkes
On Sun, May 5, 2019 at 9:47 PM Carl Eugen Hoyos wrote: > > Am So., 5. Mai 2019 um 21:18 Uhr schrieb Hendrik Leppkes > : > > > > On Sun, May 5, 2019 at 9:08 PM Carl Eugen Hoyos wrote: > > > > > > Hi! > > > > > > Attac

Re: [FFmpeg-devel] [PATCH 1/2] Revert "avcodec/qtrle: Do not output duplicated frames on insufficient input"

2019-05-05 Thread Hendrik Leppkes
On Sun, May 5, 2019 at 8:51 PM Marton Balint wrote: > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6. > > I don't think it is a good idea to drop frames from CFR input just because > they > are duplicated, that can cause issues for API users expecting CFR input. Also > it can

Re: [FFmpeg-devel] [PATCH]lavf/utils: Do not read "@" without ":" as user name separator

2019-05-05 Thread Hendrik Leppkes
On Sun, May 5, 2019 at 9:08 PM Carl Eugen Hoyos wrote: > > Hi! > > Attached patch fixes ticket #7871 without re-introducing #7816. > There is no patch here. However, please note that its perfectly valid to have a username without a password (ie. an @ without a ":") - while it is not valid to

Re: [FFmpeg-devel] [PATCH v2] lavf/h264: Add support for raw h264 stream from Arecont camera, fixes ticket #5154

2019-05-04 Thread Hendrik Leppkes
On Sat, May 4, 2019 at 10:52 AM Shivam Goyal wrote: > > The improved patch is for ticket #5154. > > Support for Raw h264 stream from Arecont Camera. > > Suggest any changes required. > The format-name based check in ff_raw_read_partial_packet is really iffy. You can setup a specific read

Re: [FFmpeg-devel] [PATCH] avformat/mov: set AVFMT_SEEK_TO_PTS flag

2019-05-02 Thread Hendrik Leppkes
On Thu, May 2, 2019 at 7:42 PM Sasi Inguva wrote: > > Looks good to me. We were already doing PTS based seeking in MOV demuxer > (although it's not perfect). > There are several problems with the MOV approach however. You cannot look at AVStream->index_entries, take a timestamp of such an index,

Re: [FFmpeg-devel] [DECISION] Project policy on closed source components

2019-04-29 Thread Hendrik Leppkes
On Mon, Apr 29, 2019 at 8:35 PM Marton Balint wrote: > We can't really change this for the better unless there is a somewhat > "recognized" authority which has the power to make decisions, rules, and > enforce them. > > I hoped that this can be the voting comitte. The voting commitee is pretty

Re: [FFmpeg-devel] [PATCH] avformat/aacdec: account for small frame sizes.

2019-04-29 Thread Hendrik Leppkes
On Mon, Apr 29, 2019 at 2:39 PM Menno de Gier wrote: > > Some ADTS files have a first frame that's shorter than the 10 bytes that > are being read while checking for ID3 tags. > > Fixes #7271 > James already send another patch for this issue - https://patchwork.ffmpeg.org/patch/12913/ - which

Re: [FFmpeg-devel] [PATCH] avformat/mux: skip parameter and pts checks for data muxer

2019-04-28 Thread Hendrik Leppkes
On Sun, Apr 28, 2019 at 11:57 AM Michael Niedermayer wrote: > > On Sat, Apr 27, 2019 at 10:01:53AM +0530, Gyan wrote: > > > > > > On 27-04-2019 01:32 AM, Michael Niedermayer wrote: > > >On Fri, Apr 26, 2019 at 06:38:37PM +0530, Gyan wrote: > > >> mux.c |9 - > > >> 1 file changed, 8

Re: [FFmpeg-devel] [PATCH 2/3] avfilter: add audio upsample filter

2019-04-25 Thread Hendrik Leppkes
On Thu, Apr 25, 2019 at 7:25 PM Nicolas George wrote: > > Paul B Mahol (12019-04-25): > > I did reacted. It plays well with negotiation. > > I missed that part, sorry. But it did not address my concern. > > > Can you be more specific what exactly you mean by "plays well with > > sample rate

Re: [FFmpeg-devel] Patchwork attribution

2019-04-19 Thread Hendrik Leppkes
On Fri, Apr 19, 2019 at 8:23 PM Lou Logan wrote: > > On Thu, 18 Apr 2019 18:01:27 -0400 > "Lou Logan" wrote: > > > > But we can certainly give it a try if you like. I'm not sure how patchwork > > will handle it. > > (Didn't realize my webmail client wasn't actually wrapping my text > although

Re: [FFmpeg-devel] [PATCH] tests: don't include TARGET_PATH in the sample path needlessly

2019-04-19 Thread Hendrik Leppkes
On Fri, Apr 5, 2019 at 12:06 AM James Almer wrote: > > On 4/3/2019 7:17 PM, Hendrik Leppkes wrote: > > The transcode() helper function will already prepend the TARGET_PATH to > > the sample path, if its a relative path. This avoids an issue on > > Windows, where the relati

Re: [FFmpeg-devel] Patchwork attribution

2019-04-18 Thread Hendrik Leppkes
On Thu, Apr 18, 2019 at 9:04 PM Lou Logan wrote: > > On Thu, Apr 18, 2019, at 4:51 AM, Hendrik Leppkes wrote: > > > > Whoever setup this ML sender rewriting thing should probably look into > > options to also re-write the patch content and add a "From:" line i

Re: [FFmpeg-devel] Patchwork attribution

2019-04-18 Thread Hendrik Leppkes
On Thu, Apr 18, 2019 at 3:31 PM Gyan wrote: > > > > On 18-04-2019 06:13 PM, Hendrik Leppkes wrote: > > On Thu, Apr 18, 2019 at 12:41 PM Gyan wrote: > >> Ok. Then shouldn't it assign 'Sam John via ffmpeg-devel' as the author? > >> It did do that for 'Oliver C

Re: [FFmpeg-devel] [PATCH]lavc/alac: Make a variable unsigned

2019-04-18 Thread Hendrik Leppkes
On Thu, Apr 18, 2019 at 2:54 PM Lauri Kasanen wrote: > > On Thu, 18 Apr 2019 13:53:37 +0200 > Carl Eugen Hoyos wrote: > > > Hi! > > > > Attached patch silences a warning that is shown with some gcc versions. > > It pokes my style sense to have different things in the sizeof() and > the var. How

Re: [FFmpeg-devel] Patchwork attribution

2019-04-18 Thread Hendrik Leppkes
On Thu, Apr 18, 2019 at 12:41 PM Gyan wrote: > > > > On 18-04-2019 03:25 PM, Timo Rothenpieler wrote: > > On 18/04/2019 09:49, Gyan wrote: > >> > >> Patchwork can incorrectly assign ownership. See > >> https://patchwork.ffmpeg.org/patch/12680/ > >> > >> The author is Sam John as identified by

Re: [FFmpeg-devel] [PATCH V1 2/2] lavf: bump version/add Changelog entry when cleanup applehttp

2019-04-16 Thread Hendrik Leppkes
On Tue, Apr 16, 2019 at 10:58 AM Carl Eugen Hoyos wrote: > > 2019-04-16 10:52 GMT+02:00, myp...@gmail.com : > > On Tue, Apr 16, 2019 at 4:42 PM Hendrik Leppkes wrote: > >> > >> On Tue, Apr 16, 2019 at 7:57 AM Jun Zhao wrote: > >> > > >> >

Re: [FFmpeg-devel] [PATCH V1 2/2] lavf: bump version/add Changelog entry when cleanup applehttp

2019-04-16 Thread Hendrik Leppkes
On Tue, Apr 16, 2019 at 7:57 AM Jun Zhao wrote: > > From: Jun Zhao > > commit abfeba9 "lavf/hls: Cleanup the applehttp" missed > the version bump and Changelog entry. > > Signed-off-by: Jun Zhao > --- > Changelog |1 + > libavformat/version.h |2 +- > 2 files changed, 2

Re: [FFmpeg-devel] [PATCH v2] lavf/rtsp.c: Fix stimeout option not applied on http tunnel

2019-04-15 Thread Hendrik Leppkes
On Mon, Apr 15, 2019 at 12:46 PM Carl Eugen Hoyos wrote: > > 2019-04-15 9:42 GMT+02:00, Liu Steven : > > > > > >> 在 2019年4月11日,下午12:03,Liu Steven 写道: > >> > >> > >> > >>> 在 2019年4月11日,上午11:55,Jun Li 写道: > >>> ... > >>> > >>> Ping. > >> LGTM > > > > Pushed > > Who wrote the patch that you

Re: [FFmpeg-devel] [PATCH] avcodec: add drop_changed_frames

2019-04-15 Thread Hendrik Leppkes
On Mon, Apr 15, 2019 at 8:17 AM Gyan wrote: > > > > On 15-04-2019 12:17 AM, James Almer wrote: > > On 4/14/2019 3:29 PM, Hendrik Leppkes wrote: > >> On Sun, Apr 14, 2019 at 6:50 PM Gyan wrote: > >>> Implemented this patch > >>> http://www.ffmpe

Re: [FFmpeg-devel] [PATCH] avcodec: add drop_changed_frames

2019-04-14 Thread Hendrik Leppkes
On Sun, Apr 14, 2019 at 6:50 PM Gyan wrote: > > Implemented this patch > http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-March/241733.html > > > in libavcodec as suggested by Michael > This sure adds a lot of additional fields to the main struct for a rather specialized feature, that I

Re: [FFmpeg-devel] [PATCH] libavcodec/libdav1d: add libdav1d_get_format method to call ff_get_format

2019-04-12 Thread Hendrik Leppkes
On Sat, Apr 13, 2019 at 1:17 AM Lukas Rusak wrote: > > On Thu, 2019-04-11 at 21:03 +0200, Hendrik Leppkes wrote: > > On Thu, Apr 11, 2019 at 7:47 PM Peter F > > wrote: > > > Hi, > > > > > > Am Do., 11. Apr. 2019 um 00:50 Uhr schrieb Hendrik Leppkes

Re: [FFmpeg-devel] [PATCH] libavcodec/libdav1d: add libdav1d_get_format method to call ff_get_format

2019-04-11 Thread Hendrik Leppkes
On Thu, Apr 11, 2019 at 7:47 PM Peter F wrote: > > Hi, > > Am Do., 11. Apr. 2019 um 00:50 Uhr schrieb Hendrik Leppkes > : > > > > On Thu, Apr 11, 2019 at 12:39 AM Lukas Rusak wrote: > > > > > > This will allow applications to properly init the de

Re: [FFmpeg-devel] [PATCH, v2] lavu/hwcontext_qsv: Fix the realign check for hwupload

2019-04-11 Thread Hendrik Leppkes
On Thu, Apr 11, 2019 at 4:51 AM Li, Zhong wrote: > > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > > Of Linjie Fu > > Sent: Wednesday, April 10, 2019 7:56 PM > > To: ffmpeg-devel@ffmpeg.org > > Cc: Fu, Linjie > > Subject: [FFmpeg-devel] [PATCH, v2] lavu/hwcontext_qsv:

Re: [FFmpeg-devel] [PATCH] libavcodec/libdav1d: add libdav1d_get_format method to call ff_get_format

2019-04-10 Thread Hendrik Leppkes
On Thu, Apr 11, 2019 at 12:39 AM Lukas Rusak wrote: > > This will allow applications to properly init the decoder in > cases where a hardware decoder is tried first and and software > decoder is tried after by calling the get_format callback. > > Even though there is no hardware pixel formats

Re: [FFmpeg-devel] [RFC PATCH] avformat/utils: always seek back after avformat_find_stream_info()

2019-04-10 Thread Hendrik Leppkes
On Wed, Apr 10, 2019 at 9:55 AM Aman Gupta wrote: > > On Tue, Apr 9, 2019 at 9:49 PM Hendrik Leppkes wrote: > > > On Wed, Apr 10, 2019 at 2:21 AM Aman Gupta wrote: > > > > > > From: Aman Gupta > > > > > > Previously, the initial seek position

Re: [FFmpeg-devel] [PATCH 2/2] avformat/mxfenc: support XAVC long gop

2019-04-09 Thread Hendrik Leppkes
On Wed, Apr 10, 2019 at 3:28 AM James Almer wrote: > > > >> Two thirds of SPS is not hard to implement, so i really don't understand > >> why you're so adamantly against it. > > > > I’m adamant about re-using code between libavcodec and libavformat. > > Re-using code is _good_ > > So lets do what

Re: [FFmpeg-devel] [RFC PATCH] avformat/utils: always seek back after avformat_find_stream_info()

2019-04-09 Thread Hendrik Leppkes
On Wed, Apr 10, 2019 at 2:21 AM Aman Gupta wrote: > > From: Aman Gupta > > Previously, the initial seek position was recorded into > old_offset at the beginning of avformat_find_stream_info(), > and passed into estimate_timings(). In the case of mpegts > with a known filesize, it was further

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/h264_parse: change prefix to avpriv for usage in avformat mxf muxer

2019-04-09 Thread Hendrik Leppkes
On Wed, Apr 10, 2019 at 12:44 AM Mark Thompson wrote: > > On 09/04/2019 23:14, Baptiste Coudurier wrote: > > --- > > libavcodec/h264_parse.c | 2 +- > > libavcodec/h264_parser.c | 2 +- > > libavcodec/h264_ps.c | 4 ++-- > > libavcodec/h264_ps.h | 4 ++-- > > libavcodec/h264dec.c |

Re: [FFmpeg-devel] [PATCH 2/2] avformat/mxfenc: support XAVC long gop

2019-04-09 Thread Hendrik Leppkes
On Wed, Apr 10, 2019 at 12:21 AM Baptiste Coudurier wrote: > +return 0; > +} > +init_get_bits(, tmp, tmp_size*8); > +ret = avpriv_h264_decode_seq_parameter_set(, > (AVCodecContext*)s, , 0); The AVCodecContext cast looks like a recipe for

Re: [FFmpeg-devel] [DECISION] Include more developers in the voting committee [#4]

2019-04-08 Thread Hendrik Leppkes
On Sat, Apr 6, 2019 at 6:42 PM Balint Marton wrote: > > Hi All > > Here is a call for the people in the voting committee [1] on the decision > of extending it. > > Using the same guidelines as in the second extension [2], the following > candidates were found: > > git log libav/master..master

Re: [FFmpeg-devel] [PATCH RFC v2 2/3] libavcodec: Add thumbnail output to vaapi_h264 decoder

2019-04-08 Thread Hendrik Leppkes
On Mon, Apr 8, 2019 at 10:54 AM Zachary Zhou wrote: > > This is sample code for reference > > HW support for decode+scaling in a single HW command (VDBOX+SFC). > The primary target usage is video analytics, but can be used playback, > transcoding, etc. > > For VAAPI - >

Re: [FFmpeg-devel] [PATCH V1] lavf/matroskaenc: Fix memory leak after write trailer

2019-04-04 Thread Hendrik Leppkes
On Thu, Apr 4, 2019 at 3:05 PM Andreas Rheinhardt via ffmpeg-devel wrote: > > And I think that this memleak in mkv_write_trailer() has a twin in > mkv_write_packet(): Audio frames are not written directly, but rather > put into storage in cur_audio_pkt via av_packet_ref(). But if the > preceding

Re: [FFmpeg-devel] [PATCH V1] lavf/matroskaenc: Fix memory leak after write trailer

2019-04-04 Thread Hendrik Leppkes
On Thu, Apr 4, 2019 at 11:25 AM Jun Zhao wrote: > > From: Jun Zhao > > Fix memory leak after write trailer for #7827 > > Signed-off-by: Jun Zhao > --- > libavformat/matroskaenc.c |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/libavformat/matroskaenc.c

[FFmpeg-devel] [PATCH] tests: don't include TARGET_PATH in the sample path needlessly

2019-04-03 Thread Hendrik Leppkes
The transcode() helper function will already prepend the TARGET_PATH to the sample path, if its a relative path. This avoids an issue on Windows, where the relative path check could fail. --- tests/fate/ffmpeg.mak | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [FFmpeg-devel] [PATCH] avformat/file: add seekable option to disallow seeking

2019-04-03 Thread Hendrik Leppkes
On Wed, Apr 3, 2019 at 10:42 PM Marton Balint wrote: > > Signed-off-by: Marton Balint > --- > doc/protocols.texi | 9 + > libavformat/file.c | 5 + > 2 files changed, 14 insertions(+) > > diff --git a/doc/protocols.texi b/doc/protocols.texi > index e1caa049a5..34967ff5e2 100644 >

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/h264_parse: change prefix to avpriv for usage in avformat mxf muxer

2019-04-03 Thread Hendrik Leppkes
On Wed, Apr 3, 2019 at 2:28 PM Carl Eugen Hoyos wrote: > > 2019-04-03 11:37 GMT+02:00, Hendrik Leppkes : > > > We prefer not to expose huge modules like this as avpriv, > > as it makes it part of the ABI > > (I am sure there are cases that are difficult to avoid, > w

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/h264_parse: change prefix to avpriv for usage in avformat mxf muxer

2019-04-03 Thread Hendrik Leppkes
On Wed, Apr 3, 2019 at 11:22 AM Baptiste Coudurier wrote: > > --- > libavcodec/cbs_h2645.c | 28 ++-- > libavcodec/extract_extradata_bsf.c | 4 ++-- > libavcodec/h2645_parse.c | 6 +++--- > libavcodec/h2645_parse.h | 6 +++--- >

Re: [FFmpeg-devel] [PATCH 10/15] avformat/matroskaenc: Avoid seeking when writing level 1 elements

2019-04-02 Thread Hendrik Leppkes
On Tue, Apr 2, 2019 at 3:36 PM Andreas Rheinhardt via ffmpeg-devel wrote: > @@ -383,8 +388,8 @@ static void end_ebml_master_crc32_preliminary(AVIOContext > *pb, AVIOContext **dyn > uint8_t *buf; > int size = avio_get_dyn_buf(*dyn_cp, ); > > +put_ebml_num(pb, size,

Re: [FFmpeg-devel] [PATCH 10/15] avformat/matroskaenc: Avoid seeking when writing level 1 elements

2019-04-02 Thread Hendrik Leppkes
On Tue, Apr 2, 2019 at 5:55 PM Andreas Rheinhardt via ffmpeg-devel wrote: > > Hello, > > thanks for taking a look at this. > > Hendrik Leppkes: > > On Tue, Apr 2, 2019 at 3:36 PM Andreas Rheinhardt via ffmpeg-devel > > wrote: > >> > >> Up unt

Re: [FFmpeg-devel] [PATCH 10/15] avformat/matroskaenc: Avoid seeking when writing level 1 elements

2019-04-02 Thread Hendrik Leppkes
On Tue, Apr 2, 2019 at 3:36 PM Andreas Rheinhardt via ffmpeg-devel wrote: > > Up until now, the writing process for level 1 elements (those elements > for which CRC-32 elements are written by default) was this in case the > output was seekable: Write the EBML ID, write an "unkown length" EBML >

Re: [FFmpeg-devel] [PATCH 4/5] x86/opusdsp: implement FMA3 accelerated postfilter and deemphasis

2019-04-02 Thread Hendrik Leppkes
On Mon, Apr 1, 2019 at 4:59 PM James Almer wrote: > > On 4/1/2019 9:13 AM, Lynne wrote: > > Mar 31, 2019, 11:49 PM by jamr...@gmail.com: > > > >> A float ret value needs to be in xmm0, and you swapped m0 with m2 on > >> Win64. This is the source of the fate failure. > >> > > Attached a patch to

Re: [FFmpeg-devel] [PATCH] fate: unbreak fate with custom binary names

2019-04-02 Thread Hendrik Leppkes
On Tue, Apr 2, 2019 at 1:27 PM Gyan wrote: > > I ran full fate and some tests failed as the ffmpeg binary wasn't found. > Suffixes weren't respected. Fixed. > > I can run fate only occasionally. Maybe one of the regular FATE > submitters could set a suffix (and extension) to keep a check on this.

Re: [FFmpeg-devel] There may be a bug for .mp4 reader.

2019-04-01 Thread Hendrik Leppkes
On Mon, Apr 1, 2019 at 7:21 PM Yufei He wrote: > > Hi > > There may be a bug for .mp4 reader. > > On decoding some ntsc mp4 files with my h.264 codec, from actvx I received, > > avctx->framerate.den is 100 > > avctx->framerate.num is 2997 > > avctx->pkt_timebase.num is 1 > avctx->pkt_timebase.den

Re: [FFmpeg-devel] [FFmpeg-cvslog] avcodec/libaomenc: fix default value for row-mt option

2019-03-30 Thread Hendrik Leppkes
On Sat, Mar 30, 2019 at 2:52 PM Gyan wrote: > > > > On 30-03-2019 06:09 PM, Moritz Barsnick wrote: > > On Sat, Mar 30, 2019 at 16:50:52 +0530, Gyan wrote: > >> And what are the semantics of the user setting row_mt or enable-intrabc > >> as -1? > > The user doesn't set -1, they set 0 or 1 as bool.

Re: [FFmpeg-devel] [PATCH] avcodec/get_bits: unbreak get_bits_le() with cached reader

2019-03-26 Thread Hendrik Leppkes
On Tue, Mar 26, 2019 at 11:32 AM Carl Eugen Hoyos wrote: > > 2019-03-26 11:13 GMT+01:00, Paul B Mahol : > > Signed-off-by: Paul B Mahol > > --- > > libavcodec/get_bits.h | 82 + > > libavcodec/utvideodec.c | 4 +- > > 2 files changed, 60 insertions(+),

Re: [FFmpeg-devel] [PATCH] swscale: Remove duplicated code

2019-03-25 Thread Hendrik Leppkes
On Mon, Mar 25, 2019 at 11:35 AM Lauri Kasanen wrote: > > On Mon, 25 Mar 2019 11:17:38 +0100 > Michael Niedermayer wrote: > > > On Sun, Mar 24, 2019 at 01:04:51PM +0200, Lauri Kasanen wrote: > > > In this function, the exact same clamping happens both in the if and > > > unconditionally. > > >

Re: [FFmpeg-devel] [PATCH v2] avfilter/src_movie: change the deprecate API to new decode api

2019-03-23 Thread Hendrik Leppkes
> > @@ -524,17 +522,22 @@ static int movie_push_frame(AVFilterContext *ctx, > > unsigned out_id) > > return AVERROR(ENOMEM); > > > > frame_type = st->st->codecpar->codec_type; > > -switch (frame_type) { > > -case AVMEDIA_TYPE_VIDEO: > > -ret =

Re: [FFmpeg-devel] [PATCH 1/2] avutil/opt: Add AV_OPT_TYPE_UINT16

2019-03-22 Thread Hendrik Leppkes
On Fri, Mar 22, 2019 at 4:01 PM wrote: > > From: Nick Renieris > > Signed-off-by: Nick Renieris > --- > libavutil/opt.c | 29 +++-- > libavutil/opt.h | 1 + > 2 files changed, 28 insertions(+), 2 deletions(-) > We really don't need this type. You can just change the

Re: [FFmpeg-devel] [PATCH v5] lavc/qsvenc: add BRC sliding window setting

2019-03-18 Thread Hendrik Leppkes
On Mon, Mar 18, 2019 at 7:29 AM Zhong Li wrote: > > WinBRCMaxAvgKbps is to specify maximum average bitrate over a > sliding window with size of WinBRCSize > > WinBRCMaxAvgKbps will be ignored in CBR mode and equal to TargetKbps. > How are these modes different to ffmpeg rc_max_rate in

Re: [FFmpeg-devel] Bug in YUV decoder

2019-03-15 Thread Hendrik Leppkes
On Fri, Mar 15, 2019 at 10:13 PM Ben Hutchinson wrote: > > Also, on another note, why don't we have yuvj410p as a video format? Each > chroma-subsampled versionof yuv (partial range YUV) format should have an > equivalent chroma-subsampled version of yuvj (full range yuv). This would > allow

Re: [FFmpeg-devel] [PATCH]lavc/qtrle: Do not use aligned writes for odd addresses.

2019-03-14 Thread Hendrik Leppkes
On Fri, Mar 15, 2019 at 12:26 AM Carl Eugen Hoyos wrote: > > 2019-03-15 0:13 GMT+01:00, Hendrik Leppkes : > > On Fri, Mar 15, 2019 at 12:05 AM Carl Eugen Hoyos > > wrote: > >> > >> Hi! > >> > >> Attached patch fixes the qtrle crash on sparc

Re: [FFmpeg-devel] [PATCH]lavc/qtrle: Do not use aligned writes for odd addresses.

2019-03-14 Thread Hendrik Leppkes
On Fri, Mar 15, 2019 at 12:05 AM Carl Eugen Hoyos wrote: > > Hi! > > Attached patch fixes the qtrle crash on sparc for me. > It should be fine in cases where the pointer is being incremented by an aligned amount, ie. writing 32 and incrementing by 4, or 64 and 8, etc. Are all of those required

Re: [FFmpeg-devel] fate/proresenc_aw : Add fate test for interlace and 444 encoding

2019-03-07 Thread Hendrik Leppkes
On Wed, Feb 27, 2019 at 6:05 PM Martin Vignali wrote: > > > works here > > > > > Pushed, thanks. > These tests fail on all FATE boxes. http://fate.ffmpeg.org/ Can you check that and fix it? - Hendrik ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Reconfigure resolution on-the-fly

2019-03-06 Thread Hendrik Leppkes
On Wed, Mar 6, 2019 at 3:57 PM Oliver Collyer wrote: > > diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h > index 0ce22ec4fa..7087f82ce1 100644 > --- a/libavcodec/avcodec.h > +++ b/libavcodec/avcodec.h > @@ -3357,6 +3357,12 @@ typedef struct AVCodecContext { > * - encoding: unused >

Re: [FFmpeg-devel] [PATCH] apedec: add ability to check CRC

2019-03-06 Thread Hendrik Leppkes
On Wed, Mar 6, 2019 at 2:18 PM Carl Eugen Hoyos wrote: > > 2019-03-06 12:22 GMT+01:00, Lynne : > > The CRC flag is only signalled once every few minutes but CRC is still > > always present so the patch uses the file version instead. > > CRC on 24-bit files wants non-padded samples so skip such

Re: [FFmpeg-devel] [PATCH] doc: add missing hyphen prefix

2019-02-22 Thread Hendrik Leppkes
On Fri, Feb 22, 2019 at 12:29 PM Nicolas George wrote: > > Lou Logan (12019-02-21): > > For consistency. Fixes #7740. > > > > Signed-off-by: Lou Logan > > I do not think this is correct: the dash is not part of the option name, > it is part of the Unix command-line tradition. For consistency, it

Re: [FFmpeg-devel] [PATCH]lavf/spdifenc: Use a more flexible buffer model for TrueHD/MAT

2019-02-21 Thread Hendrik Leppkes
On Thu, Feb 21, 2019 at 3:28 PM Carl Eugen Hoyos wrote: > > 2019-02-21 10:40 GMT+01:00, Hendrik Leppkes : > > > https://files.1f0.de/samples/incredibles2-truehd-bitstreaming.thd > > (TrueHD stream) > > https://files.1f0.de/samples/incredibles2-truehd-bitstreaming.pcm.

Re: [FFmpeg-devel] [PATCH]lavf/spdifenc: Use a more flexible buffer model for TrueHD/MAT

2019-02-21 Thread Hendrik Leppkes
On Fri, Feb 15, 2019 at 1:13 AM Carl Eugen Hoyos wrote: > > > - The distance between frames can be incredibly large in some streams, > > I've seen it be larger then one whole MAT frame, and the output works > > reliably (MAT start/middle/end codes need to be placed within the > > padding space,

Re: [FFmpeg-devel] [PATCH]lavf/spdifenc: Use a more flexible buffer model for TrueHD/MAT

2019-02-14 Thread Hendrik Leppkes
On Thu, Feb 14, 2019 at 8:11 PM Carl Eugen Hoyos wrote: > > Hi! > > I created attached patch with a lot of help from Hendrik, fixes ticket #7731. > Som general comments, since I can't replay inline in this mail client: - The pseudo-timestamps are unsigned 16-bit, personally I would make all

Re: [FFmpeg-devel] [FFmpeg-cvslog] avutil/cuda_check: avoid pointlessly exporting same symbol from two libraries

2019-02-14 Thread Hendrik Leppkes
On Thu, Feb 14, 2019 at 11:36 PM Carl Eugen Hoyos wrote: > >>> No, this entire mess with duplicated ff_ symbols is specifically to > >>> avoid having to include it in the ABI. > >> > >> But old libavcodec does not work with new libavutil now or am I wrong? > > > > Is that really a thing we expect

Re: [FFmpeg-devel] [PATCH]lavf/spdifenc: Use a more flexible buffer model for TrueHD/MAT

2019-02-14 Thread Hendrik Leppkes
On Thu, Feb 14, 2019 at 8:14 PM Carl Eugen Hoyos wrote: > > 2019-02-14 20:11 GMT+01:00, Carl Eugen Hoyos : > > > I created attached patch with a lot of help from Hendrik, fixes > > ticket #7731. > > I forgot: I still need help to fix the frame distance calculation, > how is the frame rate

Re: [FFmpeg-devel] [FFmpeg-cvslog] avutil/cuda_check: avoid pointlessly exporting same symbol from two libraries

2019-02-14 Thread Hendrik Leppkes
On Thu, Feb 14, 2019 at 4:51 PM Carl Eugen Hoyos wrote: > > > > > Am 14.02.2019 um 13:39 schrieb Timo Rothenpieler : > > > > ffmpeg | branch: master | Timo Rothenpieler | Fri > > Feb 8 22:47:01 2019 +0100| [15c6390139096b7e7634bf0f6aaab1cd8b3aa509] | > > committer: Timo Rothenpieler > > > >

Re: [FFmpeg-devel] [PATCH]lavf/spdifenc: Automatically insert truehd_core bitstream filter

2019-02-12 Thread Hendrik Leppkes
On Wed, Feb 13, 2019 at 2:57 AM Carl Eugen Hoyos wrote: > > 2019-02-13 0:47 GMT+01:00, Hendrik Leppkes : > > On Tue, Feb 12, 2019 at 12:54 PM Carl Eugen Hoyos > > wrote: > >> > >> 2019-02-12 12:37 GMT+01:00, Hendrik Leppkes : > >> > On Tue, Feb 12,

  1   2   3   4   5   6   7   8   9   10   >