On Tue, 13 Aug 2019, 20:25 Stanislav Ionascu,
wrote:
> Hi All,
>
> when remuxing some of the mp4 files into the mkv container, not all
> video codecs can be properly represented.
Purely out of curiosity, what other codes does this affect?
Best,
Kieran O'Leary
Irish Film Institute
On Thu, 22 Aug 2019, 17:18 Paul B Mahol, wrote:
> Hi,
>
> patch attached.
>
Maybe it's a Gmail issue but I see no attachment. Also for those of us
unable to understand the code,what's the improvement?
Best,
Kieran
>
>
___
ffmpeg-devel mailing list
On Wed, 17 Oct 2018, 04:28 Steven Liu, wrote:
> Signed-off-by: Steven Liu
> ---
> src/documentation | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/documentation b/src/documentation
> index e3bbf4c..7569e86 100644
> --- a/src/documentation
> +++ b/src/documentation
> @@ -131,6 +1
user option, to force 10b or 12b decoding
>
Are all 444(4?) Encodings 12-bit? Also is there a way to verify if your
file should be decoded as 10 or 12-bit? Or does this code automate this
detection?
This all looks very cool.
Thanks,
Kieran O Le
On Sun, 18 Nov 2018, 21:58 Martin Vignali
> I don't know, how to get the "wanted" pix_fmt output using ffmpeg cli, and
> I don't know, what the general "rules" of this project for multiple pix_fmt
> output for the same input file.
>
> If user option for decoding precision need to be remove,
> i th
On Sat, 24 Nov 2018, 22:11 Martin Vignali Hello,
>
> Patch in attach add some improvments to prores aw encoder
>
> 012 : Add vendor option (code come from prores_ks encoder)
> 013 : Only write color properties, if defined in rdd36 (other values are
> "converted" to unspecified)
> 014 : Add XQ
On Mon, Nov 26, 2018 at 8:06 AM Kieran O Leary
wrote:
>
>
> On Sat, 24 Nov 2018, 22:11 Martin Vignali
>> Hello,
>>
>> Patch in attach add some improvments to prores aw encoder
>>
>> 012 : Add vendor option (code come from prores_ks encoder)
>> 013
Hi,
Forgive my ignorance ,but what is the difference between a parser and a
decoder in this context? What does this parser add that wasn't covered in
the decoder?
Best,
Kieran O'Leary
Irish Film Institute
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
Hi Neil,
Thanks so much for working on this - what was the impetus?
I started the ticket you mentioned. I applied your patch and tested it with
the clap.mov file from that ticket. How do I know if behaviour has changed
with this patch, how should I be testing?
I don't see any reference to the clap
Hi Neil,
I have to look deeper into the MKV side of things and most likely raise it
with the cellar mailing list so that better minds than mine can weigh in. I
do see that the rounding up to 704 could be an issue alright.
As for MOV, your patch appears to generate the same output clap values as
th
Hi,
I broke the threading with my last reply, i apologise. Here goes another
attempt:
On Tue, Apr 28, 2020 at 6:23 PM Neil Birkbeck
wrote:
> On Tue, Apr 28, 2020 at 3:18 AM Nicolas George wrote:
>
> > Andreas Rheinhardt (12020-04-28):
> > > That's expected. The patch provided only provides the
Hi,
On Fri 29 May 2020, 22:47 Neil Birkbeck, wrote:
> On Mon, May 11, 2020 at 9:37 PM Neil Birkbeck
> wrote:
>
> >
> >
> > On Wed, May 6, 2020 at 8:45 AM James Almer wrote:
> >
> >> On 5/6/2020 12:22 PM, Neil Birkbeck wrote:
> >> > On Tue,
Hi
On Tue 2 Jun 2020, 20:50 Nicolas George, wrote:
> Paul B Mahol (12020-06-02):
> > No need to reinvent yet another poor synthesizer.
>
> Which is precisely why what I implemented is something well established.
>
> Can somebody give a third opinion please?
>
I doubt my opinion means much but I
Hi all - just wondering about the status of this. I was doing some tests
with just -crf 0 with mixed results before I saw this thread.
http://ffmpeg.org/pipermail/ffmpeg-user/2020-June/048885.html
K
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
h
hi
On Mon, Jun 8, 2020 at 10:17 PM Michael Niedermayer
wrote:
> Hi
>
> ive branched release/4.3, will make the 4.3 release from its HEAD in a
> few days (maybe a week depending on comments from other developers or
> any major issues)
>
> If theres any issue remaining which you want to work on an
On Tue 9 Jun 2020, 13:21 Michael Niedermayer,
wrote:
> On Mon, Jun 08, 2020 at 11:55:15PM +0100, Kieran O Leary wrote:
> > hi
> >
> > On Mon, Jun 8, 2020 at 10:17 PM Michael Niedermayer
>
> > wrote:
> >
> > > Hi
> > >
> > > ive bra
Hi,
On Wed, 4 Sep 2019, 04:09 Mark Filipak, <
markfilipak.windows+ffm...@gmail.com> wrote:
> No one has responded. What does that indicate? Lack of interest? Lack of
> knowledge? Lack of time? Shunning of anyone who's not a current developer?
>
You didn't wait very long for a reply, also you wro
On Fri, 20 Sep 2019, 08:58 Adam Johnson, wrote:
> I have some aiff files in my music production library that I'd like to
> convert to flac. However they aren't recognized by ffmpeg:
>
> $ ffmpeg -i Raylon-190-Full.aif
> ...
> [aiff @ 0x7fc3ce80] unknown or unsupported codec tag: able is not
>
On Sun, 8 Dec 2019, 22:50 Michael Niedermayer,
wrote:
> Version 3 is since 2013 (FFmpeg 2.1) non experimental so should be widely
> supported
>
This was recently raised at the No Time To Wait conference in Budapest, so
it would be great to see version three as the default!
Best,
Kieran O'Leary
These notes are really helpful, I hope they continue for future meetings!
Best,
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ..
On Fri, 11 Jan 2019, 15:31 Nicolas George Carl Eugen Hoyos (12019-01-11):
> > I believe amount is never published (so far at least afair).
>
> I think it should. I wonder what other people think.
>
I don't see why this declaration is helpful or necessary in any way. Can
you elaborate on why it is
On Sun, 13 Jan 2019, 15:57 Nicolas George James Almer (12019-01-13):
> > And kill the project by reducing development speed to crawl? Unreviewed
>
> That is indeed the problem.
>
> > and unchallenged patches by long time devs with commit rights can and
> > will still be pushed after enough time an
On Tue, 15 Jan 2019, 00:25 Lou Logan Signed-off-by: Lou Logan
> ---
> libavformat/img2enc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/img2enc.c b/libavformat/img2enc.c
> index a09cc8ec50..bec4bf81dd 100644
> --- a/libavformat/img2enc.c
> +++ b/libavfo
Hi,
On Sat, Feb 9, 2019 at 6:10 PM Martin Vignali
wrote:
> Hello,
>
> Patchs in attach add interlace encoding support to prores aw encoding
>
Thanks so much for adding this. I can really only judge by the metadata for
now, but this all looks good to me (ffmpeg encode and mediainfo check):
$ ./
On Sun, 10 Feb 2019, 11:57 Martin Vignali Hello,
>
> >
> > > Use +ildct flag to switch between progressive and interlace encoding
> > >
> > > Use AVFrame flag to switch between tff and bff frame organization.
> > >
> >
> > Is this what you mean by altering the -setparams filter?
> >
> > In order t
On Sat, 9 Feb 2019, 06:49 Gyan
>
> On 09-02-2019 02:26 AM, Carl Eugen Hoyos wrote:
> > 2019-02-08 6:08 GMT+01:00, Gyan :
> >>
> >> On 08-02-2019 03:31 AM, Carl Eugen Hoyos wrote:
> >>> .
> >>> No strong opinion here, I hadn't realized that -crf 0 only works with
> >>> newer versions.
> >>>
> >>> C
Hi, can this be merged or is more rigourous testing necessary?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi,
Should the vf colorspace documentation be updated with this new addition?
Best,
Kieran
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, Sep 27, 2017 at 10:28 PM, Vittorio Giovara
wrote:
> As defined by the spcifications
Is this the paywalled SMPTE spec? I don't see any mention of it in the
openly available whitepaper,
https://images.apple.com/final-cut-pro/docs/Apple_ProRes_White_Paper.pdf
Just one typo below, thanks for providing the html as well.
On 28 Sep 2017 01:00, "Lou Logan" wrote:
Signed-off-by: Lou Logan
---
doc/Makefile | 1 +
doc/mailing-list-faq.texi | 204 ++
2 files changed, 205 insertions(+)
create mode
On 29 Sep 2017 03:22, wrote:
I will continue to do testing..
>
This works and captures full range (data levels, but the captured data
happens to be video levels 64-940) to the output file and the out.mov file
looks good/clean. Not sure how to flag (metadata) output color space and
levels, but
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! Thanks James!
-Kieran.
___
ffmp
Hi,
On Sun, Oct 30, 2016 at 7:07 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> Signed-off-by: Vittorio Giovara
> ---
> I couldn't find any reference to the name of the whitepoint used for 431,
> so I came up with DCI, since it looks like it is only used there.
> Please CC.
>
Could
Hi
On 2 Nov 2016 10:15 p.m., "Carl Eugen Hoyos" wrote:
>
> >
> > This fixes ticket #5743, implementing the suggestion from ticket #5903.
>
> Thank you for fixing this!
>
> Carl Eugen
>
+1 Thanks James!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg
Hi Carl,
On Fri, Nov 11, 2016 at 1:31 PM, Michael Niedermayer wrote:
> On Thu, Nov 10, 2016 at 11:08:23PM +0100, Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Not sure how useful this is but we also support gprp12.
> >
> > Please comment, Carl Eugen
>
I'm sure that this could be useful for film arch
Hi,
I've never submitted a patch for anything before, so hopefully this is OK.
I noticed that the recent commits by Vittorio Giovara were not reflected in
the filter documentation.
I'm attaching the output of git format-patch -1 as well as copy/pasting it
in this email.
>From c52eededc4a0e865a84
Hi
On 3 Aug 2016 6:58 p.m., "Michael Niedermayer"
wrote:
>
> Hi all
>
> we need ideas for Outreachy, the page is EMPTY:
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12
>
How about EBU-STL subtitle decoding? It's currently unsupported. It's a non
text based subtitle format t
Hi,
On Fri, Aug 26, 2016 at 10:37 PM, Brett Harrison
wrote:
> Allows expr evaluation in the fontsize parameter for drawtext.
Thanks for making this. I regularly use drawtext to create
watermarked/timecoded access copies in a moving image archive and I
have to use workarounds in scripts in order
Hello,
I am looking for a time/money quote for someone to add EBU-STL
subtitle decoding to ffmpeg. I saw the list of available developers on
the ffmpeg website, but I wasn't sure who was best to contact.
I work for the IFI Irish Film Archive, and we receive EBU-STL
subtitles for AS-11 UKDPP broad
Hello,
I'm cc'ing Vittorio as I don't think that he's subscribed to the list but
he's contributed to dpxenc.c and recent colorspace filters. The same with
Kate Murray from the Library of Congress who knows a lot more about DPX
than me. Apologies if this is inappropriate.
I mostly based this patch
Hi James and Carl,
Thanks for getting back to me. It looks like your comments are similar,
though you might be asking to pull the information from different places?
more below
On Wed, Feb 1, 2017 at 5:01 PM, James Almer wrote:
>
> I may be missing something and apologizes if it was already ment
Hi
On 2 Feb 2017 08:20, "Carl Eugen Hoyos" wrote:
2017-02-01 23:37 GMT+01:00 Kieran O Leary :
> DPX contains some values that are super-specific to film, such as
'Printing
> Density'. I do not see that value in either of those enums but it's a
> common value t
Hi Vittorio!
thanks for getting back to me.
On Fri, Feb 3, 2017 at 12:57 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
>
>
> Hey Kieran,
> I think the code looks fine. I am just wondering if we should also
> offer the possibility to set these flags from the standard context
> options
Hi,
A user mentioned in ffmpeg-user (
http://ffmpeg.org/pipermail/ffmpeg-user/2017-July/036571.html) that they
couldn't write the 'keywords' metadata tag. I tested this patch and it
appears to add the metadata value when using MOV and MP4 as output. I'm
sure I've messed something up so please let
Thanks Derek/Michael!
-Kieran.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
I just tested this patch non packed to 16-bit gbrp12le DPX from DaVinci
Resolve. Encoding to FFV1 and back again to DPX produced the same framemd5
values.
Does any more testing need to happen before this can be merged?
Best,
Kieran
___
ffmpeg-devel mai
Hi
On Tue, Apr 10, 2018 at 11:34 AM, Carl Eugen Hoyos wrote:
> 2018-04-10 12:28 GMT+02:00, Kieran O Leary :
>> I just tested this patch non packed to 16-bit gbrp12le DPX from DaVinci
>> Resolve.
>
> Testing is good, apart from more brackets (and less comments) it would
Actually, here's another test that might be a bit more meaningful.
This is using graphicksmagic and the identify/signature command in
order to generate sha256 hashes for the image data only.
It is producing identical hashes for:
1. The original 12-bit DPX from Da Vinci Resolve (not packed to 16-bi
On Tue, Apr 10, 2018 at 3:16 PM, Paul B Mahol wrote:
> On 4/10/18, Kieran O Leary wrote:
>>
>> Hopefully this is a bit better than just using ffmpeg?
>
> No, you must not use tragic software ever.
>
> Besides ffmpeg also can give you checksums for image only.
> S
Hi Carl,
On Sat, Dec 16, 2017 at 2:31 PM, Carl Eugen Hoyos wrote:
> 2017-12-15 22:22 GMT+01:00 Tobias Rapp :
>
>> +{ "dpx_color_trc", "Transfer Characteristics", OFFSET(color_trc),
>> AV_OPT_TYPE_INT, { .i64 = DPX_TRC_UNDEFINED }, DPX_TRC_UNDEFINED,
>> DPX_TRC_NB-1, VE, "trc" },
>
> This s
On Wed, Apr 11, 2018 at 9:42 AM, Tobias Rapp wrote:
> On 11.04.2018 10:23, Kieran O Leary wrote:
>>
>> Hi Carl,
>>
>> On Sat, Dec 16, 2017 at 2:31 PM, Carl Eugen Hoyos
>> wrote:
>>>
>>> 2017-12-15 22:22 GMT+01:00 Tobias Rapp :
>>>
>
On Thu, 26 Apr 2018, 14:42 Daniel Oberhoff,
wrote:
>
> > On 26. Apr 2018, at 14:40, wm4 wrote:
> >
> > On Thu, 26 Apr 2018 14:12:14 +0200
> > Hendrik Leppkes mailto:h.lepp...@gmail.com>>
> wrote:
> >
> >> On Thu, Apr 26, 2018 at 2:02 PM, Daniel Oberhoff
> >> wrote:
> >>>
> Am 26.04.2018 um
Hi Jerome,
Thank you so much for this patch.
I ran a quick test and ffmpeg and ffplay seems to decode these files
just fine. I noticed that taking a short 12-bit sequence (i didn't
even realise that they were big endian actually) from the Blackmagic
Cintel Scanner turned into FFV1 version 3 in Ma
Hi both,
I'm just wondering if the past duration errors in my earlier email mean
anything,or should they be ignored?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Woah, this is unexpected and amazing. Which versions of Cintel RAW does
this support? If I recall correctly, there's a lossy mode, lossless
compression mode and maybe originally it was uncompressed raw?
Best,
Kieran O'Leary
National Library of Ireland
Woah, more amazing film preservation patches, thank you!
From my uninformed reading of the code, does this only support the
detection of Linear, 709, 240M, 170M, Gamm22? The reason I ask is that you
frequently see Printing Density appear as well, which has a value of '1'
in the 801/802 offset..
Pinging as I think my comment got lost in the conversation, my main concern
is about the Printing Density value aka 1,
K
On Thu, Oct 8, 2020 at 10:25 AM Kieran O Leary
wrote:
> Woah, more amazing film preservation patches, thank you!
> From my uninformed reading of the code, does thi
On Fri, Oct 9, 2020 at 12:10 PM Paul B Mahol wrote:
> On Fri, Oct 09, 2020 at 10:08:45AM +0100, Kieran O Leary wrote:
> > Pinging as I think my comment got lost in the conversation, my main
> concern
> > is about the Printing Density value aka 1,
>
> This patch is for
Hi,
On Thu, Jul 9, 2020 at 1:56 AM Manolis Stamatogiannakis
wrote:
> On Tue, 7 Jul 2020 at 16:27, Nicolas George wrote:
>
> > Manolis Stamatogiannakis (12020-07-07):
> > > If I reply to the email, my response will appear online in the issue/PR
> > > page.
> >
> > That is good to know. I have ne
I'd love to see some documentation and to know how timecode is stored in
the output file. This looks like a really welcome development!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi Jonathan,
On Fri, May 25, 2018 at 6:32 PM, Jonathan Morley wrote:
> Hi Kieran,
>
> To answer your question, this change basically takes the first valid TC as a
> string and sticks it in the video’s avstream metadata dictionary where other
> muxers and encoders look. It does not make an indep
Hi
On Thu, 19 Jul 2018, 14:04 Paul B Mahol, wrote:
> Hi,
>
> I want that FFmpeg community sponsor addition of new code I gonna
> develop in following days/months.
>
Are you suggesting a patreon type payment?
___
ffmpeg-devel mailing list
ffmpeg-devel@
Hi,
On Thu, Feb 22, 2018 at 4:15 PM, Philip Langdale wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 22 Feb 2018 12:39:16 +0100
> Nicolas George wrote:
>
>> Philip Langdale (2018-02-21):
>> > Negotiation is part of Paul's larger changeset, and will be a useful
>> > feature.
Woah, can't test this but it would be a brilliant addition to ffmpeg!
Best,
Kieran O'Leary
National Library of Ireland
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link abo
64 matches
Mail list logo
