>
> On Tue, 2 Nov 2021, Eran Kornblau wrote:
>
> > Hi all,
> >
> > The attached patch makes the default behavior of caching HTTP redirects
> > optional.
>
> Is caching a redirected URL allowed per the HTTP spec? If not, then no
> caching should tak
Hi all,
First, I apologize for asking a question not directly related to ffmpeg
development, but hope you can still help me...
I'm looking for some code to calculate the frame rate of audio, based on
parameters such as the codec id,
sampling rate, channels, codec private data etc.
For example,
>
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Hendrik
> Leppkes
> Sent: Tuesday, March 3, 2020 11:08 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] Calculating audio frame rate
>
> On Tue, Mar 3, 2020 at 8
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Anton
> Khirnov
> Sent: Tuesday, March 3, 2020 1:11 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] Calculating audio frame rate
>
> There is av_get_audio_frame_duration[2]() in libavcodec, but i
> Been trying to figure out how to decrypt SAMPLE-AES and eventually hit an
> issue with my lack of understanding how H264 and ffmpeg work.
>
> Example
>
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fd3iki3eydrtvsa.cloudfront.net%2FChernobyl_20200618213021%2FHLS%2FChernobyl
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of ?
> ?
> Sent: Friday, June 4, 2021 9:27 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libavformat/movenc: Support encryption of
> H265 stream in AnnexB format
>
>
> Ping.
>
> This change is
Hi all,
I'm trying to transcode some video file (MP4/h264 baseline vfr/AAC) with
ffmpeg, and I would like to have the
frame timestamps in the transcoded file perfectly match the source video. This
is in order to have them both
play together adaptively without issues (from my experience, DASH is
Ping
From: Eran Kornblau
Sent: Tuesday, March 28, 2017 3:13 PM
To: FFmpeg development discussions and patches
Subject: Match source video timestamp
Hi all,
I'm trying to transcode some video file (MP4/h264 baseline vfr/AAC) with
ffmpeg, and I would like to have the
frame timestamps i
Pinging again...
Thanks
Eran
From: Eran Kornblau
Sent: Monday, April 3, 2017 12:29 PM
To: 'FFmpeg development discussions and patches'
Subject: RE: Match source video timestamp
Ping
From: Eran Kornblau
Sent: Tuesday, March 28, 2017 3:13 PM
To: FFmpeg development discussions a
> Hi all,
>
> I'm trying to transcode some video file (MP4/h264 baseline vfr/AAC) with
> ffmpeg, and I would like to have the
> frame timestamps in the transcoded file perfectly match the source video.
> This is in order to have them both
> play together adaptively without issues (from my exper
Ping, re-attaching the same patch
Eran
-Original Message-
From: Eran Kornblau
Sent: Sunday, April 23, 2017 12:32 PM
To: 'FFmpeg development discussions and patches'
Subject: RE: Match source video timestamp
> Hi all,
>
> I'm trying to transcode some video fil
gt; 2017-04-30 13:09 GMT+02:00 Eran Kornblau :
>
> >> I'm trying to transcode some video file (MP4/h264 baseline vfr/AAC)
> >> with ffmpeg, and I would like to have the frame timestamps in the
> >> transcoded file perfectly match the source video.
>
>
stamp
>
> Le primidi 11 floréal, an CCXXV, Eran Kornblau a écrit :
> > Ping, re-attaching the same patch
>
> Hi. Thanks for the bug report and patch. I do not know the issue well enough
> to address the core validity in principle, but I have a few design comments
> that w
Ping
Eran
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Eran
Kornblau
Sent: Wednesday, May 3, 2017 11:59 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] Match source video timestamp
[This sender failed our
Hi all,
We bumped into an issue with the mp4 encryption support we submitted a while
ago -
in case ffmpeg decides to write a timecode track in the output mp4, it crashes.
The reason is that mov_create_timecode_track calls ff_mov_write_packet on a
track that doesn't
have 'cenc' initialized, this
Ping
Eran
From: Eran Kornblau
Sent: Wednesday, May 17, 2017 12:50 PM
To: FFmpeg development discussions and patches
Subject: mp4 encryption with time code track
Hi all,
We bumped into an issue with the mp4 encryption support we submitted a while
ago -
in case ffmpeg decides to write a
Hi all,
We're trying to make ffmpeg output a format tag of 'hvc1' for HEVC, since it
seems that only hvc1 works in iOS 11 beta.
We saw that '-tag:v hvc1' does the trick, but it only works in 'mov' format,
and not in 'mp4' format (we're using mp4
format for all our videos)
The reason is that ff_c
>
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> liyoubdu
> Sent: Monday, June 19, 2017 11:20 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] hev1 vs. hvc1
>
> >>
> i think mov is mp4
Hi all,
I did some work around parsing HEVC headers, and while looking at ffmpeg's
implementation, I noticed
a few bugs and a few style issues. I'm not submitting a patch, since my
familiarity with the decoder is
very limited, but hopefully the maintainers will go over the list below and
change
Hi all,
Found out today that my patch for supporting encrypted MP4's does not support
seek...
Patch attached
Thanks,
Eran
0001-mov-support-seek-in-encrypted-mp4.patch
Description: 0001-mov-support-seek-in-encrypted-mp4.patch
___
ffmpeg-devel mailing
Bumping... same patch attached
Thanks
Eran
0001-mov-support-seek-in-encrypted-mp4.patch
Description: 0001-mov-support-seek-in-encrypted-mp4.patch
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> Thanks for that clarification. Unfortunately the http server is a third
> party camera that broadcasts a WiFi hotspot. Therefore we don't really
> have control over the underlying server. However, what I do know is
> that the ffmpeg command I quoted previously seems to be able to
> grab a chun
Ping
Thanks
Eran
0001-mov-support-seek-in-encrypted-mp4.patch
Description: 0001-mov-support-seek-in-encrypted-mp4.patch
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> can you create a fate test for this ?
> maybe seek-test could be simply used?
>
Sure, can you point me to some existing test that is similar enough for me to
use as a reference ?
I read the Wiki page about adding a test, but not quite sure how to apply it
here
> thanks
>
> [...]
> --
> M
>
> check tests/fate/seek.mak
> also you can pass parameters to seek-test see fate-seek-cache-pipe
> i dont know if there is anything else special needed for this
>
Thanks Michael, I looked at this some more, and there's one thing that I'm still
missing - where do I get the sample encrypted file f
> > >
> > > check tests/fate/seek.mak
> > > also you can pass parameters to seek-test see fate-seek-cache-pipe
> > > i dont know if there is anything else special needed for this
> > >
> > Thanks Michael, I looked at this some more, and there's one thing that I'm
> > still
> > missing - where do
Hi all,
We found today that this change:
https://github.com/FFmpeg/FFmpeg/commit/ca6cae73db207f17a0d5507609de12842d8f0ca3
can break the decryption of MP4s encrypted with common encryption.
I would like to submit a patch for that, but wanted to consult first about the
best approach.
The problem
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Sasi
> Inguva
> Sent: Friday, January 6, 2017 8:25 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] mov: support for multiple edits and cenc
> decryption
>
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Sasi
> Inguva
> Sent: Wednesday, January 18, 2017 3:30 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] mov: support for multiple edits and cenc
> decryption
>
> inconsistet in git
>
> some say:
> Author: erankor
>
> some say:
> Author: Eran Kornblau
>
> Is the way the patches are intended ?
> Just double checking as it cannot be changed later
>
Thanks Michael & Sasi!
My GitHub user is erankor, that's t
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, February 1, 2017 3:53 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] mov: support for multiple edits and cenc
> d
265 stream.
> >> ---
> >> On 06/03/18 17:27, Hendrik Leppkes wrote:
> >>> On Tue, Mar 6, 2018 at 3:51 PM, Eran Kornblau
> >>> wrote:
> >>>> Hi all,
> >>>>
> >>>> The attached patch adds a parameter that enables t
Hi all,
The attached patch adds a parameter that enables the user to choose which
AVC/HEVC NAL units to include in the output.
The parameter is supplied as a bitmask in order to keep things simple.
A short background on why we need it - in our transcoding process, we partition
the video in chun
Hi,
This patch adds 2 options to http:
- reconnect_on_status - a list of http status codes that should be retried. the
list can contain explicit status codes or the strings 4xx/5xx.
- reconnect_on_err - reconnects on arbitrary errors during connect, e.g.
ECONNRESET/ETIMEDOUT.
The retry employs
Ping
Thanks,
Eran
From: Eran Kornblau
Sent: Sunday, October 25, 2020 3:40 PM
To: FFmpeg development discussions and patches
Subject: [PATCH] http: support retry on connection error
Hi,
This patch adds 2 options to http:
- reconnect_on_status - a list of http status codes that should be
Pinging again...
Thanks,
Eran
From: Eran Kornblau
Sent: Sunday, October 25, 2020 3:40 PM
To: FFmpeg development discussions and patches
mailto:ffmpeg-devel@ffmpeg.org>>
Subject: [PATCH] http: support retry on connection error
Hi,
This patch adds 2 options to http:
- reconnect_on_stat
Another ping... would be great to have some feedback on this...
Eran
From: Eran Kornblau
Sent: Sunday, November 8, 2020 8:59 AM
To: FFmpeg development discussions and patches
Subject: RE: [PATCH] http: support retry on connection error
Pinging again...
Thanks,
Eran
From: Eran Kornblau
Sent
Hi,
The attached patch adds rendering of ATSC A/53 captions as HEVC SEI messages.
The option name/implementation is aligned with the corresponding libx264
feature.
Thanks
Eran
0001-libx265-support-ATSC-A-53-captions.patch
Description: 0001-libx265-support-ATSC-A-53-captions.patch
___
Ping
From: Eran Kornblau
Sent: Monday, 17 October 2022 19:29
To: FFmpeg development discussions and patches
Subject: [PATCH] libx265: support ATSC A/53 captions
Hi,
The attached patch adds rendering of ATSC A/53 captions as HEVC SEI messages.
The option name/implementation is aligned with the
Another ping…
From: Eran Kornblau
Sent: Monday, 17 October 2022 19:29
To: FFmpeg development discussions and patches
mailto:ffmpeg-devel@ffmpeg.org>>
Subject: [PATCH] libx265: support ATSC A/53 captions
Hi,
The attached patch adds rendering of ATSC A/53 captions as HEVC SEI message
Trying again…
From: Eran Kornblau
Sent: Monday, 17 October 2022 19:29
To: FFmpeg development discussions and patches
mailto:ffmpeg-devel@ffmpeg.org>>
Subject: [PATCH] libx265: support ATSC A/53 captions
Hi,
The attached patch adds rendering of ATSC A/53 captions as HEVC SEI message
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Timo
> Rothenpieler
> Sent: Tuesday, 8 November 2022 13:33
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libx265: support ATSC A/53 captions
>
> >
> > The attached patch adds rendering of ATSC A/53 captions a
>
> On 08.11.2022 15:25, Eran Kornblau wrote:
> >>
> >> -Original Message-
> >> From: ffmpeg-devel On Behalf Of
> >> Timo Rothenpieler
> >> Sent: Tuesday, 8 November 2022 13:33
> >> To: ffmpeg-devel@ffmpeg.org
> &g
Hi Marton,
Thank you for the feedback, and sorry for my late reply :)
Please see my responses inline, updated patch attached.
Thanks
Eran
> -Original Message-
> From: ffmpeg-devel On Behalf Of Marton
> Balint
> Sent: Wednesday, November 18, 2020 10:46 PM
> To: FFmpeg development discus
Resending...
-Original Message-
From: Eran Kornblau
Sent: Thursday, December 3, 2020 10:52 AM
To: FFmpeg development discussions and patches
Subject: RE: [FFmpeg-devel] [PATCH] http: support retry on connection error
Hi Marton,
Thank you for the feedback, and sorry for my late reply
Ping...
-Original Message-
From: Eran Kornblau
Sent: Thursday, December 10, 2020 8:25 AM
To: FFmpeg development discussions and patches
Subject: RE: [FFmpeg-devel] [PATCH] http: support retry on connection error
Resending...
-Original Message-
From: Eran Kornblau
Sent
Pinging again... hope this can be merged...
-Original Message-
From: Eran Kornblau
Sent: Wednesday, December 16, 2020 9:18 PM
To: FFmpeg development discussions and patches
Subject: FW: [FFmpeg-devel] [PATCH] http: support retry on connection error
Ping...
-Original Message
It's been 2 months since I submitted this patch (25/10), got a single reply to
which I answered below... Can this be merged?
Thanks,
Eran
-Original Message-
From: Eran Kornblau
Sent: Wednesday, December 23, 2020 8:14 PM
To: FFmpeg development discussions and patches
Subjec
Hi all,
We're thinking about adding support for MP4 files encrypted using the CENC
scheme to ffmpeg (such as the ones supported by GPAC -
https://gpac.wp.mines-telecom.fr/mp4box/encryption/common-encryption/)
The motivation is to be able to transcode files without having the media ever
resident
vember 25, 2015 1:56 AM
To: FFmpeg development discussions and patches
Cc: Eran Kornblau ; Eran Etam
Subject: Re: [FFmpeg-devel] support for reading / writing encrypted MP4 files
On Tue, 24 Nov 2015 12:10:43 +
Eran Kornblau wrote:
> Before we start working on this feature, since we really
> Hi,
>
> Please do not top post.
>
Sorry, I hope this one comes out fine, didn't find a reasonable way to do it
with Outlook ;-(
>
> Please send the patches to the mailing list. See
> https://github.com/FFmpeg/FFmpeg/pull/153
>
Attached, note there are two files, the second commit is just a tiny
Hi
> No, please merge them (without adding trailing whitespace, it cannot
> be committed to our repository).
> While at it, please fix this nit (several times):
> > +}
> > +else {
>
> should be on one line, there is tools/patcheck that should have told
> you (and also tells you about tr
Hi
> One more question: Is FFmpeg able to decrypt the files (if the keys are
> available)? If not, it would be nice if you could also add the decryption
> function...
> (I only realize now that the subject promises both.)
> In any case, a fate test will be needed (but is not necessarily part of
Hi,
Sorry for spamming, ran some more tests and found a bug in my patch, updated
patch file attached.
The bug was that in case subsample encryption was enabled (the default for AVC)
the subsample size
reported in the 'saiz' atom was wrong - it did not include the size of the IV.
I originally tes
>
> changes to libavutil and libavformat should likely be in seperate
> patches/commits, more generally any independant changes should be
> in seperate patches (i dont know if there are any other changes that
> should be split off)
>
Done, new patch files attached, I also included the patch for d
Hi,
Bumping up this thread... please let me if you want me to make any additional
changes or this can be merged.
Attaching the patch files again (same ones I sent in my last post)
Thank you
Eran
0001-libavutil-add-aes-ctr-support.patch
Description: 0001-libavutil-add-aes-ctr-support.patch
0
>
> using a random IV value would break any regression tests
> see AVFMT_FLAG_BITEXACT
>
Fixed, only generating a random IV when bitexact is not enabled.
Updated patch files attached.
>
> is this filling in a random IV that later is overridden ?
> random_seed() can be slow so it would be better
> are these encrypted mp4 files some kind of standard encryption?
>
Yes, these files conform to the common encryption specification ISO/IEC 23001-7
> rephrased... will encrypted files created by ffmpeg be able to be
> decrypted/decoded and played by quicktime? or any other player?
> (assuming oth
> >
> > +struct AVAESCTR;
>
> Is this needed?
>
Indeed compiles for me without it, I matched the existing code in aes.h, and in
general I prefer to define the structs in advance.
If you prefer that I will remove it, please let me know
> > +subsample_count = AV_RB16(sc->cenc.auxiliary_info_
Bumping up this thread, would love to see this getting merged
(attaching the same patch files)
Thank you
Eran
0001-libavutil-add-aes-ctr-support.patch
Description: 0001-libavutil-add-aes-ctr-support.patch
0002-movenc-support-cenc-common-encryption.patch
Description: 0002-movenc-support-cenc-
>
> Weren't patches 1&2 already applied?
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=23ac99dc
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=4469e8eb
>
You're right, didn't know that.
Please let me know if there are any changes you want me to apply in order to
push the third o
r
'enca'
please let me know which one you prefer, and I will update the patch.
> [...]
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
Thanks a lot, Michael !
Eran
0001-add-Eran-Kornblau-to-maintainers.patch
Description: 0001-add-
> you are not subscribed (with this email address you used here at least
> it seems)
>
Right, apparently the subscription confirmation message went to the junk
folder...
Anyway, glad this one is now resolved :-) and sorry for the trouble.
> > >
> > > > +id = mov_codec_id(st, format);
> > > >
Bumping up this thread (latest patch attached)
Happy holidays !
Eran
0001-mov-support-cenc-common-encryption.patch
Description: 0001-mov-support-cenc-common-encryption.patch
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mail
> > +case MKTAG('e','n','c','v'):// encrypted video
> > +case MKTAG('e','n','c','a'):// encrypted audio
> > +id = mov_codec_id(st, format);
> > +st->codec->codec_id = id;
>
> this seems missing a check for st->codec->codec_id being "unset"
> before setting i
> > > > +case MKTAG('e','n','c','v'):// encrypted video
> > > > +case MKTAG('e','n','c','a'):// encrypted audio
> > > > +id = mov_codec_id(st, format);
> > > > +st->codec->codec_id = id;
> > >
> > > this seems missing a check for st->codec->codec_id being "u
> > Please let me know if you think that is ok, and I will resubmit the patch
> > with all fixes.
>
> should be ok
>
Updated patch attached, diff from previous patch is:
--- a/libavformat/mov.c
+++ b/libavformat/mov.c
@@ -4026,6 +4026,14 @@ static int mov_read_frma(MOVContext *c, AVIOContext *p
> after having updated our application to latest head, we get tons of
> annoying warnings like this one:
>
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x102007800] ignoring 'frma' atom of 'mp4a',
> stream format is 'mp4a'
>
Patch attached - it simply doesn't print the warning when the format contained
in the
Hi all,
We encountered a rather extreme edge case with qt-faststart - we transcoded
some video with ffmpeg,
and the offset of the last video frame in the resulting mp4 was slightly less
than 4GB.
Since it was less than 4GB, ffmpeg used an 'stco' atom and not a 'co64' atom.
When we ran qt-faststa
Hi,
The attached patch fixes a couple of input validation issues in fast start that
I noticed while going over the code
Thanks
Eran
0001-qt-faststart-stricter-input-validations.patch
Description: 0001-qt-faststart-stricter-input-validations.patch
__
Hi,
The attached is a slightly more optimized (and IMHO elegant) code for updating
the stco/co64 offsets
Thanks
Eran
0002-qt-faststart-optimize-the-offset-change-loop.patch
Description: 0002-qt-faststart-optimize-the-offset-change-loop.patch
___
ffm
>
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, May 30, 2018 12:37 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] qt-faststart - optimize the offse
> On Wed, May 30, 2018 at 05:39:50AM +0000, Eran Kornblau wrote:
> > >
> > >
> > > -Original Message-
> > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> > > Behalf Of Michael Niedermayer
> > > Sent: Wedn
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Eran
> Kornblau
> Sent: Friday, May 25, 2018 4:40 PM
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] qt-faststart bug near 4GB
>
> Hi
> On Thu, May 31, 2018 at 10:11:38AM +0000, Eran Kornblau wrote:
> > >
> > > -Original Message-
> > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> > > Behalf Of Eran Kornblau
> > > Sent: Friday, May 25, 2018 4:40 PM
>
Ping
-Original Message-
From: Eran Kornblau
Sent: Friday, June 1, 2018 10:00 AM
To: FFmpeg development discussions and patches
Subject: RE: [FFmpeg-devel] qt-faststart bug near 4GB
> On Thu, May 31, 2018 at 10:11:38AM +0000, Eran Kornblau wrote:
> > >
> > >
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Saturday, June 9, 2018 9:17 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
>
> > +
> > +if
> On Sun, Jun 10, 2018 at 01:20:10PM +0000, Eran Kornblau wrote:
> > >
> > > -Original Message-
> > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> > > Behalf Of Michael Niedermayer
> > > Sent: Saturday, June 9, 2018 9:17
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, June 13, 2018 1:41 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
>
>
> this is not ma
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, June 13, 2018 12:26 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
>
> fails on mingw64
This patch makes qt-faststart output errors to stderr instead of stdout,
following a discussion with Michael on another thread...
Thanks!
Eran
0001-qt-faststart-print-errors-to-stderr.patch
Description: 0001-qt-faststart-print-errors-to-stderr.patch
> Hi
>
> I've recently been looking at formal proof systems for minimizing bugs.
> One common example is SPARK, which is an Ada variant which uses contracts,
> guaranteed termination and lack of dynamic allocation to make reasoning about
> SPARK programs much easier. This allows automatic checki
-concept
> (kinda)
>
> > fre 2018-06-22 klockan 14:07 + skrev Eran Kornblau:
> > First, regarding the if you added, it's redundant - if you look a few lines
> > above, you'll see 'if (atom.size < atom.header_size)'.
> > atom.header_size is eithe
Hi all,
I noticed today that the cc decoder doesn’t support multiple channels – I have
some MPEG-TS file with 3 cc languages,
when I request ‘-data_field 0’, I’m getting the first two together, while
‘-data_field 1’ returns the third one.
This patch adds another optional param ‘channel’ that can
84 matches
Mail list logo
