Re: [FFmpeg-devel] avformat/mxfenc: SMPTE RDD 48:2018 Amd 1:2022 (FFV1 in MXF) support

let 1 open with no change than fixing no issue >> because we wouldn't be sure for 1 of the 2. > > I suspect we are lucky because 720i doesn't really exist in the real > world, and 576i and 480i are both multiples of 32. > > IMO mxfenc shouldn't lie, but looking a

Re: [FFmpeg-devel] [PATCH 1/3] avformat/mxfdec: SMPTE RDD 48:2018 support

ead_ffv1_sub_descriptor, sizeof(MXFFFV1SubDescriptor), > FFV1SubDescriptor }, > { { > 0x06,0x0e,0x2b,0x34,0x02,0x53,0x01,0x01,0x0d,0x01,0x01,0x01,0x01,0x01,0x3A,0x00 > }, mxf_read_track, sizeof(MXFTrack), Track }, /* Static Track */ > { { > 0x06,0x0e,0x2b,0x34,0x02,0x53,0x01,0x01,0x0d,

Re: [FFmpeg-devel] [PATCH v2] avcodec: Add dv marker bsf

> On Mar 12, 2022, at 1:09 PM, Michael Niedermayer > wrote: > > On Sat, Mar 12, 2022 at 10:11:52AM -0500, Dave Rice wrote: >> >> >>> On Mar 10, 2022, at 4:41 AM, Tobias Rapp wrote: >>> >>> On 09/03/2022 19:18, Michael Niederm

Re: [FFmpeg-devel] [PATCH v2] avcodec: Add dv marker bsf

...] > The filter options look nice to me now. Have not actually tested the > bitstream filter on DV files, though. I tested this and this works well for me. Here's a few samples that demonstrate the filter: ./ffmpeg -i https://samples.ffmpeg.org/archi

[FFmpeg-devel] Mailing list conduct

ourage one another, offer fair critical reviews, and work collaboratively towards rough consensus. Kind Regards, The CC James Almer Thilo Borgmann Carl Eugen Hoyos Jean-Baptiste Kempf Dave Rice ___ ffmpeg-

Re: [FFmpeg-devel] [PATCH] avformat/dv: always set audio packet duration

ted this patch and it does correct some errors. For instance, before this patch frame 3 of the output only offers half of the needed duration, so the resulting audio track is (1001/3)/2 shorter than the video. But after the patch, the video and audio outputs have the same length. ffmpeg -i

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

Hi Marton, > On Feb 23, 2021, at 3:07 PM, Dave Rice wrote: > >> On Feb 23, 2021, at 2:42 PM, Marton Balint wrote: >> >> On Sat, 20 Feb 2021, Dave Rice wrote: >> >>> Hi, >>> >>>> On Oct 31, 2020, at 5:15 PM, Marton Balint >&g

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

> On Feb 23, 2021, at 2:42 PM, Marton Balint wrote: > > > > On Sat, 20 Feb 2021, Dave Rice wrote: > >> Hi, >> >>> On Oct 31, 2020, at 5:15 PM, Marton Balint >> <mailto:c...@passwd.hu>> wrote: >>> On Sat, 31 Oct 2020, Da

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

Hi, > On Oct 31, 2020, at 5:15 PM, Marton Balint <mailto:c...@passwd.hu>> wrote: > On Sat, 31 Oct 2020, Dave Rice wrote: >>> On Oct 31, 2020, at 3:47 PM, Marton Balint >> <mailto:c...@passwd.hu>> wrote: >>> On Sat, 31 Oct 2020, Dave Rice wrote: &g

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

> On Nov 14, 2020, at 7:14 PM, Marton Balint wrote: > > On Fri, 6 Nov 2020, Michael Niedermayer wrote: > >> On Wed, Nov 04, 2020 at 10:44:56PM +0100, Marton Balint wrote: >>> >>> >>> On Wed, 4 Nov 2020, Michael Niedermayer wrote: >>> we have "millisecond" based formats, rounded timestam

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

e > rate jittering / some droped samples ? > Its important to know as in one instance its the timestamps that need > adjustment > while in the other the samples need adjustment > ATM its down to the user to figure out on a file by file base how to deal or > ignore this. Instead i

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

de | Max divergence as percentage of frame duration NTSC 48000 | 0.3742511235 NTSC 44100 | 0.3869807536 NTSC 32000 | 0.3929636797 PAL 48000 | 0.3125 PAL 44100 | 0.3117913832 PAL 32000 | 0.3125 0.3929636797 is the max divergence, at least according to the spec’s limit of the allowable

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

> On Oct 31, 2020, at 5:15 PM, Marton Balint wrote: > On Sat, 31 Oct 2020, Dave Rice wrote: >>> On Oct 31, 2020, at 3:47 PM, Marton Balint wrote: >>> On Sat, 31 Oct 2020, Dave Rice wrote: >>>> Hi Marton, >>>>> On Oct 31, 2020, at 12:5

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

> On Oct 31, 2020, at 3:47 PM, Marton Balint wrote: > On Sat, 31 Oct 2020, Dave Rice wrote: > >> Hi Marton, >> >>> On Oct 31, 2020, at 12:56 PM, Marton Balint wrote: >>> Fixes out of sync timestamps in ticket #8762. >> >> Although Michael’

Re: [FFmpeg-devel] [PATCH] avformat/dv: fix timestamps of audio packets in case of dropped corrupt audio frames

flags:0 ts: 0.88 > ret: 0 st: 0 flags:1 dts: 0.88 pts: 0.88 pos:3168000 > size:144000 > ret: 0 st: 0 flags:1 ts:-0.24 > ret: 0 st: 0 flags:1 dts: 0.00 pts: 0.00 pos: 0 > size:144000 > -ret: 0 st: 1 flags:0 ts: 2

Re: [FFmpeg-devel] [PATCH 1/2] avformat/dv: allow returning damaged audio

> On Aug 3, 2020, at 5:16 PM, Michael Niedermayer > wrote: > > On Mon, Aug 03, 2020 at 10:38:21PM +0200, Marton Balint wrote: >> >> >> On Sun, 2 Aug 2020, Dave Rice wrote: >> >>> >>> >>>> On Aug 1, 2020, at 5:26 PM, Marton

Re: [FFmpeg-devel] [PATCH 1/2] avformat/dv: allow returning damaged audio

> On Aug 1, 2020, at 5:26 PM, Marton Balint wrote: > > > > On Sat, 1 Aug 2020, Michael Niedermayer wrote: > >> On Sat, Aug 01, 2020 at 07:28:53PM +0200, Marton Balint wrote: >>> >>> >>> On Sat, 1 Aug 2020, Michael Niedermayer wrote: >>> Fixes: Ticket8762 Signed-off-by: Michael N

Re: [FFmpeg-devel] [PATCH] avformat/mov: fix memleak

Hi Andreas, > On Jun 27, 2020, at 5:09 PM, Andreas Rheinhardt > wrote: > > Zhao Zhili: >> Remove the check on dv_demux since dv_fctx will leak if allocate >> dv_demux failed. >> --- >> libavformat/mov.c | 7 +++ >> 1 file changed, 3 insertions(+), 4 deletions(-) >> >> diff --git a/libavform

Re: [FFmpeg-devel] [PATCH v1] avfilter: add colorstats, colorrgbstats, coloryuvstats video filter

> On Dec 27, 2019, at 10:49 AM, Paul B Mahol wrote: > > That is because signalstats is doing more stuff. signalstats includes options to disable some of the calculations, possibly this could be extended to enable or disable the ones you want. It would be interesting to merge these ideas rathe

Re: [FFmpeg-devel] [PATCH] avformat/movenc: always write a colr atom

Hi James, > On Jul 16, 2019, at 9:47 AM, James Almer wrote: > > -{ "write_colr", "Write colr atom (Experimental, may be renamed or > changed, do not use from scripts)", 0, AV_OPT_TYPE_CONST, {.i64 = > FF_MOV_FLAG_WRITE_COLR}, INT_MIN, INT_MAX, AV_OPT_FLAG_ENCODING_PARAM, > "movflags" },

Re: [FFmpeg-devel] [PATCHv3 1/2] ffplay: options to specify window position

From caa816d70e69f85d49556ff341addab24ebcd942 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Mon, 1 Oct 2018 17:07:44 -0400 Subject: [PATCH 1/2] ffplay: options to specify window position --- doc/ffplay.texi | 4 fftools/ffplay.c | 6 +- 2 files changed, 9 insertions(+), 1 deletion

Re: [FFmpeg-devel] [PATCH 2/2] avdevice/sdl2 : add option to set window position

> On Oct 2, 2018, at 1:32 AM, Gyan wrote: > > On Tue, Oct 2, 2018 at 2:47 AM Dave Rice wrote: > >> Allows arrangement of multiple windows such as: >> ffmpeg -re -f lavfi -i mandelbrot -f sdl -window_x 1 -window_y 1 >> mandelbrot -vf waveform,format=yuv420p -f

[FFmpeg-devel] [PATCHv2 1/2] ffplay: options to specify window position

Thanks Marton for comments. Here is a revision to the first patch. From 3fe6a9e5279a280af9a06843621737ddc44529cc Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Mon, 1 Oct 2018 17:07:44 -0400 Subject: [PATCHv2 1/2] ffplay: options to specify window position --- doc/ffplay.texi | 4

[FFmpeg-devel] [PATCH 2/2] avdevice/sdl2 : add option to set window position

00438983c96b5db227b9975a2c160fc6aac5219d Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Mon, 1 Oct 2018 17:08:35 -0400 Subject: [PATCH 2/2] avdevice/sdl2 : add option to set window position --- libavdevice/sdl2.c | 9 + 1 file changed, 9 insertions(+) diff --git a/libavdevice/sdl2.c b/libavdevice/sdl2.c

[FFmpeg-devel] [PATCH 1/2] ffplay: options to specify window position

From 14d6833b564bd672613d50ecc4c3ede1768eee37 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Mon, 1 Oct 2018 17:07:44 -0400 Subject: [PATCH 1/2] ffplay: options to specify window position --- fftools/ffplay.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/fftools

Re: [FFmpeg-devel] [PATCH] avformat/matroskaenc: add reserve free space option

/version.h > +++ b/libavformat/version.h > @@ -33,7 +33,7 @@ > // Also please add any ticket numbers that you believe might be affected here > #define LIBAVFORMAT_VERSION_MAJOR 58 > #define LIBAVFORMAT_VERSION_MINOR 18 > -#define LIBAVFORMAT_VERSION_MICRO 100 > +#define LIBAVFORMAT_VERSION_MICRO 101 > > #define LIBAVFORMAT_VE

Re: [FFmpeg-devel] Register for VDD 2018 conference

forked alternative to the work on FFV1 version 4 by the IETF cellar working group. https://twitter.com/retokromer/status/884030201050648576?s=21 Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On Jun 7, 2018, at 5:01 PM, Marton Balint wrote: > > On Thu, 7 Jun 2018, Dave Rice wrote: > > [...] > >> >> Before I only tested with vitc but now have a serial cable connected as well >> and found a source tape that has distinct values for LTC and VI

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On Jun 7, 2018, at 12:12 PM, Dave Rice wrote: > > >> On Jun 6, 2018, at 5:32 PM, Marton Balint wrote: >> >> On Wed, 6 Jun 2018, Dave Rice wrote: >> >>>> On Jun 6, 2018, at 4:50 PM, Marton Balint wrote: >>>> On Mon, 4 Jun 2018, Dave

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On Jun 6, 2018, at 5:32 PM, Marton Balint wrote: > > On Wed, 6 Jun 2018, Dave Rice wrote: > >>> On Jun 6, 2018, at 4:50 PM, Marton Balint wrote: >>> On Mon, 4 Jun 2018, Dave Rice wrote: >>>>>> In my testing the timecode value set here has

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On Jun 6, 2018, at 4:50 PM, Marton Balint wrote: > > On Mon, 4 Jun 2018, Dave Rice wrote: > >> >>>> In my testing the timecode value set here has corrected been associated >>>> with the first video frame (maintaining the timecode-to-first-frame

Re: [FFmpeg-devel] [PATCH 1/2] avdevice/decklink_dec: use a custom memory allocator

> On Jun 5, 2018, at 1:17 PM, Marton Balint wrote: > > On Tue, 5 Jun 2018, Dave Rice wrote: > >>> On Jun 4, 2018, at 4:21 PM, Marton Balint wrote: >>> >>> The default memory allocator is limited in the max number of frames >>> available, &g

Re: [FFmpeg-devel] [PATCH 1/2] avdevice/decklink_dec: use a custom memory allocator

> On Jun 4, 2018, at 4:21 PM, Marton Balint wrote: > > The default memory allocator is limited in the max number of frames available, > and therefore caused frame drops if the frames were not freed fast enough. I’ve been testing this patchset today. Yesterday I was occasionally getting “Deckli

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On Jun 4, 2018, at 12:24 PM, Marton Balint wrote: > > On Fri, 1 Jun 2018, Dave Rice wrote: > >>> On May 31, 2018, at 5:29 PM, Marton Balint wrote: >>> On Thu, 31 May 2018, Jonathan Morley wrote: >>>> Thank you for the clarification, Dave. It migh

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On May 31, 2018, at 5:29 PM, Marton Balint wrote: > > On Thu, 31 May 2018, Jonathan Morley wrote: > >> Thank you for the clarification, Dave. It might be that the Blackmagic >> approach to collecting timecode doesn’t work for that one source because it >> is in the horizontal space (HANC) i

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

avg: 65536.000 > I will add that to the next patch, but it might be a minute before I get to > it. Thank you again for taking a look. > > I guess we got really lucky in our use case. > > Thanks, > Jon > >> On May 31, 2018, at 12:39 PM, Dave Rice wrote: >> &

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

umptions or changes either. I’ve replicated it with Matroska which simply moves the timecode into metadata as a string. > Please keep me posted. Meanwhile I will look into what could be causing all > the error chatter. Thanks! > Thanks, > Jon > >> On May 31, 2018, at 7:5

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

l the Media Express captures are Non-Drop Frame and all the ffmpeg captures are Drop Frame, so one has to be wrong. I’ll try to find a source that can provide a known df and ndf signal to determine which is correct. Thanks for the update, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On May 25, 2018, at 17:15, Jonathan Morley wrote: > > Thank you for trying it out, Dave. > > 1) Can you please tell me more about how you tested? J30 digibeta deck playing a Betacam SP with SDI to an Ultrastudio 3D with ffmpeg with your patch and configured with decklink. > 2) Did you ru

