MOTUnation.com

Following your lead, I created a similar test case, using a series of 9 ticks spaced apart by 32nd notes.

Upon stopping, I hear 3 ticks. When resuming I hear all 9.

(project attached) I suppose with some manipulations, we could mess with tempo and find out more precisely how far off it is.

If I slow the tempo in your project to 40bpm I get either 1 or 2 clicks before the stop. At 20 or 30 bpm, it's a consistent 1 click. At 20bpm. if the second click if a little over 12,000 samples after the first, it will not play. Any closer and it does play. So it's overshooting by about 250ms, as you suggested earlier (200ms)but the overshoot seems to depend on tempo. (I'm assuming the first click will always play because it starts at the stop point.)

I'm getting the same results that you are getting. (I'm truly grateful for your efforts in chasing this down.)

We should not be hearing ANY clicks, because the wiper is stopping before that audio region starts. The sample is short enough that it will play because of this error, and changes in tempo won't come close to causing the tick to fall outside that error zone.

At 30 BPM, and with auto-stop turned off, if I manually cue up the wiper to just before the first tick, and then I manually hit stop it right after I hear the first click; the cursor is then parked where I think I stopped it, but nonetheless, I still hear two clicks before playback actually stops.

I suppose one possible explanation is that some amount of audio is "leaking" after stop. The fact that it is not entirely consistent (i.e., at 40 BPM) means that there is some "slop", and not connected to a specific amount of buffering or other digital setting.

Remember when DP was boasting about sample accurate MIDI?

Even though it's a fairly minor issue, it does make editing more difficult, because my eyes and ears aren't getting the same information. I have about 4-6 more hours of editing to do, and there's no way MOTU will fix this before I do it. I had hoped it was some setting I was missing, but it does seem to be bug.

Thanks to your helpful test scenario, and my example project, MOTU's support was able to replicate the issue, and has passed it on to the engineering team.

stubbsonic wrote: ↑Tue Dec 17, 2024 9:11 am Thanks to your helpful test scenario, and my example project, MOTU's support was able to replicate the issue, and has passed it on to the engineering team.

Perfect. It was a good catch you made.

I was surprised by how much such a little difference between wiper position and audio feedback would affect my editing flow. It's been a while since I've done this much detailed VO editing, so I don't know how far back this particular oddity goes back.