| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This was a typo.
|
|
|
|
| |
This commit permits any stacking of FFTs of any size.
|
|
|
|
|
| |
Rather than using a list of lengths supported, this goes a step beyond
and uses all registered codelets to come up with a good decomposition.
|
|
|
|
| |
Necessary for generalizing PFAs.
|
| |
|
|
|
|
|
| |
Now prints the actual codelet size used, as well as the number of
allowed factors.
|
| |
|
|
|
|
|
| |
This function allows implementations to clean up a context after
successfully initializing subcontexts.
|
| |
|
|
|
|
| |
Only powers of two are currently supported.
|
|
|
|
| |
Enables its use everywhere else in the framework.
|
| |
|
|
|
|
| |
Allows them to be used in general PFAs.
|
|
|
|
| |
This is much faster than the loop.
|
|
|
|
| |
No longer necessary.
|
|
|
|
|
| |
This makes testing easier, as a unified path can be used for in/out of
place transforms.
|
|
|
|
|
| |
We assume that _all_ in-place transforms can operate out of place,
which isn't true, because the C ptwo transforms were always in-place (dst).
|
|
|
|
|
| |
The same as naive but with precomputed tables. Makes it more useful
for odd-factors we don't support yet.
|
|
|
|
| |
Allows them to be picked just like any other transform.
|
|
|
|
| |
Not that useful, but it gives us fast small odd-length transforms.
|
|
|
|
| |
They all overwrote in[0] and then used it as a DC.
|
|
|
|
|
|
|
|
|
|
|
| |
The encoder is sensitive to changes in precision, and its test target
was a compromise. It was already close to failing on x87 FPUs.
ff_mdct_init used double precision entirely from the scale to computing
the MDCT exp tables. av_tx_init uses single-precision for the scale,
with a small input change which was enough to tip the test into failing on
x87 FPUs.
Increase the fuzz factor in line with other AAC encoder tests to fix.
|
|
|
|
| |
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
| |
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
|
|
|
|
|
|
|
| |
AVCodecContext.frame_number is actually only incremented
in case encoding was successfull; if e.g. the ff_alloc_packet()
below fails, it won't be incremented and therefore it is possible
for the previous_frame buffer to be allocated for multiple
first frames, leaking every one except the last.
So check for whether there already is a previous frame instead.
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
| |
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
| |
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The earlier code did not account for the frame header as well
as the block headers; furthermore, in case a large part of
a block is unused (due to padding), the output size may
exceed 3 * width * height (where the dimensions correspond
to the visible pixels) due to the overhead of the zlib header,
so use the padded dimensions to calculate the maximum packet size
(which is also what the actual call to compress2() uses).
Fixes ticket #10053.
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
|
|
|
| |
Fixes the crash in ticket #10050.
Also ensure that we don't overflow before ff_get_encode_buffer().
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
|
|
|
|
|
|
| |
Bring it up to date with current practice, as the current text does not
cover everything. Drop the reference to unprefixed exported symbols,
which do not exist anymore.
|
|
|
|
|
|
| |
It describes a general development policy, not code formatting. It is
also not true, as these days we tend to prioritize correctness, safety,
and completeness over code size.
|
|
|
|
| |
It logically belongs there.
|
|
|
|
|
|
|
|
| |
It is currently very out of touch with reality.
* declare we are using C99 fully, rather than C90 plus extensions
* mention our use of stdatomic.h
* mention forbidden C99 features, like VLAs and complex numbers
|
|
|
|
|
| |
It makes more sense to first describe the language we are using and only
then document how to format code in it, rather than the reverse.
|
|
|
|
| |
They are not used since 520a5d33f0ea9f8838dbc7282470db700d248065.
|
|
|
|
|
|
|
|
|
| |
Do it in set_dispositions() rather than during stream creation.
Since at this point all other stream information is known, this allows
setting disposition based on metadata, which implements #10015. This
also avoids an extra allocated string in OutputStream that was unused
after of_open().
|
|
|
|
| |
Avoids conflicts, e.g. when 'i' is used in the outvar expression.
|
| |
|
|
|
|
|
| |
There can be zero input streams, with input provided by lavfi complex
filtergraphs.
|
|
|
|
|
|
|
|
|
| |
Replace it with an array of streams in each InputFile. This is a more
accurate reflection of the actual relationship between InputStream and
InputFile.
Analogous to what was previously done to output streams in
7ef7a22251b852faab9404c85399ba8ac5dfbdc3.
|
|
|
|
| |
Skip unusable streams early and do not compute any scores for them.
|
|
|
|
|
| |
This is simpler. The indirection via an index exists for historical
reasons that longer apply.
|
|
|
|
|
|
| |
This code was supposed to affect copying stream dispositions, but it
does not achieve that after bd55552d69, since dispositions are set
earlier.
|
|
|
|
|
|
| |
Encoding init code will currently fall back to a 25fps default when no
framerate is known or specified, but only if there is a known source
input stream. There is no good reason for this condition, so drop it.
|
| |
|