Steps to reproduce:
- create a Pad of any type on page 1 in slot 1
- create a second Pad on page 2 in slot 2 (slot 1 on page 2 needs to be empty)
- follow the Lua tutorial to parse the patch name from a device’s Sysex respsonse
- initiate a Patch Response
Observed behavior:
- when page 1 is active, the Pad’s name is updated correctly with the received Patch Name
- when page 2 is active, the Pad from page 1 is appearing on page 2 (or any other active page), once the Patch Name is received
Workaround:
- the problem is only apparent with empty slots. When the slot on the active page is not empty, you still see the control flickering when the Patch Name is received, but the Pad doesn’t become visible on that other page
- alternatively, use pages.display () to switch to the desired page before updating the control’s name