SynthMaker

Delayed comparison workaround [FAIL]

Archive · 2010 5 old posts

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

JIftw ·

EDIT: I no longer recommend using the posted workaround. Use the "de-threader" instead. See later posts for explanation.

Hi,

Just stumbled across a little problem and found a workaround. Thought I'd share it, in case it'd be useful to other beginners like myself.

On the left, you see the problematic case where the equality test is correctly solved only when it is no longer true. (Delayed response) On the right the little hack. Simply use the integer as an index for the selector which chooses the correct boolean response.

JIftw ·

Um.. I made a mistake.

The selector keeps the last entry when (index# +1) > total entries. So the preceding hack was not a test of equality, it was "if greater or equal to 1".

For strickly "If equal to 1" you must also connect the "False" boolean to the selector's last input.

EDIT: Replaced external link with assatchment as per infuzion's recommendation.

infuzion ·

Might be a reportable bug if the triggers are not moving as they should. BTW, it is preferred to post/upload images on the forum, so they will not be lost later.

JIftw ·

I no longer recommend using the posted workaround. Use the "de-threader" instead.

The de-threader is in the Wiki, article name "MIDI and Timers". (Shouldn't this be in the official documentation ?)

My failed workaround is okay for the actual data, but not for the triggers which should be sent further down the code.

Sorry if this thread has been the cause of confusion / additional trouble.

Explanation:

I faced a similar problem earlier in my code for converting a Bool to an Int (once again, using the selector instead of simply connecting the bool to an int "solved" it.) After having done so, there was no need for the workaround that occured later in the code. But, even with the workaround, I still had issues when using an external MIDI keyboard (but not PC keyboard, strangely) SM would crash very often when I would connect basic elements deep in the code, trying to see if the data was changing as it should, making analysis very difficult. Still managed to find triggers were not being sent properly when using an external MIDI keyboard. Inserting a de-threader solved everything. Many thanks to whoever posted that article in the wiki.

SM made me lose my hair 😉

MyCo ·

you should keep an eye on the trigger flow. You shouldn't search for workarounds, instead you should fix your trigger issues.

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.