Behaviour of INTERNAL_TRIGGER_MULTI

The expected behaviour of INTERNAL_TRIGGER_MULTI should be clarified.

Currently, it requires to run startAcq before each image, but uses internal trigger. This gives significant overhead of restarting the acquisition thread.
It seems it should use software trigger and just trigger the camera, either in startAcq or by other means, depending on what is expected by client applications.