SynthMaker

Code activating prematurely [0.9.4g]

Archive · 2005 1 old post

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

infuzion ·

In whyt's envStageTestbed, dropping any primitive or module into the "Testbed Module" will trigger the Codes to activate, even if they aren't connected to anything.

EDIT: Actually, anything you do to the GUI will cause the Code to trigger, moving, labeling, typing something in... except flipping the TrigIn Int with my flipper. If you type "0" in the TrigIn Int it works as it should, but using the flipper doesn't seem to.

test file

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.