Yes, I's a finite acquisition and the delay setting is INSIDE the loop.
I guess you completely recreate the MX task every time you change a property ?
I do not, I stop it but I don't recreate it.
I use a queued loop to make the acquisition
However I solved my problem by recreating the task if the delay needs to be zero.
If it is zero then I don't touch those delay properties.
If it is non-zero I set them to the desired value.
All the other properties like sample rate, channels, ... can be changed without recreating the task
I'm surprised that you can set it the delay to zero.
I always get this error as in the attached screencopy. It doesn't matter what timebase (Clock, ticks, secs) I choose.
Best regards
Johan