Re: [FFmpeg-devel] [PATCH] Limited timecode support for lavd/decklink

> On May 25, 2018, at 1:08 PM, Jonathan Morley wrote: > >> On May 25, 2018, at 8:32 AM, Marton Balint > > wrote: >> >> On Fri, 25 May 2018, Jonathan Morley wrote: >> >>> I apologize in advance for the formatting of this message. My mail >>> configuration impeded my effor

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

consensus to appoint a CoC committee and as needed the CoC committee finds consensus (as a small group) on how to respond to concerns from the community and to implement the CoC. b) the larger ffmpeg community finds consensus on how to implement the CoC directly each time there’s a concern fro

Re: [FFmpeg-devel] [RFC] Exporting virtual timelines as stream side data

> On Mar 27, 2018, at 5:16 PM, wm4 wrote: > > On Tue, 27 Mar 2018 16:45:23 -0400 > Dave Rice mailto:d...@dericed.com>> wrote: > >>> On Mar 27, 2018, at 4:33 PM, wm4 wrote: >>> >>> On Tue, 27 Mar 2018 16:11:11 -0400 >>> Dave R

Re: [FFmpeg-devel] [RFC] Exporting virtual timelines as stream side data

> On Mar 27, 2018, at 4:33 PM, wm4 wrote: > > On Tue, 27 Mar 2018 16:11:11 -0400 > Dave Rice wrote: > >>> On Mar 27, 2018, at 4:01 PM, Derek Buitenhuis >>> wrote: >>> >>> On 3/27/2018 8:52 PM, Rostislav Pehlivanov wrote: >>>>

