SynthMaker

"Always" playing OSC

Archive · 2011 5 old posts

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

lesobrod ·

Hi! For some purposes I need sound source that playing constantly, not only when MIDI signal comes. Let we have simple Sine OSC. What I should do to force it to play?? I try to connect Freq input with a knob, a float value, but no sound comes.

philter5 ·

if you want a "always" playing osc you have to connect the OSC module directly to the blue audio outputs. if you use a poly(white) to mono (blue) converter after the OSC it won´t run always..

infuzion ·

Welcome to SM lesobrod! You can do blue as philter5 says, or just send a MIDI "Note On" command to the MIDI to Poly if you want to stay white Stream. Then do not send a "Note Off". May be tricky; might have to use a trigger De-threader to get that Note On to work...

trogluddite ·

Hi there lesobrod, There are mono-to-poly and poly-to-mono modules in the 'Audio' toolbox to handle blue->white and white->blue conversions - however, to be able to always hear the oscillator it's important that every 'link in the chain' from oscillator to audio outputs is in blue; even one white section in the chain will cause it to only sound when there is a note present.

Knob control is simple - stream inputs will happily accept a 'green' float value without any conversion needed. The only thing to watch out for is that SM has 3 different ways of specifying oscillator frequency values...

Normalised frequency - the range for this one is 0 to 1, where 1 represents half your soundcard sampling rate. Frequency in Hz - just what it says; there is a 'Hz to 0-1' module in the toolbox if you need to convert this to the normalised format. MIDI Pitch - represents a MIDI note number, usually these inputs will be labelled 'Pitch' rather than 'Frequency'. Again, there are conversion modules if you need them.

Primitives (the parts that you can't look inside) tend to always use the 'normalised' 0-1 range, but for the more complex oscillator modules you'll need to experiment (or poke around inside them) to be sure which is the correct number range.

A 'de-zipper' module may be also useful at the oscillator frequency input to smooth out the green data so that you don't hear the stepping between values - again, it depends which oscillator module you use, some may already have this built in (usually easy to spot if you have a quick look inside the module).

lesobrod ·

OK, thanx a lot to all! The problem was a bit tricky.. My Sin OSC was connected with Combiner module so Sin input/output stay white, even when I disconnect Combiner from DS-out.

Connect Sin only with DS-out was wright. Well, SM is great thing 😍 In fact I like NI Reaktor, but it can't compile VST and (especially) has "non-friendly" interface (too small for my eyes). So I'm going to learn SM in detail 😉

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.