31–40 of 47 posts
Earlier quoted context omitted.
The question you should be asking is 'why I still see animated gifs in 2020?'
Do you? I thought many ‘animated GIFs’ aren’t GIF files anymore. Twitter, for example, serves MP4 files ( https://techcrunch.com/2014/06/19/gasp-twitter-gifs-arent-ac... )
If I wanted to develop a custom JPEG decoder, what would be the easiest way to get image data from a jpeg file into Tensorflow (or numpy, Pytorch, etc.) tensors? I mean the raw DCT coefficients, and the coefficient table?
Thought about writing an hex editor or adding the hex fiend functionality to other hex editors based on the templates of hex fiend.
[0] http://ridiculousfish.com/hexfiend/
why i still see jpeg in 2020 ?
It works incredibly well for a format its age. It's simple, and widely supported. Internally, JPEG has the key techniques required to compress photos well, and nothing else. Most newer formats are based on the same principles, except each bit is upgraded to the point of diminishing returns. HEIF and AVIF compress twice as well as JPEG, but in terms of complexity and computational requirements are hundreds of times mo…
The economics of the camera market right now will make adoption of new formats (and the additional/more expensive hardware in the camera to support it) slow and jpeg is a very reasonable format for photographers to shoot when they don't want/need to shoot raw.
H.261 (a video format) is roughly of the same if not slightly less complexity, and also makes a good weekend project.
I think they mean JAY-pheg.
Hexfiend (open source hex editor for mac) [0] and synalize it [1] (closed source hex editor for mac) both support a similar feature (hexfiend only in the newest github release) that shows the structure of known file formats similar to what wireshark [2] does for network packages. Thought about writing an hex editor or adding the hex fiend functionality to other hex editors based on the templates of hex fiend. [0] htt…
If you're looking for a fun project that can be completed in a weekend or less, one of the things I recommend is to write a (baseline) JPEG decoder. The official spec (linked from the article near the top) is quite readable as far as standards go, and even contains helpful flowcharts for basically the whole process. When I did it, it took less than 1kLoC of C, including some minor optimisations like array-based Huffm…