Re: [FFmpeg-devel] [RFC] Exporting virtual timelines as stream side data

themselves - and I figured > some would argue that point. +1 I’m willing to contribute what information or samples would be needed to help with Matroska support with virtual timelines. IMO, this would be a valuable feature to have in ffmpeg. Dave Rice _

Re: [FFmpeg-devel] [Cellar] [PATCH] avcodec/ffv1: Support for RGBA64 and GBRAP16

very close to a last call and submission to the IESG (chairs are welcome to offer other opinions ;) ). So while I encourage resolution to these pull requests, it seems we have a good system to manage concurrent work on both FFV1 goals of the charter. Kind Regards, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] ffmpeg.c: use sigterm_handler with sigpipe

gt; SIGPIPE. This patch has been working for me and ffmpeg terminates cleanly with SIGPIPE with a valid output (moov atom written with mov or cues/seekhead written with mkv). Not sure if I understand well the disadvantage of this patch. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] ffmpeg.c: use sigterm_handler with sigpipe

From 0faa2954010feb8428542fc33aa81e898a280c88 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 11 Jan 2018 15:52:36 -0500 Subject: [PATCH] ffmpeg.c: use sigterm_handler with sigpipe Based on a suggestion by Moritz Barsnick at http://ffmpeg.org/pipermail/ffmpeg-user/2018-January/038549.html

