FFmpeg

117855 Commits

37 Branches

400 Tags

492 MiB

Tag: Branch: Tree: f298507323

Commit Graph

Author	SHA1	Message	Date
Lynne	eb536d97a0	ffv1enc_vulkan: support buffers larger than 4GiB Unlike the software FFv1 encoder, none of our buffers are allocated by FFmpeg, which supports at most 4GiB large allocations. For really large sizes, the maximum size of the buffer can exceed 4GiB, which the software encoder optimistically tries to allocate as 4GiB in the hopes that the encoder will compress to under that amount. We can just let Vulkan allocate us a larger buffer, and switch to 64-bit offsets.	3 months ago
Lynne	66093c5b94	ffv1enc_vulkan: restrict number of execution contexts to 1 This only leads to wasting memory in a single-threaded operation. Limit this to 1 for now and leave a comment.	4 months ago
Lynne	ed2391d341	ffv1enc: add a Vulkan encoder This commit implements a standard, compliant, version 3 and version 4 FFv1 encoder, entirely in Vulkan. The encoder is written in standard GLSL and requires a Vulkan 1.3 supporting GPU with the BDA extension. The encoder can use any amount of slices, but nominally, should use 32x32 slices (1024 in total) to maximize parallelism. All features are supported, as well as all pixel formats. This includes: - Rice - Range coding with a custom quantization table - PCM encoding CRC calculation is also massively parallelized on the GPU. Encoding of unaligned dimensions on subsampled data requires version 4, or requires oversizing the image to 64-pixel alignment and cropping out the padding via container flags. Performance-wise, this makes 1080p real-time screen capture possible at 60fps on even modest GPUs.	4 months ago

Author

SHA1

Message

Date

Lynne

eb536d97a0

ffv1enc_vulkan: support buffers larger than 4GiB

Unlike the software FFv1 encoder, none of our buffers are allocated by
FFmpeg, which supports at most 4GiB large allocations.

For really large sizes, the maximum size of the buffer can exceed 4GiB,
which the software encoder optimistically tries to allocate as 4GiB
in the hopes that the encoder will compress to under that amount.

We can just let Vulkan allocate us a larger buffer, and switch to
64-bit offsets.

3 months ago

Lynne

66093c5b94

ffv1enc_vulkan: restrict number of execution contexts to 1

This only leads to wasting memory in a single-threaded operation.
Limit this to 1 for now and leave a comment.

4 months ago

Lynne

ed2391d341

ffv1enc: add a Vulkan encoder

This commit implements a standard, compliant, version 3 and version 4
FFv1 encoder, entirely in Vulkan. The encoder is written in standard
GLSL and requires a Vulkan 1.3 supporting GPU with the BDA extension.

The encoder can use any amount of slices, but nominally, should use
32x32 slices (1024 in total) to maximize parallelism.

All features are supported, as well as all pixel formats.
This includes:
 - Rice
 - Range coding with a custom quantization table
 - PCM encoding

CRC calculation is also massively parallelized on the GPU.

Encoding of unaligned dimensions on subsampled data requires
version 4, or requires oversizing the image to 64-pixel alignment
and cropping out the padding via container flags.

Performance-wise, this makes 1080p real-time screen capture possible
at 60fps on even modest GPUs.

4 months ago

3 Commits (f298507323a688bf89e9d3b44d7529edf80de909)