Daemon404

5 ms·

1.
Tell HN: Bending Spoons laid off almost everybody at Vimeo yesterday
471 points by Daemon404 8mo ago|505 comments
2.
by Daemon404 1y ago
There's quite some time until the next release, I believe, so it should be. The biggest thing missing right now is NACK support, and one of the authors has said they intend to do this (along with fixing old OpenSSL version support, and
3.
by Daemon404 1y ago
(long time FFmpeg dev here) You are being downvoted, but you are entirely correct. This is also explicitly not allowed in FFmpeg, but this was pushed after many months, with no heads up on the list, no final review sign off, and with some d
4.
Native VVC decoder merged into FFmpeg Git(twitter.com)
4 points by Daemon404 3y ago|0 comments
5.
by Daemon404 3y ago
It is widely known and accepted that you need to dynamically link to satisfy the LGPL (you can static link if you are willing to provide your object files on request). There is a tl;dr here that isn't bad: https://fossa.co
6.
by Daemon404 3y ago
You have that backwards - it must be dynamically linked. Static linking without providing your source would violate the LGPL.
7.
by Daemon404 4y ago
This is a constant issue for me (Chrome on Android) on GMail's Web UI (yes, I insist on using the Web UI...). So many emails are entirely unreadable since they go right off the right side, and you can't zoom.
8.
by Daemon404 4y ago
Pretty much everyone (including my $dayjob) seems to do some webm parsing, rewiting, and/or remuxing in JS, or on the backend post-record. There are half a dozen ad hoc webm parsers floating around GitHub for this reason, and a few mor
9.
by Daemon404 5y ago
I can only speak for myself here, but why would step 1 be "become a user"? I ask because I don't fully grok why I would want to contribute to a project I don't use (either in my personal time, or work time)?
10.
by Daemon404 5y ago
The demo seems to never load for me on Android Chrome? It sits with an off-center spinner forever.
11.
by Daemon404 5y ago
Chrome does seem to save the JPEG version on some WebP or AVIF URLs where there is also a JPEG version available too, although it seems to be 'clever' about it rather than explicitly offering the option, which can make saving the
12.
by Daemon404 5y ago
It's been my experience that part of the reason browsers get stuff wrong even when it's clear what to do, is that entirely different teams work on parts of the browser that all need a poper color pipeline, and while one team will
13.
by Daemon404 5y ago
This is one place the ISOBMFF spec really screwed up, in my opinion. They should have included semantics for the colr box, i.e. which takes precedence. Intead we get: "Colour information may be supplied in one or more ColourInformation
14.
FFmpeg is 20 years old today(twitter.com)
462 points by Daemon404 6y ago|93 comments
15.
by Daemon404 6y ago
> discontinuing RD in to the browser space Not just the browser space; they axed e.g. all their people involved in AOM and video R&D, despite being a founding member.
16.
by Daemon404 6y ago
I would perhaps wait until rav1e 0.4, because there is a bug in the FFmpeg wrapper (of which I am the author) right now that breaks timestamps. If you wish to build with rav1e master, you can apply this to fix it: https://github.
17.
A Future Without MPEG(blog.chiariglione.org)
103 points by Daemon404 6y ago|61 comments
18.
by Daemon404 6y ago
Sounds mostly like the issue is nobody has bothered to submit a proposal for it then? (There is so much in-the-wild experience and code dealing with this issue, I cannot imagine the second point being problematic.) On the third point, I h
19.
by Daemon404 6y ago
An easy (and problematic) example is decimal separators (radix characters) being parsed or written differently based on locale.
20.
by Daemon404 6y ago
What has been the rationale or hinderance for not adding locale-independent versions of various stdlib functions? Practically every second C codebase on earth has their own implementations of these at some point, and it remains a huge probl
21.
by Daemon404 7y ago
Not a commit but from the same author, so you may enjoy: https://github.com/wm4/dingleberry-os/blob/master/README.rst It does go off on a few tangents, but it's an interesting read.
22.
Why does Google open source stuff but not care about open source?(github.com)
3 points by Daemon404 7y ago|0 comments
23.
by Daemon404 7y ago
Based on the rest of the blog, I can't actually tell if this is tongue-in-cheek or not...
24.
by Daemon404 7y ago
Possibly, yes. Although, having a usable QUIC library and/or adding it to libcurl would have been less controversial.
25.
by Daemon404 7y ago
Their motivation isn't really made clear in the bug (easier for developers to switch to is a little too vague), but if I had to guess, I'd bet the actual reason is that they want the debug/insight/whatever features from
26.
by Daemon404 7y ago
Part of the problem is that the documentation is so vast (the page you link is only one of many, many pages; the documentation has been split out into multiple pages for a while now) that as a user, it's fairly insane to try and consum
27.
by Daemon404 7y ago
You've got cause and effect backwards there (mostly; it goes both ways). Disclosure: FFmpeg contributor and Vimeo employee.
28.
by Daemon404 8y ago
> In my experience the behavior is stable i.e. doesn't often change between rebuilds (at least in VC++). This is less true when you try and support many versions of many compilers, however, in my experience.
29.
by Daemon404 8y ago
> It will get there, I remember a collegue saying about 10 years ago "software encoding SD in realtime is fine, but you won't be able to do it reliably in HD" As an aside, you could already do realtime H.264 HD encoding 10
30.
by Daemon404 8y ago
The slice approach should be pretty readily doable today with e.g. libx264 (which you can force exactly N rectangular (full-row) slices with, using i_slice_count), and calculating N based on the resolution of the eleven vertically and horzi

More ›