FAQ

Not now, not in the near future, but possibly some time after version one. No guarantees.

It might come in the future, especially now that Apple has moved over to the Intel platform. But it’d be a huge task for us devs, since we’d have to first reimplement all the graphical stuff with an abstraction layer and THEN add implementations for both PC and Mac, using that abstraction layer. So it’s not something we’re about to do soon or anything. It is not “harder” to code for Mac, but none of us devs are Mac users and well, it’s different. Not harder, just a bit different.

Some primitives that come with SynthMaker have not been fully tested or may not be functioning 100% correctly, to avoid confusion or problems these primitives they have been assigned as ‘R&D’. If you wish to use these primitives, you have to switch on the ‘R&D Components’ in the advanced preferences. R&D primitives will be highlighted red in the toolbox.

Also, a few primitives have been superseded by newer versions, and no longer are listed, though perhaps the older versions will still function.

Audio that is passed to the soundcard has to be in the range -1 to +1, anything exceeding this range is wrapped around into the range. So for example if a value of 1.1 is passed to the output it will be converted to the value of -0.9. For audio this results in extreme distortion. So if you play 2 two notes on your synth, each with a volume of 1, the total output can easily exceed the -1,+1 range.

To remedy this you should do two things: Firstly scale the output of the synth so when playing more than one note the total volume shouldn’t go above 1, secondly add a stereo clip module before the audio output to limit the output so the range is never exceed. It is recommended to have a clip module.

The reason for this is the developers of SynthMaker decided that they would like hide as few of the background processes as possible from the user, giving the user maximum flexibility with the application.

• seconds to Hz Hz = 1 / seconds
• Degrees x 0.0175 = Radians
• Radians x 57.3 = Degrees

• logb(x) = loga(x) / loga(b)
  • log2(ratio) = log10(ratio) / log10(2)
  • 1/log10(2) = 3.321928

• ratio = 2 ^ (pitch / 12)
• pitch = log2(ratio) * 12

2 inputs: Original BPM and Target BPM
1 output: Pitch change in semitones

  ratio = 180 / 140
  pitch = log2(ratio) * 12 -> ~ 4.35 semitones

The long:
The short:

• MIDIpitch~=log10(1/Pitch to Frequency)*39.8631

Ensure you connect a wireless input into the view input connector on the master MGUI, and turn on “Toggle Front Panel” (G) on the menu on the bottom of the module.

They can be caused by several things:

• when there is a sudden jump of values (eg +1 to -0.7)
  1. pops in the beginning of a note are from short attacks coupled with an OSC waveform not starting at 0. Have your OSC start at 0, or/and lengthen the Attack.
  2. If you don’t like the clicks when re-triggering notes, then toggle the Hold & Smooth Retrig
  3. clicks at the end of a note, try an "R” (found in the Envelope toolbox folder) at the end of the module chain. Start with a very very short Release… then keep lengthening the Release until about where you don’t hear any more pops. The Amount should be about 100%, but you can rip out that part altogether.
  4. If you don’t like the clicks when re-triggering notes and the above tips do not help you, then toggle the “Hold” & “Smooth Retrig” in your envelopes’ preferences. Also edit the MIDI to Poly to toggle the “Hold Stolen”, “Retrigger New”, “Retrigger Stolen”.
  5. static or clicks when a knob is used needs a De-zipper
  6. A “smoother” will help rake in the pops in between, but risks making the audio quieter and less dynamic.
• negative frequencies sent to the ins of a OSC primitive
• too small driver audio buffer

—- thanks to: stefan, oddson, re8, trogluddite