Re: [FFmpeg-devel] [PATCH] lavfi: add drawgraph filter

> On Jun 27, 2015, at 3:47 AM, Paul B Mahol wrote: > > Dana 26. 6. 2015. 21:26 osoba "Dave Rice" napisala je: >> >> Hi, >> >>> On Jun 26, 2015, at 11:27 AM, Paul B Mahol wrote: >>> >>> Signed-off-by: Paul B Mahol >>&g

Re: [FFmpeg-devel] [PATCH] lavfi: add drawgraph filter

gt; +} > + > +out: > +av_frame_free(&in); > +return ff_filter_frame(outlink, av_frame_clone(s->out)); > +} > + > +static int config_output(AVFilterLink *outlink) > +{ > +DrawGraphContext *s = outlink->src->priv; > + > +outlink->w = s->w; > +outlink->h = s->h; > +outlink->sample_aspect_ratio = (AVRational){1,1}; > + > +return 0; > +} > + > +static av_cold void uninit(AVFilterContext *ctx) > +{ > +DrawGraphContext *s = ctx->priv; > + > +av_expr_free(s->fg_expr); > +av_frame_free(&s->out); > +} > + > +static const AVFilterPad drawgraph_inputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.filter_frame = filter_frame, > +}, > +{ NULL } > +}; > + > +static const AVFilterPad drawgraph_outputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.config_props = config_output, > +}, > +{ NULL } > +}; > + > +AVFilter ff_vf_drawgraph = { > +.name = "drawgraph", > +.description = NULL_IF_CONFIG_SMALL("Draw a graph using input video > metadata."), > +.priv_size = sizeof(DrawGraphContext), > +.priv_class= &drawgraph_class, > +.query_formats = query_formats, > +.init = init, > +.uninit= uninit, > +.inputs= drawgraph_inputs, > +.outputs = drawgraph_outputs, > +}; > -- > 1.7.11.2 With this version using a color name for foreground no longer works: This works: ffplay -f lavfi -i mandelbrot -vf signalstats,drawgraph=metadata=lavfi.signalstats.YAVG:min=0:max=255:slide=scroll:bg=green:fg=0xFF This doesn’t: ffplay -f lavfi -i mandelbrot -vf signalstats,drawgraph=metadata=lavfi.signalstats.YAVG:min=0:max=255:slide=scroll:bg=green:fg=red Also here’s an example with blend: ffplay -f lavfi -i mandelbrot -vf "signalstats,split=3[a][b][c];\ [a]drawgraph=metadata=lavfi.signalstats.YAVG:min=0:max=255:slide=scroll:fg=0x:mode=dot[a1];\ [b]drawgraph=metadata=lavfi.signalstats.UAVG:min=0:max=255:slide=scroll:fg=0xFF00FF00:mode=dot[b1];\ [c]drawgraph=metadata=lavfi.signalstats.VAVG:min=0:max=255:slide=scroll:fg=0xFF00:mode=dot[c1];\ [a1][b1]blend=and[ab];[ab][c1]blend=and[out]” Thanks, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] lavfi: add drawgraph filter

> On Jun 28, 2015, at 11:07 AM, Paul B Mahol wrote: > > On 6/28/15, Dave Rice wrote: >> Hi, >> >>> On Jun 27, 2015, at 4:52 PM, Paul B Mahol wrote: >>> >>> Signed-off-by: Paul B Mahol >>> --- >>> doc/filters.texi

Re: [FFmpeg-devel] [PATCH] lavfi: add drawgraph filter

> On Jun 28, 2015, at 1:54 PM, Paul B Mahol wrote: > > On 6/28/15, Dave Rice wrote: >> >>> On Jun 28, 2015, at 11:07 AM, Paul B Mahol wrote: >>> >>> On 6/28/15, Dave Rice wrote: >>>> Hi, >>>> >>>>> On Jun 27

Re: [FFmpeg-devel] [PATCH] lavfi: add (a)drawgraph filter