Re: [FFmpeg-devel] [PATCH] avfilter/avf_showwaves: add draw grid support

; pixstep; s++) { > +out->data[0][(yskip + j * ystep - 1) * > out->linesize[0] + x * pixstep + s] = showwaves->grid_rgba[s]; > +} > +} > + > +yskip += j * ystep; > +} > +} > } > return 0; > } > -- > 2.11.0 Seems interesting but do the gridlines convey any meaning? Perhaps a flags value too similar to waveform that should label the lines in dB or as a float. Also perhaps worth adjustment the placement of the gridlines depending on a scale (log vs lin). Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov

> On Nov 20, 2017, at 11:22 AM, Derek Buitenhuis > wrote: > > On 11/20/2017 3:19 PM, Dave Rice wrote: >> TN2162 requires a colr atom for uncompressed yuv (including v210, v308, >> v408, etc) in mov, so I'd prefer to write it in this case. Note that the >&g

Re: [FFmpeg-devel] [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov

> On Nov 20, 2017, at 9:55 AM, Derek Buitenhuis > wrote: > > On 11/20/2017 2:50 PM, Dave Rice wrote: >> I am hesitant to see write_colr option removed since the guesswork used here >> https://github.com/FFmpeg/FFmpeg/blob/8f4702a93f87f9f76563e80f1ae2141a40029d9d/li

Re: [FFmpeg-devel] [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov

> On Nov 20, 2017, at 9:01 AM, Carl Eugen Hoyos wrote: > > 2017-11-20 2:24 GMT+01:00 James Almer <mailto:jamr...@gmail.com>>: >> On 11/18/2017 11:19 PM, Dave Rice wrote: >>> From 41da5e48f8788b85dd7a382030bb2866c506cc03 Mon Sep 17 00:00:00 2001 >>> F

Re: [FFmpeg-devel] [PATCH] avfilter/vf_tile: add queue option

8:overlap=7:queue=1' filmstrip.mkv @end example Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH 4/4] fate: add v210 mov test

From fe9e3aa13ecf3b4cb81f279696bcc21602662e7a Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Sat, 18 Nov 2017 20:32:33 -0500 Subject: [PATCH 4/4] fate: add v210 mov test --- tests/fate/vcodec.mak | 4 tests/ref/vsynth/vsynth1-mov-v210 | 4 2 files changed, 8 insertions

[FFmpeg-devel] [PATCH 1/4] avformat/movenc: correct ImageDescription for uncompressed ycbcr

26d9ca470f104d8448000b13c2cc97b8fc5c15ba Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 16 Nov 2017 11:53:32 -0500 Subject: [PATCH 1/4] avformat/movenc: correct ImageDescription for uncompressed ycbcr Per https://developer.apple.com/library/content/technotes/tn2162/_index.html . --- libavformat/movenc.c | 20

[FFmpeg-devel] [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov

From 41da5e48f8788b85dd7a382030bb2866c506cc03 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Sat, 18 Nov 2017 20:31:27 -0500 Subject: [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit

[FFmpeg-devel] [PATCH 2/4] avformat/movenc: write clap atom for uncompressed yuv in mov

From e9079167c199791e652fe9cd3550333b819a8a9a Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 16 Nov 2017 11:29:06 -0500 Subject: [PATCH 2/4] avformat/movenc: write clap atom for uncompressed yuv in mov fixes 6145 --- libavformat/movenc.c | 19 +++ 1 file changed, 19

Re: [FFmpeg-devel] [PATCH] avformat/movenc: correct ImageDescription depth for v210 v410

> On Nov 16, 2017, at 6:08 PM, Carl Eugen Hoyos wrote: > > 2017-11-16 17:54 GMT+01:00 Dave Rice : > >> +if (track->mode == MODE_MOV && track->par->codec_id == AV_CODEC_ID_V410) >> +avio_wb16(pb, 0x18); >> +else if (

Re: [FFmpeg-devel] [PATCH] movenc: write clap tag

> On Nov 16, 2017, at 11:30 AM, Dave Rice wrote: > >> On Jul 9, 2017, at 7:26 PM, Dave Rice wrote: >> >>> On Jul 7, 2017, at 7:06 PM, Derek Buitenhuis >>> wrote: >>> >>> On 7/7/2017 10:13 PM, James Almer wrote: >>>> I

[FFmpeg-devel] [PATCH] avformat/movenc: correct ImageDescription depth for v210 v410

162/_index.html>. From 47def189b270ac93245e002580463b254daf8484 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 16 Nov 2017 11:53:32 -0500 Subject: [PATCH] avformat/movenc: correct ImageDescription depth for v210 v410 Per https://developer.apple.com/library/content/technotes/tn2162/_inde

Re: [FFmpeg-devel] [PATCH] movenc: write clap tag

> On Jul 9, 2017, at 7:26 PM, Dave Rice wrote: > > >> On Jul 7, 2017, at 7:06 PM, Derek Buitenhuis >> wrote: >> >> On 7/7/2017 10:13 PM, James Almer wrote: >>> Isn't this necessary only for files with raw video? As is, this box >>&

Re: [FFmpeg-devel] [PATCH RFC] libavdevice/decklink: Add support for EIA-708 output over SDI

tps://twitter.com/ajaprez/status/910100436224499713>. I’m glad to hear that handling other VANC data is in the works, I’m particularly interested in VITC and EIA-608 with inputs. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

> On Oct 18, 2017, at 3:07 PM, Marton Balint wrote: > > On Mon, 16 Oct 2017, Dave Rice wrote: > >> Hi, >> >> I tested this with my Ultrastudio Express and confirmed that I'm getting >> higher bit depth recordings with the abitscope filter. This patch

Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

> On Oct 17, 2017, at 3:30 PM, Douglas Marsh wrote: > > On 2017-10-17 09:10, Dave Rice wrote: > >>>> -audio_depth .D.. audio bitdepth (from 0 to 1) >>>> (default 16bits) >>>>16bits .D.. > >

Re: [FFmpeg-devel] decklink 24/32 bit question

only defines two BMDAudioSampleType values: bmdAudioSampleType16bitInteger and bmdAudioSampleType32bitInteger. I don't think there's an easy way to support a 24 bit input here. Generally in this case I've used bmdAudioSampleType32bitInteger and then encode it at pcm_s24le. Dave Rice ___

Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

> On Oct 17, 2017, at 11:48 AM, Paul B Mahol wrote: > > On 10/17/17, Moritz Barsnick wrote: >> On Tue, Oct 17, 2017 at 11:12:46 -0400, Dave Rice wrote: >> >>> Thanks for pointing me in the right direction. I am attaching an >>> updated patch below; how

Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

Hi Moritz, > On Oct 17, 2017, at 10:40 AM, Moritz Barsnick wrote: > > On Tue, Oct 17, 2017 at 09:22:27 -0400, Dave Rice wrote: >>>> --- a/libavdevice/decklink_dec_c.c >>>> +++ b/libavdevice/decklink_dec_c.c >>>> @@ -72,6 +72,7 @@ static cons

Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

Hi Paul, > On Oct 16, 2017, at 3:56 PM, Paul B Mahol wrote: > > On 10/16/17, Dave Rice mailto:d...@dericed.com>> wrote: >> Hi, >> >> I tested this with my Ultrastudio Express and confirmed that I'm getting >> higher bit depth recordings with the ab

[FFmpeg-devel] [PATCH] libavdevice/decklink: 32 bit audio support

http://trac.ffmpeg.org/ticket/6708 and is partly based upon Georg Lippitisch's earlier draft at https://ffmpeg.org/pipermail/ffmpeg-devel/2015-January/167649.html. From fbf2bd40471c8fa35374bb1a51c51a3f4f36b992 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 12 Oct 2017 13:40:59 -0400 Subje

[FFmpeg-devel] [PATCH] libavcodec: fix field_order labelling

below I suggest using “top first (interleaved)” for TB and “bottom first (interleaved)” for BT. Comments? From de871b3fa891fa0ae6856461c1f8305cc889cde7 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Sat, 12 Aug 2017 12:30:43 -0400 Subject: [PATCH] libavcodec: fix field_order labelling --- libavcodec/

Re: [FFmpeg-devel] [PATCH] ffmpeg: fix setting field_order during muxing

id/DTS40013070-CH1-TNTAG10-THE__FIEL__IMAGEDESCRIPTION_EXTENSION__FIELD_FRAME_INFORMATION (Figure 4) From testing we have found that ffmpeg's behavior here is matching some Apple mov muxers in the assignment of a field order value, so the patch may be unneeded or the reason may need

Re: [FFmpeg-devel] [PATCH] movenc: write clap tag

mit. If the patch only impacts “uncompressed Y´CbCr” would any fate updates be needed? Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] movenc: write clap tag

> On Jul 7, 2017, at 11:32 AM, Derek Buitenhuis > wrote: > > On 7/7/2017 3:20 AM, Dave Rice wrote: >> Resolves https://trac.ffmpeg.org/ticket/6145 and writes a clap atom that is >> coincident with the frames width and height. >> >> >> From 23d80d0d4

[FFmpeg-devel] [PATCH] movenc: write clap tag

Resolves https://trac.ffmpeg.org/ticket/6145 and writes a clap atom that is coincident with the frames width and height. From 23d80d0d47829fed61e817b1e7c3f6d420c9ab5c Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 6 Jul 2017 21:12:38 -0400 Subject: [PATCH] movenc: write clap tag

Re: [FFmpeg-devel] [RFC][PATCH] movenc: write clap tag

> On Jul 6, 2017, at 9:39 PM, Derek Buitenhuis > wrote: > > On 7/7/2017 2:20 AM, Dave Rice wrote: >> Currently this patch writes the clap atom under this condition >> "track->par->codec_id == AV_CODEC_ID_RAWVIDEO & track->mode == MODE_MOV”; >>

[FFmpeg-devel] [RFC][PATCH] movenc: write clap tag

her comments welcome. Thanks. From a5e399c6eeaa64aef52dc498cc62114428f42941 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Thu, 6 Jul 2017 21:12:38 -0400 Subject: [PATCH] movenc: write clap tag --- libavformat/movenc.c | 19 +++ 1 file changed, 19 insertions(+) diff --git a/libavformat/mo

Re: [FFmpeg-devel] [WIP][PATCH] avfilter: add video oscilloscope filter

> On Apr 26, 2017, at 2:37 AM, Paul B Mahol wrote: > > On 4/26/17, Dave Rice wrote: >> >> >> I'm curious why floats are used for x,y coordinates within a frame rather >> than integers. > > So it the position be set relatively. And for similar

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

> On Apr 24, 2017, at 5:03 PM, Paul B Mahol wrote: > > On 4/24/17, Dave Rice wrote: >> >>> On Apr 24, 2017, at 4:47 PM, Paul B Mahol wrote: >>> >>> On 4/24/17, Dave Rice wrote: >>>> >>>> I tested this filter and find it ver

Re: [FFmpeg-devel] [WIP][PATCH] avfilter: add video oscilloscope filter

_comps; c++) { > +if ((1 << c) & s->components) { > +int x = i * s->width / s->nb_values; > +int px = (i - 1) * s->width / s->nb_values; > +int py = 255 - s->values[i-1].p[c]; > +

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

> On Apr 24, 2017, at 4:47 PM, Paul B Mahol wrote: > > On 4/24/17, Dave Rice wrote: >> >> I tested this filter and find it very useful, but could it be adjusted to >> handle full range video. Currently when I test with a sample such as: >> >> ./ffplay

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

X + 18, Y + > 30 + 200 + 2, text, 0); > +snprintf(text, sizeof(text), "%c %07.1f %05d %05d\n", s->is_rgb ? > rgba[0] : yuva[0], average[s->rgba_map[0]], min[s->rgba_map[0]], > max[s->rgba_map[0]]); > +draw_text(&s->draw, in, s->is_rgb ? &s->red : &s->white, X + 18, Y + > 30 + 200 + 15, text, 0); > +snprintf(text, sizeof(text), "%c %07.1f %05d %05d\n", s->is_rgb ? > rgba[1] : yuva[1], average[s->rgba_map[1]], min[s->rgba_map[1]], > max[s->rgba_map[1]]); > +draw_text(&s->draw, in, s->is_rgb ? &s->green : &s->blue, X + 18, Y + > 30 + 200 + 30, text, 0); > +snprintf(text, sizeof(text), "%c %07.1f %05d %05d\n", s->is_rgb ? > rgba[2] : yuva[2], average[s->rgba_map[2]], min[s->rgba_map[2]], > max[s->rgba_map[2]]); > +draw_text(&s->draw, in, s->is_rgb ? &s->blue : &s->red, X + 18, Y + > 30 + 200 + 45, text, 0); > + > +return ff_filter_frame(outlink, in); > +} > + > +static const AVFilterPad pixscope_inputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.filter_frame = pixscope_filter_frame, > +.config_props = pixscope_config_input, > +.needs_writable = 1, > +}, > +{ NULL } > +}; > + > +static const AVFilterPad pixscope_outputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +}, > +{ NULL } > +}; > + > +AVFilter ff_vf_pixscope = { > +.name = "pixscope", > +.description = NULL_IF_CONFIG_SMALL("Pixel data analysis."), > +.priv_size = sizeof(PixscopeContext), > +.priv_class= &pixscope_class, > +.query_formats = query_formats, > +.inputs= pixscope_inputs, > +.outputs = pixscope_outputs, > +}; > -- > 2.9.3 I tested this filter and find it very useful, but could it be adjusted to handle full range video. Currently when I test with a sample such as: ./ffplay -f lavfi -i color=c=white:s=640x480,format=yuv444p,lutyuv=y=255:u=248:v=10,pixscope The outputs list Y=235, U=240, V=16. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCHv3] add signature filter for MPEG7 video signature

