Correct me if I'm wrong, but:
It might be worth noting a fundamental difference of this feature on DSOs compared to analog scopes:
When the Holdoff is set to e.g. 100 ns, it actually means that the next data acquisition will be armed at some integer multiple of 100ns after the previous acquisition time, when also the minimum re-arm time is exceeded!
This is of course due to the low capture rate of DSOs. Even with a (DSO) state-of-the-art capture rate of 1 000 000 wfrm/s, the scope can't acquire a new data set as soon as just 100 ns after the previous acquisition, it's at least 1 us in between.
So on a DSO the term "Capture holdoff" might be a better description of the feature than "Trigger holdoff".
It's a bit of shame that this useful feature has been moved down into some meny selection on DSOs, but it's also understandable, partly due to all other features that would be nice to have separate knobs for, partly due to the facts above. It would be misleading to place it in the trigger section of the scope's front panel, but (maybe) confusing to place it in the horizontal section.
I think it's interesting to speculate on how DSO's trigger section might be designed. It seems reasonable to me that the max trigger rate (not to be confused with capture rate which is what we can detect at "Trig out") actually is the Holdoff value (inverted). Otherwise I don't see how the scope could "sync" to the above mentioned capture holdoff?
Or is it just that we think that it work as good as on analog scopes? I admit I haven't tested, anyone else who has?
//C