hi friends, its my second time asking a question about this issue, last time with no reply – never the less i try again as i feel i know more about the problem –
im trying to store and recall presets of 42 live gui objects which are spread in 6 bpatchers (18xlive.grid, 12xlive.text, 12xlive numbox) and encountering quite a lag while recalling. is there any way to deal with that?
thank you for your time!
I’m trying to tackle this end of m4l currently aswell. My test patch was just 8 itables. Depending on how fast I scanned them I was able to get abletons UI to slow down:) So I was assuming I needed to learn some process prioritising and use of speedlim, but it seems more related to limits in updating visual components? An itable preset isn’t exactly processor intensive code, but I would get slow preset loads and some crashes on mouseover from itable’s value pop-up I believe.
A never ending progression of almost doing exactly what you want, thus is life my friend.
I’ve been getting a similar problem when trying to load roughly 300 umenu settings with time-sensitive bangs to "get parameter" messages – I’ve tried clientwindow prioritization and greedy, but I’m at a total loss for how to continue.
Try lowering the update limit of each parameter to 30 ms (default 1 ms which is way too fast) and also adding a speedlim (30) to other objects to reduce the amount of data that has to be processed.
C74 RSS Feed | © Copyright Cycling '74