http://archive.is/K5Fpv
TIL: EE, a mobile provider, blocks archive.is as unsafe content for people under 18. https://twitter.com/nvartolomei/status/1133644305812381696
Adventures with ffmpeg and color ranges
51–60 of 94 posts
Re: Adventures with ffmpeg and color ranges
#52Not sure if this kind of meta-comment is appropriate, but I find it difficult to follow a link like this because of the lack of human readable information contained in the URL. If the story was hosted on a personal blog I recognised (like Julia Evans to take a random example), then perhaps the domain would be enough for me to choose to read the article to see if the content is interesting. If the link was to a broade…
Another site that comes to mind is the Financial Times, which uses UUIDs for article urls, with no other indication of content. https://www.ft.com/ https://www.ft.com/content/13be9132-8149-11e9-b592-5fe435b57...
Oh wow, you really have to hope these are not the canonical links. If so, they are doing themselves an incredible disservice and the fact that no one has brought it to management's attention speaks gravely to the workplace culture there.
Re: Adventures with ffmpeg and color ranges
#53For all of our sanity, please don't start producing 8-bit H.264 videos with full 0-255 range.
If you have enough control over the decoder and renderer to make that hack work, you should just be producing 10-bit HEVC/AV1 video – which does not suffer from these 8-bit banding issues – with a modern color space (Rec 2020, PQ, etc.).
And if you don't have choice or control over the decoder and renderer, then it's a good sign that this would be a fragile hack.
Re: Adventures with ffmpeg and color ranges
#54Not sure if this kind of meta-comment is appropriate, but I find it difficult to follow a link like this because of the lack of human readable information contained in the URL. If the story was hosted on a personal blog I recognised (like Julia Evans to take a random example), then perhaps the domain would be enough for me to choose to read the article to see if the content is interesting. If the link was to a broade…
The title actually used to say Carmack, so I guess a HN moderator removed it...
Re: Adventures with ffmpeg and color ranges
#55For all of our sanity, please don't start producing 8-bit H.264 videos with full 0-255 range. If you have enough control over the decoder and renderer to make that hack work, you should just be producing 10-bit HEVC/AV1 video – which does not suffer from these 8-bit banding issues – with a modern color space (Rec 2020, PQ, etc.). And if you don't have choice or control over the decoder and renderer, then it's a good…
Logitech C920 family cameras do exactly that. H264 full range.
Re: Adventures with ffmpeg and color ranges
#56Earlier quoted context omitted.
Another site that comes to mind is the Financial Times, which uses UUIDs for article urls, with no other indication of content. https://www.ft.com/ https://www.ft.com/content/13be9132-8149-11e9-b592-5fe435b57...
Oh wow, you really have to hope these are not the canonical links. If so, they are doing themselves an incredible disservice and the fact that no one has brought it to management's attention speaks gravely to the workplace culture there.
Not only does the full URL not show in my browser (Safari), the full URL doesn't even show on this forum (for me it is cut off after "content"). When you receive a URL via chat or on social networks, it is in the form of a preview and might not even show the domain name. The user also isn't typing these URLs in, with or without human readable text in the path. Essentially all of the arguments for making URLs more brittle (which is what you are doing by adding human readable text) are obsolete in a world where URLs have been relegated back to what they were always supposed to be: permanent identifiers to a semantically stable unit of content.
Re: Adventures with ffmpeg and color ranges
#57Earlier quoted context omitted.
No, limited range is the most common and expected range for YUV videos. Many players don't look or respect the container metadata such as nclx in MP4 or the bitstream VUI flags and assume limited range.
This is correct. In fact, the following statement from the post is nonsense: > For arcane reasons related to TV broadcast limitations, many video formats restrict the YUV color components to be in the 16..235 or 16..240 range instead of the full 0..255 range. Losing 14% of the already-barely-enough 8 bit dynamic range is bad enough, but it also often results in the black range starting at a quite visible grey value b…
Wow! Talladega nights was the first movie I saw on a Bluray setup. (PS3 at a friends.) I was shocked at how badly mastered it was. It sounds exactly like that problem. Everything was washed out.
Re: Adventures with ffmpeg and color ranges
#58Not sure if this kind of meta-comment is appropriate, but I find it difficult to follow a link like this because of the lack of human readable information contained in the URL. If the story was hosted on a personal blog I recognised (like Julia Evans to take a random example), then perhaps the domain would be enough for me to choose to read the article to see if the content is interesting. If the link was to a broade…
Isn‘t a quick glance at the article enough to decide whether or not to read the article? It‘s not like you are forced to read the article after all.
Re: Adventures with ffmpeg and color ranges
#59Version you can view with JS disabled: https://mbasic.facebook.com/permalink.php?story_fbid=2413101...
Re: Adventures with ffmpeg and color ranges
#60http://archive.is/K5Fpv
TIL: EE, a mobile provider, blocks archive.is as unsafe content for people under 18. https://twitter.com/nvartolomei/status/1133644305812381696
That sounds correct to me, since it could contain NSFW content, and by default, mobile providers in England have content controls switched on.