gt;sample_aspect_ratio = (AVRational){1,1}; > + > +return 0; > +} > + > +static av_cold void uninit(AVFilterContext *ctx) > +{ > +DrawGraphContext *s = ctx->priv; > +int i; > + > +for (i = 0; i < 4; i++) > +av_expr_free(s->fg_expr[i]); > +av_frame_free(&s->out); > +} > + > +#if CONFIG_DRAWGRAPH_FILTER > + > +AVFILTER_DEFINE_CLASS(drawgraph); > + > +static const AVFilterPad drawgraph_inputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.filter_frame = filter_frame, > +}, > +{ NULL } > +}; > + > +static const AVFilterPad drawgraph_outputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.config_props = config_output, > +}, > +{ NULL } > +}; > + > +AVFilter ff_vf_drawgraph = { > +.name = "drawgraph", > +.description = NULL_IF_CONFIG_SMALL("Draw a graph using input video > metadata."), > +.priv_size = sizeof(DrawGraphContext), > +.priv_class= &drawgraph_class, > +.query_formats = query_formats, > +.init = init, > +.uninit= uninit, > +.inputs= drawgraph_inputs, > +.outputs = drawgraph_outputs, > +}; > + > +#endif // CONFIG_DRAWGRAPH_FILTER > + > +#if CONFIG_ADRAWGRAPH_FILTER > + > +#define adrawgraph_options drawgraph_options > +AVFILTER_DEFINE_CLASS(adrawgraph); > + > +static const AVFilterPad adrawgraph_inputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_AUDIO, > +.filter_frame = filter_frame, > +}, > +{ NULL } > +}; > + > +static const AVFilterPad adrawgraph_outputs[] = { > +{ > +.name = "default", > +.type = AVMEDIA_TYPE_VIDEO, > +.config_props = config_output, > +}, > +{ NULL } > +}; > + > +AVFilter ff_avf_adrawgraph = { > +.name = "adrawgraph", > +.description = NULL_IF_CONFIG_SMALL("Draw a graph using input audio > metadata."), > +.priv_size = sizeof(DrawGraphContext), > +.priv_class= &adrawgraph_class, > +.query_formats = query_formats, > +.init = init, > +.uninit= uninit, > +.inputs= adrawgraph_inputs, > +.outputs = adrawgraph_outputs, > +}; > +#endif // CONFIG_ADRAWGRAPH_FILTER > -- > 1.7.11.2 I re-tested and all looks great. The new default size, 900x256, makes sense and I'm glad to see it now works with audio metadata (would love to be able to use astats with this someday). I'm having a little trouble getting an example working with the MIN/MAX variables, do you have a sample command? Thanks, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] lavfi: add (a)drawgraph filter

> On Jun 29, 2015, at 2:09 PM, Paul B Mahol wrote: > > On 6/29/15, Dave Rice wrote: >> Hi, >> > > [...] > >> >> I re-tested and all looks great. The new default size, 900x256, makes sense >> and I'm glad to see it now works with audio

Re: [FFmpeg-devel] [PATCH] avfilter/af_astats: export metadata

on could either be graphed frame-by-frame or summarized as it accumulates. With my samples the filter defaulted to an audio frame size of 1024. I realize that I could set asetnsamples before astats to change that, but could the audio frame size be set within the astats filter.

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

Hi, > On Jul 7, 2015, at 10:35 AM, Michael Niedermayer wrote: > > On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote: >> Hi all, >> Last month I posted a draft of the FFV1 specification formatted in Markdown >> [1], whereas it currently lives in lyx. From tha

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer wrote: > > On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote: >> Hi, >> >>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer wrote: >>> >>> On Thu, Jul 02, 2015 at 09:50:21AM -0400,

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 10, 2015, at 1:47 PM, Michael Niedermayer > wrote: > > On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote: >> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote: >>> >>>> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 10, 2015, at 1:51 PM, Michael Niedermayer > wrote: > > On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote: >> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote: >>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

yer wrote: >>>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote: >>>>> >>>>>> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer wrote: >>>>>> >>>>>> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer > wrote: > > On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote: >> >>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer >>> wrote: >>> >>> On Fri, Jul 10, 2015 at 07:51:20PM

Re: [FFmpeg-devel] [PATCH] avfilter/af_astats: export metadata

> On Jul 1, 2015, at 4:10 AM, Paul B Mahol wrote: > > On 6/30/15, Dave Rice wrote: >> Hi Paul, >> >>> On Jun 29, 2015, at 7:40 PM, Paul B Mahol wrote: >>> >>> Signed-off-by: Paul B Mahol >>> --- >>> doc/filters.texi

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer > wrote: > > On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote: >> >>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer >>> wrote: >>> >>> On Fri, Jul 10, 2015 at 07:51:20PM

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 10, 2015, at 4:55 PM, Michael Niedermayer > wrote: > > On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote: >> >>> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer >>> wrote: >>> >>> On Fri, Jul 10, 2015 at 03:47:45PM -04

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

Hi Michael, > On Jul 20, 2015, at 7:52 AM, Michael Niedermayer > wrote: > > On Sat, Jul 18, 2015 at 11:23:16AM -0400, Dave Rice wrote: >> >>> On Jul 10, 2015, at 4:55 PM, Michael Niedermayer >>> wrote: >>> >>> On Fri, Jul 10, 2015 at 04

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

eg.org/>. Then within the README of the FFV1 repo we could link to the rendered copy on ffmpeg.org <http://ffmpeg.org/>. [...] Best Regards, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] decklink: support all valid numbers of audio channels

03. However in Media Express (the free utility that comes with Decklink products) it only places all channels in a single track with unspecified arrangement. I think mimicking Media Express is appropriate and avoid presuming too much about the audio. If needed the

