kierank

6 ms·

1.
by kierank 10mo ago
Then you and your security friends will create lots of FUD about FFmpeg being "insecure" with lots of red and the word "critical" everywhere.
2.
by kierank 10mo ago
FFmpeg is developed almost entirely by volunteers. We have no "customers".
3.
Falsehoods programmers believe about [video](haasn.dev)
1 points by kierank 1y ago|0 comments
4.
Maintaining bug-for-bug compatibility between our SRT implementation and libsrt(obe.tv)
1 points by kierank 2y ago|0 comments
5.
by kierank 2y ago
We in FFmpeg need all the instructions and we often need to do register allocations by hand.
6.
by kierank 2y ago
I have tried with Grok3 and Claude. They both seem to have an understanding of the algorithms and data patterns which is more than I expected but then just guess a solution that's often nonsensical.
7.
by kierank 2y ago
I am the author of these lessons. Ask me anything.
8.
by kierank 2y ago
It's crazy that you have to use this custom "embedded" tooling when the vendor should be implementing support in vanilla Linux distros.
9.
by kierank 2y ago
This is premature optimisation. The bus bandwidth and latency needed to get a few Mbps of compressed video to the PC is microscopic. It's completely unnecessary to lock yourself into NVIDIA just to create some UDP packets.
10.
by kierank 2y ago
Because latency is a distribution and these photos are often selected at the best-case P0 end of all the encode/decode processes whereas actually what matters is the worst case P99. A proper implementation will make sure the worst-case
11.
by kierank 2y ago
Backstage feeds go in uncompressed via HD-SDI and have a latency of lines (microseconds to single digit milliseconds). Totally different ballgame.
12.
by kierank 2y ago
I wrote a blog post about how numbers like "30ms latency" are thrown around called "How to lie about latency": https://www.obe.tv/how-to-lie-about-latency/ It's left as an exercise to the reade
13.
How to Lie about Latency(obe.tv)
5 points by kierank 2y ago|0 comments
14.
by kierank 2y ago
I actually saw numerous issues with segments being one frame out of sync with the rest.
15.
by kierank 2y ago
Imagine Ethernet was designed like this and you had to implement mandatory congestion control and other cruft. The layer of the stack that has knowledge of the content should be implementing the congestion control.
16.
by kierank 2y ago
I'm sure SAP reads mastodon and will be right on it
17.
by kierank 2y ago
The Firefox PDF reader is atrocious. Opening any non-trivial PDF causes it to crash even on an i9 with 32GB of RAM. I guess this is because it's rendering the pdf to HTML.
18.
by kierank 2y ago
VVC is marked as experimental as fuzzing continues on it.
19.
by kierank 2y ago
(author of the post on X) We cannot tell volunteers to not do something (i.e help Microsoft) in the same way we cannot tell volunteers to do something.
20.
by kierank 2y ago
(author of the post on X) To clarify, Microsoft didn't offer a one-time payment to fix any bug. A volunteer explained for free that a command line option had changed between FFmpeg versions. Microsoft offered a one-off payment instead
21.
by kierank 2y ago
Hi, this is a high priority ticket and FFmpeg is used in highly visible products all over the world. We have developers working for free while trillion dollar corporations want urgent help from volunteers. Please help, /s
22.
by kierank 2y ago
v210_planar_pack_8_c: 2298.5 v210_planar_pack_8_ssse3: 402.5 v210_planar_pack_8_avx: 413.0 v210_planar_pack_8_avx2: 206.0 v210_planar_pack_8_avx512: 193.0 v210_planar_pack_8_avx512icl: 100.0 23x speedup. The compiler isn't going to com
23.
by kierank 2y ago
x86inc.asm takes care of the different OS ABI differences for you.
24.
by kierank 2y ago
FFmpeg code by definition is not "basic SIMD code". And it supports numerous other compilers other than LLVM.
25.
by kierank 2y ago
That "20 minute patch" will need to be maintained for decades to come in FFmpeg, long after a standalone JPEG-XL library. Potentially centuries as archives like the Library of Congress are storing FFmpeg. So that's why it&#x2
26.
by kierank 3y ago
This isn't a surprise from an organisation that opened a ticket on the FFmpeg tracker asking volunteers for free "high priority" support: https://trac.ffmpeg.org/ticket/10341#comment:4
27.
by kierank 3y ago
> It is impossible for the audio to drift ahead of or behind the video, regardless of the video framerate or audio samplerate. How is this "impossible" if the video clock and audio clock are on different physical devices?
28.
Library of Congress: Embracing FFV1 in Matroska Container as a Preferred Format(blogs.loc.gov)
1 points by kierank 3y ago|0 comments
29.
by kierank 3y ago
Exactly, just pretending to ignore the 80% of the market that isn't critical or safety of life and saying it's not true "embedded industry" (or True Scotsman) is just ignoring the reality.
30.
by kierank 3y ago
Exactly as you see in this comment chain, engineers at startups get fed up of the embedded industry being stuck in the 1980s (long sales process with many meetings and salespeople, custom blobs galore, custom distros, long lead times, high

More ›