SynthMaker

Green constants into poly AND mono

Archive · 2010 2 old posts

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

mwvdlee ·

I just noticed this weird behaviour. Don't know if it's a bug or a known "feature", but here it is:

If you use a single green constant (i.e. Integer) as input to both a poly (white) Code module and for a mono (blue) Code module, the signals can get mixed up.

Simply put; I have an algorithm which uses a number of Code modules, one poly and a few mono. If I use a single green constant (i.e. an Integer module) as input for the mono Code modules, everything works fine. If I use it as input for the poly Code module, everything works fine. If I use it as input for both poly and mono Code modules at the same time, my mono signals seem to get mixed up; completely unrelated mono modules produce values which seem to come from the green constant.

Here's one workaround, which isn't really usefull: If I use two copies of the green as input for the poly and mono Code modules, everything works fine again.

And here's the REALLY weird bit: If I route the single green constant through ANY modules (this includes one of the group modules from my MissingLinks set, which does absolutely nothing but connect an input to an output directly), I can hook up one type of Code module BEFORE the module and the other type AFTER, and everything works fine as well.

Why do signals get scrambled when hooking up a single green to both a poly and a mono Code module? Why does routing the green through a dummy module fix it?

I'm sorry I don't have any example code at the moment. It's hard to isolate an example that easily demonstrates the scrambled mono signals.

infuzion ·

From an email from Malc 1.5 years ago: Look at the Bus labeled Poly. Trace back from the LFO1 input to the two Stream Mults and one Stream Add. These take input from Float outputs that also connect into the Mono section. This is where the link is between Poly and Mono. If you use separate Float outputs for each section then you'll be fine.

The golden rule is that any Float (or Int or Bool) should never connect directly into Poly and Mono at the same time. If you need to use the same calculated value in both sections then the simple workaround is to connect a Float comp to the float output and use the output from that in the Poly say and the output from the original in the Mono.

Edit: I should note that I tend to reduce my OSMs to as few parts as possible. Most people would accidentally avoid this issue.

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.