> On Mar 20, 2017, at 10:13 AM, Paul B Mahol wrote: > > On 3/20/17, Dave Rice wrote: >> On Jan 6, 2017, at 1:34 PM, Gerion Entrup >> wrote: >>> >>> On Donnerstag, 5. Januar 2017 02:26:23 CET Michael Niedermayer wrote: >>>> On Wed, Ja

Re: [FFmpeg-devel] [PATCHv3] add signature filter for MPEG7 video signature

av_get_frame_filename(filename, sizeof(filename), sic->filename, >>> input); >> >> its more robust to use a av_assert*() on the return code if its assumed >> to be never failing than just a comment as a comment cannot be >> automatcially checked for validity currently. > I chose av_assert0 because the check is done only nb_inputs times. > > The attached patch also fixes the file writing for every frame the one input > is > longer than the other. Just bumping this thread. I've been using the patch and find it very helpful and would like to see it in libavfilter. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH]lavf/matroska: Support codec id V_FFV1 for FFV1.

Tobias > > Well, that makes things a bit more complex. > Maybe the Matroska spec should follow and also avoid mentioning v2? > That way we could just pretend those files don't exist and not bother > trying to drop their extradata during muxing. I agree. In the FFV1 spec, it is careful to say that it intentionally does not describe FFV1 version 2. I will submit a patch to the Matroska specification to avoid using relative language based on version 2. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 2/3] ffprobe: report field order for video streams

