The concern is that you don't seem to be aware of these issues (including ongoing encoding issues) without the help of a community member, so how can you say you've fixed the issues? Have you changed anything in your review process that lets you catch these issues before they do? If so why are there ongoing encoding issues?
I realize that this is a long,
long thread. But I have on multiple occasions specifically described changes to our process that we have made to improve the results of our encoding. As just one example, we developed and implemented a new automated color monitoring tool to ensure that no issues with color creep in that cause the encoded file to differ from the mezzanine. This is not a trivial undertaking, by the way. Because of the value of those mezzanine files, they are processed in a highly secure and audited environment. It requires specific tooling to be able to compare final product against those mezzanine files, and we have implemented that.
As a second example, we have also added additional validation for metadata that accompanies the mezzanine files, because we've had instances where, for example, the HDR brightness values that we were sent were invalid.
I think it's also important to note here that when we talk about "ongoing encoding issues", we need to be a bit careful. Many of the titles that have been posted here were encoded many years ago. So while you may see a new
message posted here, that doesn't necessarily make that
title an "ongoing encoding issue", but rather it may be a report of something that was encoded long ago. Such a report is a perfectly valid report that should be addressed, to be clear, but interpreting a report of a problem with a title that was encoded in 2017 as an "ongoing encoding issue" is not valid.
Let me quote from an earlier post by Rmarci:
Their newer encoding parameters are good but there are definitely plenty of older encodes with issues (poor encoding, DNR, or green/red tint). They can also still make the occasional mistake or get a bad source, which might be the case with Alien 1979.
That leads into my next point. As I also stated previously, we were aware that there were quality issues with some older encodes, and had scheduled work to revisit them and update them. Rmarci's reports have identified other issues as well, which we appreciate. In some cases, those reports have identified not an issue with a title, but an issue with a
class of titles. And so those titles have been added to the queue of movies to revisit and update. Such work takes time and costs money, so it is necessarily an incremental process, which is why that work is also prioritized according to the popularity of the titles. However, as I also previously posted on this thread, we're undertaking an effort to accelerate that work, because it's important and we want to deliver the best experience we can to our customers.
Finally, I want to note that some of the reports here have been comparisons against other services, or against physical media. This is certainly valid, but consider: for new-release titles, we have no way to make such a comparison as part of our process, because we don't have access to any of that other media to compare against during our encoding. So while it's possible after the fact to do a comparison, it's not like we can have a pre-release QA step where we look at a finished encoded file and say, "Huh, this looks more red than what was on <your favorite service here>." A perfect example of this was the issue with "red push" on a number of recent titles from one studio. Our encodes were faithful to the mezzanine file. It turned out to everyone's surprise that there was an issue with the mezzanines, which is why our updates of those specific titles are proceeding as we receive new mezzanine files.
I hope that helps to clarify a little bit. We do appreciate the feedback that we've received. Sincerely. We take it seriously, and we have made changes to both our encoding and QA processes to prevent problems from happening again.