[FFmpeg-devel] clarification on General Description for FFV1 Draft Specification

From this reading it seems like 2 planes is possible; however, are 2 plane encodings possible (grayscale with alpha or Y with only Cb)? Re: "since it is most likely that the RCT will immediately be converted to RGB during decoding”. Is there anyone other conversion possible? Best Regards, Dave

Re: [FFmpeg-devel] [PATCH] decklink: support all valid numbers of audio channels

tion (c608) and timecode streams. > - introduce options to select video and audio input, e.g. the new > low-cost cards have SDI and HDMI inputs I have a BlackMagic UltraStudio which adds Composite and Component inputs. Happy to test patches. > - port those changes to decklink out

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

> On Jul 21, 2015, at 10:24 AM, Michael Niedermayer > wrote: > > On Mon, Jul 20, 2015 at 11:55:41PM -0400, Dave Rice wrote: >> >>> On Jul 20, 2015, at 8:52 PM, Michael Niedermayer >>> wrote: >>> >>> On Tue, Jul 21, 2015 at 02:14:11A

[FFmpeg-devel] Remote participation options for IETF session on MKV/FFV1 at July 22 @ 9 CEST

'm also participating remotely and will be logging in to relevant chatrooms about a half hour before it starts tomorrow. Best Regards, Dave Rice ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [libav-devel] Remote participation options for IETF session on MKV/FFV1 at July 22 @ 9 CEST

> On Jul 21, 2015, at 2:59 PM, Michael Niedermayer > wrote: > > On Tue, Jul 21, 2015 at 02:03:16PM -0400, Ronald S. Bultje wrote: >> Hi, >> >> On Tue, Jul 21, 2015 at 12:58 PM, Kostya Shishkov >> wrote: >> >>> On Tue, Jul 21, 201

[FFmpeg-devel] FFV1/MKV IETF Session followup

me > together. Steve Lhome, an original author of Matroska, said he would > continue to participate where ever the work was going to happen. > > Cullen and Dave Rice pointed out the needs for lossless video. Cullen > felt the specifications didn't support interoperability as the

Re: [FFmpeg-devel] Add support for j2ki/mxf

world for it). >> >> Also it might be specific to jpeg2000 (see below), i'll have to look again >> at the mxf/jpeg2000 spec again. >> > > I have added a 4 frame example to the trac ticket of interlaced IMX50 > material. I added more jpeg2000 / MXF sample files t

Re: [FFmpeg-devel] [libav-devel] FFV1/MKV IETF Session followup

Hi all, Further reporting on the IETF happenings below. > On Jul 22, 2015, at 7:44 PM, Dave Rice wrote: > > Hi all, > > An HTML5 presentation of today's IETF meeting on FFV1 and Matroska is > available at > http://recordings.conf.meetecho.com/Playout/watch.jsp

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

> On Aug 11, 2015, at 2:31 PM, Paul B Mahol wrote: > > On 8/11/15, Paul B Mahol wrote: >> Hi, >> >> This should also address ticket #2824. I tested this with in-phase and out of phase audio and it worked great. I'm glad there's a way

Re: [FFmpeg-devel] Why is writing the colr atom not the default in the mov muxer?

ch as raw uyvy422 and v210), see: https://developer.apple.com/library/mac/technotes/tn2162/_index.html#//apple_ref/doc/uid/DTS40013070-CH1-TNTAG9. I'd propose that colr be written by default. The interpretation may be different but, since a file with a colr atom is more self-descriptive, the

[FFmpeg-devel] standardization route for FFV1 specification

-devel for consideration. Within the repository the ffv1.lyx aims to be the basis for FFV1 standardization efforts but we hope to regularly update the html rendering within the repo as well. Best Regards, Dave Rice [1] https://github.com/MediaArea/MediaConch/blob/master/StandardsNarrative.md <https

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] [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] [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] [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

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

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

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

> 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

> 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 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 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] 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] 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 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 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] 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] 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: 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

[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 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

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 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] 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 2/2] doc/filters: add a signalstats example

Here is an updated patch based on the advice from Stefano and Timothy. Thanks much, Dave Rice >From f0d063bbe5b275f4fa293400ee218b50c52823f9 Mon Sep 17 00:00:00 2001 From: Dave Rice Date: Tue, 8 Jul 2014 23:36:36 -0400 Subject: [PATCH 2/3] doc/filters: add a signalstats example Signed-off

Re: [FFmpeg-devel] [PATCH] avformat/dv: implement fallback in dv_extract_pack()

On Jul 16, 2014, at 10:57 PM, Michael Niedermayer wrote: > Fixes Ticket2340 > Fixes Ticket2341 I tested with the samples from tickets 2340 and 2341. In both cases the patch fixes the originally reported issue. Thanks! Dave Rice ___ ffmpeg

<    1   2