: tests/ref/fate/ffprobe_compact: patch does not apply >> error: Did you hand edit your patch? >> It does not apply to blobs recorded in its index. >> > > Could be due to encoding problems or long lines. Have rebased the patch onto > current git HEAD and attached it as a

Re: [FFmpeg-devel] [PATCH] avformat/matroskaenc: write DisplayWidth and DisplayHeight elements only if they differ from PixelWidth and PixelHeight

tom" which is DisplayWidth=40 DisplayHeight=200 which is wrong, since the original file intended to show the cropped 40x200 image in a 320x240 display. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 2/2] avformat/matroskaenc: write a DisplayUnit element when aspect ratio is unknown

> On Oct 15, 2016, at 7:54 PM, Kieran O Leary wrote: > > Hi, > > On Sat, Oct 15, 2016 at 11:09 PM, James Almer wrote: > >> >> -#sar 0: 1/1 >> +#sar 0: 0/1 >> > > This commit looks very useful. A few archivists (including myself) > encountered this issue, so this is a wonderful contribution

Re: [FFmpeg-devel] [PATCH] mov: add option to ignore moov atoms which are detected in free atoms.

> On Oct 13, 2016, at 1:56 PM, Hendrik Leppkes wrote: > > Am 13.10.2016 19:03 schrieb "liangsi" : >> >> --- >> libavformat/isom.h | 1 + >> libavformat/mov.c | 5 - >> 2 files changed, 5 insertions(+), 1 deletion(-) >> > > Can you elaborate on the reasons of why someone would want this? Pr

