Re:Minih264 – Minimalistic, single-header library for encodi...
by userbinator on Saturday September 22, 2018 @01:33PM
(#18046930)
Wow. The MP3 decoder that just appeared on HN ( https://news.ycombinator.com/item?id=18046114 ) is impressive enough, this is even more amazing --- especially given the fact that the standard doesn't detail how encoding works, only decoding.
The fact that a single person can write a working H.264 encoder is very inspirational, in the same way as tiny C compilers and the like --- writing software which is commonly thought of as being impossible for a single person to accomplish in a reasonable amount of time really gives a better idea of the actual minimal complexity to those studying such software.
Re:Minih264 – Minimalistic, single-header library for encodi...
by userbinator on Saturday September 22, 2018 @05:07PM
(#18047996)
Especially if it's meant to be an educational and in any case non-realtime encoder, intrinsics are not really necessary and make the code less portable.
I also wonder how much the compiler can do autovectorisation on code like this --- it's pretty much exactly the type of code that autovectorisation is intended for.
Edit: I noticed in the benchmark that it compressed the 10s foreman.cif (demo video) in half a second, so it's already 20x faster than realtime on that small resolution.
Re:Minih264 – Minimalistic, single-header library for encodi...
by apocalypses on Saturday September 22, 2018 @03:35PM
(#18047605)
I found this very interesting, particular the comparison to x264 (which I had never heard of).
Looking into it I found x264 looked really easy to use with a nice C api but was encode only - does anyone know of a library very similar to x264 which is both encode/decode?
Re:Minih264 – Minimalistic, single-header library for encodi...
by Game_Ender on Saturday September 22, 2018 @05:07PM
(#18047998)
It has very limited support for H264 advanced profiles that are usually used, which is a down side. I was honestly surprised about the lack of a good decode library.
Re:Minih264 – Minimalistic, single-header library for encodi...
by bloopernova on Saturday September 22, 2018 @03:25PM
(#18047565)
Nice job!
Please forgive my poor understanding of C, but is it possible to add the missing features as extra options/files/headers so you can pick and choose which features you want to enable and/or include?
Re:Minih264 – Minimalistic, single-header library for encodi...
by lieff on Saturday September 22, 2018 @03:53PM
(#18047682)
There already defines to include\exclude features: H264E_MAX_THREADS=n, H264E_SVC_API=1, MINIH264_ONLY_SIMD.
Complete documentation still in progress and subject to change. For now only comments in minih264e.h and minih264e_test.c can tell how to use it.
Re:Minih264 – Minimalistic, single-header library for encodi...
by rjeli on Saturday September 22, 2018 @06:00PM
(#18048234)
Very impressive. Nice work!
I’ve been learning a lot about h264 and h265 recently, and I’ve read that hevc is somewhat more straightforward to decode. Is that true? I might try writing a decoder for it.
Re:Minih264 – Minimalistic, single-header library for encodi...
by disqard on Saturday September 22, 2018 @06:43PM
(#18048385)
Apologies for the OT question, but does anybody know why the foreman video clip is used as a standard test sequence for video encoding? Thanks in advance!
Re:Minih264 – Minimalistic, single-header library for encodi...
by microcolonel on Saturday September 22, 2018 @12:21PM
(#18046582)
These types of encoders are very useful, and I hope to see something in this style emerge for AV1 (an encoder which produces reasonable quality in real time on commodity CPUs, using the appropriate subset of bitstream tools for that job).
The fact that a single person can write a working H.264 encoder is very inspirational, in the same way as tiny C compilers and the like --- writing software which is commonly thought of as being impossible for a single person to accomplish in a reasonable amount of time really gives a better idea of the actual minimal complexity to those studying such software.
It's nice to have a reference implementation, but it's not like that's the only way it can be done.
That's a good point --- you can write an H.264 encoder that doesn't compress at all, and as expected, the amount of code to do so is quite small:
https://cardinalpeak.com/blog/worlds-smallest-h-264-encoder/
However, minih264 may currently be the smallest encoder that does compress.
The only grip I have is the 13k lines of C + intrinsics.
How are you supposed to get acceptable performance without intrinsics?
I also wonder how much the compiler can do autovectorisation on code like this --- it's pretty much exactly the type of code that autovectorisation is intended for.
Edit: I noticed in the benchmark that it compressed the 10s foreman.cif (demo video) in half a second, so it's already 20x faster than realtime on that small resolution.
Looking into it I found x264 looked really easy to use with a nice C api but was encode only - does anyone know of a library very similar to x264 which is both encode/decode?
Please forgive my poor understanding of C, but is it possible to add the missing features as extra options/files/headers so you can pick and choose which features you want to enable and/or include?
I’ve been learning a lot about h264 and h265 recently, and I’ve read that hevc is somewhat more straightforward to decode. Is that true? I might try writing a decoder for it.
There is also this rather amusing "4k remake":
https://www.youtube.com/watch?v=pjA-YW71ZOg