As seen in the previous post, a whole category of x264 improvements has now been completed and committed. So, many have asked–what’s next? Many major features have, from the perspective of users, seemingly come out of nowhere, so hopefully this post will give a better idea as to what’s coming next.
Big thanks to everyone who’s been helping with a lot of the changes outside of the core encoder. This, by the way, is one of the easiest ways to get involved in x264 development; while learning how the encoder internals work is not necessarily that difficult, understanding enough to contribute useful changes often takes a lot of effort, especially since by and large the existing developers have already eliminated most of the low-hanging fruit. By comparison, one can work on x264cli or parts of the libx264 outside the analysis sections with significantly less domain knowledge. This doesn’t mean the work is any less difficult–only that it has a lower barrier to entry.
For most specific examples given below, I’ve put down an estimated time scale as an exercise in project estimation. This is no guarantee as to when it will be done; just a wild guess by me. Though it might serve as a personal motivator for the tasks that I’ve assigned to myself. Don’t harass any of the other developers based on my bad guesses
Do also note that even though projects have time scales doesn’t even necessarily mean that they will be finished at all: not everything that we plan ends up happening. Many features end up sitting on the TODO list for months or even years before someone decides that it’s important enough to implement. If your company is particularly interested in one of these features, I might be able to offer you a contract to make sure it gets done much sooner and in a way that best fits your use-case; contact me via email.