Re: [FFmpeg-devel] [PATCH] avformat/matroska: fix MatroskaVideoFieldOrder enum values

t; > typedef enum { > -- > 2.9.1 LGTM. Thanks for fixing this. It now aligns to the same list in QuickTime as was intended in the spec. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/2] avformat/matroskaenc: fix Tags master on seekable output if there are tags after the last stream duration

t; duration_string, 20); >> } >> } >> +avio_seek(mkv->tags_bc, curr, SEEK_SET); >> } >> if (mkv->tags.pos && !mkv->is_live) { >> avio_seek(pb, mkv->tags.pos, SEEK_SET); > > > Ping. It's a recent regression on a muxer, so I'd like to solve it asap. > I'll push it later today if nobody comments. I tested this and it does fix the issue so that the added "key" tag is properly formed, whereas the tag is only null bytes without the patch. Thanks! Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 00/11] CRC32 support for Matroska muxer

> On Oct 6, 2016, at 4:33 PM, James Almer wrote: > > On 10/6/2016 3:28 PM, Michael Niedermayer wrote: >> On Thu, Oct 06, 2016 at 11:27:08AM -0300, James Almer wrote: >>> On 10/6/2016 7:29 AM, Michael Niedermayer wrote: On Mon, Oct 03, 2016 at 08:36:56PM -0300, James Almer wrote: > This

Re: [FFmpeg-devel] [PATCH 00/11] CRC32 support for Matroska muxer

rks well and resolves ticket #4347. The CRC-32 Elements are in the right positions according to the latest CELLAR drafts on Matroska and the resulting files pass mkvalidator. Thanks much for this. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg

Re: [FFmpeg-devel] [PATCH 1/3] avformat/matroska: write FlagInterlaced element in WebM

to webM to consider adding FieldOrder to the format rather than see FieldOrder removed from the webM muxer in FFmpeg. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH]lavf/movenc: Allow to disable writing the timecode track

