Repeating the entered value again always worked.

Yes, because it updates the lowest level remembered on the 1st try, and gives the correct result on the 2nd try. If you try a 3rd time with a lower value, it will go wrong again.

haven't been able to predict what value will be assigned when one is typed.

For each slider, it seems to remember the lowest level you've manually entered (initially zero), even when the resulting level is different. When you manually enter a level below its lowest, the resulting level includes double the amount below its lowest. The following python code reproduces the input/output behavior:

lowest = 0
while (True):
    level = int(input("\nlevel in:  "))
    print("level out: ", end="")

    if (level < lowest):
        print(lowest - 2*(lowest - level))
        lowest = level
    else:
        print(level)

Changing a level with a slider doesn't affect the next level that results when you manually enter a value. This feels like some kind of trim calculation gone wrong, triggered by manual entry.

I was manually entering values for compressor and EQ settings for a live session last night. Often after I typed a value, what was actually saved was not the value I entered. I assumed I mistyped carelessly, but it kept happening. When I paid attention and typed slowly, I saw it was not saving what I typed. Repeating the entered value again always worked.

A video showing the (disconcerting) phenomenon is posted at https://littlemountainmusic.org/downloa … Errors.mp4. We can provide a workspace file if needed, but it occurs after a total mixer reset.