Object Attributes

[smoge]

@Dasha

My main problem is that I see computer music as a stream of numbers, and the timing should always be sample based to ensure synchronicity. But Collider’s architecture makes it impossible cause sending a message and retrieving, delays the information. Or in your example, you will have to trigger the SendReply each sample to be sure the information you are getting is the one you wanted. And of course this is not possible cause you will saturate the server with thousands of requests.

It’s a bit too convoluted to leave it here too. Splitting.

I try to touch at least one of the confusions here:

Re: Confusion between Frame-Sizes vs categorical DSP contexts

Continuing a secondary topic from this discussion by @Dasha https://scsynth.org/t/object-attributes/10394/18?u=smoge That is a limitation of all real-time audio/dsp environments. If you want to avoid a frame-based approach, there is no problem in rewriting the code as a sample-based operation. The downside is that there is a price, you will use most of your CPU, and you won’t be able to vectorize and use SIMD instructions. And in the end, it won’t work. It will not be a professional system. …