At the moment, our approach is not to announce what is coming in the immediate version until the release candidate (RC) firmware file meets the following criteria:
- Confirm to correctly deliver on our request through internal checks by our team.
- Pass the quality and reliability engineering (QRE) testing, which means the changes in this update stay consistent through prolonged use and do not introduce unexpected behaviors.
- Pass the cross-check from electrical engineers, which verifies the integrity of changes typically unreachable by internal and QRE tests.
- Green-light by the printed circuit board (PCB) factory as suitable for deployment in the continuation of mass production.
When incorrect implementation is caught among these tests, we frequently face a trade-off between scrapping one change for this version or taking more time. The time-consuming part is that the QRE and PCB factory tests must be re-conducted each time we modify the RC file for correction. Moreover, to efficiently use our time, we work on changes for future versions while the RC file is in testing.
Our current bottleneck on this matter is to have DDC commands for each item and make them survive through power cycles. Its implantation on the firmware structure works like storing items on a shelf, and the catch is that a customized holding place needs to be created prior to storing an item, and the shelf has limited space, no need to mention that the item itself needs to be created in the first place. Therefore, it is a complicated task, and we are in the process of evaluating its feasibility.
FYI @jonwatso @AerialX @DeeKay
If we successfully implement DDC commands for more items, it’ll require a firmware update as it involves changes within the firmware.
Our team has decided that firmware tracking is not something we’ll do in the community. Creating, maintaining, liaising, and decision-making on such a public tracker is not meaningful use of team resources. Instead, it’ll be meaningful for us to take a deep look at more of your comments and take as many of your suggestions into account as we can.
Could you please explain the benefit of these colors beyond the three (white, red, black) that we already have?
Would you please detail your use case of this function? Typical source devices such as PCs and consoles have automatic screen-off and device-off settings, which can be used to let ES07D03 enter power-saving mode after a desired period.
This is not possible because ES07D03’s built-in USB hub cannot communicate with the HDMI input.
@Techmo Thanks for the info and pictures. We are looking into it.
No auto low-latency mode is a scaler limit. We have manual low-latency mode.
For the honor and glory! These are taken with the release candidate firmware installed.