When I select "section" mode on my Mikro Mk3, the controller immediately switches to that mode, but the software display on my Mac does not immediately switch to the "section" display... it only does so at the next event which is, for example, by pressing a controller's pad. THEN the computer switches its display. Everything works properly, but it seems to me that the software should switch its context in sync with the controller, which it doesn't strictly do. Is this by design?
I can imagine that the application designers didn't want to persist a section-mode's detailed properties when exiting that mode, and then need to retrieve those properties when the mode is next invoked. However, short of my thinking the design through on their behalf, it would seem that there may be a suitable way to make the switch in sync, while still requiring the next defining event, such as a pad press.
Regardless of my musing over future changes, can someone confirm that the behavior I am seeing is "as designed" or "as experienced" by other users, of this great product?
THANKS!!