5492. >> --- >> doc/muxers.texi |3 +++ >> libavformat/movenc.c |6 -- >> libavformat/movenc.h |1 + >> 3 files changed, 8 insertions(+), 2 deletions(-) > > should be ok, but please wait a day with applying so others can > comment too +1

Re: [FFmpeg-devel] calculation of probe score

Note that some containers (like H.264 Annex B or ADTS) correspond > to a codec, so for containers that "allow" random codecs (like mpeg > streams) the same probe functions that allow detecting formats can > be used to detect codecs. [...] Best Regards, Dave Rice

Re: [FFmpeg-devel] [VDD2016] Technical Discussion Results

8 - Bayer pixel format support in FFV1 - Support for additional color information in FFV1 to better handle lossless DPX->FFV1->DPX transfer while preserving characteristics such as if the sampling is logarithmic or linear. Probably others. Feel welc

Re: [FFmpeg-devel] [PATCH] ffprobe: add -show_headers_first option

lid ffprobe xml. ffprobe.xsd defines the elements in a `sequence`, so if the order of elements is really arbitrary it should be changed to a `choice`. Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] libavformat/matroskaenc: omit segment UID for webm

t would cause the Segment element to > terminate. At that point, the file is pretty broken because now there > is no Segment element containing the Clusters and other elements. > > [1]: "The end of a Master-element with unknown size is determined by > the beginnin

Re: [FFmpeg-devel] [PATCH] libavformat/matroskaenc: omit segment UID for webm

I think "EBML Element" in this case should be considered to mean "EBML Elements as defined by the EBML DocType". The webm EBML Schema does not define a SegmentUID Element as Matroska does, so the Element is meaningless in webm. It may happen to follow the EBML Header pattern

[FFmpeg-devel] [PATCH 2/2] avfilter/vf_histogram: indent histogram options

Some indentation after the previous patch. Dave Rice 0002-avfilter-vf_histogram-indent-histogram-options.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH 1/2] avfilter/vf_histogram: shortcuts for histogram options

This patch adds some shortcuts for the histogram filter's options in a way that is consistent with the waveform and vectorscope filter. Dave Rice 0001-avfilter-vf_histogram-shortcuts-for-histogram-option.patch Description: Binary data ___ f

  1   2   >