When I change from page to page it looks like there is some internal initializing that takes place (are things firing on me without asking?) that throws things all out of expected states? Exactly what happens internally when you change a page? How can you stop any unwanted re-initialization? Thanks.
Page changes should not change anything. Very probably the issue is elsewhere. Did you give every parameter (within the same type) a different ID? Do you have the same parameter with the same type and ID on purpose on different pages?
1 Like
Yea might have been same id issue. That can be a problem as with MPE. The real issue is there is no global initialization function. OnLoad is called before other internal initialization. This to me is not a feature but a terrible bug that needs to be fixed. When I call Onload that should be the last thing done so any other initialization that is automatically performed can easily be overridden with the init params I want vs. trying to create some silly flags to keep things from being initialized without my intent. The software would be so nice if this was done to make things totally predictable for initialization.
Not sure what you mean. You 'll have to be specific about what values in what code for what synth/device you see changed in a way that is not predictable, for the community to help you, I’m afraid.
2 Likes
Well it looks like when I change a page, control #1 is being called or some strange reason.
When pages are switched, the only callback called is pages.onChange(). All other callbacks related to controls are driven by the value changes. In order to help, I’d need to see the preset.
Thanks. Let me see if I can create a simple version that does this. I’m not directly calling pages.onChange.