I'll have to agree with most of Martin's points in the video. Though I think I'll give my unit a proper review of some of the issues he mentions.
The continuity meter delay is worse at lower thresholds...this is somewhat intuitive, setting it back to 50 Ohms makes it more responsive than Martin's test shows. I think my old Fluke uses 40 Ohms for the threshold and rarely do I fault it's continuity check. If I really want to know how many Ohms it is, I'll flip the unit to resistance to see what it really is.
Again, I don't agree that you can fault the meter for having a slow update when you want 1s integration time. I suppose there are ways to have a running average rather than a non-overlap average and still maintain a 1s integration time, but since the display is updating 1 time/sec, you can expect the display to update 2 times/sec.
One other thing I notices, even in the later firmware is that the dual reading between ACV and freq is dog slow. These two measurements should not require relay switching, but still, the time to make each measurement really bogs down the machine. Also for dual measurements, beyond the current disconnect issue point out both by Martin and the Signal Path, I can understand the latency in measurements for current/voltage measurements being slow as the relay probably requires some settling time...though I hope they can improve this in the future and not require an open circuit period.
And if Siglent can do another couple rounds (or just one good one) of firmware updates with the same improvements as R12->R13, that would be great.
Oh yeah, and Siglent, just publish a change log, it would take 30 minutes of time to make. I'm sure you're not fixing 100's of bugs per releases.