DP 10.11 Scrolling issue

[MIDI Life Crisis]

In a nutshell, the tracks overview is not reiably updating to show scrolling if the segment displayed in the TO window is past the wiper position (with he wiper offscreen). The measure numbers will shift accordingly when the wiper is updating, but the actual wiper itself is not visible until at least when it hits the current measure visual in the TO window. If the view is before the wiper and I press play, the window follows the cursor as expected. If the wiper is onscreen, it will scroll. But if the wiper is not visible and before the time segment in the TO view, it doesn't update to scroll.

Yes, I have checked my preferences on scrolling.

As here:

http://www.midilifecrisis.com/misc_imag ... entest.mov

Techlink created.

[MIDI Life Crisis]

BUMP!

This is a substantial issue for me. MOTU responded to my tech link but offered no viable solution.

No one else is seeng this? Amazing.

[waterstrum]

Hey MLC,
I'm trying to replicate your issue on my setup and I can't.
The wiper jumps to the new location and doesn't wait to show up.
Looks like you have the Auto Rewind and Overdub modes active.
I tried that too and in my case, the wiper behaved as expected.

Ah hah! ... maybe a solution,
Just noticed your memory start and stop times are crazy.
start 675/2/471 stop 152/1/1000
Is that even possible?
Maybe that is the cause of this anomaly.

[MIDI Life Crisis]

The start and stop times are crazy. I don’t know how that happened but it’s not how they’re usually set. Duh! Good eye, man! Thanks for that. I’ll play with that and check your other suggestions. Surprised the MOTU tech missed that. Frankly, I’m surprised I missed it as well.

[bayswater]

Did this ever get sorted out? I'm seeing the wiper jump to the correct position regardless of the scroll position in the TO. But I notice start times after stop times, and out times after in times. I don't remember this happening before. Didn't they used to flip positions if you dragged one of them past the other?

[MIDI Life Crisis]

It appears that setting the end time to before the start time is the culprit. However, I don't usually set an end time, only update start times when needed and it always worked before (regardless of the end time). Guess I'll have to change my Rx.

Thanks for you help, guys. Much appreciated.