Frank Barknecht wrote:
It already runs even in a separate process from the audio engine. But both are tied together very closely and communicate a lot with each other, which leads to dropouts on gfx-intensive operations e.g. moving a lot ob objects or displaying and updating large graphical arrays.
Ok.
Use [table] everyhwere, you don't need to see the data, and avoid graphical objects for debugging in performance situations, only use them to input data.
Thanks for the info, very clear, I think I got a better sense of tos and not-tos...