SynthMaker

polycode modules corrupt asio on 4block spawn

Archive · 2009 1 old post

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

MichaelBenjamin ·

the 4 block voice spawning quite quickly produces asio stream corruption resulting in clicks on attack when you use array mem inside polycodemodules. seems the initialisation is very slow, even for small arrays<1024. would there not be a way to somehow cache just the array data in memory for say, 32x4 polyblocks on pluginload?

edit: even without the arrays, the polyspawn seems to be too slow - when you stack several (even low ~1.5%cpu) vstis there is the same dropout on 4 block spawn. so the whole spawning process for the next blocks should be cached somehow.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.