gyan

The version number gaps are misleading.

Any change in major or minor number indicates a new release branch. And the convention since 5.0 has been to go 0 --> 1 --> 0 --> 1 ... for each new branch.

Changelog:

- Extend AMF Color Converter (vf_vpp_amf) HDR capabilities

- LCEVC track muxing support in MP4 muxer

- Playdate video encoder and muxer

- Add v360_vulkan filter

- HE-AAC 960 decoding (DAB+)

- transpose_cuda filter

- Add AMF Frame Rate Converter (vf_frc_amf) filter

- SMPTE 2094-50 metadata support and passthrough

- ProRes RAW VideoToolbox hwaccel

- APV Vulkan hwaccel

- Animated WebP decoder

- Animated WebP demuxer

- Remove CELT decoding support (doesn't affect Opus CELT)

- Remove ogg/celt parsing

- Bitstream filter to split Dolby Vision multi-layer HEVC

- Add AMF hardware memory mapping support.

- ONNX Runtime DNN backend with GPU execution provider support

- Remove deprecated NVENC options and support for pre-11.1 SDK versions

If that was the case, the graph would never have gotten to the heights it did.

What happened is that as the corpus of useful info increased, the need to pose new Qs decreased. AI much accelerated that decline by making available an 'oracle' trained on that corpus.

> I’m selling my farm next year.

What will you do for ice cream then?

Yeah, what is the recognition of Jeeves/Wooster among the millennials?

How big is this page and what's the font size?

If you do open PRs at code.ffmpeg.org, remember to disclose and describe the AI contribution. You will also need to add FATE tests.

Changelog:

ffprobe -codec option

EXIF Metadata Parsing

gfxcapture: Windows.Graphics.Capture based window/monitor capture

hxvs demuxer for HXVS/HXVT IP camera format

MPEG-H 3D Audio decoding via mpeghdec

D3D12 H.264 encoder

drawvg filter via libcairo

ffmpeg CLI tiled HEIF support

D3D12 AV1 encoder

ProRes Vulkan hwaccel

DPX Vulkan hwaccel

Rockchip H.264/HEVC hardware encoder

Add vf_scale_d3d12 filter

JPEG-XS parser

JPEG-XS decoder and encoder through libsvtjpegxs

JPEG-XS raw bitstream muxer and demuxer

IAMF Projection mode Ambisonic Audio Elements muxing and demuxing

Add vf_mestimate_d3d12 filter

xHE-AAC Mps212 decoding support (experimental)

Remove the old HLS protocol handler

Vulkan compute codec optimizations

swscale Vulkan support

LCEVC metadata bitstream filter

Add vf_deinterlace_d3d12 filter

ffprobe: only show refs field in stream section when reading frames

ProRes Vulkan encoder

LCEVC parser

LCEVC enhancement layer exporting in MPEG-TS

My earlier flotsam: https://news.ycombinator.com/item?id=47404142

Changelog:

ffprobe -codec option

EXIF Metadata Parsing

gfxcapture: Windows.Graphics.Capture based window/monitor capture

hxvs demuxer for HXVS/HXVT IP camera format

MPEG-H 3D Audio decoding via mpeghdec

D3D12 H.264 encoder

drawvg filter via libcairo

ffmpeg CLI tiled HEIF support

D3D12 AV1 encoder

ProRes Vulkan hwaccel

DPX Vulkan hwaccel

Rockchip H.264/HEVC hardware encoder

Add vf_scale_d3d12 filter

JPEG-XS parser

JPEG-XS decoder and encoder through libsvtjpegxs

JPEG-XS raw bitstream muxer and demuxer

IAMF Projection mode Ambisonic Audio Elements muxing and demuxing

Add vf_mestimate_d3d12 filter

xHE-AAC Mps212 decoding support (experimental)

Remove the old HLS protocol handler

Vulkan compute codec optimizations

swscale Vulkan support

LCEVC metadata bitstream filter

Add vf_deinterlace_d3d12 filter

ffprobe: only show refs field in stream section when reading frames

ProRes Vulkan encoder

LCEVC parser

LCEVC enhancement layer exporting in MPEG-TS

> with ffmpeg you need to make two temporary videos and then concatenate them

It can be done in a single command, no temp files needed.

> These guys did not even bother with an official huggingface space

https://huggingface.co/sarvamai

The dupe is what I linked. The orig is https://superuser.com/questions/601972

The orig wants a mono output with one of the original channels as signal source. This involves downmixing i.e. rematrixing the audio.

The dupe want to just mute one of the channels, not repan it. One can't apply map_channel to do what the dupe wants.

One can use a couple of methods to achieve the dupe, including pan. But the syntax of pan needed for the dupe case is not the same as the orig, or deducible from it. They need to consult the docs (fortuitously, the dupe case is an illustrated example) or get a direct answer. The 'technique' shown in the orig is not intuitively adaptable to the dupe - one needs to know about the implicit muting that pan applies, which is not documented or evident in the orig answer. So it's not a duplicate of the source Q.

> But if you had a personal experience, it will be easier to look within your questions on your profile page.

I answer Qs on this topic, not post them.

----

Here's an example I found:

https://superuser.com/questions/1929615/ (the canonical q is about extracting as mono, the closed q is about muting one channel)

> Please feel free to cite specific examples. I'll be happy to explain policy.

How do I search for Qs closed as duplicates with a certain tag?

You are positing that only questions with cosmetic or extraneous differences are marked as duplicates.

That's not the case. As a maintainer of a popular project who has engaged with thousands of Qs on SO related to that project, I've seen many Qs marked as duplicate where the actual answer would be different in a non-trivial manner. When I look at who all moderated on those Qs, they are usually users who haven't contributed to that topic at SO.

corrected

Except for their immune systems or lactose tolerance.

Remittances for 2023 made up 23% of state GDP.

Table 5.2, pg 51 of https://iimad.org/wp-content/uploads/2024/06/KMS-2023-Report...

> You can’t solve the problem of understanding norms by writing copy

You can mitigate the problem by adding a short summation before or in between something they're likely to read.

Not quite frosted, but I went for a glass pane effect on the sidebar at https://www.gyan.dev/ffmpeg/builds/

> There's a feature request for the open source & cross-platform x265 codec to support transparency, but it doesn't seem to be going anywhere.

x265 has added support for alpha very recently, but only using their standalone CLI. https://bitbucket.org/multicoreware/x265_git/commits/c8c9d22...

No, 16-bit PCM is the default audio codec. If no `-c` is specified for a stream, ffmpeg will encode using the default codec. But if `-c X` is declared where X=`copy` or something else, then that is honored.

This uses the hash muxer in ffmpeg, which consolidates all streams into one. Use the streamhash muxer to emit hashes per-stream, which can isolate any changes to specific streams.