Topic: Control Delay loop
An interesting tech support call came today about a "looping" Control Delay. They were saying that the delay was not tracking correctly, that it would shift during the day, and that the PowerPC on the Nion must not be clocking correctly. We had them send in the Project, and what we found is this;
From seven in the morning until 6pm, a wav file would be triggered to play every 10 minutes. The Pulse output is what was wired to the play button of the player. The pulse was set for 1 second, (they wanted to make sure the pulse was long enough to trigger the play button). So then the loop would kick in, and 10 minutes later, the wav would play again. But what was forgotten, is that it was actually 10 minutes and one second after the first wav started. At the end of the first hour, it was 6 seconds off, and by the end of the 11 hours that the wav was playing, it was off 66 seconds. Of course it was the Nion's fault, the clock was drifting....
BTW. 20ms is enough to trigger the play button, but that still meant the time would be off by 13.2 seconds at the end of an 11 hour day.
Anyway, I bring this up because I would like to hear from others on the forum about whether the "loop" should begin after the "pulse" has finished, or should it the loop start immediately. I have always felt that it should start immediately, so every ten seconds, a pulse would occur. Maybe a button to set it one way or the other, but that might be confusing.
Your thoughts...
